When the Local Host Cache (LHC) is enabled, during a Site database outage _____________ will reference _____________ to broker new sessions. (Choose the correct option to complete the sentence.)
When the Local Host Cache (LHC) is enabled, during a Site database outage _____________ will reference _____________ to broker new sessions. (Choose the correct option to complete the sentence.)
When the Local Host Cache (LHC) is enabled and there is a Site database outage, the principal Delivery Controller will reference its local database to broker new sessions. The principal Delivery Controller becomes the High Availability service during the outage, taking over the role of brokering sessions from its local data sources, while other Delivery Controllers remain inactive for this role.
A is Correct https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/manage-deployment/local-host-cache.html
The reference states the principal broker, so the answer is correct A. https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/manage-deployment/local-host-cache.html
https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/manage-deployment/local-host-cache.html
Man, they blew this one. Of course it is A. Works the same way with Cloud deployment and CCs.
see Local Host Cache during an outage
I think it is wrong. It should be C. There are no dcc known as principal. just the broker is principal. therefore every dcc will relay on its principal broker to access to their local db.
part of the DCC is the principal broker - this is what communicates with the site database. In the event of an outage, one DCC per zone is elected to be the High Availability service and brokers requests from it's local database. All other DCC servers reject requests so answer A is correct
I agree, A is correct. During the outage, all VDAs re-register with the elected secondary broker. The non-elected secondary brokers in the zone will actively reject incoming connection and VDA registration requests.
When an outage begins: The principal broker can no longer communicate with the Site database, and stops listening for StoreFront and VDA information (marked X in the graphic). The principal broker then instructs the secondary broker (High Availability Service) to start listening for and processing connection requests (marked with a red dashed line in the graphic).
During an outage: The secondary brokers communicate with each other on a separate channel. They use an alphabetical list of FQDN names of the machines they’re running on to determine (elect) which secondary broker will be in charge of brokering operations in the zone if an outage occurs. During the outage, all VDAs re-register with the elected secondary broker. The non-elected secondary brokers in the zone will actively reject incoming connection and VDA registration requests. If an elected secondary broker fails during an outage, another secondary broker is elected to take over, and VDAs will re-register with the newly-elected secondary broker.