Free VMware 3V0-12.26 Practice Exam with Questions & Answers | Set: 2

C, E, and F most directly satisfy the stated performance, isolation, lossless-fabric, and deterministic-failover requirements.

C provides the physical separation and bandwidth demanded by the scenario. VMware recommends high-bandwidth networking for demanding vSAN ESA workloads; 100 GbE is specifically recommended for performance-intensive ESA deployments , because high-performance NVMe devices can saturate lower-speed links. Dedicated RDMA-capable NIC ports also prevent TCP-based management, vMotion, and NSX traffic from competing with the RoCE storage path. ( VMware Blogs )

E addresses two explicit requirements. RoCE v2 requires correctly configured DCB/PFC to provide the lossless Ethernet behavior required by RDMA, and jumbo-frame configuration must remain consistent end-to-end through VMkernel adapters, NICs, and physical switching. Broadcom explicitly requires DCB and PFC configuration for vSAN RDMA. ( Support Portal )

F provides deterministic path selection and redundancy. vSAN RDMA does not support Load-Based Teaming , LACP, or IP-hash because an RDMA connection cannot dynamically spread across multiple RNICs. Broadcom supports explicit failover and recommends Active/Passive behavior for predictable vSAN networking. ( Support Portal )

D is therefore specifically inappropriate for RDMA. Although a leaf-spine topology in B is architecturally strong, it is not itself mandatory to satisfy these host/RDMA requirements; DCB/PFC and lossless behavior are already explicitly implemented by the selected fabric configuration.

Study Guide References/Topics: vSAN ESA Network Design; vSAN over RDMA/RoCE v2; DCB and PFC; Jumbo Frames; RDMA NIC Teaming Restrictions; Active/Standby Failover; High-Performance ESA Physical Networking.

the networking requirements

RAID-6 with FTT=2 is the appropriate vSAN storage policy for Site A because it satisfies both requirements: tolerance of two simultaneous host failures and maximum storage efficiency.

In vSAN, Failures to Tolerate (FTT)=2 means that a storage object remains accessible after two concurrent failures within the applicable fault-domain model. Both RAID-1 FTT=2 and RAID-6 FTT=2 can provide this level of protection, but their capacity overhead differs significantly.

RAID-1 FTT=2 uses three mirrored copies of the data, resulting in approximately 3× raw-capacity consumption for the protected object. By comparison, RAID-6 FTT=2 uses erasure coding with dual parity, providing two-failure tolerance with substantially better usable-capacity efficiency.

Site A contains 16 ESX hosts , providing more than enough hosts/fault domains to support RAID-6 FTT=2 placement requirements. This makes erasure coding the preferred choice where the design explicitly prioritizes storage efficiency while maintaining dual-failure protection.

A and D provide only FTT=1 and therefore cannot tolerate two simultaneous host failures. B provides the required resilience but consumes considerably more storage capacity than RAID-6.

Study Guide References/Topics: vSAN Storage Policy-Based Management; Failures to Tolerate; RAID-1 Mirroring; RAID-5/RAID-6 Erasure Coding; Capacity Efficiency; vSAN Cluster Sizing and Fault Domains.

The design must satisfy both monitoring capacity and single-node resiliency . C is correct because the solution already contains 10,000 virtual machines, and the requirement additionally includes monitoring guest operating systems and infrastructure components. A two-node Small configuration is unsuitable: the supplied sizing table limits a Small multi-node deployment to 12,000 objects and 2.8 million metrics , leaving insufficient practical headroom once guest OS and infrastructure monitoring objects are included. Three Medium nodes provide substantially greater object and metric capacity and support future operational growth.

B is required because the logical design explicitly specifies the VCF Operations High Availability Model . Enabling VCF Operations HA provides application-level resilience by maintaining replicated analytics data so the Operations service can continue after failure of one cluster node.

A is also required because the VCF Operations nodes should be separated across ESX hosts. A DRS anti-affinity rule prevents multiple Operations nodes from running on the same physical host, ensuring that a single ESX host failure cannot simultaneously remove multiple Operations nodes.

D lacks adequate capacity and resilience headroom. E would intentionally colocate nodes and create a common failure domain. F is unnecessary because VCF Operations provides its own supported application-level HA mechanism.

Study Guide References/Topics: VCF Operations Sizing Guide; High Availability Model; Analytics Cluster Design; VCF Operations Node Sizing; vSphere DRS Anti-Affinity; Single-Node Failure Resilience.

B is correct. The principal architectural advantage of a Distributed Transit Gateway (DTGW) is that it provides external VPC connectivity directly from the ESX hosts to the physical network , without requiring NSX Edge VMs or a Tier-0 gateway. In the distributed connectivity model, the Transit Gateway maps directly to an external VLAN shared by the participating ESX hosts . This reduces infrastructure footprint, removes an additional forwarding hop, and accelerates VPC onboarding. ( VMware Blogs )

For workloads requiring external connectivity, addresses can be allocated from the VPC ' s external IP block associated with that VLAN. The distributed gateway then forwards traffic between the VPC and physical network without forcing traffic through centralized Edge appliances. VCF 9.x specifically positions DTGW as the simpler model when customers need basic connectivity and do not require the complete centralized network-services stack. ( VMware Blogs )

A is incorrect because DTGW intentionally eliminates the NSX Edge cluster and therefore does not depend on static routing policies configured there. C is incorrect because centralized stateful services—particularly VPN—are characteristic of the centralized Transit Gateway model; VPN remains exclusive to centralized connectivity. D is incorrect because DTGW does not instantiate distributed Tier-0 service routers in an Active/Active Edge topology. Its northbound connectivity is directly to the physical VLAN.

