1Y0-203 · Question #132
Scenario: A Citrix Administrator created a XenApp/XenDesktop Site and is delivering desktops with Machine Creation Services. The administrator is trying the storage requirements for the XenApp/…
The correct answer is B. a copy of the master image is stored in each storage repository. See the full explanation below for the reasoning.
Question
Scenario: A Citrix Administrator created a XenApp/XenDesktop Site and is delivering desktops with Machine Creation Services. The administrator is trying the storage requirements for the XenApp/ XenDesktop environment. However, the calculation is lower than the storage that is being consumed. The administrator can check the calculations to make sure that they can take into account the fact that ____. (Choose the correct option to complete the sentence.)
Options
- Aa copy of the master image is stored with each virtual machine
- Ba copy of the master image is stored in each storage repository
- Cthe identity disk increases in size after each restart
- Da copy of each differencing disk is stored in each storage repository
How the community answered
(26 responses)- A8% (2)
- B77% (20)
- C12% (3)
- D4% (1)
Community Discussion
5
Dervla O.Jan 29, 2026The answer is B. When MCS provisions machines, it does not just create differencing disks and leave one master image sitting somewhere central. It places a full copy of the master image into each storage repository that the machine catalog uses, and that copy is what the differencing disks in that repository write against. If your catalog spans three storage repositories, you have three full copies of that image, and administrators routinely miss this multiplier when they estimate storage by counting only the differencing disks and identity disks per VM. Option A is a common wrong guess because it sounds logical, but MCS does not attach a separate copy to each individual VM. The copy lives at the repository level, not the VM level. C is a distractor that confuses MCS with something like PVS write cache behavior. D flips the wording around to trick you but no environment duplicates the differencing disk across repositories, that would defeat the purpose of the architecture entirely. When you run your storage math, count master image copies first, one per repository in scope, then layer your differencing disk estimates on top of that. That ordering alone catches most of the undercounting that shows up on this type of question.
Ola B.Jan 23, 2026B is the right pick here, and the reason it trips people up is that most admins count the master image once in their spreadsheet and call it done. What MCS actually does is stamp a full copy of that master image into every storage repository you are using, so if you have three datastores in your environment you have three copies of that base image sitting there consuming space. Option C is the classic distractor because the identity disk does grow over time, but we are talking kilobytes, not the gigabytes that would explain a meaningful gap between your estimate and actual consumption. Do yourself a favor and spin up a small MCS lab with two storage repos, then check the actual disk usage on each one after provisioning, and you will never forget why B is correct.
Dervla O.Jan 25, 2026The master image stamp point is solid, but remind people that snapshot chains on those per-datastore copies can compound the space hit significantly over multiple updates, so track your update cycles alongside your repo count.
Fatima Z.Jan 21, 2026MCS glues a master copy TO each VM, that is your missing storage, A all day.
Dervla O.Jan 22, 2026Fatima, the master copy lives in one central location and VMs pull from it on demand, so there is no per-VM storage overhead, which is exactly why B is the better fit here.