Download ECSA101/ ECSA 101 Hyperspace: Questions and Verified Answers and more Exams Marketing Business-to-business (B2B) in PDF only on Docsity!
ECSA101/ ECSA 101 Hyperspace Chapter
1,2,3 & 4 | Questions and Verified Answers|
100% Correct ( New 2024/ 2025 Update )
QUESTION
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.
QUESTION
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.
QUESTION
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- toserver dependencies; then yes, the client would be able to connect.
QUESTION
What version does 85.0.47 represent?
Answer: The digits before the first decimal represent the release, in this case August 2018. The digit after the first decimal and before the second decimal represents the Interim Update, in this case there is no IU as August 2018 has no IUs. The digits after the second decimal represent the package, in this case package number 47. A package is a collection of Special Updates.
QUESTION
Which of the following is always true about dependencies? Choose one.
Answer: A. [Incorrect] A newer client will ALWAYS have unmet dependencies on the server. B. [Incorrect] A newer server will ALWAYS have unmet dependencies on the client. C. [Correct] A newer client will SOMETIMES have unmet dependencies on the server. D. [Incorrect] A newer server will SOMETIMES have unmet dependencies on the client
QUESTION
Sherlock
Answer: A tool can help you track the status of an investigation and share information between all teams involved?
QUESTION
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.
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
QUESTION
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.......
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;
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;
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;
QUESTION
What are the three targeted Hyperspace deployment options?
Answer: Published application, virtual desktops, and full clients.
QUESTION
When using VDI, where should you install Hyperspace? Why?
Answer: Hyperspace should be installed locally in the VDI image. This will ensure peripherals on the end-point can be used by the Hyperspace session. This also avoids unneeded complexity.
QUESTION
True or False? Hyperspace Web is independent of Hyperspace.
Answer: False. Users access Hyperspace Web from within Hyperspace. Issues with Hyperspace can impact Hyperspace Web.
QUESTION
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.
QUESTION
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.
QUESTION
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.
QUESTION
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
QUESTION
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.
QUESTION
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.
QUESTION
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
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.
QUESTION
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
QUESTION
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.
QUESTION
%CLIENTNAME%
Answer: Your organization ONLY uses full clients and virtual desktops as your Hyperspace deployment methods. Which of the following will you NEVER use at your organization as a Client ID?
QUESTION
EPIC Release 84
Answer: EPIC 2018
QUESTION
EPIC Release 85
Answer: August 2018
QUESTION
Answer: August 2018 Release with IU placeholder digit and package 17.
QUESTION
Answer: August 2018 with IU placeholder digit
QUESTION
Release
Answer: EPIC's primary versioning scheme
Answer: A Deployment tool used to deploy many EPIC products.
QUESTION
Client Packs
Answer: A collection of all relevant special updates into a single patch. A cumulative collection of all new and previously installed SU's.
QUESTION
Features of a Client Pack
Answer:
- Are Microsoft Patches, *.MSPs
- Are superseding; only one patch appears to the OS
- Contain Old SUs and New SUs and are therefore cumulative
- Are specific to your organization
- Must be installed using InstallMSP.exe; no double-click
- Have a sequencing number that is always higher than any previous - Client Pack, though the numbers might not be sequential.
QUESTION
InstallMSP.exe
Answer: The utility used by an ECSA to validate and later apply a Client Pack. While it makes it possible to directly apply a Client Pack, we recommend leveraging your 3rd-party distribution system to deploy your Client Pack using a pre-built batch file. This process ensures that there are no issues with the Client Pack prior to update night.
QUESTION
InstallMSP.vbs
Answer: A VB script to serve as a wrapper for InstallMSP.exe. Used for SCCM deployment.
QUESTION
Update Procedure
Answer: RA Signed--> Download Software from SU-EEDS, Validate Client Pack-->ODBA Updates ENV, Deploy Client Pack.
QUESTION
Why is it important to validate your Client Pack well ahead of when you'll apply the Client Pack?
Answer: If validation fails, Epic may need to generate a new Client Pack for your organization. If you don't validate ahead of time, you may not get your Client Pack deployed during your change window.
QUESTION
What is a representative client?
Answer: A representative client is a machine with Hyperspace on the same code version as all other machines that support the Epic operational database environment currently being updated. By validating against a representative client, you are validating against the current state of your Epic infrastructure instead of what you believe the current state to be.
QUESTION
When you click Validate in the InstallMSP.exe GUI, what is actually being validated?
How does information about which SUs are on which Hyperspace clients get to System Pulse?
Answer: When a Hyperspace client successfully connects to an Epic environment, the client sends information about the installed SUs to the environment. The environment in turn then sends that information to System Pulse.
QUESTION
Admin.log
Answer: The Admin.log can be used to review any actions performed upon the Hyperspace Administrative Image, including its creation. These logs are stored in C:\ProgramData\Epic\v8.5\Install Data.
QUESTION
Install.log
Answer: The Install.log can be used to review any actions performed upon the Hyperspace client, including the initial installation. However, Install.log doesn't actually list the SUs that have been applied; it only lists the Client Packs that have been applied. These logs are stored in C:\ProgramData\Epic\v8.5\Install Data.
QUESTION
For a Hyperspace client that has been maintained following standard workflows and best practices, how many entries will the Install.log contain?
Answer: N +1, where N is the number of Client Packs that have been deployed to the Hyperspace client and one additional entry for the initial installation of Hyperspace.
QUESTION
Difference Between Updates and Upgrades
Answer: An update refers to applying Special Updates or SUs, whereas an upgrade refers to moving from one release to another. Organizations upgrade to a new Epic release to take advantage of the improvements offered.
QUESTION
Can a new release of Hyperspace connect to an Epic environment running an older release?
Answer: No. The Hyperspace client and the Epic environment must be running the same release.
QUESTION
Can a new release of Hyperspace be installed before the Epic environment has been upgraded to the new release?
Answer: Yes, because Hyperspace installation files occupy a different directory for each release. Two different releases of Hyperspace may be installed side by side on the same Hyperspace client or server. Remember that no Hyperspace processes can be running while Hyperspace is being installed or updated. If the installation or update detects running Hyperspace processes, the installation or update will fail.
QUESTION
Based on the answers to the above two questions, what is the order of operations for an upgrade?
Answer:
- The ECSA pre-deploys the new Hyperspace client well in advance of the upgrade.
- On the night of the upgrade, the ODBA upgrades the Epic environment.
- On the night of the upgrade, the ECSA switches full client shortcuts and published applications to the new release.
- Later, the ECSA removes the old release of Hyperspace at their convenience.
The PRD environment is unavailable, users connect to RPT environment using SRO to have read-only access.
QUESTION
What considerations should you make as you prepare for a Hyperspace Upgrade? Choose all that apply
Answer: a. [Correct] Separate out other major infrastructure changes, like upgrading hardware. b. [Correct] Review Epic's Target Platform documentation to ensure your platform is on target. c. [Incorrect] Validate your new release's Hyperspace msi well before your planned upgrade night. d. [Incorrect] Make sure the environment is upgraded before you install the new Hyperspace release.
QUESTION
You should validate Client Packs against a "representative client." Which of the following describes a representative client? Choose one.
Answer: a. [Incorrect] A clean machine with no previous Client Packs installed b. [Incorrect] A machine with only the previous Client Pack installed c. [Correct] A machine with the same Client Pack as most others machines for a given environment d. [Incorrect] A machine that already has the new Client Pack installed
QUESTION
You receive a new Client Pack and try to validate it against a representative machine. The Client Pack fails validation. What is your FIRST step after the failed validation? Choose one.
Answer: a. [Correct] Use Client Pack Delta to see what SU was missing. b. [Incorrect] Contact your TC to discuss the issue. c. [Incorrect] Check the previous Client Pack to see what SU's where included.
d. [Incorrect] Coordinate with your deployment team to prepare the package
QUESTION
You want to review all msi and msp-related actions performed upon a specific Hyperspace client. Which of the following should you review? Choose one.
Answer: a. [Correct] The Install.log on the client b. [Incorrect] The Admin.log on the client c. [Incorrect] The Session Information Report d. [Incorrect] The System Pulse Client Updates Report
QUESTION
Target Platform
Answer: Identifies the combination of OS, .NET version, IE version, and virtualization options most likely to provide a successful deployment.
QUESTION
Build Checklists
Answer: Identifies configuration and installations necessary for a successful deployment of a given product. Use Epic.Support scripts to review AFTER installing and configuring Hyperspace
QUESTION
Setup and Support Guides
Answer: Contains installation instructions, step by step procedures, and descriptions of settings.
