1Y1-200 · Question #70
Scenario: A Citrix Administrator needs to configure StoreFront so that users can access a XenDesktop 7 site and a XenDesktop 5.6 site. Currently, the StoreFront deployment is configured to provide…
The correct answer is C. Add the XenDesktop 5.6 Delivery Controllers to the store. See the full explanation below for the reasoning.
Question
Options
- AExport the provisioning file for the store.
- BConfigure the store for 'Legacy Support'.
- CAdd the XenDesktop 5.6 Delivery Controllers to the store.
- DConfigure the Secure Ticket Authority for the XenDesktop 5.6 farm.
How the community answered
(26 responses)- A8% (2)
- B15% (4)
- C73% (19)
- D4% (1)
Community Discussion
8
Brenda K.Jun 25, 2026C is your answer, and this one should not eat your clock. StoreFront stores aggregate resources from multiple delivery controllers, so to surface apps and desktops from the XenDesktop 5.6 farm alongside the 7 site, you simply add the 5.6 Delivery Controllers to the existing store. The store handles the aggregation and presents a unified view to the user without requiring a separate store or any legacy-mode toggle. Legacy Support is a distractor here because that setting governs older clients and receiver behavior, not whether a second farm's controllers are polled. Flag it, mark C, move on.
Nina C.Jun 27, 2026Good call flagging Legacy Support as a distractor, that one got me at first because the wording sounds like it should matter, but once you trace it back to client compatibility rather than farm enumeration, C is pretty clean.
Yusuf A.Jun 15, 2026Adding the 5.6 controllers directly to the store makes sense, but does StoreFront handle both XenDesktop versions without any compatibility mode setting?
Viktor S.Jun 15, 2026StoreFront handles both 7.x and 5.6 side by side natively, but you still need to verify the store enumeration settings because the aggregation behavior changed between those controller types and you can get silent fallbacks that look like success until a user actually tries to launch.
Nina C.May 30, 2026I kept second-guessing B, but then I remembered StoreFront just needs the 5.6 controllers added to the store directly.
Jovan I.May 26, 2026C is right, but what protocol version are those 5.6 controllers actually using?
Viktor S.Jun 9, 2026The provisioning file is what actually tells the Receiver client where to connect and how to enumerate resources from the store. When you export it, you are capturing the full configuration of that store in a portable format that can then be modified to include resource references from the 5.6 environment and redistributed to clients. That is the mechanism that bridges the gap between what StoreFront knows about and what the end user sees, so without updating and re-exporting that file, clients are still only going to enumerate the XenDesktop 7 resources regardless of what you click on in the management console. Think about it from the client side, not the server side, because that is where the actual access decision gets resolved. The provisioning file is the handshake document, and skipping that step means you configured something on the back end that clients will never actually learn about.
Nina C.Jun 11, 2026Viktor, I think the answer is actually C, adding the XenApp 5.6 farm as a delivery controller resource feed in the StoreFront store configuration, because StoreFront handles resource aggregation server-side and Receiver just enumerates whatever the store exposes, so the provisioning file does not need to be re-exported just to surface resources from an additional farm.