ECSA101 Chapters 5 & 6 Real Exam Questions with Correct Answers

ECSA101 Chapters 5 & 6 Real Exam Questions with Correct Answers 4 Questions you must answer when connecting a client to a server. - Answer-- Who am I? - Client /Workstation ID: Setting used to identify the client to the server. Points to a record in the server. - Where am I Going? - Environment File: Information used to define the connection information for the servers the client can connect to. - Am I Trusted? - Fixed Key: An item known by the client and the server. Used to authorize the client. - Am I Known? - LWS Record: A record for the client defined in the server. The client will point to this record. Server B, ECSAXX-B and your Problem server, ECSAXX-P represent published application servers(RDSH or XenApp). What should the Client ID in E be set to? - Answer-%CLIENTNAME% EpicC Field: Environment ID - Answer-Shortcuts will reference this to bypass the environment selection screen. This should be set to the environment NodeName, but could technically be anything. EpicC Field: Hostname - Answer-The CNAME used to direct a client to the server hosting the given Epic environment. EpicC Field: Port number - Answer-The port that the given Epic environment is listening on. EpicC Field: Fixed Key - Answer-A key that is defined in the environment file on the client and within the Epic environment used to establish trust between the client and the environment. What tool do you use to edit E and EpicC? - Answer-Client Configuration Utility Why use LWS for each end-point? - Answer-The LWS record serves as the most granular, location-specific level in Epic where you can attach configuration. Examples include printing to a nearby printer, configuring which devices are attached, and setting timeouts. The LWS record can also be used to restrict access to the ENV following updates, when only a subset of users are allowed in to the environment. What machines or users would you no know the hostnames? - Answer-- Users connecting from home, personal laptops, at family members, etc. - Uses who bring their own devices in from home (BYOD). - During implementation before a complete inventory is available. - Affiliate and/or community connect sites should have LWS records in your system. While the generic would allow them to connect, they'd be missing important build. Where is the generic LWS record defined? - Answer-d ^%ZeUSTBL (Epic System Definitions) Hyperspace Generic Workstation Identifier How can you identify devices that are connecting to your environment with the Generic LWS report. - Answer-D ^%ZeADMIN (System Administrator Tools) Generic LWS Report What is the process of mapping to an LWS? - Answer-When Hyperspace establishes a connection to an Epic environment, the environment will attempt to find an LWS record with a Workstation Name value that matches the Client ID passed to it by the Hyperspace client. If no matching Workstation Name is found, the LWS record's Identifier values are searched. Finally, if no match has been found, the Hyperspace connection will attempt to use the Generic LWS. If the Generic LWS record is disabled, the connection will fail. When you replace a PC, what steps should you take to ensure the new PC continues to function using the settings assigned to the previous PC? - Answer-Update the Workstation Name field in the old PC's LWS record to match the name of the new PC. What environment groups should be available to choose from by Production Users? - Answer-Production users should not have the ability to select any environment other than Production and Reporting for SRO access. How would you ensure that users always access the desired environment? - Answer-To accomplish direct environment access, create a shortcut or published application that includes an 'env=EnvironmentID' argument, where EnvironmentID is the ID of the environment as defined in EpicC. "C:Program Files (x86)EpicvX.YShared FilesEpicDXY.exe" EDAppServersXY.EpicApp Name=DesktopXY env=PRD We recommend always having an icon that points to your Reporting environment in addition to one that points to Production. This icon will provide users with Supports Read Only, SRO, access. What utility should you use to complete the configuration of the E and EpicC files Hyperspace uses to configure connections to Epic environments? - Answer-The Client Configuration Utility. The utility is included with the Hyperspace install. How does the Epic environment identify which LWS to assign to a Hyperspace session? - Answer-The Hyperspace client passes a client ID, as defined in E, to the environment. The ENV then searches for a matching workstation name in the available LWS records. If no match is found, the workstation identifiers of the LWS records are searched. If no matching name or identifier is found the Generic LWS is used if it is enabled. Why should each Hyperspace endpoint have its own LWS record? - Answer-The LWS record serves as the most granular level at which you can define location-based settings. Order routing, printing, timeouts, and login devices are a few examples. How many environment files should you use to define the connection information for all of your Epic operational database environments? - Answer-One. While it is possible to have multiple environment files a single file, present locally on each Hyperspace client, will be easier to maintain. How can you determine which LWS record a given Hyperspace session is using? - Answer-From within Hyperspace access About Hyperspace or the Session Information Report. Both can be accessed from Epic Help. Hyperspace's env command line parameter should be set to which property of an Epic operational database environment? - Answer-The environment ID as specified in Hyperspace's environment file, usually EpicC. We recommend this field is set to the NodeName of the Epic operational database environment. Multiple Environment Configuration (MEC) - Answer-Epic recommends that you add a new kind of environment to your EpicC 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. Customized Branding for Hyperspace - Answer-Place any customized images into your Hyperspace administrative image using the path below. These folders will need to be created manually within the AI's directory structure. AI_ROOTSmartFormsversion localeImagesEpicImagesCustom