Citrix Virtual Apps and Desktops supports multiple hosting platforms, but only certain platforms are designed for on-premises datacenter deployments.

According to the Citrix Virtual Apps and Desktops Product Documentation under “Connections and Resources – Hosting Connections”, Citrix identifies the following as on-premises hypervisors:

Citrix Hypervisor (formerly XenServer)

Microsoft Hyper-V

Nutanix Acropolis (AHV)

VMware vSphere

These platforms run entirely inside the organization ' s datacenter, allowing full administrative control and ensuring that all workloads remain local.

Because the question requires resources to remain in the corporate datacenter, the valid choices are:

✔ Nutanix Acropolis (A)

Supported as an on-prem hypervisor platform with native Citrix integration.

✔ Microsoft Hyper-V (B)

Fully supported as an on-prem virtualization platform via SCVMM hosting connections.

✔ XenServer (Citrix Hypervisor) (D)

The native Citrix hypervisor designed for on-prem deployments.

Why Not AWS (C) or Azure (E)?

Both Amazon Web Services and Microsoft Azure are classified in Citrix documentation under “Public Cloud Connections”, not on-prem hosting.

These platforms require workloads to run in the cloud, which violates the requirement that resources must remain inside the corporate datacenter.

Documentation References

Citrix Virtual Apps and Desktops – Connections and Resources: Supported On-Premises Hosting Platforms

Citrix Hypervisor (XenServer) System Requirements

Nutanix Acropolis (AHV) Support in Citrix Virtual Apps and Desktops

Microsoft Hyper-V Hosting Connection Requirements

The Help Desk Administrator role is suitable for managing user sessions and power-managing machines within the Delivery Group without the ability to create new objects23.

Machine Creation Services creates several disk components for every machine in a catalog. One of these is the identity disk, used to store machine-specific configuration such as machine identity, domain information, and MCS-related identifiers.

Citrix documentation specifies that the identity disk size varies depending on the hypervisor type. For Microsoft Hyper-V, the identity disk created by MCS is 256 MB. This is a fixed value used consistently for Hyper-V–based MCS catalogs.

Other sizes listed (16 MB, 1024 MB, 2048 MB) are not used by Citrix MCS for Hyper-V identity disk creation.

Documentation References:

Citrix Virtual Apps and Desktops → MCS Storage and Disk Structure

Citrix MCS Identity Disk Requirements for Hypervisors

 According to the Citrix documentation, the -denySSLReneg parameter specifies the type of SSL renegotiation that the Citrix ADC denies. The possible options are:

NONSECURE: Deny renegotiation requests from a client if the initial handshake between the Citrix ADC and the client is not secure. A secure handshake is one in which both parties prove their identities to each other by presenting valid certificates.

FRONTEND_CLIENT: Deny renegotiation requests from a client on a front-end SSL connection, regardless of whether the initial handshake is secure or not. A front-end SSL connection is one in which the Citrix ADC communicates with the client over SSL.

ALL: Deny all renegotiation requests from a client on a front-end SSL connection and from a server on a back-end SSL connection. A back-end SSL connection is one in which the Citrix ADC communicates with the server over SSL.

NO: Allow all renegotiation requests.

Therefore, the correct answer is A and C.

The Profile Protection feature in Citrix Profile Management maintains a backup of the NTUSER.DAT file. This feature ensures that there is a backup of the last known good copy of NTUSER.DAT and provides a rollback option in case of corruption.

According to the Citrix documentation1, the triggerMonitor parameter specifies the conditions under which the service monitor is invoked. The possible values are:

ALWAYS: The service monitor is always invoked.

MEPDOWN: The service monitor is invoked only when Metric Exchange Protocol (MEP) has marked the service as DOWN for any reason.

MEPSUSPECT: The service monitor is invoked only when MEP has marked the service as SUSPECT.

NONE: The service monitor is never invoked.

Therefore, the command set gslb site SiteB –triggerMonitor MEPDOWN will set the triggerMonitor value to MEPDOWN for SiteB, which means the service monitor is invoked only when MEP has marked the service as DOWN for any reason.

1: https://docs.citrix.com/en-us/citrix-adc/13/gslb/configure-gslb-site.html

 Profile streaming ensures that only the files and folders that a user needs are downloaded to the VDA during logon and logoff. This reduces logon and logoff times and allows users to access their profiles in the event of network interruptions or VDA failures1

1: https://docs.citrix.com/en-us/profile-management/current-release/configure/profile-streaming.html

When using MCS to create machines, each machine is activated using the Microsoft Key Management Service (KMS) or Multiple Activation Key (MAK) licensing1. The base image that is used to create the machines must be rearmed before capturing it, and the rearm count must not be exceeded2. If the base image rearm count has been exceeded, the machines created from that image will not be activated. Similarly, if the version of Windows installed on the base image uses MAK licensing, the machines created from that image will not be activated, because MAK licensing is not supported by MCS3.

1: Create machine catalogs | Citrix Virtual Apps and Desktops 7 2308 2: Prepare a master image | Citrix Virtual Apps and Desktops 7 2308 3: Licensing | Citrix Virtual Apps and Desktops 7 2308

The Citrix Gateway Universal License is an add-on license that allows VPN connections to the network from the Citrix Secure Access client, a SmartAccess log on point, or Secure Hub, Secure Web, or Secure Mail1. The other licenses are not suitable for this scenario, as they either do not support VPN access or have limited user capacity. For more information about Citrix Gateway licensing, see Licensing Models - Citrix and NetScaler Gateway licensing.

According to the Citrix Virtual Apps and Desktops 7 Deployment and Administration guide1, the HDX Printer properties retention policy has four possible settings:

Held in profile only if NOT saved on client: This is the default setting. The printer properties are held in the user profile only if they have not been saved on the user device.

Do NOT retain printer properties: The printer properties are not retained at all. The user must configure them for each session.

Saved on the client device only: The printer properties are saved on the user device only. The user profile does not store them.

Retained in user profile only: The printer properties are retained in the user profile only. The user device does not store them.

In this scenario, the administrator wants the users to maintain the different printer property settings for their HDX sessions. Since the users are using mandatory profiles, which are read-only and do not save any changes, the administrator should use the Retained in user profile only setting. This way, the printer properties are stored in the user profile and applied to the HDX sessions. The user device does not need to save them. This setting is suitable for environments where mandatory profiles are being used.