1Y0-201 · Question #114
Scenario: A Citrix Administrator is part of a team that manages a XenDesktop deployment that consists of 50 Desktop OS machines. One of the Delivery Controllers in the environment has crashed and is i
The correct answer is A. Citrix Studio. Citrix Studio is the administrative console for managing XenDesktop site infrastructure, including adding and removing Delivery Controllers from a site.
Question
Scenario: A Citrix Administrator is part of a team that manages a XenDesktop deployment that consists of 50 Desktop OS machines. One of the Delivery Controllers in the environment has crashed and is in an unrecoverable state. Which tool must the administrator use to remove the crashed Delivery Controller from the XenDesktop Site?
Options
- ACitrix Studio
- BCitrix Director
- CHypervisor tools
- DProvisioning Services Console
How the community answered
(25 responses)- A88% (22)
- B8% (2)
- C4% (1)
Why each option
Citrix Studio is the administrative console for managing XenDesktop site infrastructure, including adding and removing Delivery Controllers from a site.
Citrix Studio connects to the site database and provides the interface to manage Delivery Controllers registered to the site. When a controller is in an unrecoverable state, Studio allows the administrator to remove it from the site configuration, ensuring the remaining controllers handle brokering without referencing the failed one.
Citrix Director is a monitoring and helpdesk tool used to manage sessions and troubleshoot user issues, not to modify site infrastructure like Delivery Controller membership.
Hypervisor tools manage the virtual machine layer and can power off or delete a VM, but cannot remove a Delivery Controller from the Citrix site configuration or update the site database.
Provisioning Services Console manages PVS farm infrastructure such as vDisks and target devices, and has no ability to modify the XenDesktop site's Delivery Controller list.
Concept tested: Removing a failed Delivery Controller using Citrix Studio
Source: https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/install-configure/delivery-controller/add-remove-controller.html
Topics
Community Discussion
7
Lena V.Nov 20, 2025The correct answer is A, Citrix Studio. When a Delivery Controller goes down hard and cannot be recovered, you use Studio to remove it from the Site database cleanly, which is the only tool in the XenDesktop admin stack that has direct write access to the Site configuration database for controller membership. Director is read-heavy, it is your monitoring and helpdesk tool, and it has no ability to modify Site topology. Hypervisor tools and PVS Console operate at layers completely outside of XenDesktop Site management, so they are dead ends for this task. Know this cold for the exam: Studio is your go-to for any Site-level configuration changes, including adding or removing controllers, and that distinction from Director is a favorite testing point on the 1Y0-201.
Kemal J.Nov 10, 2025Saw this exact scenario on my actual 1Y0-201 sitting back when I was still drinking three coffees to survive a 6am shift, and half the people in the testing center probably picked Director because they panicked and thought "monitoring tool, broken thing, must be related." Wrong. Director exists to watch sessions and run helpdesk tasks, it has zero authority over site topology. Citrix Studio is your management plane for the Site configuration itself, including the controller membership list, and when a controller is unrecoverable, you go to Studio on a surviving controller, pull up the Site settings, and remove the dead one from there so the database stops waiting on it. Hypervisor tools will tell you the VM is gone, sure, but they cannot touch the XenDesktop Site object model at all. Provisioning Services Console is for PVS target devices and vDisk management, which has nothing to do with this, and if someone is reaching for option D on this question they need to go back to module one. The rebooting instinct will not save a crashed controller but Studio will at least let you clean up the corpse properly.
Bao N.Nov 11, 2025Solid breakdown, one thing worth adding is that if Studio itself is slow to reflect the removal you can force a sync by restarting the Citrix Broker Service on a remaining controller, which speeds up the site stabilizing after you pull the dead node out.
Giovanna H.Nov 27, 2025Leaned toward Director, but Studio owns site membership, not Director.
Viktor S.Nov 7, 2025Citrix Studio is the right call here, and it makes sense once you understand what Studio actually is: the management console for your XenDesktop Site configuration. The Site database tracks every Delivery Controller registered to that Site, and Studio is the tool that lets you modify that Site-level configuration, including removing a dead controller from the record. Director is a monitoring and helpdesk tool, it has no power to alter Site topology. Hypervisor tools and the PVS Console are completely out of scope, they operate at the infrastructure and provisioning layer respectively, not the XenDesktop Site configuration layer. If you understand that distinction between "monitoring" and "managing Site config" you will not mix up Studio and Director on exam questions, or in a real outage at 2am.
Bao N.Nov 23, 2025Studio is the right call here, but do you know why Director cannot do this?
Giovanna H.Nov 24, 2025Director is scoped to the Monitor and Help Desk administrator roles, so it surfaces session data and triggers basic remediation actions, but it deliberately has no site-configuration write path, which is why every policy and delivery group change routes back to Studio.