VCF Operations offers different deployment models based on scale and availability requirements:

Simple Model → Recommended for minimal footprint and greenfield deployments, where the organization wants to start small and expand later.

High Availability Model → Larger environments requiring immediate redundancy and scale.

Advanced / Standard Models → Targeted for more complex architectures with multi-site or advanced collection needs.

Since the customer’s goal is minimal footprint with future scalability , the Simple Model is the correct choice.

Validating a BCDR strategy in VCF with vSAN DP requires both impact analysis and active testing :

B. Assess the impact of failover scenarios – Ensures application dependencies, such as inter-site routing, DNS, and external services, are validated against failover scenarios. This prevents unexpected downtime due to overlooked dependencies.

D. Planned and unplanned failover tests – VMware best practices emphasize testing both scheduled and unexpected recovery workflows to validate RTOs and confirm operational procedures.

Why not the others?

A (annual testing only) contradicts VMware guidance, which recommends frequent and scenario-based validation .

C (generic plans) reduces workload alignment; VMware requires application-aware recovery plans .

E (vSphere HA/DRS) does not replace site-level recovery orchestration and validation — HA/DRS only handles local host failures, not site disasters.

According to the VMware Cloud Foundation 9.0.1 Design Framework , Technical Requirements describe how the business and functional goals are to be implemented through technology, configuration, and design mechanisms. The document defines:

“Technical requirements determine how a solution’s business and functional objectives are achieved using technical means such as architecture components, configurations, and integrations.”

These are distinct from business requirements , which define what must be achieved, and constraints , which limit design options. Technical requirements translate abstract needs (for example, availability, scalability, performance) into actionable design implementations (such as anti-affinity rules, distributed switches, NSX federation, or vSAN stretched clusters).

By following VMware’s VCF Design Methodology , architects use technical requirements to shape logical and physical architectures , ensuring that all solution components meet the identified business outcomes and compliance standards.

References (VMware Cloud Foundation documents):

VMware Cloud Foundation 9.0.1 Design and Architecture Guide — Requirements Classification and Technical Requirements Definition (pp. 58–61).

VMware Cloud Foundation 9.0.2 Design Framework — Business, Functional, and Technical Requirement Mapping to Design Decisions.

The Conceptual Model identifies high-level requirements, constraints, assumptions, and risks. The Logical Design translates those into how solution components (clusters, networks, storage, security zones, etc.) are structured to meet dependencies and requirements.

Physical Design comes after Logical Design and defines specific hardware, IP addresses, VLANs, etc.

High Availability Design is a subset of the logical/physical design focusing only on resiliency.

Configuration Guide is implementation-level documentation, not design.

Thus, the Logical Design defines how the infrastructure’s capabilities are arranged to satisfy conceptual dependencies.

VMware Cloud Foundation scales using workload domains (WLDs) . Each WLD provides its own vCenter Server, NSX Manager, and lifecycle independence through SDDC Manager.

By using multiple WLDs for each department, the architecture supports independent scaling, policy separation, and lifecycle management .

Option A or C restricts flexibility as all tenants would share a single WLD, leading to lifecycle constraints and “noisy neighbor” issues.

Option D contradicts best practices: multiple departments should not share a single cluster inside a WLD when separation and lifecycle flexibility are required.

This design ensures seamless addition of new workload domains as departments and applications grow.

