1Y0-203 · Question #108
Which Layer contains the Citrix Director in a XenApp and XenDesktop Architecture model?
The correct answer is C. Control. See the full explanation below for the reasoning.
Question
Which Layer contains the Citrix Director in a XenApp and XenDesktop Architecture model?
Options
- AResource
- BUser
- CControl
- DAccess
How the community answered
(39 responses)- A5% (2)
- B3% (1)
- C82% (32)
- D10% (4)
Community Discussion
7
Luis F.May 12, 2026Citrix Director lives in the Control Layer because that is where all the monitoring and administration tools sit, giving admins the ability to manage sessions, troubleshoot user issues, and oversee the entire XenApp/XenDesktop environment from one place. So the answer is C, Control Layer, and if you remember that Director is basically your admin dashboard for the whole deployment, it makes total sense that it belongs there.
Mateus R.Jun 7, 2026Think of the Control layer as the manager's office where the foreman watches all the workers on a big wall of monitors, which is exactly what Director is, a real-time dashboard for watching and troubleshooting sessions, so it belongs in the Control layer (C) and not the Access layer, which trips people up because you open Director through a browser, but where you walk in the front door is not the same as what room you end up in.
Ingrid P.May 24, 2026Director lives in Control, not Access where you might expect admin tools.
Luis F.May 25, 2026Yeah that caught me off guard too when I was studying, but once I remember that Control is where you manage the actual Microsoft 365 service settings (compliance, security, admin center access), it clicked, though I'd add that some admin roles DO get configured in the Azure AD / Entra ID portal which kind of blurs that line a bit.
Wesley A.Jun 12, 2026The Control layer is where Director lives because that whole layer is about managing and monitoring the environment, not delivering resources or authenticating users, and once I stopped confusing it with the Access layer I started getting these architecture questions right every time. Quick question though, do you have a solid picture of what else sits in the Control layer alongside Director, like the Delivery Controllers and the SQL database, because understanding the full picture of what that layer owns is what keeps you from second-guessing yourself on the related drag-and-drop items?
Luis F.Jun 13, 2026Yeah that full picture really locks it in, and the piece I kept forgetting to include alongside Director, the Delivery Controllers, and the SQL database was Studio and the License Server, because once you realize the Control layer basically owns everything that makes decisions and keeps records about the site, those two slot in perfectly and you stop second-guessing the drag-and-drop items that try to trick you into putting them in the Access layer.
Prof. SaraMay 3, 2026The answer is C, Control Layer, and this one trips up a lot of candidates because Director looks like an "access" tool since admins open it in a browser. The Access Layer in this architecture is specifically about brokering the end-user path to resources, think StoreFront and NetScaler Gateway, not about administrator consoles. Director lives in the Control Layer alongside Delivery Controller, Studio, and the License Server, because its job is to monitor and manage the delivery infrastructure itself, not to serve as an entry point for user sessions. A quick mnemonic that has helped my students lock this in: think of the Control Layer as the "cockpit," and Director is literally the instrument panel you use to see what the plane is doing, so it belongs with the controls, not the boarding gate.