3V0-12.26 VMware Advanced VMware Cloud Foundation 9 Architect Free Practice Exam Questions (2026 Updated)

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.

A is correct. VCF Identity Broker is the central identity-federation component used by VCF Single Sign-On . It allows VCF management components to use a common authentication architecture instead of maintaining independent identity configurations for each vCenter, NSX instance, or other management service. Broadcom states that VCF SSO uses VCF Identity Broker and enables administrators to sign in across VCF management components, provided the appropriate permissions are assigned.

The corporate identity provider can authenticate users through modern federation protocols. Broadcom specifically documents VCF Identity Broker integration with external identity providers using OIDC or SAML , including modern providers such as Microsoft Entra ID and Okta.

B conflicts directly with the requirement to eliminate per-domain identity silos. C can centralize the directory source but still requires individual component-level identity configuration and does not provide the unified federation architecture required here. D is incorrect because OAuth 2.0 alone is an authorization framework , not the identity authentication protocol requested. VCF uses OpenID Connect (OIDC) on top of OAuth mechanisms where applicable, or SAML 2.0 for federation.

Therefore, the correct logical identity design is a central VCF Identity Broker federated to the enterprise IdP, with VCF SSO consumed by VCF management components .

Study Guide References/Topics: VCF Single Sign-On; VCF Identity Broker; Identity and Access Management; SAML 2.0; OpenID Connect; Enterprise Identity Federation; Centralized Management-Plane Authentication.

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 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.

C satisfies the requirement for a highly scalable, policy-based principal storage platform . VMware vSAN is tightly integrated with VCF and uses Storage Policy-Based Management (SPBM) to apply workload-specific requirements for availability, performance, capacity, and placement. VMware specifically identifies vSAN as the preferred principal-storage option for workload domains because it provides integrated deployment, scaling, and lifecycle management within VCF. ( VMware )

B satisfies the second tier requirement. NFS v3 provides file-based storage and can be expanded independently of the ESX cluster, making it appropriate for workloads with large or independently growing datasets. Supplemental storage is specifically intended to add additional storage capacity or storage types after the workload-domain cluster has been created, and NFS is supported for this purpose. ( VMware )

A provides block-based FC storage, not the requested file-based tier. D is inappropriate because NFS v4.1 is not available as principal storage through the standard greenfield VCF Installer workflow. E is similarly not available as principal storage through that greenfield workflow; Broadcom documents iSCSI principal storage through VCF import/convergence instead.

Study Guide References/Topics: VCF Storage Models; Principal vs. Supplemental Storage; vSAN SPBM; NFS Storage; Workload Domain Storage Design; VCF Installer Storage Support.

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.

For this question, VMware ' s architecture course material distinguishes functional/business requirements from non-functional/technical requirements according to whether the statement expresses a required business capability or outcome versus a measurable technical operating characteristic.

B is functional because the customer requires the architecture to provide a resilient multi-site topology . This is a required solution capability and directly drives the architecture that must be delivered.

C is also treated as a functional/business requirement in the VMware course material because the completed solution must support 20 percent growth over three years . This establishes a required business capability for future expansion.

D is likewise a functional requirement because the application service must remain available with essentially no interruption. The requirement defines the business outcome that the infrastructure must provide.

By contrast, A, E, and F are technical/non-functional requirements in the VMware course classification. A specifies a measurable transaction-processing characteristic, E defines a technical scaling trigger based on sustained compute utilization, and F defines a specific network latency characteristic before path failover. VMware training material explicitly uses these latter statements as examples of non-functional/technical requirements . ( Scribd )

The current VMware Cloud Foundation Architect exam guide also requires candidates to distinguish business and technical requirements and translate them into VCF design decisions. ( Broadcom Docs )

Study Guide References/Topics: Conceptual Design; Functional/Business Requirements; Non-Functional/Technical Requirements; Requirements Classification; Availability; Scalability; Multi-Site Architecture.

