VMware 3V0-12.26 Advanced VMware Cloud Foundation 9 Architect Exam Practice Test

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.

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.

The existing vSphere environment can be converged into a new VCF instance by using the VCF Installer. In this deployment pathway, the existing vCenter and its clusters are reused to establish the VCF management domain rather than requiring a completely new infrastructure deployment. During conversion, VCF installs the additional platform components needed to transform the existing environment into a fully managed VCF instance. Broadcom specifically states that when an existing vCenter environment is converged, NSX is deployed as part of the conversion process when it is not already present. ( VMware Blogs )

Therefore, C is correct .

A is incorrect because VCF 9 lifecycle management is image-based; legacy vSphere Update Manager baselines are not the target lifecycle model. Broadcom explicitly notes that VUM baselines must transition to vSphere Lifecycle Manager images. ( VMware Blogs )

B is incorrect because conversion does not require the existing NFS storage to be replaced by vSAN. VCF supports convergence of clusters using external storage , including NFS. ( VMware Blogs )

D is incorrect because the VCF Installer can be deployed in the same cluster as the existing vCenter appliance; migrating vCenter to a standalone host is not required.

Study Guide References/Topics: VCF Installer; Brownfield vSphere Convergence; Creating a New VCF Fleet; NSX Deployment; External NFS Storage; vSphere Lifecycle Manager Images.

Keep practicing VCF design

Compare VCF convergence with a new deployment

Review brownfield VCF conversion prerequisites

Manageability (B) is the dominant design trait. The scenario emphasizes standardized deployment, repeatability, automation, minimal manual intervention, and rejection of one-off custom integrations . These are classic manageability concerns because the objective is to make the platform consistently deployable, maintainable, and operationally sustainable across hundreds of tenants. VMware Cloud Foundation explicitly uses automation and orchestration to standardize infrastructure deployment, provisioning, patching, and lifecycle operations, reducing configuration drift and administrative effort. ( VMware )

Security (C) is the second applicable trait because the scenario explicitly identifies inconsistent identity handling as a concern. Identity consistency, authentication, access control, credential governance, and centralized identity federation are security-design considerations. Current VCF guidance emphasizes centralized identity services, least-privilege access, and consistent identity governance as core security controls. ( VMware Blogs )

Availability is not the primary concern because the scenario does not specify uptime, redundancy, or failure tolerance. Performance is not driven by latency, throughput, or response-time requirements. Recoverability is also not stated because there are no RPO, RTO, backup, or restoration requirements.

Study Guide References/Topics: AMPRS Design Qualities; Manageability; Security; Automation and Standardization; Identity Management; Configuration Consistency; Operational Governance.

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.

C and D are the primary factors that directly determine the required vSAN storage capacity and its performance/redundancy characteristics.

C is correct because the selected vSAN storage policy determines how VM objects are placed and how much physical capacity they consume. Broadcom documents that Failures to Tolerate (FTT) controls redundancy, while the RAID method determines capacity efficiency and performance. For example, RAID-1 with FTT=1 creates mirrored data and consumes approximately 2× the logical data size, while FTT=2 mirroring consumes approximately 3× . Stripe width can also affect performance and component consumption.

D is correct because workload quantity and sizing establish the fundamental storage demand. The proposed 725 VMs (475 + 250) at an average 275 GB each represent approximately 199.4 TB of logical VM disk capacity before applying redundancy, metadata, operational reserve, and growth allowances. Storage policies then multiply or otherwise alter that physical-capacity requirement.

E affects cluster architecture and determines whether certain policies can be supported—for example, RAID-6 FTT=2 requires at least six hosts—but with 15 hosts already specified , host count is not the principal sizing factor among the choices. A concerns management-network redundancy, while B addresses workload networking rather than vSAN capacity design.

Study Guide References/Topics: vSAN Storage Policy-Based Management; Failures to Tolerate; RAID-1/5/6; Stripe Width; Workload Profiling; Storage Capacity Planning; VCF Workload Domain Storage Design.

The design requires a scalable routed fabric, high bandwidth, redundant host connectivity, jumbo frames, and no physical multicast dependency .

A satisfies the end-to-end jumbo-frame requirement. VCF guidance requires consistent MTU configuration throughout the complete path; Broadcom specifically notes that jumbo frames increase throughput and that the physical and virtual path must support the configured MTU. Geneve encapsulation also adds overhead, making sufficient MTU headroom essential.

B is correct because NSX head-end replication replicates BUM frames in software from the originating transport node and therefore does not require multicast support in the physical underlay.

