VMware 2V0-13.24 Practice Exams
Last updated on Nov 16,2026- Exam Code: 2V0-13.24
- Exam Name: VMware Cloud Foundation 5.2 Architect
- Certification Provider: VMware
- Latest update: Nov 16,2026
A customer defined a requirement for the newly deployed SDDC infrastructure which will host one of the applications responsible for video streaming. Application will run as part of a VI Workload Domain with dedicated NSX instance and virtual machines. Required network throughput was defined as 250 Gb/s. Additionally, the application should provide the lowest possible latency.
Which design decision should be recommended by an architect for the NSX Edge deployment?
- A . Deploy 2 NSX Edges using NSX console and add to Edge cluster created in SDDC Manager.
- B . Deploy 4 extra large edges using vCenter Server console.
- C . Deploy NSX bare-metal Edges and create Edge Cluster using NSX console.
- D . Deploy 2 large NSX Edges using SDDC Manager.
C
Explanation:
For 250 Gb/s throughput and low latency in a VI Workload Domain, NSX Edges must handle high-performance traffic.
Option C, "Deploy NSX bare-metal Edges and create Edge Cluster using NSX console," is optimal: bare-metal Edges in NSX-T 3.2 (VCF 5.2) support up to 100 Gb/s per node, and
clustering multiple nodes achieves 250 Gb/s with minimal latency due to direct hardware access, ideal for video streaming.
Option A (2 VM Edges) and D (2 large VM Edges) cap at ~20 Gb/s per node, insufficient for 250 Gb/s.
Option B (4 extra-large VM Edges) improves throughput but increases latency via virtualization overhead. Bare-metal is the verified high-performance choice.
Reference: NSX-T 3.2 Reference Design Guide, Edge Node Performance; VMware Cloud Foundation 5.2 Networking Guide, NSX Edge Deployment Options.
Which standard does VMware vSAN use for disk group configuration?
- A . SCSI
- B . NFS
- C . FAT32
- D . RAID
D
Explanation:
vSAN employs RAID for configuring disk groups.
A company plans to expand its existing VMware Cloud Foundation (VCF) environment for a new application. The current VCF environment includes a Management Domain and two separate VI Workload Domains with different hardware profiles.
The new application has the following requirements:
The application will use significantly more memory than current workloads.
The application will have a limited number of licenses to run on hosts.
Additional VCF and hardware costs have been approved for the application.
The application will contain confidential customer information that requires isolation from other workloads.
What design recommendation should the architect document?
- A . Implement a new Workload Domain with hardware supporting the memory requirements of the new application.
- B . Deploy a new consolidated VCF instance and deploy the new application into it.
- C . Purchase sufficient matching hardware to meet the new application’s memory requirements and expand an existing cluster to accommodate the new application. Use host affinity rules to manage the new licensing.
- D . Order enough identical hardware for the Management Domain to meet the new application requirements and design a new Workload Domain for the application.
A
Explanation:
In VMware Cloud Foundation (VCF) 5.2, expanding an existing environment for a new application involves balancing resource needs, licensing, cost, and security. The requirements―high memory, limited licenses, approved budget, and isolation―guide the design.
Let’s evaluate:
Option A: Implement a new Workload Domain with hardware supporting the memory requirements of the new application
This is correct. A new VI Workload Domain (minimum 3-4 hosts, depending on vSAN HA) can be tailored to the application’s high memory needs with new hardware. Isolation is achieved by dedicating the domain to the application, separating it from existing workloads (e.g., via NSX segmentation). Limited licenses can be managed by sizing the domain to match the license count (e.g., 4 hosts if licensed for 4), and the approved budget supports this. This aligns with VCF’s Standard architecture for workload separation and scalability.
Option B: Deploy a new consolidated VCF instance and deploy the new application into it
This is incorrect. A consolidated VCF instance runs management and workloads on a single cluster (4-8 hosts), mixing the new application with management components. This violates the isolation requirement for confidential data, as management and application workloads share infrastructure. It also overcomplicates licensing and memory allocation, and a new instance exceeds the intent of “expanding” the existing environment.
Option C: Purchase sufficient matching hardware to meet the new application’s memory requirements and expand an existing cluster to accommodate the new application. Use host affinity rules to manage the new licensing
This is incorrect. Expanding an existing VI Workload Domain cluster with matching hardware (to maintain vSAN compatibility) could meet memory needs, and DRS affinity rules could pin the application to licensed hosts. However, mixing the new application with existing workloads in the same domain compromises isolation for confidential data. NSX segmentation helps, but a shared cluster increases risk, making this less secure than a dedicated domain.
Option D: Order enough identical hardware for the Management Domain to meet the new application requirements and design a new Workload Domain for the application
This is incorrect. Upgrading the Management Domain (minimum 4 hosts) with high-memory hardware for the application is illogical―management domains host SDDC Manager, vCenter, etc., not user workloads. A new Workload Domain is feasible, but tying it to Management Domain hardware mismatches the VCF architecture (Management and VI domains have distinct roles). This misinterprets the requirement and wastes resources.
Conclusion:
The architect should recommend A: Implement a new Workload Domain with hardware supporting the memory requirements of the new application. This meets all requirements―memory, licensing (via domain sizing), budget (approved costs), and isolation (dedicated domain)―within VCF 5.2’s Standard architecture.
Reference: VMware Cloud Foundation 5.2 Architecture and Deployment Guide (Section: Workload Domain Design)
VMware Cloud Foundation 5.2 Planning and Preparation Guide (Section: Isolation and Sizing)
Which Broadcom products are essential for maintaining high-speed storage connectivity in VMware Cloud Foundation?
- A . Broadcom Fibre Channel HBAs
- B . Broadcom NVMe SSDs
- C . Broadcom Ethernet adapters
- D . Broadcom RAID controllers
A
Explanation:
Broadcom Fibre Channel HBAs are essential for high-speed storage connectivity.
What are the benefits of Broadcom 25GbE Ethernet Adapters in VMware environments?
- A . Improved Throughput
- B . Enhanced Security
- C . Reduced Latency
- D . Increased Storage Capacity
A, C
Explanation:
Broadcom 25GbE Ethernet Adapters improve throughput and reduce latency in VMware environments.
Which VMware tools are used for managing multi-cloud environments in VMware Cloud Foundation?
- A . VMware NSX
- B . VMware HCX
- C . VMware vRealize Operations
- D . VMware vSphere
B, D
Explanation:
VMware HCX and vSphere are essential for managing multi-cloud environments in VMware Cloud Foundation.
How does Broadcom hardware improve VMware vRealize Automation (vRA) performance?
- A . Scalability for automation workflows
- B . Data protection
- C . High-speed storage
- D . Optimized network traffic
A, B, C, D
Explanation:
Broadcom hardware enhances vRealize Automation performance by improving storage speed, network traffic optimization, scalability, and data protection.
Which Broadcom products are used to ensure high availability in VMware Cloud Foundation environments?
- A . Broadcom Ethernet adapters
- B . Broadcom Fibre Channel HBAs
- C . Broadcom RAID controllers
- D . Broadcom NVMe SSDs
B, C
Explanation:
Broadcom RAID controllers and Fibre Channel HBAs enhance high availability in VMware Cloud Foundation.
Which factors should be considered when designing a VMware vSphere network using Broadcom solutions for maximum scalability?
- A . vSphere Distributed Switch (VDS)
- B . Broadcom RAID Controller
- C . 25GbE Ethernet Adapter
- D . vSAN
A, C
Explanation:
The 25GbE Ethernet Adapter and vSphere Distributed Switch (VDS) are crucial for network scalability in VMware vSphere.
As part of a VMware Cloud Foundation (VCF) design, an architect is responsible for planning for the migration of existing workloads using HCX to a new VCF environment.
Which two prerequisites would the architect require to complete the objective? (Choose two.)
- A . Extended IP spaces for all moving workloads.
- B . DRS enabled within the VCF instance.
- C . Service accounts for the applicable appliances.
- D . NSX Federation implemented between the VCF instances.
- E . Active Directory configured as an authentication source.
C, E
Explanation:
VMware HCX (Hybrid Cloud Extension) is a key workload migration tool in VMware Cloud Foundation (VCF) 5.2, enabling seamless movement of VMs between on-premises environments and VCF instances (or between VCF instances). To plan an HCX-based migration, the architect must ensure prerequisites are met for deployment, connectivity, and operation. Let’s evaluate each option:
Option A: Extended IP spaces for all moving workloads
This is incorrect. HCX supports migrations with or without extending IP spaces. Features like HCX vMotion and Bulk Migration allow VMs to retain their IP addresses (Layer 2 extension via Network Extension), while HCX Mobility Optimized Networking (MON) can adapt IPs if needed. Extended IP space is a design choice, not a prerequisite, making this option unnecessary for completing the objective.
Option B: DRS enabled within the VCF instance
This is incorrect. VMware Distributed Resource Scheduler (DRS) optimizes VM placement and load balancing within a cluster but is not required for HCX migrations. HCX operates independently of DRS, handling VM mobility across environments (e.g., from a source vSphere to a VCF destination). While DRS might enhance resource management post-migration, it’s not a prerequisite for HCX functionality.
Option C: Service accounts for the applicable appliances
This is correct. HCX requires service accounts with appropriate permissions to interact with source and destination environments (e.g., vCenter Server, NSX). In VCF 5.2, HCX appliances (e.g., HCX
Manager, Interconnect, WAN Optimizer) need credentials to authenticate and perform operations like VM discovery, migration, and network extension. The architect must ensure these accounts are configured with sufficient privileges (e.g., read/write access in vCenter), making this a critical prerequisite.
Option D: NSX Federation implemented between the VCF instances
This is incorrect. NSX Federation is a multi-site networking construct for unified policy management across NSX deployments, but it’s not required for HCX migrations. HCX leverages its own Network Extension service to stretch Layer 2 networks between sites, independent of NSX Federation. While NSX is part of VCF, Federation is an advanced feature unrelated to HCX’s core migration capabilities.
Option E: Active Directory configured as an authentication source
This is correct. In VCF 5.2, HCX integrates with the VCF identity management framework, which typically uses Active Directory (AD) via vSphere SSO for authentication. Configuring AD as an authentication source ensures that HCX administrators can log in using centralized credentials, aligning with VCF’s security model. This is a prerequisite for managing HCX appliances and executing migrations securely.
Conclusion:
The two prerequisites required for HCX migration in VCF 5.2 are service accounts for the applicable appliances (Option C) to enable HCX operations and Active Directory configured as an authentication source (Option E) for secure access management. These align with HCX deployment and integration requirements in the VCF ecosystem.
Reference: VMware Cloud Foundation 5.2 Architecture and Deployment Guide (Section: HCX Integration)
VMware HCX User Guide (VCF 5.2 compatible): Prerequisites and Configuration
VMware Cloud Foundation 5.2 Planning and Preparation Guide (Section: Identity and Access Management)