The scenario maps directly to Availability, Manageability, and Recoverability , three of VMware ' s core AMPRS design qualities. VMware defines availability as the ability of a system to continue operating without interruption, recoverability as its ability to recover following failure or disaster, and manageability as how easily the environment can be deployed, configured, and controlled. ( VMware )

Recoverability (D) is central because the environment can enter a corrupted state and must be restored to a known reliable condition without damaging historical data. Recovery sequencing, backups, recovery points, and dependency-aware restoration therefore become critical design considerations.

Manageability (C) is required because restoration involves a complex and sensitive dependency chain. The design should reduce operational complexity through standardized procedures, automation, orchestration, configuration control, and repeatable recovery workflows. A recovery process that depends heavily on error-prone manual sequencing represents a manageability risk.

Availability (A) is required because stakeholders want some services to remain operational while the broader environment is being restored. The architecture therefore needs mechanisms that preserve service continuity or degraded-but-functional operation during recovery.

Performance and Scalability are not stated concerns. Security remains important generally, but the audit-data issue here concerns preserving recoverable state rather than an explicit confidentiality, access-control, or threat-protection requirement.

Study Guide References/Topics: AMPRS Design Qualities; Availability; Manageability; Recoverability; Business Continuity; Dependency-Aware Recovery; Operational Resilience.

A, D, and E meet the availability, sizing, and fault-domain requirements.

A is required because Continuous Availability (CA), rather than standard HA, provides fault-domain resilience. Broadcom states that VCF Operations CA stretches cluster nodes across two fault domains and can tolerate the loss of an entire fault domain without cluster downtime. Standard VCF Operations HA protects only against one node failure , so C does not satisfy the stated requirement for a single fault domain failure. CA requires equal node distribution across the two fault domains and a witness in a third location.

E is correct because 15,000 VMs plus all monitored infrastructure objects exceed the practical capacity of the Small configuration. Two Small nodes support only 12,000 maximum cluster objects before CA replication considerations . Four Medium nodes provide sufficient capacity and can be distributed as two analytics nodes per fault domain. Broadcom also notes that CA replication effectively reduces available object capacity compared with a non-CA deployment.

D ensures Operations analytics nodes are separated across physical hosts rather than sharing a common failure point. Broadcom specifically recommends DRS anti-affinity to keep Operations nodes on separate hosts.

Study Guide References/Topics: VCF Operations Sizing; Continuous Availability; Fault Domains; Analytics Node Placement; DRS Anti-Affinity; High Availability versus Continuous Availability.

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

The appropriate blueprint is VCF Fleet in a Single Site . This model is designed for organizations operating a primary data center in a single availability zone while still requiring enterprise-grade high availability. The architecture supports a multi-rack deployment , allowing hosts and infrastructure components to be distributed across racks to reduce the impact of rack-level failures. It also explicitly relies on vSphere HA for fault detection and automated VM recovery , supplemented by application-level clustering for critical management and control-plane services. ( VMware TechDocs )

This differs from the minimal-footprint single-site blueprint , which prioritizes lower resource consumption and consolidation. Because the scenario explicitly states that resource consumption is not a concern, the standard single-site blueprint is the better architectural match.

A introduces multiple sites and stretched-cluster requirements that are not specified. C adds both a stretched primary region and additional regions, introducing unnecessary complexity. D is intended for geographically distributed, multi-region environments and is likewise beyond the stated requirements. Current VCF design guidance distinguishes the standard single-site blueprint as the production model for high availability within one site , including multi-rack architecture and vSphere HA. ( VMware TechDocs )

Study Guide References/Topics: VCF Design Blueprints; VCF Fleet in a Single Site; Multi-Rack Architecture; vSphere HA; Management Domain Availability; Single-Site Production Design.

VCF Automation provides two consumption models that align directly with the two departmental workload patterns.

