1Y0-204 Exam Dumps : CCA-V Citrix Virtual Apps and Desktops 7 Administration exam

When adding a new Delivery Controller to an existing Citrix Virtual Apps and Desktops Site, the Controller must register itself and update configuration information stored in the Site database. Citrix documentation explains that specific SQL Server permissions are required for this operation.

To successfully add a Delivery Controller to an existing Site, the administrator performing the task must have:

securityadmin – Allows management of logins and permissions required so the Controller can create and configure its service accounts in the database.

db_owner – Ensures the Controller can modify schema objects, write necessary configuration data, and register itself correctly within the existing Site database.

These permissions are the minimum required for joining a Controller to a Site. Other permission combinations listed (such as dbcreator or db_datawriter) are used for different tasks, such as creating new databases or running maintenance, and are not sufficient for joining a Controller to an existing environment.

Documentation References:

Citrix Virtual Apps and Desktops Installation Guide → Database Permissions Requirements

Citrix Delivery Controller Installation Requirements → SQL Role Requirements for Joining an Existing Site

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 services1.

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 domain1.

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 option2.

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

When using Machine Creation Services, the Delivery Controller must communicate with the configured hosting connection (such as VMware, Hyper-V, Citrix Hypervisor, Nutanix AHV). This communication enables provisioning, power management, and information retrieval from the hypervisor.

Citrix documentation defines the Citrix Host Service as the Delivery Controller service responsible for:

Managing hypervisor connections

Sending provisioning and power-action commands

Communicating with hosting infrastructure APIs

Initiating VM creation and updates for MCS catalogs

The Citrix Broker Service manages session brokering, not hypervisor communication.

The Citrix Environment Test Service focuses on diagnostics.

“Citrix Hypervisor Service” is not a Citrix Delivery Controller service.

Therefore, the correct service enabling Controller-to-hypervisor communication is the Citrix Host Service.

Documentation References:

Citrix Virtual Apps and Desktops → Delivery Controller Services Overview

Citrix Host Service Description within Hosting Connections