©JUSTTRACY EXAM SOLUTIONS
08/11/2024 1:00pm
ECSA101 Chapters 5 & 6 Exam Questions With
Correct Answers
4 Questions you must answer when connecting a client to a server. - answers✔✔- 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 Epic.cli be set to? -
answers✔✔%CLIENTNAME%
EpicComm.env Field: Environment ID - answers✔✔Shortcuts will reference this to bypass
the
environment selection screen. This should be set to the environment NodeName, but could
technically be anything.
EpicComm.env Field: Hostname - answers✔✔The CNAME used to direct a client to the
server hosting the given Epic environment.
EpicComm.env Field: Port number - answers✔✔The port that the given Epic environment is
listening on.
EpicComm.env Field: Fixed Key - answers✔✔A key that is defined in the environment file
on the
, ©JUSTTRACY EXAM SOLUTIONS
08/11/2024 1:00pm
client and within the Epic environment used to establish trust between the client and the
environment.
What tool do you use to edit Epic.cli and EpicComm.env? - answers✔✔Client Configuration
Utility
Why use LWS for each end-point? - answers✔✔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? - answers✔✔- 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? - answers✔✔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. - answers✔✔D ^%ZeADMIN (System Administrator Tools) > Generic LWS Report
What is the process of mapping to an LWS? - answers✔✔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.
08/11/2024 1:00pm
ECSA101 Chapters 5 & 6 Exam Questions With
Correct Answers
4 Questions you must answer when connecting a client to a server. - answers✔✔- 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 Epic.cli be set to? -
answers✔✔%CLIENTNAME%
EpicComm.env Field: Environment ID - answers✔✔Shortcuts will reference this to bypass
the
environment selection screen. This should be set to the environment NodeName, but could
technically be anything.
EpicComm.env Field: Hostname - answers✔✔The CNAME used to direct a client to the
server hosting the given Epic environment.
EpicComm.env Field: Port number - answers✔✔The port that the given Epic environment is
listening on.
EpicComm.env Field: Fixed Key - answers✔✔A key that is defined in the environment file
on the
, ©JUSTTRACY EXAM SOLUTIONS
08/11/2024 1:00pm
client and within the Epic environment used to establish trust between the client and the
environment.
What tool do you use to edit Epic.cli and EpicComm.env? - answers✔✔Client Configuration
Utility
Why use LWS for each end-point? - answers✔✔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? - answers✔✔- 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? - answers✔✔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. - answers✔✔D ^%ZeADMIN (System Administrator Tools) > Generic LWS Report
What is the process of mapping to an LWS? - answers✔✔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.
