What are two Cloud Pod Architecture feature limitations? (Choose two.)

Question

Options

• ACloud Pod Architecture does not support Active Directory two-way trusts between domains.
• BCloud Pod Architecture is not supported with Unified Access Gateway appliances.
• CKiosk mode clients are not supported unless a workaround has been implemented.
• DCloud Pod Architecture cannot span multiple sites and data centers simultaneously.
• EThe Cloud Pod Architecture feature is not supported in an IPv6 environment.

• A
  77% (33)
• B
  2% (1)
• D
  14% (6)
• E
  7% (3)

Explanation

Cloud Pod Architecture is a feature that allows administrators to link multiple Horizon pods across sites and data centers to form a single logical entity called a pod federation. Cloud Pod Architecture enables global entitlements, which allow users to access desktops and applications from any pod in the pod federation. Cloud Pod Architecture also provides load balancing, high availability, and disaster recovery capabilities for Horizon deployments. However, Cloud Pod Architecture has some feature limitations that administrators should be aware of. Two of these limitations are: Cloud Pod Architecture does not support Active Directory two-way trusts between domains: This means that the domains that contain the Horizon pods in the pod federation must have a one-way trust relationship, where the domain that contains the Cloud Pod Architecture home site trusts all the other domains, but not vice versa. A two-way trust relationship, where each domain trusts and is trusted by all the other domains, is not supported by Cloud Pod Architecture and can cause authentication and entitlement issues. Kiosk mode clients are not supported unless a workaround has been implemented: This means that users who log in to Horizon Client in kiosk mode, which is a mode that allows users to access a single desktop or application without entering credentials, cannot access desktops or applications from a Cloud Pod Architecture implementation. Kiosk mode clients are not compatible with global entitlements and load balancing features of Cloud Pod Architecture. However, there is a workaround that involves creating a dedicated user account and a dedicated desktop pool for each kiosk mode client and using a script to launch Horizon Client with the appropriate parameters. For instructions, see VMware Knowledge Base (KB) article 21488881.

No community discussion yet for this question.