Pearson 3V0-12.26 New Attempt

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.

Recoverability requires independent, restorable recovery points plus controlled lifecycle procedures that can recover VCF after component, site, or upgrade failure. A directly addresses this requirement because VCF Operations requires VM-level/image-based protection for disaster recovery, while VCF Operations for Networks supports full backup and restoration of its platform and collector nodes. Keeping these backups offsite prevents a regional outage from destroying both production and recovery copies. Broadcom specifically documents image-based protection for VCF Operations and backup/restore procedures for Operations for Networks.

B addresses the post-upgrade-failure scenario. VCF lifecycle prechecks verify component health, backup readiness, compatibility, and the supported upgrade path before changes occur; postchecks validate component state after lifecycle operations. Broadcom explicitly requires valid, recent backups for recoverability before infrastructure updates and recommends confirming supported upgrade paths and completing upgrade prechecks.

D is fundamental to instance-level disaster recovery. VCF documentation states that backup storage should reside in a different fault domain from the protected environment. External, replicated storage therefore protects SDDC Manager, NSX, vCenter, and automation state against management-domain or regional loss. ( Broadcom Developer )

C is not a supported NSX recovery strategy; appliance clones can introduce state and identity consistency problems. E unnecessarily fragments recovery data and does not inherently provide regional resilience. F provides availability against VM/host failure, but HA is not a backup or disaster-recovery mechanism and cannot recover destroyed configuration state or an entire VCF instance.

Study Guide References/Topics: VCF AMPRS Considerations – Designing for Recoverability; Management Domain – Platform-Based Protection Mechanisms; VCF Upgrade Considerations; Day 2 Operations; Backup and Restore of VMware Cloud Foundation. ( globalknowledge.com )