Free Advanced VMware Cloud Foundation 9 Architect Practice Questions

A and E best satisfy the multi-instance scale requirement while keeping the identity-management footprint as small as possible.

A VCF Identity Broker should be associated with the management infrastructure , not deployed independently in workload domains. Broadcom documentation shows VCF Identity Broker as part of the VCF management-plane architecture and identifies the management domain as the normal installation location for the identity service. ( VMware Blogs )

The scale requirement determines the number of Identity Broker deployments. Broadcom states that an external/appliance VCF Identity Broker is intended for multi-instance fleets and is recommended to support up to five VCF instances . ( VMware Blogs ) With seven VCF instances , one broker would exceed that recommended scale boundary, while seven embedded brokers would create unnecessary compute footprint and operational overhead. The minimum practical topology is therefore two VCF Identity Broker deployments , distributed through the VCF Management Services architecture.

VCF 9.1 further integrates identity services with the broader VCF Management Services platform, and Broadcom requires the Identity Broker to reside on the same management network as those services.

B is incorrect because workload domains are not the preferred hosting boundary for centralized fleet identity. C creates the largest footprint. D is insufficient by itself because a single Identity Broker does not meet the recommended scale for seven VCF instances.

Study Guide References/Topics: VCF Identity Broker; Fleet-Level SSO; VCF Management Services; Management Domain Placement; Multi-Instance Identity Design; Identity Broker Scale and Footprint.

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.

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.

Term

Correct Definition

Must Have

Non-negotiable.

Should Have

Important but are not necessary to success.

Could Have

Desirable but not necessary for success.

Won ' t Have

Will not be delivered as part of this scope of work.

The MoSCoW prioritization method classifies requirements according to how critical they are to the success and scope of a solution.

A Must Have requirement is non-negotiable . Failure to satisfy it means the solution does not meet an essential business or technical requirement.

A Should Have requirement is important and normally expected, but the project can still succeed without it if necessary. Such requirements may be deferred when schedule, cost, or resource constraints demand prioritization.

A Could Have requirement is desirable but has lower business impact. These capabilities are implemented when time and resources permit and can be removed from the current delivery with comparatively little effect on overall success.

A Won ' t Have requirement is explicitly excluded from the current scope. It is not necessarily permanently rejected; it may be reconsidered in a later phase or release.

For VCF architecture work, MoSCoW helps convert workshop findings into prioritized requirements and prevents optional functionality from competing with mandatory architectural objectives.

Study Guide References/Topics: Requirements Gathering; MoSCoW Prioritization; Conceptual Design; Business and Technical Requirements; Scope Management.