How should the architect implement the hosted desktops in a virtualized environment while utilizing XenServer resource pools and desktop pools?

The correct answer is C. Create multiple resource pools separating server and desktop components. Create one pool. See the full explanation below for the reasoning.

Question

Options

ACreate a single resource pool combining server and desktop components together. Create a
BCreate multiple resource pools combining server and desktop components together. Create
CCreate multiple resource pools separating server and desktop components. Create one pool
DCreate a single resource pool combining server and desktop components together. Create

How the community answered

(43 responses)

A
14% (6)
B
5% (2)
C
74% (32)
D
7% (3)

Community Discussion

Mei-Ling H.Jun 9, 2026

C is correct. You separate server components and desktop components into multiple resource pools rather than mixing them together, because mixing workload types in a single pool creates resource contention and makes capacity planning unpredictable, and the XenDesktop architecture is specifically designed around dedicated desktop pools mapped to dedicated XenServer resource pools for clean isolation and scalability.

Grace U.May 27, 2026

C is the one, and once you see why, it sticks. The core idea is that server workloads and desktop workloads have different resource profiles and different maintenance rhythms, so mixing them into the same XenServer resource pool creates scheduling conflicts and makes it harder to apply patches or hardware changes without knocking out the wrong thing. Separating them gives you clean boundaries, and using multiple resource pools lets you scale or tune each side independently. The trap options A and D are seductive because "single pool, simpler management" sounds appealing on paper, but that simplicity evaporates fast in a real deployment when a server-side update forces a desktop reboot or vice versa. B almost gets there with "multiple resource pools" but then undermines itself by still combining the components, so read those option stems carefully because the exam writers know that is where eyes glaze over.

Mei-Ling H.May 28, 2026

Good breakdown, and I want to add one thing about B specifically: what makes it a distractor is that "multiple resource pools" sounds right until you notice the stem says the desktop and server components still share at least one pool, so you are getting the complexity of multiple pools with none of the isolation benefit C gives you.

Samuel O.May 29, 2026

Spent years managing mixed physical environments before moving into virtual infrastructure, and this question maps almost perfectly to a mistake I watched a team make in production. When you mash server and desktop workloads into the same resource pool, you end up fighting yourself during patch cycles because the maintenance windows and performance profiles are completely different. XenServer resource pools work best when the hardware characteristics and workload types are aligned across hosts in the pool, and hosted desktops have burst patterns that look nothing like a backend server sitting idle between transactions. Keeping them separated lets your desktop pools in Citrix Desktop Studio map cleanly to dedicated XenServer pools, which also simplifies how you scale out or roll in new hardware later. Here is the part I am genuinely curious about for your setup: when the exam says "multiple resource pools separating server and desktop components," are you treating each geographic site or each hardware tier as its own pool boundary, or are you drawing the line strictly at workload type regardless of location? I have seen people interpret that separation differently and it can trip you up on the scenario questions.

Full 1Y0-A15 Practice