3V0-12.26 Exam Preparation Material | Advanced VMware Cloud Foundation 9 Architect

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

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

Explanation:
C and E provide the centralized SSO architecture required while minimizing operational complexity. The VCF Identity Broker can provide identity services across a fleet containing multiple VCF instances, eliminating the need to deploy and manage an independent identity stack for every VCF instance. Broadcom describes the external Identity Broker model as providing identity services across a VCF Fleet, with centralized SSO covering VCF Operations, vCenter, NSX, and other platform components. (VMware Blogs)
Deploying the Identity Broker with the first VCF instance at DC01 (C) establishes the centralized identity service.
E then allows additional VCF instances within the same private cloud to consume that existing VIDB rather than introducing redundant identity infrastructure at every site.
This architecture also supports REQ02. VCF Identity Broker federates authentication to supported enterprise identity providers, including SAML-based providers, Entra ID, Okta, and others. Multi-factor authentication can therefore be enforced by the corporate identity provider and applied across the VCF management stack. (VMware Blogs)
A unnecessarily duplicates VIDB infrastructure and increases administration.
B similarly creates additional identity components without a requirement for separate identity domains.
D incorrectly references a VIDB hosted at DC02 when the centralized design establishes the first VIDB at DC01.
Study Guide References/Topics: VCF Single Sign-On; VCF Identity Broker; Fleet-Level Identity Management; Multi-Instance VCF Design; Identity Federation; MFA/Two-Factor Authentication; Centralized Management Services.

Explanation:
The two design qualities represented by the requirements are Availability and Performance.
Availability (D) is the dominant requirement because each manufacturing site must continue providing its critical local production functions even when connectivity to headquarters is lost. The architecture therefore needs to eliminate inappropriate WAN dependencies and provide sufficient local compute, storage, networking, and service redundancy so that a WAN or remote-site failure does not cause the business service itself to become unavailable. VMware infrastructure design uses redundancy, clustering, and fault-domain separation specifically to maintain service availability during component or connectivity failures. Broadcom’s VCF guidance similarly associates sufficient cluster redundancy with satisfying availability requirements.
Performance (E) is also explicitly represented because the customer identifies degraded order-processing response during periods of high traffic. Performance is concerned with throughput, latency, resource contention, and maintaining acceptable response characteristics as demand changes. Broadcom notes that excessive network latency can degrade workload performance and recommends minimizing latency for stable operation during high-demand periods. Network I/O controls can likewise protect critical traffic during contention.
Recoverability concerns restoration after failure rather than continuous operation during a connectivity outage. Manageability and Security remain general architectural concerns but are not the primary qualities expressed in this scenario.
Study Guide References/Topics: Architecture Quality Attributes; Availability and Resiliency; Performance and Scalability; Fault Domains; Network Latency and Contention; Distributed/Site-Local Service Design.

Explanation:
B addresses the network-isolation requirement by keeping security-policy enforcement within the individual VPC boundary. VMware VPCs are designed as isolated networking and security domains in which tenant administrators can maintain VPC-specific firewall and networking policies. NSX VPC security provides distributed firewalling and microsegmentation close to workload interfaces, allowing east-west traffic to be restricted without depending on a shared tenant security object. Broadcom describes VPC administrators ' network and security policies as contained within their VPC and not affecting other VPCs. (VMware Blogs)
C addresses identity isolation. VCF Automation organizations provide independent administrative and access-control boundaries, and each organization can configure its Identity Provider connection and organization-specific users/groups. This enables API consumers to authenticate within the appropriate organizational identity scope instead of sharing credentials or tenant identities.
A introduces shared provider-managed security constructs, conflicting with the no-shared-security-objects requirement. D concerns IP-address efficiency rather than zero-trust enforcement. E introduces shared routing infrastructure and depends on route filtering rather than enforcing isolation directly at each VPC boundary.
Study Guide References/Topics: VCF VPC Security Architecture; VPC Isolation; Distributed Firewall and Microsegmentation; VCF Automation Organizations; IAM and Identity Provider Integration; Zero-Trust Tenant Design.