ECSA101 / ECSA 101 Hyperspace Chapter 1,2,3 & 4 Questions and Verified Answers | 100% Correct (Latest 2024 / 2025 Update)

ECSA101 / ECSA 101 Hyperspace Chapter 1,2,3 & 4 Questions and Verified Answers | 100% Correct Q: 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. Q: 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 Q: Release Authorizations Answer: Actions that change your build should follow your internal change control procedures and policies. Any change made by Epic requires a _____________. There are two types of________________; those associated with delivery of new code, and those associated with changes made by Epic personnel. Q: 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. Q: 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. Q: 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. Q: 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 Q: 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. Q: Target Platforms Answer: A list of of what platforms that will most likely result in a successful EPIC deployment. The