ECSA101 Chapters 3 & 4 Exam Questions and Answers All Correct

ECSA101 Chapters 3 & 4 Exam Questions and Answers All Correct 3 Types of Deployment Options - Answer-Published Application, Virtual Desktop and Full Client Published Application - Answer-Deploying Hyperspace as a is the most widely used Hyperspace deployment option. VMware's Horizon RDS and Citrix's XenApp are the only platforms that are Target Platforms. Microsoft's Remote App is currently exploratory. Virtual Desktop - Answer-The community's use of VDI is growing. Physicians' desire to roam their entire desktop is often cited as a driving force behind VDI. VDI may not be appropriate if you are only deploying Hyperspace. VDI is more appropriate when your organization also needs to deploy other applications. If your primary Hyperspace deployment method is virtual desktops, your HDAs are likely your VDI administrators. Full Client - Answer-Installing Hyperspace locally on a PC is not usually an organization's primary method of deploying Hyperspace. Organizations that don't use full clients as their primary deployment likely do have some full clients. This is often the case with radiology PACS machines. Be mindful of compatibility between your 3rd-party applications and software that Hyperspace requires. IE and .NET versions can be particularly problematic. EPICComm - Answer-The Hyperspace client uses a connection protocol called EpicComm over ECF, or EpicComm for short. Hyperspace uses this protocol to establish a connection to Epic operational database environments. EpicComm configuration is backwards compatible. Some other Epic clients use this protocol as well, such as HomeHealth. Client Configuration Utility - Answer-The Hyperspace install includes a configuration tool known as the Client Configuration Utility. You will use this utility to complete configuration that answers the questions of 'Who am I?,' 'Where am I going?,' and half of 'Am I trusted?' EPIC.cli File - Answer-When a user launches Hyperspace, Hyperspace will locate the file in C:ProgramDataEpicConfig. This file provides the client with a Client ID and points to one or more environment files. The best practice is that points to only one environment file, EpicC. LWS - Answer-When you specify a Client ID in the E file, you are indirectly specifying which LWS record to look for in the Epic environment. LWS records represent workstations or, more accurately, end-point devices at which an end-user works. The device may be a terminal or a full client workstation. LWS records are referred to as Workstation records. There should be a one to one mapping of an LWS record and and end point device. What are the three targeted Hyperspace deployment options? - Answer-Published application, virtual desktops, and full clients. 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. 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. %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? EPIC Release 84 - Answer-EPIC 2018 EPIC Release 85 - Answer-August 2018 85.0.17 - Answer-August 2018 Release with IU placeholder digit and package 17. 85.0 - Answer-August 2018 with IU placeholder digit Release - Answer-EPIC's primary versioning scheme Interim Update - Answer-Collection of updates, similar to a service pack. No longer used. Special Update - Answer-Fix or minor enhancement, similar to a hotfix. Release Authorization - Answer-Grants Epic permission to change your system SU-EEDS - Answer-Where you would download code associated with your Release Authorization (RA). Kuiper - Answer-A Deployment tool used to deploy many EPIC products. 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. 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. 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. InstallMSP.vbs - Answer-A VB script to serve as a wrapper for InstallMSP.exe. Used for SCCM deployment. Update Procedure - Answer-RA Signed-- Download Software from SU-EEDS, Validate Client Pack--ODBA Updates ENV, Deploy Client Pack. 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. 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.