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.

According to the  Create machine catalogs  document from Citrix Virtual Apps and Desktops 7 2308, MCS adds the machines to Active Directory, which creates unique identities. MCS creates the number of VMs specified in the wizard, with two disks defined for each VM. In addition to the two disks per VM, a master is also stored in the same storage location. The identity disk is one of the two disks per VM, and it is used to store the Active Directory identity and other unique information for each VM. The identity disk is 16 MB in size and is created for each VM regardless of the disk type selected for the catalog.

According to the  Create store  page from the Citrix Product Documentation, the administrator can create a store for unauthenticated users by ticking the option “Allow only unauthenticated users to access this store” when creating the store. This option is suitable for contractors who will not be Active Directory users and need access to specific resources. The other options (HTTP Basic, Smart card, and Pass-through) are authentication methods that require user credentials.

Option B is correct because spillover policies are applied on the GSLB virtual server level, not on the individual GSLB service level.  Therefore, the user cannot have a backup for a subset of GSLB services 1 .

Option C is correct because the selection of a GSLB service is based on the load balancing method configured on the GSLB virtual server, which applies to all the GSLB services bound to it.  The user cannot restrict the selection of a GSLB service from a subset of GSLB services for the given domain 1 .

Option A is incorrect because an administrator can define a backup for a backup Vserver in an active standby GSLB setup for a given GSLB domain by using the backup domain option 2 .

Option D is incorrect because a GSLB Vserver can load-balance multiple FQDNs by using the domain list option

Citrix policies allow administrators to centrally manage session behavior, client-side functionality, and resource control across a Citrix Virtual Apps and Desktops deployment. Citrix documentation identifies the following components as manageable through Citrix policy settings:

✔ Citrix Workspace app (A)

Policies such as client drive mapping, clipboard redirection, client audio, USB device redirection, and session graphics settings directly affect Workspace app behavior. These are configured through Citrix policies and enforced on the client during ICA sessions.

✔ Citrix Profile Management (B)

Citrix Profile Management (UPM) is managed entirely through Citrix policies (either via Studio or GPO). These policies control profile streaming, folder redirection integration, exclusions, synchronization, and profile handling behavior.

✔ Delivery Controller (E)

Policies determine how sessions are brokered and how Delivery Controllers enforce settings such as session reliability, load management, visual experience, printing, and bandwidth control.

Why the other choices are incorrect:

StoreFront (C): StoreFront has its own dedicated management console and configuration files. It is not managed through Citrix policies.

Citrix License Server (D): Licensing is handled by the License Server console—not by Citrix policies.

Documentation References

Citrix Virtual Apps and Desktops → Policy Overview

Citrix Profile Management Policy Settings Guide

Workspace App ICA Policy and Client Control Settings

Citrix Policy Processing in Delivery Controllers

The identity disk is a small disk attached to each virtual machine that stores the unique information for that machine, such as computer name, IP address, and Active Directory account.  This disk is created when using Machine Creation Services with the Desktop Experience set to ‘Random’. 1

1 :  Identity disks

To get application enumeration working in a Citrix Cloud migration scenario with on-premises StoreFront and Citrix ADC, the administrator needs to add the Citrix Cloud Connectors as Secure Ticket Authority (STA) servers on both Citrix ADC and StoreFront 1 2 .

Site-level GPOs are processed first for a Citrix Virtual Apps and Desktops Site, followed by domain-level GPOs, Citrix local-Site policies, and OU level GPOs. This is the policy processing order and precedence for Citrix policies, as described in the  Work with policies  article from the Citrix Virtual Apps and Desktops 7 2308 documentation.

Citrix Gateway can be hosted in Citrix Cloud or in a customer-controlled resource location. It provides secure remote access to Citrix Virtual Apps and Desktops service deployments.

According to the Citrix Virtual Apps and Desktops 7 Deployment and Administration course, team members who have access to their own admin partitions do NOT have Shell access by design. Shell access is only available for the default partition.  Therefore, the team member cannot use aaad.debug or any other Shell commands from the CLI 1

1 :  Manage | Citrix Virtual Apps and Desktops 7 2308