B & D https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-6-long-term-service-release/xad-controller-intro.html

B&D are correct! https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/manage-deployment/vda-registration.html

A and B Two types of deployments in which the auto-update policy for VDA registration will be self-managed are: A. Deployments that use Citrix Provisioning with a write cache drive. In this deployment, the VDA machines use a local copy of the broker service to manage their own registration and re-registration. B. Deployments that use the Delivery Controllers or Controller SIDs policy setting. In this deployment, the Delivery Controller is not used to manage VDA registration, and instead, the VDA machines control their own registration and re-registration based on the Controller SIDs policy setting. C. is incorrect as Controller groups do not affect the auto-update policy for VDA registration. D. is incorrect as ListOfSIDs is a policy setting that specifies a list of Delivery Controller SIDs that the VDA machine should contact for registration. It does not affect the auto-update policy for VDA registration.

B & D A is wrong : Self-managed is Pvs WITHOUT a write cache drive C is wrong : Self-managed for deployments that USE Controller groups

B and D are correct (be careful where "NOT" is used in the possible answers) - The following types of deployments cannot use auto-update, and must self-manage: • Deployments that use Controller groups. • Deployments that use ListOfSIDs for security reasons. (Deployments that use ListOfSIDs to decrease the Active Directory load can use auto-update.) • Deployments that use Citrix Provisioning without a write cache drive. • Deployments that use the Controllers or Controller SIDs policy setting.

C & D are correct All of you are wrong - this is about auto-update method for DDC list The following types of deployments cannot use auto-update, and must self-manage: Deployments that use Controller groups - answer C Deployments that use ListOfSIDs for security reasons - answer D Deployments that use Citrix Provisioning without a write cache drive - then answer A is wrong Deployments that use the Controllers or Controller SIDs policy setting - answer B is wrong If you use auto-update method then you cannot use a GPO because it will override it a PVS will not save auto-update results to registry

Agree with Dan53. Answer A and B. In addition on the the comments of Dan53. Auto-update is supported when using MCS or Citrix Provisioning to provision machines, except for Citrix Provisioning server-side cache. Server-side cache is not a common scenario because there is no persistent storage for auto-update cache. Read -> Only "Cache on Server" is not supported with AutoUpdate Answer A is "A Write cache drive" That can be any write cache, like Cache in device RAM. https://support.citrix.com/article/CTX119469

D is wrong, https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/manage-deployment/vda-registration.html "If you need to manually configure the ListOfSIDs for security reasons (as distinct from reducing Active Directory load), you cannot use the auto-update feature." I would go with A and B.

I believe this is A and D - PVS can be used as long as it's not using server-side caching (answer states write cache drive, so it'd be local). Also, ListofSIDs shouldn't generally be changed unless there is a very specific reason - this was used in earlier versions of XA when you used to separate the XML and registration roles of a controller server

B and D is the correct answer !