Free 2V0-13.24: VMware Cloud Foundation 5.2 Architect Exam Questions and Answers

Correct answer: B, C, E

Explanation

In VMware Cloud Foundation (VCF) 5.2, Cloud Automation (e.g., Aria Automation) and Operations (e.g., Aria Operations) products rely on identity management for authentication. The customer's requirements—corporate directory authentication, Active/Standby across two sites, disaster recovery (DR), network zoning, slow firewall processes, and a 3-month deployment timeline—shape the design decisions. The architect must ensure authentication works efficiently across sites while meeting the timeline and DR needs. Let's evaluate: Key Constraints and Context: Authentication: All users/administrators use the corporate directory (e.g., Active Directory in the corporate zone). Deployment: Active/Standby across two sites, with management apps in a separate tooling zone behind firewalls. DR: Management apps must recover to the standby site. Firewall Delays: 8-week minimum per rule, but deployment must occur within 12 weeks (3 months). Identity Broker: In VCF, VMware Workspace ONE Access (or similar) acts as an identity broker, bridging VCF components with external directories (e.g., AD via LDAP/S). Evaluation of Options: Option A: The Cloud Automation and Operations products will be reconfigured to integrate with the Identity Broker solution instance at the standby site in case of a Disaster Recovery incident This implies a single Identity Broker at the primary site, with reconfiguration to a standby instance post-DR. Reconfiguring products (e.g., updating SSO endpoints) during DR adds complexity and downtime, contradicting the Active/Standby goal of seamless failover. It's feasible but not optimal given the need for continuous operation and the 3-month timeline. Option B: The Identity Broker solution will be deployed at both the primary and standby site This is correct. Deploying Workspace ONE Access (or equivalent) at both sites supports Active/Standby by ensuring authentication availability at the primary site and immediate usability at the standby site post-DR. It aligns with VCF's multi-site HA capabilities and avoids reconfiguration delays, addressing the DR requirement efficiently within the timeline. Option C: The Identity Broker solution will be connected with the corporate directory service for user authentication This is correct. The requirement states all users/administrators authenticate via the corporate directory (in the corporate zone). An Identity Broker (e.g., Workspace ONE Access) connects to AD via LDAP/S, acting as a proxy between the management tooling zone and corporate zone. This satisfies the authentication need and simplifies firewall rules (one broker-to-AD connection vs. multiple app connections), critical given the 8-week delay. Option D: The Identity Broker solution will be deployed at the primary site and failed over to the standby site in case of a disaster This suggests a single Identity Broker with DR failover. While possible (e.g., via vSphere Replication), it risks authentication downtime during failover, conflicting with Active/Standby continuity. The 8-week firewall rule delay for the standby site's broker connection post-DR also jeopardizes the 3-month timeline and DR readiness, making this less viable than dual- site deployment (B). Option E: The Cloud Automation and Operations products will be integrated with a single instance of an Identity Broker solution at the primary site This is correct. Integrating Aria products with one Identity Broker instance at the primary site during initial deployment simplifies setup and meets the 3-month timeline. It leverages the broker deployed at the primary site (part of B) for authentication, minimizing firewall rules (one broker vs. multiple apps). Pairing this with a standby instance (B) ensures DR readiness without immediate complexity. Option F: The Cloud Automation and Operations products will be integrated directly with the corporate directory service This is incorrect. Direct integration requires each product (e.g., Aria Automation, Operations) to connect to AD across the firewall, necessitating multiple rule requests. With an 8-week minimum per rule and several products, this exceeds the 3-month timeline. It also complicates DR, as each app would need re-pointing to a standby AD, violating efficiency and zoning policies. Conclusion: The three design decisions are: B: Identity Broker at both sites ensures Active/Standby and DR readiness. C: Connecting the broker to the corporate directory fulfills the authentication requirement and simplifies firewall rules. E: Integrating products with a primary-site broker meets the 3-month deployment goal while leveraging B and C for DR.This trio balances timeline, security, and DR needs in VCF 5.2. References: VMware Cloud Foundation 5.2 Architecture and Deployment Guide (Section: Identity and Access Management) VMware Aria Automation 8.10 Documentation (integrated in VCF 5.2): Authentication Design VMware Cloud Foundation 5.2 Planning and Preparation Guide (Section: Multi-Site and DR Considerations)