3V0-12.26 Advanced VMware Cloud Foundation 9 Architect Questions and Answers

NSX Federation uses a Global Manager to centrally define and synchronize global networking and security objects across the Local Managers at participating sites, making F fundamental to the architecture. Broadcom confirms that configuration is performed through the active Global Manager and synchronized to the applicable locations. ( Broadcom TechDocs )

A is required for stretched North/South routing: a Global Tier-0 can span locations, with site-local service routers and BGP connectivity to the physical network. Federation also uses RTEPs on Edge Nodes for cross-site Geneve transport.

B reflects the important 150-ms cross-location Edge-to-Edge RTT limit for stretched networking. Newer NSX releases permit higher latency between some manager components, but the inter-site Edge data path remains subject to the tighter latency consideration.

C is correct because NSX overlay networking requires additional MTU for Geneve encapsulation. Broadcom specifies 1600 bytes as the minimum and 1700 bytes as the recommended value , making 1700 the appropriate design target.

E separates site-local routing from stretched workloads: local Tier-1 gateways serve site-specific segments, while a Global/spanning Tier-1 provides cross-site connectivity. Broadcom confirms that local Tier-1 gateways can connect to a Global Tier-0 in Federation.

D is too absolute, particularly with distributed VPC connectivity models. G is incorrect because Edge TEP addressing is normally based on NSX IP pools/static allocation rather than requiring DHCP. H provides insufficient MTU for Geneve overlays.

Study Guide References/Topics: NSX Federation Architecture; Global and Local Managers; Stretched Tier-0/Tier-1 Gateways; RTEPs; Multi-Site BGP Routing; Geneve MTU; Local versus Global Networking Objects; Multi-Site Availability.

vSAN Express Storage Architecture (ESA) was specifically designed for modern, high-performance NVMe-based storage devices . Therefore, selecting ESA imposes a fundamental hardware-design implication: the storage devices contributing capacity to the ESA storage pool must meet the supported NVMe device requirements. VMware describes ESA as being optimized for high-performance NVMe storage and replacing the traditional two-tier cache/capacity architecture with a single-tier storage pool . ( VMware )

D is therefore correct. ESA eliminates dedicated cache devices; every claimed storage device participates in both performance and capacity. This architecture allows ESA to achieve highly efficient RAID-5/RAID-6 erasure coding while maintaining performance much closer to RAID-1 than was traditionally possible. ( VMware Blogs )

A is incorrect because ESA does not impose a universal mandatory 100-Gbps physical-network requirement. Network requirements depend on cluster sizing and workload characteristics.

B is incorrect and is particularly important architecturally: NVMe devices behind Tri-Mode controllers can be an unsupported vSAN configuration . Broadcom states that supported NVMe devices should be directly connected through the appropriate PCIe topology rather than relying on a Tri-Mode controller configuration.

C is incorrect because ESA explicitly removes the disk-group construct . ESA creates a host-level storage pool instead of organizing cache and capacity devices into disk groups. ( VMware Blogs )

Study Guide References/Topics: vSAN Express Storage Architecture; ESA Storage Pools; ESA Hardware Requirements; RAID-5/RAID-6 Erasure Coding; vSAN ReadyNode Design; VCF Workload Domain Storage Design.

The correct design is the Continuous Availability VCF Operations Model because the requirement is to survive the loss of an entire availability zone/fault domain without service interruption .

Broadcom states that VCF Operations Continuous Availability (CA) stretches the analytics cluster across two fault domains and allows the deployment to tolerate the complete failure of one fault domain while continuing to operate without cluster downtime. CA requires an equal number of analytics nodes in each fault domain plus a witness node located in a third failure domain to prevent split-brain conditions.

The use of an external load balancer also aligns with a multi-node VCF Operations design by providing a common service endpoint and directing UI/API traffic to available cluster members. VCF Operations 9.x does not provide a built-in VIP for multi-node deployments, so an external HTTP load balancer is required when a resilient common endpoint is used.

B is insufficient because standard High Availability protects against one node failure , not loss of an entire fault domain. C is a connectivity/federation concept rather than an availability topology. D is the smallest footprint but provides no protection against an AZ failure.