Study Guide References/Topics: VCF VPC Networking; Distributed Transit Gateway; Distributed External Connectivity; Edgeless Networking; External VLAN Connectivity; VPC External IP Blocks; Centralized vs. Distributed Transit Gateway Design.

A and C match the VCF Edge pattern of centralized management with dedicated remote workload domains .

A is correct because the VCF management infrastructure can reside centrally at DC1 , providing lifecycle management and centralized operations for remote edge locations. Broadcom ' s documented VCF Edge architecture describes a central data center containing the management workload domain, with remote edge workload domains managed centrally through the VCF management plane. This avoids deploying a complete VCF instance at every branch and substantially reduces footprint and operational complexity. The stated minimum 10 Mbps bandwidth and maximum 100 ms latency also correspond directly to the documented connectivity requirements for centrally managed remote VCF edge sites. ( VMware Blogs )

C is correct because each branch must operate independently and have compute resources dedicated to that location. A dedicated workload domain for each branch creates an appropriate infrastructure and lifecycle boundary while retaining centralized VCF management. Broadcom explicitly identifies the pattern of deploying a dedicated workload domain for each edge site. ( VMware Blogs )

B and E would cause workload domains to span geographically separate branches, conflicting with the requirement for branch-specific dedicated resources and introducing WAN dependencies. D unnecessarily deploys a full VCF instance at every location, increasing resource consumption and management overhead.

Study Guide References/Topics: VCF Edge Design Patterns; Remote Workload Domains; Centralized Management; Edge Site Connectivity Requirements; Workload Domain Isolation; Remote Cluster Architecture; NFS Storage for Edge Sites.

B and E provide the required physical-network redundancy without introducing common single points of failure.

B is essential because NIC teaming should use uplinks located on different physical NIC cards . If both teamed ports reside on the same adapter, failure of that adapter, PCIe device, or associated hardware path can remove both uplinks simultaneously. Using separate physical adapters preserves connectivity when one NIC card fails. vSphere NIC teaming provides passive failover when one network adapter or network path becomes unavailable.

E is correct because each rack should contain redundant Top-of-Rack switches , with every ESX host connected to both switches. Loss or maintenance of one ToR therefore leaves the host connected through the surviving uplink and switch. Broadcom ' s operational guidance specifically validates redundant ToR designs by requiring each ESX host to have active uplinks to both ToR switches and confirming that traffic continues when either uplink is disabled.

C retains a NIC-card-level single point of failure. D creates a rack-level network failure domain. A requires cross-rack host cabling and is not the standard ToR redundancy pattern; rack resilience is achieved by distributing cluster hosts across racks while providing redundant ToRs within each rack.

Study Guide References/Topics: VCF Physical Network Design; NIC-Level Redundancy; NIC Teaming; Dual ToR Design; Rack Fault Domains; vSphere HA; Elimination of Single Points of Failure.

C is required because BGP uses the AS_PATH attribute for loop prevention . If a Tier-0 gateway uses an autonomous-system number already present in an incoming route ' s AS path, the advertisement can be rejected as a routing loop. Assigning a unique private ASN to each Tier-0 gateway prevents this condition and is the documented VCF physical-network design consideration for the VPC Full Services model.

D addresses the explicit constraint that BFD cannot be used . Without BFD, failure detection falls back to BGP keepalive/hold timers. Broadcom ' s VCF configuration guidance uses 4-second Keep Alive and 12-second Hold Down timers when BFD is disabled, allowing three missed keepalives before declaring the peer unavailable. Therefore, the wording “3 retries and 12 hold down” is expressing this timer behavior.

E is not automatically justified by a 40+ Gbps requirement: UPT requires compatible DPU/SmartNIC-backed Edge interfaces and is not a generic VPC Full Services prerequisite. F does not solve AS-path loop detection. A conflicts with the centralized Full Services forwarding model, while B is unnecessary for a single-tenant design.

Study Guide References/Topics: NSX VPC Full Services Model; Tier-0 Gateway Physical Design; BGP Autonomous Systems and Loop Prevention; BGP Failure Detection; BGP Keepalive/Hold Timers; NSX Edge Connectivity.

VMware Cloud Foundation maintains the management domain as the foundational administrative domain for the VCF instance. It hosts the infrastructure components required to operate and lifecycle-manage the environment. Broadcom documentation identifies management components such as vCenter, SDDC Manager, NSX Manager, VCF Operations, VCF Operations Fleet Management, VCF Identity Broker, logging, networking operations, and VCF Automation as management-domain components.

Therefore, when hardware consolidation is required, the supported architectural direction is to run appropriate user workloads within the management-domain infrastructure , rather than moving the VCF management plane into a workload domain. This corresponds to a consolidated deployment model while preserving the management domain ' s architectural role.

A is incorrect because workload domains depend on centralized VCF management and should not replace the management domain. B is incorrect because lifecycle services are integrated into the VCF management architecture; an independent external vCenter does not replace those services. D is incorrect because the management domain is not merely a bootstrap construct. Broadcom explicitly describes it as a foundational cluster for automated lifecycle management, with mandatory architectural characteristics.

The distinction is important: consolidation does not eliminate the management domain—it consolidates workloads into it when the deployment model and sizing permit.

Study Guide References/Topics: VCF Deployment Models; Management Domain Architecture; Workload Domain Design; VCF Operations Fleet Management; Infrastructure Consolidation; VCF Lifecycle Management.