A is correct. A VM Apps Organization provides the traditional VM-centric automation model based on constructs such as cloud accounts, cloud zones, projects, image mappings, flavor mappings, templates, and blueprints. It is therefore appropriate for departments whose requirement is primarily standardized, policy-controlled VM deployment. Broadcom describes VM Apps as providing the classic Automation experience centered on virtual-machine consumption.

C is correct. An All Apps Organization provides the modern application-consumption model using Supervisor-backed resources and supports both virtual machines and application-platform services. It is designed for departments that need broader application lifecycle capabilities rather than only template-based VM provisioning. All Apps organizations receive resource allocations through regional quotas and provide the modern VCF Automation multitenancy model. ( VMware Blogs )

Creating an organization for every department (B) increases administrative overhead and conflicts with the requirement to minimize organization count. D is incorrect because Regions represent infrastructure/resource locations, not departmental tenancy boundaries. E oversimplifies the design by forcing fundamentally different consumption models into one organization; projects provide delegated governance but do not replace the appropriate VM Apps versus All Apps tenancy model.

Study Guide References/Topics: VCF Automation Tenant Design; VM Apps Organizations; All Apps Organizations; Projects and Organizations; Regional Quotas; Governance and Application Consumption Models.

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.

A homogeneous cluster (A) is the appropriate VCF design because equivalent host configurations across both availability zones provide predictable compute, memory, and storage capacity during normal operation and site failure. Broadcom specifically recommends uniform host configurations because they provide predictable performance and minimize the impact of rebuild and resynchronization operations.

C reflects the stretched-cluster requirement to maintain substantial compute failover capacity. A two-availability-zone design must be capable of running the affected workloads on the surviving site. VCF stretched designs therefore reserve approximately 50% CPU and memory capacity for availability-zone failure. Of the supplied choices, maintaining peak compute utilization below 45% is the correct design choice. With an absolute corporate ceiling of 85%, a conservative implementation would actually target approximately 42.5% or lower where workload demand can effectively double after site loss; however, C is the intended and only valid failover-oriented option provided.

F is correct because vSAN requires operational slack capacity for rebalancing, rebuilds, policy changes, and failures. Broadcom recommends approximately 25–30% free capacity , making 70% maximum utilization an appropriate design target.

B introduces unpredictable capacity symmetry. D leaves insufficient vSAN operational reserve, while E cannot provide adequate compute headroom following loss of an availability zone.

Study Guide References/Topics: VCF Stretched Cluster Design; Management Domain Capacity Planning; Availability Zone Failure; Homogeneous Host Configuration; vSAN Reserved/Slack Capacity; vSphere HA Capacity Planning.

A directly improves NSX Edge availability. VMware/Broadcom guidance recommends placing Edge appliances on separate ESXi hosts using VM-VM anti-affinity so that a single host failure cannot remove multiple routing instances simultaneously. Broadcom specifically notes that Edge anti-affinity keeps Edge Nodes on different hosts and preserves NSX services if one ESXi host becomes unavailable.

B provides the required North/South forwarding resilience. An Active/Active Tier-0 design allows service routers on multiple Edge Nodes to forward simultaneously and supports ECMP north-south routing . If an Edge Node or forwarding path fails, remaining active paths continue carrying traffic. Distributing Edge Nodes across independent fault domains further avoids concentrating routing availability on one host or failure domain. Broadcom ' s VCF guidance explicitly documents Active/Active Tier-0 gateways and ECMP across Edge Nodes.

C does not itself create redundancy; BFD accelerates failure detection, but merely sharing a profile is not an availability architecture. D unnecessarily concentrates gateway services and increases failure-domain dependency. E addresses NSX Federation management/policy continuity rather than North/South forwarding availability; Global Manager failover is also manual, while existing data-plane forwarding can continue without it.

Study Guide References/Topics: NSX Edge High Availability; Edge Node Placement; VM Anti-Affinity; Tier-0 Active/Active HA; ECMP Routing; BGP/BFD Convergence; Fault-Domain Design; VCF Network Availability.

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.

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.