During a Site database outage with Local Host Cache enabled, which component references its local database to broker new sessions?

During a Site database outage with Local Host Cache enabled, which component references its local database to broker new sessions?

• A. the principal Delivery Controller
• B. the local XML file of the principal DC
• C. all Delivery Controllers
• D. all Delivery Controllers’ local XML files

Answer: (A)

Local Host Cache lets a Delivery Controller continue brokering new sessions by using a locally stored copy of the Site data when the Site database is unavailable. In a outage scenario, the principal Delivery Controller is the component that references its local copy to handle new session requests. It acts as the primary broker, using its cached Site data to evaluate and assign sessions while the database is down. Other Delivery Controllers maintain their own caches, but they don’t independently broker new sessions during the outage; they rely on the principal controller to manage session brokering. The local XML cache files are part of the mechanism, but the actual broker role during the outage centers on the principal Delivery Controller using its local data.

Local Host Cache lets a Delivery Controller continue brokering new sessions by using a locally stored copy of the Site data when the Site database is unavailable. In a outage scenario, the principal Delivery Controller is the component that references its local copy to handle new session requests. It acts as the primary broker, using its cached Site data to evaluate and assign sessions while the database is down. Other Delivery Controllers maintain their own caches, but they don’t independently broker new sessions during the outage; they rely on the principal controller to manage session brokering. The local XML cache files are part of the mechanism, but the actual broker role during the outage centers on the principal Delivery Controller using its local data.