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.
