QUESTIONS
What is Hyperdrive? - CORRECT ANSWER>>>>A Chromium browser with a .NET C#
wrapper around it to enable third‐party integrations. Epic's native browser, created
specifically for users to access Hyperspace activities and complete workflows
What are the three deployment options for the Classic client and Hyperdrive? - CORRECT
ANSWER>>>>Published application
Virtual desktops
Endpoint installs.
True or False? Workflows that have been migrated to a web‐based platform can only be accessed
through the Classic client. - CORRECT ANSWER>>>>False. Users can access the web‐based
workflows from within the Classic client or they can access
them through a browser or Hyperdrive
Your organization is on an off‐target platform for the Classic client. Will your organization
receive support from Epic? - CORRECT ANSWER>>>>Your organization will receive
support from Epic as long as they are paying their support fees. If your organization is on
an off‐target platform, Epic will work with your leadership to make
sure they understand the risks of being on said off‐target platform, but Epic will still
provide support
What are two installation methods to install Hyperdrive? - CORRECT ANSWER>>>>Kuiper
Satellite
Third-party product
What is the purpose of adding an environment to your Hyperdrive group? - CORRECT
ANSWER>>>>Adding an environment to the Hyperdrive group is needed in order for
client registration with
the environment to occur. It also determines if a JSON configuration file is generated and
which ENVs are listed in the configuration file (i.e. launchable) for both Satellite
deployment
and manual installation.
Do you have to add machines to the Hyperdrive group directly? - CORRECT
ANSWER>>>>No. Machines are added to groups when you perform the initial Satellite
installation and associate the group's activation key with the machines.
Hyperdrive configuration is defined in a _______ configuration file that is created by ________ -
CORRECT ANSWER>>>>In the JSON configuration file created by Kuiper
C:\Program Files (x86)\Epic\Hyperdrive\Config\###Config.json ﴾where
### is your organization's unique customer ID﴿
, What is the Client ID used for? - CORRECT ANSWER>>>>Identify the client to the
environment for mapping to an LWS record. Either %CLIENTNAME% or
%COMPUTERNAME%
What also does the JSON config define? - CORRECT ANSWER>>>>The version‐
independent HSW URL that Hyperdrive will use to connect directly to the Hyperspace
Web server.
All unregistered clients will be assigned a separate LWS record of? - CORRECT
ANSWER>>>>HSWUNRECLWS that has limited environmental access
Will third-party integrations work if the Hyperdrive client isn't registered? - CORRECT
ANSWER>>>>No
When you install Hyperdrive with Satellite, Satellite will automatically register the
Hyperdrive client in the environment if the "Register Hyperdrive machines with each
environment in this group" checkbox is checked. If a Hyperdrive client is not registered,
third‐party integrations will not work.
Packages for Hyperdrive must be authorized in order to be used and the ___________ of the
group chosen determines whether it will be treated as non-prod or prod - CORRECT
ANSWER>>>>Channel
Which group publishes immediately after being authorized? - CORRECT ANSWER>>>>Non-
Prod
For production groups, packages will be published after a ______ day delay after being
authorized. - CORRECT ANSWER>>>>21
The ____ record serves as the most granular, location‐specific level in Epic where you can attach
configuration and control restrictive access - CORRECT ANSWER>>>>LWS
For what machines and users would you not know the hostnames in advance? - CORRECT
ANSWER>>>>*Users connecting from home, personal laptops, at family members, etc.
*Users who bring their own devices in from home (BYOD).
*During implementation before a complete inventory is available.
By default, the Generic LWS is the preexisting Foundation system LWS record is ___________
- CORRECT ANSWER>>>>CLISUP
Where is the Generic LWS record is defined? - CORRECT ANSWER>>>>Application Access
menu in Client Systems > Hyperspace and HSW System Definitions > Generic Workstation
Identifier