1Y0-312 Advanced Site Architecture Practice Question
A Citrix architect is designing a multi-zone Citrix Virtual Apps and Desktops 7 site. The site database is hosted on a SQL Server in the primary zone. The architect needs to ensure that if the SQL Server becomes unavailable, users can still launch applications. The architect has already deployed Delivery Controllers in each zone. What should the architect do next?
⚠ Common exam trap
The trap here is assuming that SQL Server Always On alone solves the outage, but without LHC, Delivery Controllers cannot broker if the database is unreachable.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable Local Host Cache on all Delivery Controllers.
Local Host Cache is the Citrix feature that enables Delivery Controllers to broker sessions when the site database is unreachable. Enabling LHC on all Delivery Controllers ensures that users can continue to launch applications during a database outage. While database high availability is also important, LHC is the specific Citrix mechanism that provides brokering continuity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure SQL Server Always On availability groups.
Why it's wrong here
SQL Server Always On provides database high availability, but it does not eliminate the need for Local Host Cache. If the database becomes unavailable due to a failure that Always On cannot handle quickly, Delivery Controllers still need LHC to broker sessions. Moreover, Always On is a database-level solution, not a Citrix-specific one. The question asks what the architect should do next in Citrix, so LHC is the priority.
- ✓
Enable Local Host Cache on all Delivery Controllers.
Why this is correct
Local Host Cache allows Delivery Controllers to continue brokering sessions when the site database is unavailable. By enabling LHC on all Delivery Controllers, the architect ensures that session launches can continue even if the SQL Server fails. This is the built-in mechanism for database outage resilience in Citrix Virtual Apps and Desktops.
- ✗
Deploy additional StoreFront servers in each zone.
Why it's wrong here
StoreFront servers handle authentication and resource enumeration, but they rely on Delivery Controllers for brokering. If the database is unavailable and LHC is not enabled, Delivery Controllers cannot broker sessions regardless of how many StoreFront servers exist. Therefore, deploying more StoreFront servers does not address the database outage requirement.
- ✗
Implement zone preference to direct users to the primary zone.
Why it's wrong here
Zone preference directs users to a preferred zone for brokering, but it does not provide resilience if the database is down. In fact, directing users to the primary zone would be counterproductive if the database there is unavailable. Zone preference is about routing, not high availability.
About these practice questions
Courseiva writes every 1Y0-312 question from scratch — 186 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Citrix exam blueprint
This 1Y0-312 practice question is part of Courseiva's free Citrix certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 1Y0-312 exam.