This statement expresses a financial limit — “Remaining budget” — constraining future expenditures on hardware. This is clearly a constraint , as it restricts the design options (e.g., can ' t procure new hardware). In the VMware Conceptual Model framework, constraints are factors that limit design choices without introducing risk or goal definitions.

During VCF bring-up , SDDC Manager requires control of a clean vCenter deployment . Since the existing environment already has a vCenter managing the clusters, the vCenter VM must be migrated to a standalone host so that VCF bring-up can properly deploy its own vCenter instance.

A: NSX deployment happens later during WLD creation, not at fleet bring-up.

C: vSAN isn’t auto-configured — it requires explicit design.

D: VCF uses vLCM images , not baselines, post-deployment.

According to the VMware Cloud Foundation 9.0.4 Architecture and Design Guide , under the section “VKS Cluster Networking” , VMware Kubernetes Service (VKS) supports two Container Network Interface (CNI) options — Antrea and Calico — for pod and service networking. The documentation explicitly states:

“A VKS cluster provisioned by the VKS supports two CNI options: Antrea (default) and Calico.”

It further explains that Antrea is automatically selected as the default and requires no explicit configuration unless the user specifies Calico in the cluster YAML file.

Antrea, developed by VMware, leverages Open vSwitch (OVS) for networking and supports advanced features such as network policy enforcement, encapsulation, and traffic visibility , making it the optimal default CNI for VKS clusters. Calico, using Linux bridge and BGP, remains an alternative for organizations requiring specific network topologies or integrations.

Thus, unless otherwise defined, all new VKS workload clusters in VMware Cloud Foundation are deployed using Antrea as the default network provider to maintain consistency, integration with NSX networking, and full compatibility with VCF lifecycle management.

References (VMware Cloud Foundation documents):

VMware Cloud Foundation 9.0.4 Design Guide – “VKS Cluster Networking: Antrea (default) and Calico options.”

VMware Cloud Foundation 9.0.4 – “Set the Default CNI for VKS Clusters” (System-defined default: Antrea).

According to the VMware Cloud Foundation 9.0.1 Design Guide (Table 543 & vSAN Storage Cluster Separation Distributed Switch Model) , when an organization enforces strict network zoning and isolation, two vSphere Distributed Switches (vDS) are used to separate management/storage traffic from workload/overlay traffic.

The vDS01 handles Management, vMotion, and Storage (vSAN/NFS) traffic within the secure zone 1 , ensuring no cross-zone connectivity. The vDS02 is dedicated to workload and NSX overlay traffic (Host TEPs, Edge TEPs, and Edge uplinks) within zone 2 , which aligns with NSX networking and security best practices.

This dual vDS model enforces compliance with security zone isolation policies and eliminates inter-zone traversal, as required by the design. It also aligns with VCF best practices which state:

“Provides support for traffic separation across different uplinks or vSphere Distributed Switches. Each vDS supports a distinct set of traffic types, ensuring isolation and compliance with network zoning policies.”

References (VMware Cloud Foundation documents):

VMware Cloud Foundation 9.0.1 Design Guide — “vSAN Storage Cluster Separation Distributed Switch Model” (p.808–809)

VMware Cloud Foundation 5.2 Networking Design — “Multiple vSphere Distributed Switches and Traffic Separation.”

When gathering business requirements, VMware’s VCF Design and Planning methodology (referenced in the VMware Cloud Foundation 9.0 Architecture and Design Guide ) specifies that architects must first analyze the business-level inputs that define availability, manageability, and compliance objectives . The documentation identifies Service-Level Agreements (SLAs) and Organizational Structure as key influencing factors on design decisions because they define the scope of reliability, operational responsibility, and risk tolerance of the solution.

SLAs determine the required uptime, RPO/RTO targets, and recovery policies , directly impacting design elements such as stretched clusters, backup configuration, and resource redundancy. Similarly, the organizational structure affects operational models and determines how administrative domains, roles, and tenancy will be separated — influencing whether to implement single-tenancy or multi-tenancy within VCF Automation and how management domains are segregated.

Other options such as product versions, VM sizes, or storage capacity are important for implementation and scaling phases, not the business requirements stage. VMware explicitly distinguishes between business requirements (goals, SLAs, governance) and technical requirements (capacity, configuration) in the VCF Design Library .

References (VMware Cloud Foundation documents):

VMware Cloud Foundation 9.0 Design Guide — Business Requirements Gathering Framework (VCF-DES-PLN-BREQ-001).

VMware Cloud Foundation 9.0 Architecture Overview — SLAs and Organizational Models Impact on Design Decisions .

VMware Cloud Foundation 9.0.1 Design Library — Mapping Business Requirements to Design Factors .