Free Practice Questions for VMware 3V0-12.26 Exam

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.

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.

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.

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.

RAID-6 with FTT=2 is the appropriate vSAN storage policy for Site A because it satisfies both requirements: tolerance of two simultaneous host failures and maximum storage efficiency.

In vSAN, Failures to Tolerate (FTT)=2 means that a storage object remains accessible after two concurrent failures within the applicable fault-domain model. Both RAID-1 FTT=2 and RAID-6 FTT=2 can provide this level of protection, but their capacity overhead differs significantly.

RAID-1 FTT=2 uses three mirrored copies of the data, resulting in approximately 3× raw-capacity consumption for the protected object. By comparison, RAID-6 FTT=2 uses erasure coding with dual parity, providing two-failure tolerance with substantially better usable-capacity efficiency.

Site A contains 16 ESX hosts , providing more than enough hosts/fault domains to support RAID-6 FTT=2 placement requirements. This makes erasure coding the preferred choice where the design explicitly prioritizes storage efficiency while maintaining dual-failure protection.

A and D provide only FTT=1 and therefore cannot tolerate two simultaneous host failures. B provides the required resilience but consumes considerably more storage capacity than RAID-6.

Study Guide References/Topics: vSAN Storage Policy-Based Management; Failures to Tolerate; RAID-1 Mirroring; RAID-5/RAID-6 Erasure Coding; Capacity Efficiency; vSAN Cluster Sizing and Fault Domains.

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.

C is required because BGP uses the AS_PATH attribute for loop prevention . If a Tier-0 gateway uses an autonomous-system number already present in an incoming route ' s AS path, the advertisement can be rejected as a routing loop. Assigning a unique private ASN to each Tier-0 gateway prevents this condition and is the documented VCF physical-network design consideration for the VPC Full Services model.

D addresses the explicit constraint that BFD cannot be used . Without BFD, failure detection falls back to BGP keepalive/hold timers. Broadcom ' s VCF configuration guidance uses 4-second Keep Alive and 12-second Hold Down timers when BFD is disabled, allowing three missed keepalives before declaring the peer unavailable. Therefore, the wording “3 retries and 12 hold down” is expressing this timer behavior.

E is not automatically justified by a 40+ Gbps requirement: UPT requires compatible DPU/SmartNIC-backed Edge interfaces and is not a generic VPC Full Services prerequisite. F does not solve AS-path loop detection. A conflicts with the centralized Full Services forwarding model, while B is unnecessary for a single-tenant design.

Study Guide References/Topics: NSX VPC Full Services Model; Tier-0 Gateway Physical Design; BGP Autonomous Systems and Loop Prevention; BGP Failure Detection; BGP Keepalive/Hold Timers; NSX Edge Connectivity.

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.