Therefore, the simplest topology that actually satisfies zero interruption during a single AZ failure is Continuous Availability .

Study Guide References/Topics: VCF Operations Deployment Models; Continuous Availability; Fault Domains; Witness Node; External Load Balancing; High Availability versus Continuous Availability.

A is the technical requirement because it defines a specific technical capability that the VCF architecture must provide: application resiliency across at least two separate physical locations . This requirement directly affects infrastructure topology, availability zones, network connectivity, storage replication, workload placement, and potentially multi-site or stretched-cluster design decisions.

C is primarily a business/service-level requirement . The 99% SLO expresses the level of service the business expects from the platform. The architect subsequently translates that availability objective into technical mechanisms such as redundancy, vSphere HA, fault-domain placement, and multi-site architecture.

B establishes a regulatory/compliance obligation . DORA and SOX may generate multiple technical requirements, but merely stating that the organization is subject to those regulations does not itself prescribe a technical capability.

D is a constraint because the existing procurement agreement restricts the design by requiring specified server hardware to be used.

The VMware Cloud Foundation Architect exam explicitly requires architects to distinguish business from technical requirements and separately identify requirements, constraints, assumptions, dependencies, and risks when constructing a VCF design. ( Broadcom Docs )

Study Guide References/Topics: Conceptual Design; Business vs. Technical Requirements; Requirements, Constraints and Compliance; Availability and Resiliency; Multi-Site Architecture; Design Traceability.

B, C, and D represent the intended physical-design decisions for this requirement set.

B aligns with VCF network design because 10 GbE is an accepted baseline for ESX hosts , while moving to 25 GbE provides additional headroom for vSAN, NSX overlay, management, and future workload-domain traffic. Broadcom identifies 10-Gbps-or-faster NICs as a minimum hardware consideration for VCF hosts.

C aligns with the customer ' s preference for an all-flash architecture and future scalability. vSAN ESA uses a single-tier, high-performance storage model and is the appropriate architecture when designing new VCF infrastructure around modern flash/NVMe storage. The exact raw-capacity figure should always be validated against the selected storage policy, RAID scheme, FTT, operational reserve, and growth assumptions, but ESA is clearly preferable to the hybrid OSA design in F .

D provides sufficient compute and memory headroom for the management stack and anticipated growth. Management-domain sizing must consider not only current vCenter, NSX, SDDC Manager, and VCF services but also future lifecycle and operational services.

A is incorrect because VCF guidance recommends uniform host configurations within the management-domain cluster to ensure predictable performance and rebuild behavior. E is incorrect because a standard single-site vSAN-backed VCF Management Domain requires a minimum of four ESX hosts , not three.

Study Guide References/Topics: VCF Management Domain Physical Design; Host Sizing; vSAN ESA Design; Network Architecture and MTU; Management Domain Scalability; Uniform Host Configuration; Capacity and Growth Planning.

B is correct. A single VCF instance minimizes management-plane footprint while still allowing separate workload domains to provide dedicated hardware pools for each tenant or department. In VCF, each VCF instance contains one management domain , while additional workload domains can be created for different workload types and hardware requirements. Broadcom specifically describes workload domains as infrastructure boundaries that can contain host clusters configured to meet the requirements of a particular workload set. ( VMware Blogs )

This design maps cleanly to the requirements. The Analytics department can receive a workload domain built from GPU-capable hosts, allowing specialized accelerators to be dedicated to analytics and AI workloads. VMware guidance also uses separate VCF workload domains for GPU-enabled infrastructure because workload domains provide their own infrastructure and policies for these specialized workloads. ( VMware Blogs )

The Finance department can receive another workload domain backed by physically separate ESX hosts. That satisfies the requirement that financial workloads not share hardware with other departments.

Creating a separate VCF instance for every tenant, as proposed in C and D , would unnecessarily multiply management domains and management components, directly conflicting with the minimum-footprint requirement. A is architecturally invalid because a VCF instance has a single management domain, not one management domain per tenant, and a shared workload domain would not provide the required physical isolation.

