ECSA101 Chapters 1 & 2 Exam Questions and Answers All Correct

ECSA101 Chapters 1 & 2 Exam Questions and Answers All Correct USER WEB FORUM - Answer-- Allows you to participate in discussions with your colleagues from other organizations. - Keeps you up to date by reviewing the latest EPIC announcements. XGM ARCHIVES - Answer-Provides access to past XGM System Roundtable or SRT presentations Galaxy - Answer-One stop documentation stop. Includes Build Checklists, Target Platforms, Technical KB Articles. Allows organization of your favorite documents within your UserWeb profile. Nova - Answer-EPIC's release note review tool. Review release notes for upgrades or special updates. Nova also provides information regarding the honor roll checklist and deadlines. Sherlock - Answer-Used by the the customer and EPIC to track Support Logs (SLGs), Sign Release Authorizations (RA's) and review reportable issues. Newer versions also provide checklists that track major projects, such as server builds and EPIC upgrades. Client Server Infrastructure - Answer-The EPIC DB is a single database. It is referred to as an EPIC Operation Database Environment or simply just Environment. Hyperspace Clients are installed on workstations, virtual desktops and Windows Servers. Clients connect to the EPIC operation database Who am I? - Answer-You must identify a Workstation Record, or LWS record, for a connection to be successful. This LWS record can be specific to the machine establishing the connection, a generic LWS, or a record shared by several connections depending on the type of client. ECSAs define a Client or Workstation ID to identify which LWS record a client should use. This ID answers the question....... Where am I going? - Answer-You must define destination environments for each client. You must provide details such as the host name of the server running the Epic operational database and the TCP port the environment uses. You can define connection information for all your environments within the same environment file. This environment connection information answers the question; Am I Trusted? - Answer-You will use a fixed key to restrict access to environments and to authorize clients. The same fixed key must be in the Epic operational database environment as well as in the environment file. Fixed keys answer the question; Am I Known? - Answer-When a client connects to an Epic operational database environment, the environment attempts to identify an LWS record. This record will match the Client or Workstation ID in the client's connection configuration. If the environment finds no match, the environment will assign a generic LWS, if enabled. This generic record is CLISUP by default, but you can configure any LWS record to act as the generic LWS record. The LWS record defined in the Epic environment answers the question; EPIC Releases - Answer-The Epic release is our primary versioning scheme and will contain the most significant changes. Starting with the August 2018 release, Epic is switching to a new release strategy. With this new strategy, Epic will create a new release approximately every three months. Most Epic clients on one release cannot connect to an Epic operational database environment on another release. Epic 2017 = Release 83 Epic 2018 = Release 84 August 2018 = Release 85 We recommend that you install Epic releases in your production environments every three months. EPIC Special Updates or SU's - Answer-As with any software, updates are necessary to fix issues, improve existing workflows, or introduce new functionality. These SUs are a lot like hotfixes. Each SU is specific to a given Epic release and is either a client update or a server update. Client Update CXX##### - Where XX is the Release number, and ##### is a unique update ID Server Update EXX##### - Where XX is the Release number, and ##### is a unique update ID Release Authorizations - Answer-Actions that change your build should follow your internal change control procedures and policies. Any change made by Epic associated with delivery of new code, and those associated with changes made by Epic personnel. Dependency - Answer-when a piece of code installed in one location requires a corresponding piece of code in another. Within an Epic release, an Epic client can depend on the Epic operational database environment, but never the other way around. Individual SUs for a client can even depend on other client SUs, even across multiple clients. Client code can, but doesn't always, depend on the server code. The newer client cannot connect to the older code in the environment if there is a missing dependency. Not all client Special Updates introduce a dependency on the server. These dependencies drive the order of operations for patching and upgrading your Epic infrastructure. If an Epic client is running August 2018, could it connect to an environment running August 2018 update package 23? - Answer-Yes, a client can always connect to an environment on the same release that is more up to date. Could an Epic client running August 2018 update package 15 connect to an environment running August 2018? - Answer-Possibly, but not likely. A client that is more up to date than the environment likely depends on SUs that the environment doesn't have. If Client Pack 15 contained no client-to-server dependencies, then the client could connect without issue. Code Environment Strategy - Answer-After downloading new code associated with an RA from SU-EEDS you will place it in your package directory. You should then follow a predetermined path to apply this code. This path is known as the . The same path is followed when you upgrade from one release to another. POC--TST&TSTRPT--MST, ACEs, PLY, PRD &SUP--RPT Environment Strategy - Answer-The build environment strategy is vastly different that the code environment strategy. The build strategy covers Data Courier, environment refreshes, copy downs, and mirroring. The build strategy is significantly more complicated that the code environment strategy. Whenever discussing environment strategies, be clear which environment strategy you are referring to. Target Platforms - Answer-A list of of what platforms that will most likely result in a successful EPIC deployment. The "Roadmap" details which platforms meet all of the requires to be on target and projects two years into the future to assist with planning and budgets. Transitional Platforms - Answer-Transitional Platforms are platforms that were previously Target Platforms. Community members can continue to use a Transitional Platform for a limited period of time. This helps provide clean upgrade paths from a previous Epic release. Separating platform upgrades from Epic upgrades reduces the risk associated with each. Transitional platforms have an end date, after which they become Off-Target platforms. Exploratory Platforms - Answer-An Exploratory Platform is a platform EPIC is testing to determine whether it can become a Target Platform. Not all Exploratory Platforms will become Target Platforms. Off-Target Platforms - Answer-An Off-Target Platform is any platform that does not qualify as a Target, Transitional, or Exploratory Platform. You will continue to receive support from us if you choose to go off-target. Using an Off Target Platform diminishes our ability to ensure top notch performance. We will work with you and your business leadership to ensure you understand the risks of using an Off-Target Platform. Incompatible platforms - Answer-Some platforms are more than just off-target, they are incompatible. In these cases we will still provide your personnel support. However, the software will not work properly or at all. Build Checklists - Answer-These documents include a multitude of build recommendations that Epic has vetted. These checklist items often address issues found at other organizations running Epic. Checklists are available on Galaxy. EPIC.Support PowerShell Scripts - Answer-We have the Epic.Support PowerShell scripts to aid you as you review your servers for build checklist compliance. You will use the Epic.Support PowerShell scripts to review Build Checklist compliance. The scripts cannot automate the entire review process as some items cannot be programmatically reviewed. After you have gone through the checklist, use the scripts to identify any missed steps Hardware Configuration Guide - Answer-Guides to provide preliminary sizing for your servers along with an estimate of your storage needs. This document also provides information on the RAM and CPU you'll need for each of these servers. We base the sizing in these guides on information provided by your organization. How is trust established between an Epic client and the Epic operational database environment? - Answer-You define a fixed key on the client, usually in some type of environment file, and import it into Epic operational database environments. What documents should you reference prior to building a new Epic client? - Answer-- Epic 2018+ Target Platform Roadmap - Relevant Build Checklist - Relevant Setup and Support Guides - Also reach out to your Client Systems representatives to discuss your plans. If you were to update an Epic client before a given Epic environment, would the client be able to connect to this older environment? - Answer-Possibly. If the update to the client introduced new client-to-server dependencies; then no, the client would not be able to connect. If the update to the client did not introduce new client-to-server dependencies; then yes, the client would be able to connect.