C best satisfies the high-throughput and redundancy requirements. Dual 25-GbE NICs provide substantial bandwidth for consolidated vSAN, vMotion, management, and overlay traffic while allowing redundant attachment to separate ToR switches. Broadcom specifically recommends higher-speed networking for demanding vSAN environments.

F provides the required scalable physical fabric. A Layer-3 leaf-spine/CLOS topology using BGP and ECMP delivers predictable latency, multiple equal-cost paths, horizontal rack expansion, and eliminates dependence on large Layer-2 failure domains.

D conflicts directly with the no-multicast constraint, E provides less bandwidth than the design target, and G introduces unnecessary Layer-2 extension rather than a scalable routed underlay.

Study Guide References/Topics: VCF Physical Network Design; Leaf-Spine/CLOS Architecture; BGP and ECMP; NSX Geneve Overlay; BUM Replication; Jumbo Frames; vSAN Network Design; ESX Host Uplink Redundancy.

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.

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.

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.

D is correct. VMware Cloud Foundation 9 uses VCF Identity Broker as the SSO provider, and it supports two deployment modes: Embedded and Appliance . The appliance deployment is specifically intended for environments requiring greater availability or where VCF components cannot reliably reach the management-domain vCenter.

The Embedded Mode runs the Identity Broker inside the management-domain vCenter. Although this minimizes infrastructure footprint, it ties authentication availability to that vCenter. This conflicts directly with the requirement that some VCF components cannot access the management-domain vCenter. Broadcom ' s design guidance explicitly identifies this condition as a reason to choose the appliance deployment model. ( VMware Blogs )

The Appliance Mode deploys VCF Identity Broker as an external, resilient cluster. Broadcom describes the appliance implementation as a three-node Identity Broker cluster , providing resiliency and allowing authentication services to survive failure of a single Identity Broker node. It can also provide identity services independently of the management-domain vCenter ' s availability. ( VMware Blogs )

Because three nodes are the minimum appliance topology needed to satisfy the stated single-node-failure requirement, this also meets the requirement to deploy the fewest nodes possible while retaining resiliency .

Options A and C are incorrect because VCF LDAP Services is not the VCF 9 SSO provider deployment model. B lacks the required independence and node-level resiliency.

Study Guide References/Topics: VCF Single Sign-On; VCF Identity Broker Deployment Models; Embedded vs Appliance Mode; Identity Broker High Availability; Management Domain Dependency; Identity and Access Architecture.

B and E are correct because the customer has supplied VM counts and service-level objectives, but has not supplied the actual workload resource profile required to translate those VM counts into physical compute and storage capacity.

E establishes the average VM footprint—principally vCPU, RAM, and storage . Without these values, an architect cannot calculate aggregate capacity for either the initial 2,000-VM state or the projected 8,000-VM state. VMware capacity-management metrics explicitly account for allocated vCPU, memory, and VM disk consumption when evaluating cluster capacity.

B is equally important because provisioned resources are not the same as actual demand. Average utilization determines realistic CPU and memory consumption, consolidation ratios, oversubscription assumptions, and required growth headroom. Broadcom ' s guidance states that VM CPU and memory should be sized against real workload demand measured over representative periods , while VCF Operations uses utilization/demand information for capacity planning.

A may affect individual application compatibility but is not the primary aggregate sizing assumption. C is a configuration/design decision rather than a workload-sizing input. D is relevant to achieving the two-hour RPO, but the specific backup product does not establish the core compute, memory, and storage capacity required for 2,000–8,000 VMs.

The official VCF Architect exam guide explicitly includes capacity planning, scalability, and documenting assumptions as core architect competencies. ( Broadcom Docs )

Study Guide References/Topics: Capacity Planning; Workload Profiling; Assumptions and Constraints; VM Resource Sizing; Scalability; VCF Physical 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.

Functional requirements describe what the solution must accomplish or how it must behave , whereas non-functional requirements specify measurable qualities or operational characteristics such as performance, recoverability, security, and service levels. Broadcom ' s VCF architecture guidance explicitly distinguishes functional behavior from non-functional characteristics such as performance, scalability, and resilience. ( VMware Blogs )

A is functional because the platform must interact with the corporate password vault to store and retrieve service-account credentials. B specifies required identity functionality: authentication must integrate with an external SAML identity provider. C specifies required application behavior during a site failure—the applications must continue to tolerate loss of one data center. E is a clear user-facing function requiring users to view and track request progress.

