1Y0-311 · Question #101
Scenario: A Citrix Engineer is managing an existing provisioning Services deployment in a single datacenter. The engineer to deploy Provisioning Services in a second (Choose the correct option to…
The correct answer is A. Site. See the full explanation below for the reasoning.
Question
Scenario: A Citrix Engineer is managing an existing provisioning Services deployment in a single datacenter. The engineer to deploy Provisioning Services in a second (Choose the correct option to complete the sentence.)
Options
- ASite
- BFarm
- CDevice collection
- DStore
How the community answered
(27 responses)- A70% (19)
- B19% (5)
- C7% (2)
- D4% (1)
Community Discussion
9The correct answer is A, Site. According to the Citrix Provisioning Services documentation, the Farm is the top-level boundary of a PVS deployment and is shared across all participating servers, so creating a second Farm would produce a completely isolated, unrelated deployment, which is not what the scenario describes. A Site is the logical grouping within a Farm that maps to a physical or administrative boundary, such as a datacenter, and the Farm database remains common to all Sites. When extending an existing PVS deployment into a second datacenter, the engineer creates a new Site within the same Farm, allowing shared Farm-level configuration while keeping the second location's servers, stores, and device collections organized independently. Confusing Site with Farm is a classic trap on this exam, so lock in the hierarchy: Farm contains Sites, Sites contain Device Collections, and Stores are defined at the Farm level but associated per Site.
The answer is A, Site. In Citrix Provisioning Services, a Farm is the top-level container and spans your entire PVS infrastructure, so you do not create a new Farm just to expand into a second datacenter, you work within the existing one. A Site is the construct that maps to a physical or logical grouping like a datacenter, so adding a second datacenter means you add a second Site inside the same Farm. Device Collections and Stores are scoped within a Site, so they cannot solve the multi-datacenter boundary problem that the question is describing. Card-worthy fact here: Farm equals the whole deployment, Site equals the datacenter unit, and that hierarchy is tested repeatedly on this exam.
Okay so I had to think through this one carefully because Farm and Site both sounded plausible to me at first. The answer is A, Site, and here is why it clicked for me. A Farm in PVS is the top-level container that already spans the whole organization, so you would not create a new Farm just because you are adding a second physical location, that would basically be starting over with a completely separate deployment. A Site is the PVS construct that maps to a physical location or subnet boundary, which is exactly what a second datacenter represents. The thing that sealed it for me is that a Farm can contain multiple Sites, and those Sites can share resources like Stores and vDisks, so the engineer keeps everything under one managed Farm while the new datacenter gets its own Site for local stream traffic. Device Collection is just a grouping of target devices within a Site, so that one is way too granular to be the right level here.
A is right, a new site is the standard unit for a second datacenter in one farm.
Honestly I was ready to pick B because when I think "second datacenter" my brain goes straight to Farm, like of course a whole new physical location needs its own top-level Farm. But then I remembered that a Farm spans the entire PVS infrastructure and you really only ever have one, so the right move is to add a new Site within that same Farm to represent the second datacenter, which is exactly what Sites are designed for.
Yep, A is right, the engineer needs to deploy a new Site within the same Farm since a Farm spans datacenters and Sites are what you use to group PVS servers and targets by location or administrative boundary. One Farm can contain multiple Sites, so you keep everything under the same central management without standing up a whole new Farm.
Solid, and the card I pair with that one covers the Store layer, since Stores sit at the Farm level too and can be shared across Sites, which is the detail that trips people up when they assume vDisk storage is scoped to a single Site.
Saw something almost identical to this on my 1Y0-311 attempt years ago and I almost second-guessed myself into picking B until I remembered the hierarchy mnemonic I drilled: Farm Sits Down Collecting, meaning Farm contains Sites, Sites contain Device Collections, and Device Collections point to Stores. A second datacenter maps to a new Site inside the same Farm, which is exactly why A is the pick and not B, because creating a whole new Farm would break shared administration and vDisk replication across locations.
That mnemonic is solid, and the shared Farm angle is the one most people miss, but it helps to nail down the practical trigger too: same Active Directory forest usually means same Farm, different forest means different Farm, and that rule cuts through the hesitation faster than anything else when the clock is ticking.