Last Updated On : 12-Jun-2026
An architect has made the following assumptions:
The customer will provide licensing for the vSphere platform.
The storage hardware has sufficient capacity for future workload scale.
The data center offers sufficient power, cooling and rack space for workload scale.
Which two risks must be documented in the design document in response to these
assumptions? (Choose two.)
A. The assumptions must be approved by the customer, architect and the architect’s company.
B. The storage may not have capacity to accommodate 20% year over year virtual machine growth.
C. The licenses provided by the customer only have support entitlement for one year.
D. The customer may not have an existing licensing subscription that covers features the architect intends to use.
E. The customer may not have sufficient data center cooling, power, and physical rack space available.
Explanation:
An assumption in a design document is a statement believed to be true but not yet verified. If an assumption is incorrect, it creates a risk to the project. The architect must document risks that directly stem from unverified assumptions.
D. The customer may not have an existing licensing subscription that covers features the architect intends to use
– Correct. The assumption states that the customer will provide licensing. However, the architect may be assuming the license edition (e.g., Enterprise Plus vs. Standard) or features (e.g., vSAN, DRS, NIOC) are available. If the customer’s actual license lacks required features, the design cannot be implemented as intended.
E. The customer may not have sufficient data center cooling, power, and physical rack space available
– Correct. The assumption states these resources are sufficient for scale. If this is false, the environment cannot grow as planned, leading to capacity failures or hardware installation delays.
Why other options are incorrect:
A. The assumptions must be approved by the customer, architect and the architect’s company
– Incorrect. This is a process or governance requirement, not a risk. Approval is a project management activity, not a consequence of an unverified assumption.
B. The storage may not have capacity to accommodate 20% year over year virtual machine growth
– Incorrect. The assumption said storage has sufficient capacity for future workload scale, but it did not specify 20% growth. This introduces a new, unstated condition. However, the risk should be that the assumption itself is false, not a specific growth rate unless agreed upon.
C. The licenses provided by the customer only have support entitlement for one year
– Incorrect. The original assumption said nothing about support duration. This introduces an extra condition not derived from the stated assumption. If support length is critical, it should have been captured as an assumption or constraint first.
Reference
VMware VCAP Design Methodology – Assumptions must be validated; unvalidated assumptions create risks. Common risks include missing license features, insufficient power/cooling/space.
Risk Management for vSphere Designs – Risks are uncertain events that, if realized, negatively impact the project. Likelihood and impact should be documented alongside each assumption.
An architect has been tasked with designing a greenfield hosting platform.
As part of a workshop, it is identified that the new solution must support the following:
Provide a centralized way to enforce virtual network security policy
Provide network security for both virtual machines and containerized applications
Deny network access between all workloads by default
Linked services should be connected to the same virtual port groups by default
Support for the security teams network monitoring solution
Which elements should the architect include in the design to meet the identified
requirements?
A. VMware Standard Switches, Access Lists and Promiscuous mode
B. Distributed Virtual Switches, Access Lists and Promiscuous mode
C. VMware Carbon Black, Distributed Virtual Switches and Traffic Filtering
D. VMware NSX, Distributed Firewalls and Port Mirroring
Explanation:
The requirements demand centralized network security policy enforcement, default deny between workloads, support for containers, and integration with network monitoring — all of which point to an overlay‑based, software‑defined networking and security platform.
D. VMware NSX, Distributed Firewalls and Port Mirroring – Correct.
VMware NSX provides centralized policy management, segmentation, and supports both VMs and containers (via NSX Container Plugin).
Distributed Firewalls enable per‑workload firewall rules with default‑deny posture, applied consistently across virtual machines and containers.
Port Mirroring (SPAN/ERSPAN) allows traffic to be copied to the security team’s network monitoring solution.
Why other options are incorrect:
A. VMware Standard Switches (VSS), Access Lists, Promiscuous mode – Incorrect.
VSS is host‑local, not centralized. Access lists are primitive and not scalable for default‑deny micro‑segmentation. Promiscuous mode is for sniffing, not policy enforcement. No container support.
B. Distributed Virtual Switches (VDS), Access Lists, Promiscuous mode – Incorrect.
VDS provides centralized networking but not advanced security. Access lists on VDS are limited and do not provide default‑deny or container security. Promiscuous mode does not enforce policies.
C. VMware Carbon Black, Distributed Virtual Switches, Traffic Filtering – Incorrect.
Carbon Black is an endpoint detection and response (EDR) tool, not a network security policy engine. It does not provide default‑deny network segmentation between workloads or container networking security.
Reference
VMware NSX Documentation (vSphere 8.x) – NSX Distributed Firewall provides per‑workload micro‑segmentation with default‑deny posture, supporting VMs and containers.
VMware NSX Port Mirroring – Enables traffic replication for monitoring, troubleshooting, and security analytics tools.
An architect is responsible for designing the upgrade of a brownfield vSphere-based
solution for a financial services customer. The customer has a requirement to host a
mission critical, latency sensitive stock trading application.
During initial meetings with the customer, the following information is provided:
The solution is currently running vSphere 7.0 U3
All vSphere distributed switches (VDS) are at version 7.0.0
The customer has provisioned new hardware with dedicated AMD Data Processing Units
(DPU)
The mission critical applications must not be adversely affected by other workloads running
in the environment
The architect has made the following design decisions:
The solution will upgrade the existing VMware vCenter Server to version 8.0
The solution will upgrade all existing VMware ESXi hosts to version 8.0
The solution will deploy VMware ESXi 8.0 for all new host servers
Which three additional design decisions should the architect make to ensure that the new
hardware can be used to support the latency-sensitive application? (Choose three.)
A. The solution will deploy new vSphere distributed switches (7.0.3) and connect the new DPU-enabled hosts.
B. The solution will configure the hosts to use Network Time protocol (NTP).
C. The solution will deploy all DPU-enabled VMware ESXi hosts into a dedicated VMware vSphere cluster.
D. The solution will configure network offloads compatibility to support DPUs.
E. The solution will deploy new vSphere distributed switches (8.0.0) and connect the new DPU-enabled hosts.
F. The solution will upgrade all existing vSphere distributed switches to version 8.0.0.
Explanation:
C: Dedicated vSphere Cluster
In vSphere 8.x, a cluster must be consistent in its use of DPUs. To ensure that the latency-sensitive application utilizes the hardware offloading capabilities of the AMD DPUs, these hosts should be placed in a dedicated cluster. This avoids compatibility issues with non-DPU hosts and ensures that Distributed Resource Scheduler (DRS) and High Availability (HA) only move the workload between hardware-compatible nodes.
D: Network Offloads Compatibility
To leverage the DPU, the Network Offloads property must be enabled on the vSphere Distributed Switch. This setting allows the ESXi networking stack to offload services (like UPT, filtering, or encryption) to the DPU hardware, significantly reducing CPU overhead and decreasing latency for the stock trading application.
E: vSphere Distributed Switch (VDS) 8.0.0
vSphere Distributed Services Engine (which manages DPUs) is a new feature that requires VDS version 8.0.0. The existing VDS version 7.0.0 or even 7.0.3 cannot recognize or manage DPU offloading. Deploying a new VDS at version 8.0 specifically for the DPU-enabled hosts is a requirement to enable the "Network Offloads" mode.
Why Other Options are Incorrect
A & F: Version 7.0.3 switches do not support the vSphere Distributed Services Engine. While upgrading existing switches (Option F) is possible, it is often safer in a brownfield environment to deploy a new 8.0 switch specifically for the new DPU hardware to isolate the mission-critical traffic and ensure dedicated configuration.
B: While NTP is a best practice for any vSphere environment, it is not a specific requirement for enabling DPU hardware or resolving the latency/offloading needs described in this scenario.
References
VMware vSphere 8.0 Documentation: Introducing vSphere Distributed Services Engine.
VMware vSphere Advanced Design Guide: Networking Design for Latency-Sensitive Workloads.
An architect is designing a new vSphere solution. The solution will be used to host
workloads that have multiple dependencies. The customer provides the following
information regarding the workloads:
Workload 1: Self-Service Portal
Workload 2: Database
Workload 3: Identity Broker
Workload 4: Reporting Tool
Workload 5: Management Tool
Application A is formed of workloads 1 and 2 and has a dependency on workload 3
Application B is formed of workloads 2 and 4 and has a dependency on workload 3
Application C is formed of workload 5 and has a dependency on workload 4
How should the architect document the vSphere HA requirements to ensure that all of the
applications can be recovered in the event of a host failure while observing the
dependencies?
A. Set vSphere HA to Restart VMs in response to a Host Failure
Set the Restart Priority of workload 3 to High
Set the Restart Priority of workload 4 to Medium
Set the Restart Priority of workloads 1, 2 and 5 to Low
B. Set vSphere HA to Shut Down and Restart VMs in response to a Host Isolation
Set the Restart Priority of workloads 3 and 4 to High
Set the Restart Priority of workload 5 to Medium
Set the Restart Priority of workloads 1 and 2 to Low
C. Set vSphere HA to Restart VMs in response to a Host Failure
Set the Restart Priority of workloads 3 and 4 to High
Set the Restart Priority of workload 5 to Medium
Set the Restart Priority of workloads 1 and 2 to Low
D. Set vSphere HA to Shut Down and Restart VMs in response to a Host Isolation
Set the Restart Priority of workload 3 to High
Set the Restart Priority of workloads 4 and 5 to Medium
Set the Restart Priority of workloads 1 and 2 to Low
Explanation:
The goal is to ensure that application dependencies are respected during recovery after a host failure. vSphere HA uses Restart Priority to control the order in which VMs are restarted. Higher priority VMs start first. Dependencies are:
Application A (Workloads 1 & 2) depends on Workload 3
Application B (Workloads 2 & 4) depends on Workload 3
Application C (Workload 5) depends on Workload 4
From this dependency tree:
Workload 3 is required by Applications A and B — must start first.
Workload 4 is required by Application C and also depends on Workload 3 (since App B includes Workload 4 and depends on 3) — must start after Workload 3.
Workloads 1, 2, and 5 depend on 3 or 4 — start last.
Thus:
High priority: Workloads 3 and 4
Medium priority: Workload 5 (depends on 4)
Low priority: Workloads 1 and 2 (depend on 3)
C. Set vSphere HA to Restart VMs in response to a Host Failure – Correct. This is the standard HA action for host failure. The Restart Priority settings match the dependency analysis exactly: 3 & 4 = High, 5 = Medium, 1 & 2 = Low.
Why other options are incorrect:
A – Incorrect. Workload 4 is set to Medium, but it should be High because Workload 5 depends on it, and Workload 4 itself depends on Workload 3. Medium priority would delay Workload 5 unnecessarily.
B – Incorrect. It uses "Shut Down and Restart VMs in response to a Host Isolation" instead of Host Failure. Host isolation is a different scenario (network partition). The question specifies recovery from a host failure. Also, priority settings are incorrect.
D – Incorrect. Uses the wrong HA response (Host Isolation) and places Workload 4 in Medium instead of High. Workload 4 must be High priority because Workload 5 depends on it and it must follow Workload 3.
Reference
VMware vSphere Availability Guide (vSphere 8.x) – vSphere HA Restart Priority determines startup order based on dependencies. Higher priority VMs are restarted before lower priority ones.
VMware Design Best Practices – For dependent workloads, set the dependency root to High priority, direct dependents to Medium, and leaves to Low.
An architect is tasked with designing a repeatable edge hosting solution using VMware
technologies that can be deployed to existing hotels across the world and operate
independently of other locations.
During interviews with stakeholders, the architect notes the following information:
There are 123 hotels in total.
All hotels have a minimum of two 1 Gbps connections for guest Internet access.
The company operates hotels in four countries: Canada, USA, Cuba and Mexico.
The company is rebranding the hotels located in Mexico.
Which of these is a business factor that will impact this design?
A. The company is rebranding the hotels located in Mexico.
B. The company operates hotels in four countries: Canada, USA, Cuba and Mexico.
C. There are 123 hotels in total
D. All hotels have a minimum of two 1 Gbps connections for guest Internet access.
Explanation:
A business factor is a non‑technical, strategic, or organizational influence that affects design decisions. It often relates to branding, compliance, mergers, acquisitions, or market positioning.
A. The company is rebranding the hotels located in Mexico
– Correct. Rebranding is a business factor because it may impose design requirements such as:
Separate or temporary naming conventions
Different security or access policies during transition
Staged deployment or rollback capabilities
Potential changes to management interfaces or certificate names
Why other options are incorrect
B. The company operates hotels in four countries – Incorrect. This is a geographical or legal boundary that could imply compliance or data sovereignty requirements, but as stated it is simply a factual location list. Without a specific business driver (e.g., legal restrictions in Cuba), it remains a general constraint, not a business factor. However, in this context, rebranding has a direct business impact; country presence alone does not drive a design change unless tied to regulation.
C. There are 123 hotels in total – Incorrect. This is a scale or sizing metric, not a business factor. It influences licensing, number of deployments, and automation effort, but it is a technical/operational constraint.
D. All hotels have two 1 Gbps connections for guest Internet access – Incorrect. This is a technical constraint related to network bandwidth and redundancy. It impacts storage replication, management traffic, or guest network design, but it is not a business factor.
Reference
VMware Design Methodology (VCAP-DCV Design) – Business factors include organizational changes (rebranding, mergers, acquisitions), financial drivers, market conditions, and strategic goals. Technical constraints include bandwidth, hardware counts, and locations.
vSphere Edge Design Guide – Business factors such as rebranding may require separate VLANs, isolated management clusters, or mutable branding elements in guest portals or monitoring tools.
A company is expanding and will be deploying new vSphere environments in multiple new
locations. All environments use datastores backed by multiple storage technologies and vendors.
How can the architect create a design to efficiently and repeatedly distribute existing
company virtual machine (VM) templates to multiple new locations?
A. Use storage array replication tools to replicate the storage volume holding the company VM templates to each remote site.
B. Upload company templates to a cloud provider and download to each new location.
C. Create a published content library and have the new locations subscribe to it.
D. Create a local content library at each site and manually copy only needed templates.
Explanation:
The customer needs an efficient, repeatable way to distribute VM templates across multiple new locations with different storage technologies and vendors. VMware Content Libraries are specifically designed for this use case.
C. Create a published content library and have the new locations subscribe to it – Correct. A published content library acts as a central source of truth for templates, ISOs, and other files. Remote sites can subscribe to it, automatically synchronizing content over HTTP/HTTPS. This works across different storage backends (VMFS, NFS, vSAN, even third‑party array types) because the library abstracts the underlying storage. Subscriptions can be synchronized on‑demand or on a schedule, and sync is incremental, reducing bandwidth usage.
Why other options are incorrect:
A. Use storage array replication tools – Incorrect.
This approach is vendor‑specific and not efficient or repeatable when multiple storage technologies and vendors exist across sites. Array‑based replication requires compatible arrays at both source and destination, which cannot be guaranteed. It also introduces unnecessary storage‑level complexity for template distribution.
B. Upload company templates to a cloud provider and download to each new location – Incorrect.
This adds unnecessary steps, cloud storage costs, and manual intervention. It is not integrated with vSphere, requires external credentials and tools, and does not provide automatic synchronization or versioning across locations.
D. Create a local content library at each site and manually copy only needed templates – Incorrect.
"Manually copy" violates the requirement for efficient and repeatable distribution. Manual processes are error‑prone, time‑consuming, and do not scale to multiple new locations. This option also does not handle updates or version control.
Reference
VMware Content Library Documentation (vSphere 8.x) – Published libraries allow centralized management of templates, with remote subscribed libraries
automatically synchronizing content across sites, independent of underlying storage types.
vSphere Design Guide for Multi‑Site Deployments – Content libraries are the recommended solution for distributing VM templates and ISOs across heterogeneous storage environments.
What is an example of a performance design quality?
A. The solution must scale to meet spikes in CPU demand.
B. The solution must provide 40 physical CPU cores and 20 TB of physical memory.
C. The solution must support applications with a maximum tolerable downtime (MTD) of four hours.
D. The solution must support applications with 1,000 transactions per second (TPS).
Explanation:
Performance design quality refers to how quickly and efficiently the system handles its workload — specifically throughput, latency, and response time under defined conditions.
D. The solution must support applications with 1,000 transactions per second (TPS) – Correct. Transactions per second (TPS) is a direct measure of throughput, which is a core performance metric. It defines how much work the system can process within a given time frame.
Why other options are incorrect:
A. The solution must scale to meet spikes in CPU demand
– Incorrect. This describes scalability or elasticity, which is related to capacity management and availability under variable load. While related to performance, scaling is generally classified as a non-functional technical requirement separate from raw performance metrics like TPS or latency.
B. The solution must provide 40 physical CPU cores and 20 TB of physical memory
– Incorrect. This is a capacity or sizing requirement, not a performance quality. It defines resources available, not how efficiently or quickly those resources are used.
C. The solution must support applications with a maximum tolerable downtime (MTD) of four hours
– Incorrect. This is an availability or recoverability requirement. MTD defines how long the application can be down before business impact occurs, not how fast it runs when operational.
Reference
VMware Design Methodology (VCAP-DCV Design) – Performance qualities include throughput (IOPS, TPS), latency (ms response time), and bandwidth. Scalability, capacity, and availability are separate design pillars.
vSphere Performance Best Practices – TPS is a common application‑level performance metric. CPU core counts and memory sizes are capacity inputs, not performance outputs.
An architect is designing a new vSphere-based solution for a customer.
During a requirements gathering workshop, the following information is provided:
0The solution must have a primary and secondary (isolated) environment
The solution must support orchestration to address application dependencies
The isolated environment must be able to scale on demand in case of a DR scenario
The solution is managed through a single interface
Which solution should the architect include in this design?
A. Site Recovery Manager with dedicated hardware
B. Disaster Recovery with VMware Cloud on AW
C. vSAN stretched cluster
D. A dedicated fault domain
Explanation:
The customer requires four specific capabilities:
Primary and secondary (isolated) environment – A true disaster recovery architecture with separate sites
Support orchestration to address application dependencies – Automated, dependency-aware failover workflows
Isolated environment scales on demand in a DR scenario – Recovery capacity can be activated only when needed
Managed through a single interface – Unified management plane
A. Site Recovery Manager with dedicated hardware – Correct. VMware Site Recovery Manager (SRM) is specifically designed for these requirements :
Provides primary/secondary site architecture with isolation between environments
Includes orchestration with dependency-aware recovery plans that respect application startup order (e.g., database before application servers)
Dedicated hardware at the recovery site can be powered off or scaled independently; SRM supports on-demand capacity activation
Fully integrated into vSphere Client as a plugin, providing single-interface management
Why other options are incorrect:
B. Disaster Recovery with VMware Cloud on AWS
– Incorrect. While VMware Cloud Disaster Recovery (VCDR) supports on-demand scaling of the recovery SDDC , it requires a cloud subscription and does not use "dedicated hardware" as specified in option A. The question asks for an on-premises solution based on the phrasing "dedicated hardware." Additionally, VCDR's management dashboard is SaaS-based, not fully integrated into the same single vSphere interface as SRM .
C. vSAN stretched cluster
– Incorrect. A vSAN stretched cluster provides active-active synchronous replication and automatic failover, but explains it has critical limitations:
Requires low latency (typically <5ms RTT) and short distances (under 100km)
Does not provide an "isolated environment" – both sites are part of the same logical cluster
Does not support complex orchestration with application dependencies; recovery is automatic and not scriptable
Both sites remain active simultaneously, contradicting the "primary and secondary (isolated)" requirement
D. A dedicated fault domain
– Incorrect. Fault domains are a vSAN feature that groups hosts by physical location (e.g., racks) to tolerate entire rack failures . Fault domains operate within a single cluster and do not provide:
Secondary isolated environment for disaster recovery
Orchestration capabilities for application dependencies
On-demand scaling of recovery capacity
Management through a single interface for two separate sites
Fault domains address availability within a data center, not disaster recovery between sites.
Reference
VMware Site Recovery Manager Documentation – SRM provides automated disaster recovery orchestration, dependency-aware recovery plans, and centralized management through vSphere Client
SRM vs. vSAN Stretched Cluster Comparison – Stretched clusters require low latency and provide automatic failover but lack orchestration and isolation; SRM supports longer distances and complex recovery workflows
| Page 2 out of 12 Pages |
| 1234 |
| 3V0-21.23 Practice Test Home |