By contrast, D specifies a security-assurance/testing target rather than platform functionality. F defines a measurable recoverability characteristic through a 10-minute RTO. G specifies a measurable SLO over a 12-month period and is therefore non-functional.

The VCF Architect exam guide specifically requires architects to distinguish business/technical requirements and relate solution requirements to AMPRS design qualities. ( Broadcom Docs )

Study Guide References/Topics: Conceptual Design; Functional vs. Non-Functional Requirements; Requirements Classification; AMPRS Design Qualities; Identity Integration; Availability and Recoverability Requirements.

D is correct. A dedicated Supervisor Cluster for each tenant establishes the strongest infrastructure and Kubernetes control-plane isolation. Each Supervisor has its own Kubernetes control plane and underlying vSphere infrastructure boundary, avoiding the shared control-plane dependency that would exist if multiple tenants used namespaces on the same Supervisor.

This design also addresses the requirement for independent failure domains . A Supervisor deployed on separate workload-domain infrastructure can be associated with distinct vSphere clusters, networking, storage, and lifecycle boundaries. Consequently, failure or maintenance affecting one tenant ' s Supervisor does not inherently affect another tenant ' s Kubernetes control plane.

The independent-upgrade requirement is also significant. Broadcom documents Supervisor and VKS lifecycle operations at the Supervisor level , including compatibility validation between the Supervisor, VKS service, and workload-cluster Kubernetes releases. VKS service upgrades are activated on the relevant Supervisor, reinforcing the Supervisor as an important lifecycle boundary.

A and B are useful security controls but do not isolate Kubernetes control planes or infrastructure failure domains. C provides namespace-level tenancy, but all namespaces still depend on the same Supervisor control plane and its lifecycle , so it cannot satisfy the stated isolation and independent-upgrade requirements.

Study Guide References/Topics: VCF VKS Architecture; Supervisor Clusters; Workload Domains; Tenant Isolation; Kubernetes Control-Plane Isolation; Failure Domains; Supervisor and VKS Lifecycle Management.

VCF Automation projects provide the access and consumption boundary for self-service catalog content . A published catalog item can be associated with specific projects, and users who belong to those projects can consume the corresponding catalog resources. Broadcom ' s VCF Automation documentation explicitly provides the ability to select a catalog item and add or remove it from projects . The catalog API likewise exposes the project IDs associated with an item, demonstrating that project association determines where that catalog item can be requested.

Therefore, A precisely implements the required entitlement matrix: Marketing → Users 1 and 5; Inventory → Users 2 and 3; HR → Users 1, 3, and 4. A user can belong to multiple projects, so Users 1 and 3 can appropriately receive multiple applications.

B does not reproduce the required application-to-user mappings. C exposes all three applications through a common project rather than enforcing application-specific visibility. D incorrectly assumes users are assigned directly to individual blueprints as the primary access-control mechanism. In VCF Automation, users are assigned project roles, while catalog content is associated or shared with projects. Broadcom also describes the Project User role as a catalog consumer capable of deploying resources from the service catalog.

Study Guide References/Topics: VCF Automation Projects; Self-Service Catalog; Blueprint/Template Publishing; Catalog Item Sharing; Project Membership and RBAC; Content Access Control.

C is the best match because this blueprint combines metro-style availability inside the primary region with disaster recovery into an additional region .

Within the primary region, two sites can use stretched vSphere/vSAN clusters . Current VCF design guidance specifies that stretched designs require high-bandwidth connectivity and less than 5 ms RTT between the data availability zones. This enables synchronous storage replication, which is the architectural mechanism required to achieve RPO 0 for Tier-1 and Tier-2 workloads. Broadcom also documents that stretched-cluster designs can provide zero RPO because data is synchronously maintained across sites.

The additional data center can then operate as a separate regional VCF instance within the same Fleet. This provides geographic separation for regional disaster recovery and supports the stated 24-hour RTO , while avoiding the operational complexity of stretching every site across every region.

A pure single-region multi-site design does not adequately address complete regional failure. Conversely, a generic multi-region design does not inherently provide the synchronous stretched-cluster architecture required for the Tier-1/Tier-2 zero-RPO requirement.

The VCF blueprint specifically described as “Multiple Sites in a Single Region plus Additional Region(s)” combines a stretched primary region with one or more standard remote regions. ( VMware TechDocs )

Study Guide References/Topics: VCF Design Blueprints; Multi-Site Single-Region Architecture; Additional Region Design; vSAN Stretched Clusters; RPO/RTO Design; Regional Disaster Recovery; Data Sovereignty; Fleet-Level Operations.

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 )