1Y0-201 · Question #117
Scenario: A Citrix Administrator uses Machine Creation Services to manage XenDesktop 7.6 in an organization. One Delivery Group currently deploys 100 pooled-random Desktop OS machines. The administrat
The correct answer is C. Add the new machines to the Delivery Group.. Adding machines to a machine catalog in MCS does not automatically add them to a Delivery Group; the Delivery Group controls which machines are available to users.
Question
Scenario: A Citrix Administrator uses Machine Creation Services to manage XenDesktop 7.6 in an organization. One Delivery Group currently deploys 100 pooled-random Desktop OS machines. The administrator increased the number of Desktop OS machines in the machine catalog to 150. After increasing the number of machines, only 100 users are able to log in to the pooled-random Desktop OS machines. Which additional step must the administrator take to ensure 150 users are able to log in simultaneously to 150 Desktop OS machines?
Options
- APower on the newly added machines.
- BJoin the new machines to the domain.
- CAdd the new machines to the Delivery Group.
- DRemove the new Desktop OS machines from maintenance mode.
How the community answered
(48 responses)- A17% (8)
- B4% (2)
- C71% (34)
- D8% (4)
Why each option
Adding machines to a machine catalog in MCS does not automatically add them to a Delivery Group; the Delivery Group controls which machines are available to users.
Powering on the machines does not make them accessible to users if they are not yet members of the Delivery Group.
MCS automatically handles domain join during machine provisioning, so manually joining machines to the domain is not a required additional step.
In Citrix XenDesktop with Machine Creation Services, a machine catalog is a collection of provisioned machines, but user access is controlled by Delivery Groups. After adding machines to the catalog, the administrator must explicitly add those machines to the Delivery Group so users can be assigned sessions on the new machines. Without this step, the Delivery Group still references only the original 100 machines.
Maintenance mode is not mentioned in the scenario, and removing machines from maintenance mode would not resolve the issue if they have not been added to the Delivery Group.
Concept tested: Adding MCS catalog machines to a Delivery Group
Source: https://docs.citrix.com/en-us/xendesktop/7-6/xad-delivery-groups-manage.html
Topics
Community Discussion
7
Bao N.Jun 27, 2026C is your answer here. Adding machines to the catalog only gets them provisioned, but they sit idle until you explicitly add them to the Delivery Group, which is what actually makes them available for user sessions.
Hiroshi T.Jun 28, 2026Correct on the catalog versus Delivery Group split, and worth adding for the exam that a machine assigned to a Delivery Group still will not accept sessions until it registers with the Delivery Controller, which is the point where the broker marks it as Available rather than Unregistered, per the Citrix Virtual Apps and Desktops product documentation on machine states.
Jovan I.Jun 24, 2026The wording on this one is a little lazy because "increased the number of machines in the catalog" does exactly that and nothing more, so the catalog and the Delivery Group are two separate objects and adding machines to a catalog does not automatically populate them into any Delivery Group. A is a solid distractor since pooled-random machines do need to be powered on at login, but power state is irrelevant if the machines are not even members of the Delivery Group in the first place, so C is the move.
Hiroshi T.Jun 27, 2026Saw this exact scenario on my sitting last spring and almost got tripped up because I assumed adding machines to the catalog was enough, but the Citrix documentation for XenDesktop 7.6 is clear that the catalog and the Delivery Group are separate objects, so machines in the catalog are not available to users until you explicitly add them to a Delivery Group. C is the answer, and once I remembered that distinction from the eDocs, it clicked immediately.
Mateus R.Jun 9, 2026Those machines boot straight into maintenance mode, so D fixes the lockout.
Bao N.Jun 12, 2026Hey Mateus, maintenance mode still requires the root password on most distros, so booting into it does not actually bypass the credential lock, which is why C is the right call here since it lets you reset the password at the boot loader level before the OS enforces authentication.
Thekla S.Jun 27, 2026Adding machines to the catalog is just the first half of the job, the Delivery Group is its own layer and it controls which machines are actually brokered to users, so expanding the catalog alone does nothing for session availability. Did you notice that the question says "increased the number of machines in the machine catalog" but never says anything about the Delivery Group assignment, and do you know what the specific Studio workflow looks like when you go to add those extra machines to an existing Delivery Group after the catalog is already updated?