Study Guide References/Topics: VCF Automation Tenant Design; VCF Instance Architecture; Management Domain; Workload Domains; Tenant Isolation; Dedicated Hardware Pools; GPU Workload 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.

A and D are requirements because they describe capabilities or outcomes that the completed architecture must deliver . VMware ' s architectural methodology distinguishes requirements from constraints, assumptions, and risks, and the current VCF Architect exam specifically expects architects to identify and document these categories independently. ( Broadcom Docs )

A defines an availability requirement: the architecture must provide a resilient multi-site topology . This states the desired behavior of the solution rather than prescribing a particular implementation technology.

D is also a requirement because it establishes a specific, measurable scalability target—20% growth over three years . It directly influences capacity planning and the logical and physical architecture.

B represents a risk/finding . An existing network single point of failure could adversely affect availability and should be documented and mitigated.

C is a constraint , because mandatory reuse of the existing storage array restricts the architect ' s available design choices. VMware defines constraints as limiting factors that affect or restrict a design. ( VMware )

E is an assumption or discovered condition regarding available storage capacity. It should be validated before relying on it for sizing because assumptions used in design decisions must be confirmed.

Study Guide References/Topics: Conceptual Design; Business and Technical Requirements; Requirements, Constraints, Assumptions and Risks; AMPRS; Capacity and Scalability Planning.

The High Availability VCF Operations model with Collector nodes at remote sites provides the strongest match for minimizing both monitoring and alerting downtime.

VCF Operations High Availability (HA) replicates monitored-object data across analytics nodes and is specifically designed to tolerate the failure of one VCF Operations cluster node . Broadcom states that HA supports one-node failure and recommends placing nodes on different ESX hosts to eliminate an infrastructure-level single point of failure. This maintains the analytics and alert-processing platform when an Operations node becomes unavailable.

Remote Collectors/Cloud Proxies place the collection function closer to the VCF instances being monitored. Broadcom ' s VCF Operations sizing guidance specifies communication between VCF Operations and VCF instance components through the Operations collector and defines latency requirements for this architecture. Current VCF releases similarly use Cloud Proxies or collector groups for remote collection.

A provides aggregation across separate Operations instances but does not itself deliver HA to each monitoring instance. C leaves the central Operations analytics service without HA. D centralizes monitoring across the Fleet but, without an HA model, retains a central service-failure risk.

Study Guide References/Topics: VCF Operations Deployment Models; High Availability; Collector/Cloud Proxy Architecture; Multi-VCF Instance Fleet Monitoring; Alerting Resiliency; Remote Data Collection.

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.

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

A and C directly support predictable storage performance for burst-heavy analytics workloads.

C is correct because the vSAN Express Storage Architecture (ESA) Adaptive Write Path dynamically selects an optimized write path when workloads generate large I/O or high outstanding I/O. Broadcom explains that this reduces write amplification, CPU processing, and network traffic while increasing throughput. Later ESA enhancements further improve write-intensive workloads by dynamically increasing parallelism, producing higher IOPS, higher throughput, and lower latency under demanding conditions. ( VMware Blogs )

A is also correct. Consistent hardware generations and balanced ReadyNode specifications provide predictable performance across the distributed vSAN cluster. Broadcom notes that node uniformity is an important clustering principle because asymmetric hosts can create resource bottlenecks and inconsistent behavior during both normal and failure conditions. ESA performance is strongly dependent on the CPU, NVMe devices, NICs, and networking available on each participating host. ( VMware Blogs )

B is incorrect because disabling automatic rebalancing avoids redistribution rather than ensuring sustained performance while balancing occurs; vSAN ' s adaptive mechanisms are intended to manage resync and workload traffic concurrently. D is an OSA capacity-efficiency setting rather than the optimal performance architecture. E introduces OSA RAID-6 write overhead, whereas ESA is specifically optimized to deliver efficient erasure coding with substantially better performance characteristics. ( VMware Blogs )

Study Guide References/Topics: vSAN ESA; Adaptive Write Path; vSAN Performance Design; Homogeneous Cluster Hardware; ReadyNode Sizing; Rebalancing and Resynchronization; Analytics Workload Performance.

