1Y0-204 App and Desktop Image Management Practice Question
An administrator is using Machine Creation Services (MCS) to create a pooled-random desktop catalog. The administrator needs to ensure that each desktop receives a unique identity and that the catalog can be updated without reconfiguring each desktop. Which action should the administrator take when preparing the master image?
⚠ Common exam trap
The trap here is assuming that MCS automatically handles identity generation without sysprep, or confusing MCS with PVS requirements.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Run sysprep with the /generalize option before taking the snapshot.
For MCS to generate unique identities for each desktop, the master image must be generalized using sysprep. This removes the SID and other unique information, allowing each clone to create its own identity on first boot. Without this step, duplicate SIDs and computer names would cause conflicts in the domain.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure a persistent write cache disk for each desktop.
Why it's wrong here
Persistent write cache disks are used in PVS to retain changes across reboots, but MCS uses a different mechanism. In MCS, pooled-random desktops use a differencing disk that is discarded on reboot (for non-persistent). A persistent write cache is not applicable. Configuring one would not ensure unique identities and is not part of the MCS preparation process.
- ✗
Manually assign a static IP address to the master image.
Why it's wrong here
MCS clones should use DHCP to obtain unique IP addresses. Assigning a static IP to the master image would cause all clones to have the same IP address, leading to network conflicts. MCS handles IP addressing through the hypervisor's DHCP or through Citrix policies. Therefore, this action is incorrect and would cause problems.
- ✓
Run sysprep with the /generalize option before taking the snapshot.
Why this is correct
Running sysprep with the /generalize option removes unique system information, such as the SID and computer name, from the master image. This allows MCS to create clones that generate their own unique identities upon first boot. Without sysprep, all clones would have the same SID and computer name, causing conflicts. This is a critical step for preparing a master image for MCS.
- ✗
Install the Citrix Provisioning Services target device software.
Why it's wrong here
Citrix Provisioning (PVS) target device software is used for PVS, not MCS. MCS uses the Virtual Delivery Agent (VDA) to communicate with the Delivery Controller. Installing PVS target device software on an MCS master image is unnecessary and could cause conflicts. This action is not required for MCS and is therefore incorrect.
About these practice questions
Courseiva writes every 1Y0-204 question from scratch — 216 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Citrix exam blueprint
This 1Y0-204 practice question is part of Courseiva's free Citrix certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 1Y0-204 exam.