Question 5
A Citrix Virtual Delivery Agent (VDA) needs to locate the Delivery Controller to register with it.
In which order of precedence, from greatest to least, will VDA locate the Delivery Controller?
Personality.ini file, ListOf DDC's key in the registry, Policy settings from AD, Auto update of controllers
Policy Settings from AD, ListOf DDC's key in the registry, Auto update of controllers, Personality.ini file
Auto update of controllers, Policy settings from AD, ListOf DDC's key in the registry, Personality.ini file
Personality.ini file, Auto update of controllers, ListOf DDC's key in the registry, Policy Settings from AD
Correct answer: B
Explanation:
Information in the ListOfDDCs and ListOfSIDs can come from several places in a deployment. The VDA checks the following locations, in order, stopping at the first place it finds the lists:A persistent storage location maintained for the auto-update feature. This location contains Controller information when auto-update is enabled and after the VDA successfully registers for the first time after installation. (This storage also holds machine policy information, which ensures that policy settings are retained across restarts.) For its initial registration after installation, or when auto-update is disabled, the VDA checks the following locations. Policy settings (Controllers, Controller SIDs). The Controller information under the Virtual Desktop Agent key in the registry. The VDA installer initially populates these values, based on Controller information you specify when installing the VDA. OU-based Controller discovery. This is a legacy method maintained for backward compatibility. The Personality.ini file created by Machine Creation Services. Reference: https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-8/manage-deployment/delivery-controllers.html
Information in the ListOfDDCs and ListOfSIDs can come from several places in a deployment. The VDA checks the following locations, in order, stopping at the first place it finds the lists:
A persistent storage location maintained for the auto-update feature. This location contains Controller information when auto-update is enabled and after the VDA successfully registers for the first time after installation. (This storage also holds machine policy information, which ensures that policy settings are retained across restarts.) For its initial registration after installation, or when auto-update is disabled, the VDA checks the following locations.
Policy settings (Controllers, Controller SIDs).
The Controller information under the Virtual Desktop Agent key in the registry. The VDA installer initially populates these values, based on Controller information you specify when installing the VDA.
OU-based Controller discovery. This is a legacy method maintained for backward compatibility.
The Personality.ini file created by Machine Creation Services.
Reference: https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-8/manage-deployment/delivery-controllers.html