B is correct. In a multi-zone VKS design, the architect should explicitly map vSphere Zones to Kubernetes failure domains within the NodePools so that cluster nodes are distributed across independent infrastructure fault domains. This provides resilience against an entire underlying vSphere cluster or zone becoming unavailable.

Current Broadcom guidance for VKS multi-zone configurations confirms that a Node Pool can have an explicit failureDomain defined. In multi-zone environments, this allows the VKS topology controller to deterministically place nodes and their associated storage in the intended availability zone. Broadcom specifically documents explicit failure-domain configuration as the mechanism for controlling Node Pool placement in a multi-zone topology.

A is incorrect because worker nodes should not be assumed to be automatically balanced across independent vSphere Zones in a way that guarantees the required cluster-level failure tolerance.

C provides recovery from individual VM or ESXi host failure within an available vSphere cluster, but it cannot restart nodes when the entire underlying cluster or zone is offline.

D relates to Kubernetes service exposure and networking and has no bearing on failure-domain placement or infrastructure availability.

By explicitly assigning NodePools to separate failure domains, the design ensures surviving nodes remain available across the other zones after loss of one vSphere cluster.

Study Guide References/Topics: vSphere Kubernetes Service; VKS Multi-Zone Architecture; vSphere Zones; NodePools; Failure Domains; Cluster API Topology; Kubernetes High Availability.

VMware vDefend Firewall is the VCF Advanced Service that directly satisfies the stated security requirements. VMware positions vDefend as the advanced lateral-security capability for VCF, providing zero-trust controls, distributed firewalling, workload-level microsegmentation, and protection against lateral movement . ( VMware Blogs )

The decisive requirement is the combination of macro-segmentation and microsegmentation with repeatable prescriptive guidance . Broadcom ' s Lateral Security for VMware Cloud Foundation with VMware vDefend Validated Solution specifically documents design decisions for securing VCF management-domain components and provides streamlined guidance for implementing both macro- and microsegmentation for workloads in workload domains. It is designed as a repeatable implementation pattern that can be applied consistently across VCF environments. ( VMware Blogs )

vDefend ' s Distributed Firewall operates close to each workload ' s virtual network interface, enabling granular east-west policy enforcement independent of the traditional physical network perimeter. This is fundamental to a zero-trust architecture because communication is explicitly controlled between applications, VMs, containers, and infrastructure services rather than implicitly trusted based on network location. ( VMware Blogs )

A primarily provides load balancing and application delivery. C addresses backup, disaster recovery, and cyber recovery. D does not provide the required lateral firewall and segmentation capabilities.

Study Guide References/Topics: VCF Advanced Services; VMware vDefend; Lateral Security; Zero Trust; Distributed Firewall; Macro-Segmentation; Microsegmentation; VMware Validated Solutions.

Active/Standby is required for this VCF Automation design because the workload model combines VM and Kubernetes consumption through VPC networking and specifically requires automatic outbound SNAT .

Broadcom documents that when activating Supervisor with an NSX VPC Connectivity Profile, Default Outbound NAT must be enabled . Critically, Default Outbound NAT can be enabled only when the associated Tier-0 Gateway is configured in Active/Standby HA mode . If the Tier-0 is Active/Active, it must be converted to Active/Standby before Default Outbound NAT can be enabled.

This also aligns with the VCF Automation All Apps consumption architecture. Broadcom ' s VCF networking guidance explicitly states that VCF Automation All Apps and vCenter Supervisor require Centralized Active/Standby connectivity. This architecture supports VPC-based isolation while providing centralized services required by VM and Kubernetes workloads. ( blogs.vmware.com )

B lacks the centralized service-router architecture required here. C does not satisfy the Supervisor/All Apps and default outbound NAT requirement. D , although capable of certain stateful NSX services in newer NSX releases, does not change the documented Active/Standby requirement for this VCF Automation/Supervisor VPC design.

Study Guide References/Topics: VCF Automation All Apps; NSX VPC Networking; VPC Connectivity Profiles; Tier-0 Gateway HA Modes; Default Outbound NAT; Supervisor and VKS Networking; Centralized Transit Gateway Design.