ECSA101 / ECSA 101 Hyperspace | Prep Questions and Verified Answers | 100% Correct (Latest 2024 / 2025 Update)
Question:
Can you run Hyperspace on x86 (32-bit) Windows 7?
Answer:
Yes, Hyperspace is technically compatible with 32-bit Windows 7; 32-bit Windows 7 is not, however, a Target Platform, and running Hyperspace on this platform caries some risk of running into previously undiscovered issues.
Question:
How is trust established between an Epic client and the Epic operational database environment?
Answer:
A fixed key will be defined on the client, usually in some type of environment file, and imported into the Epic environment.
- / 3
Question:
Why does Epic recommend creating a Hyperspace Administrative Image?
Answer:
Using a script to copy files carries a high chance of failure and would be logged separate from the installation. By creating a customized Hyperspace Administrative Image, an administrator can be sure that all necessary files will be on any client built from that customized image.
Question:
What documents should you reference prior to building a new Hyperspace server?
Answer:
Target Platform: Epic Client Systems Manager - Application Deployment
Administrator and the Hyperspace Server Build Checklist
Question:
EpicComm
Answer:
Hyperspace client uses a connection protocol called EpicComm over ECF to establish a connection to the Epic environment. The configuration is backwardscompatible with the previous connection protocol, EpicComm, so you as the ECSM don't need to worry about re-configuring your Hyperspace clients.
- / 3
Question:
Multiple Environment Configuration, MEC
Answer:
During many workflows, users need to access information from multiple records and multiple areas within the operational database environment.Because these workflows have the potential to affect end-user performance, most organizations use a Reporting or Shadow environment alongside their Production environment.
This second environment is a near real-time copy of the primary environment, often only seconds behind.Epic recommends that you add a new kind of environment to your
EpicComm.env environment file: a Multiple Environment Configuration
(MEC). Using a MEC, users will connect to the production database as normal, but this MEC will permit them to run performance-intensive workflows (such as reports) in the shadow environment automatically.
Question:
Add Additional Custom Files
Answer:
Many organizations choose to brand Hyperspace to change the look of the initial launch and login screens.
- / 3