Having configured two standalone Horizon pods, what steps should be taken to join them in...

To join two standalone Horizon pods in a Cloud Pod Architecture (CPA) deployment, the administrator needs to perform the following steps:

On one pod, initialize the CPA. This step creates a pod federation and enables global data replication among all pods in the federation. The pod that initializes the CPA becomes the first pod in the federation67.

On the second pod, join the CPA. This step adds an existing standalone pod to an existing pod federation. The pod that joins the CPA inherits the global data from the federation89.

On one pod, create Global Entitlements, and add local pools from each pod. This step allows users to access desktops or applications from any pod in the federation based on their entitlements and load-balancing policies .

The other options are not correct or complete because:

Initializing the CPA on both pods is not necessary or possible. Only one pod can initialize the CPA and create a pod federation. The other pods must join an existing pod federation68.

Syncing the CPA on the second pod is not a valid step. Syncing is a process that occurs automatically among all pods in a pod federation to ensure data consistency and availability.

Creating Cloud Entitlements is not a valid term. The correct term is Global Entitlements, which are used in CPA to entitle users to desktops or applications across multiple pods.

References := 6: VMware Horizon 8 Documentation: Initialize Cloud Pod Architecture 7: VMware Horizon 8 Documentation: Understanding Cloud Pod Architecture in Horizon 8 8: VMware Horizon 8 Documentation: Join a Pod to an Existing Pod Federation 9: VMware Horizon 8 Documentation: Understanding Cloud Pod Architecture in Horizon 8 : VMware Horizon 8 Documentation: Create a Global Entitlement : VMware Horizon 8 Documentation: Understanding Global Entitlements in Cloud Pod Architecture : VMware Horizon 8 Documentation: Understanding Cloud Pod Architecture in Horizon 8