VMware
Advanced VMware Cloud Foundation 9.0 Storage (3V0-23.25) practice questions
- Questions
- 53
- Exam length
- 135 min
- Passing score
- 300
- Instant feedback per question
- Explanation for every option
- Free, no signup
Exam overview 3V0-23.25
Choosing between an ESA storage policy that sets IOPS limits for a noisy tenant and one that simply reserves space for a latency-sensitive database is the kind of trade-off 3V0-23.25, the Advanced VMware Cloud Foundation 9.0 Storage exam, expects you to reason through rather than recite. Passing leads to the VMware Certified Advanced Professional – VMware Cloud Foundation 9.0 Storage credential (VCAP-Storage), delivered by Broadcom through Pearson VUE. The paper carries 60 questions in 135 minutes and requires 300 on a 100-500 scaled score, so the threshold is not a percentage of correct answers. Item formats span multiple choice, multiple selection, drag and drop, matching, build-list, sequencing, point-and-click and hot-area.
Storage specialists and virtualization engineers with roughly 12-18 months of hands-on vSAN time — Express Storage Architecture included — are the profile Broadcom describes for this VCAP. Preparation that transfers to the exam means building and resizing vSAN clusters, moving a workload from one striping and IOPS profile to another, deploying a stretched cluster with its witness and checking workload locality, then walking through Data-at-Rest Encryption and key management while noticing exactly where the OSA and ESA flows part ways. File Services for NFS and SMB and the iSCSI Target Service for block access deserve their own task checklists so protocol-level details do not blur together.
The storage guide spreads objectives across five sections — IT architectures, technologies and standards; VCF products and solutions; plan and design; install, configure and administrate; and troubleshoot and optimize — without publishing per-section weights, and the hard questions cluster where architectures diverge: OSA versus ESA, principal versus supplemental storage in a workload domain, the role of storage in a Supervisor context, and recovery plans built on snapshots, replication and protection schedules.
The practice bank here mirrors that decision-making. A question may hand you a resiliency requirement and ask which cluster arrangement and locality behavior satisfy it; the explanation then walks the reasoning and the distractors — why witness placement matters, why an OSA encryption step does not map onto ESA. Each item carries a detailed answer explanation, and running the set as a timed rehearsal gets you used to the mix of interactive formats before test day.
Sample questions 6 of 53 shown
-
Q1
An architect is designing a vSAN Original Storage Architecture (OSA) cluster for a VMware Cloud Foundation (VCF) Management Domain. The following details were made available:- 12 hosts, each host with: 3 x 800 GB NVMe (cache) and 12 x 3.84 TB SAS SSD (capacity).
- Planned configuration: 3 disk groups per host (1 NVMe + 4 SSD each).
- Storage policy: FTT = 2 (RAID-1), Checksum. Deduplication and Compression are Enabled.
- Network: 25 GbE dedicated vSAN network fabric, properly configured for jumbo frames.
In vSAN OSA, deduplication and compression are enabled at the cluster level but applied on a per-disk-group basis. Deduplication occurs inline when data is written back from the cache tier to the capacity tier, and compression is applied as data moves from cache to capacity. During resynchronization, vSAN must read, rewrite, deduplicate, compress, and destage data through this disk-group architecture, and that additional processing can extend resync duration even when the physical network and hardware are healthy. "Ensure Accessibility" does not trigger a full component migration; it evacuates only enough data to maintain object accessibility and may leave objects temporarily noncompliant. The number of disk groups is not inherently the cause, and NVMe cache devices are not automatically limiting throughput. The key differentiator in the scenario is that deduplication and compression are enabled while heavy resync activity is occurring. -
Q2
An architect is designing a vSAN storage solution for a remote site. The following requirements have been given:- There is enough rack space for two hosts, each with 36 CPU cores and 256 GB of RAM.
- The physical network at the remote site supports 10 Gb maximum.
- The network connecting the remote site to corporate has 10 Gb of bandwidth with an average RTT of 25 ms.
- High availability is expected for all the Virtual Machines running at the remote site.
- The solution must provide additional storage to 16 graphic design Windows based workstations.
- Active Directory is configured and available at the remote site.
- The graphic design application requires native NTFS permissions.
vSAN File Share SMB services are required because the storage must be consumed by Windows workstations and the application requires native NTFS permissions. SMB is the Windows-native file sharing protocol and integrates with Active Directory authentication. vSAN File Service supports SMB file shares, and Windows clients joined to the Active Directory domain can access those shares using the SMB path. vSAN File Service also supports Microsoft Management Console for SMB shares, including ACL management, open file viewing, active sessions, and client connection management. vSAN File Service supports two-node vSAN configurations, which matches the remote-site rack-space constraint of two hosts with a witness deployed remotely. NFSv3 does not provide native NTFS permissions for Windows clients, and vSAN Storage Cluster / HCI Mesh address capacity sharing, not SMB file access. -
Q3
An administrator is tasked with deploying a VMware Cloud Foundation (VCF) Workload Domain that meets the following requirements:- vSAN ESA as principal storage
- RAID-6 with FTT=2
- Support for Storage Traffic Separation
- Four ESX hosts, each host contains:
- * 24 CPU cores
- * 96 GB memory
- * Two 25GbE network NICs
- * 12 NVMe devices 4 TB each, connected to a single SATA/SAS/NVMe Tri-mode controller
RAID-6 (FTT=2) erasure coding creates 4 data + 2 parity components, so a minimum of six hosts is required to place components and survive failures. Storage Traffic Separation requires dedicated network paths for vSAN, vMotion, and management traffic, which needs a minimum of four 25 GbE NICs per host (two NICs cannot provide the required separation). vSAN ESA has a minimum host memory requirement of 128 GB per host for supported configurations. Finally, vSAN ESA requires storage devices attached to dedicated local NVMe controllers; a Tri-mode (SATA/SAS/NVMe) controller is not supported for ESA storage pools, so it must be replaced with a dedicated NVMe controller. 24 CPU cores already satisfies the ESA CPU minimum, and ESA does not use separate cache/capacity tiers so the tri-mode controller cannot simply be doubled. -
Q4
An architect is presented with the following requirements for the storage solution in a VMware Cloud Foundation (VCF) Workload Domain. The solution must:- Allow for rapid recovery in case of an availability zone failure.
- Provide an extremely high amount of IOPS to all applications.
- Allow for additional storage to be added as application needs grow.
- Provide the lowest latency possible for configured applications.
- Provide recovery in case of datastore failure.
- Encrypt data in transit and at rest.
A vSAN Stretched Cluster provides rapid recovery from an availability zone failure by synchronously mirroring data across two sites with a witness for quorum. A vSAN Storage Cluster (vSAN Max) is a disaggregated storage cluster based on vSAN ESA that provides an extremely high amount of IOPS, allows storage capacity to grow independently of compute, and delivers the lowest possible latency for applications. Together these two technologies address the availability zone, IOPS, scalability, latency, and datastore failure recovery requirements, and vSAN encryption covers data in transit and at rest. File Service, Data Protection Service, and iSCSI Target Service do not address the availability zone failure or massive IOPS scaling requirements. -
Q5
An administrator reports that after rebooting one host in a vSAN cluster configured with Data-at-Rest Encryption using an external Key Management Server (KMS), the host shows all vSAN disk groups as unmounted. The KMS is online and reachable from all hosts. In vCenter, the host displays the following event: "Failed to retrieve encryption key from KMS." Key ID: All other hosts in the cluster remain healthy and show "Encryption: Enabled." Why did the encryption key retrieval fail for this host?Because the KMS is online and reachable and all other hosts in the cluster can retrieve keys successfully, the problem is isolated to the trust relationship between this specific host and the KMS. vSAN encryption requires each ESX host to establish a trusted connection (certificate exchange) with the key provider. If the host's certificate or KMS trust entry is invalid or missing, the host cannot retrieve the Key Encryption Key and consequently cannot unlock the Data Encryption Keys, leaving the disk groups unmounted. A Deep Rekey is not required and would not be initiated while disks are inaccessible, restarting vCenter does not refresh per-host KMS trust, and a TPM is not used to unlock vSAN data encryption keys in a standard KMS configuration. -
Q6
A six-node vSAN ESA cluster contains multiple Virtual Machines (VMs), and a vSAN storage policy with the rule "Failures to tolerate" set to "1 failure - RAID-5 (Erasure Coding)" is assigned. A vSAN administrator has changed the rule in the assigned policy to "2 failures - RAID-6 (Erasure Coding)." What is the result of this change?Editing a storage policy does not automatically reconfigure the objects that reference it. The VMs continue to run with the previously applied (RAID-5) configuration until the administrator explicitly reapplies the policy to the VMs or datastores. When the policy is reapplied, vSAN then performs the reconfiguration to RAID-6. vSAN does not serially apply policy edits on its own, does not queue changes on a timer, and the change is valid for a six-node ESA cluster (RAID-6 requires at least five to six hosts), so it is not rejected.
Reader reviews 30 ratings
-
I was skeptical about paying for exam prep, but the 3V0-23.25 bank saved me. Covered everything I needed.
-
Bought the 3V0-23.25 pack last month and honestly the detailed explanations are where this really shines.
-
Solid VMware prep material. The 3V0-23.25 questions are well-written and the answer rationales are thorough.
-
I work full time and study at night. The 3V0-23.25 question bank allowed me to learn efficiently without wasting precious time.
-
I was pleasantly surprised by the quality of the 3V0-23.25 questions for the price. Comparable to much more expensive prep courses.
-
I passed 3V0-23.25 on my first try thanks to these practice questions. The unlimited retakes were essential for building confidence.
Frequently asked questions
How hard is 3V0-23.25 next to the VCP tier?
It sits a full level above VCP: a VCAP paper whose objectives span every storage section, from differentiating OSA and ESA through designing and sizing a vSAN solution, deploying stretched and 2-node clusters, configuring encryption and the iSCSI Target Service, and troubleshooting vSAN and non-vSAN storage. Candidates strong in one area usually find the breadth is what bites. Timed practice against the full objective set is the honest readiness check.
What should a vSAN storage policy question expect you to weigh?
The ESA policy settings — disk striping, IOPS limits, space reservations — are tested as consequences, not labels: what each setting controls, how the settings interact with a workload's performance and capacity behavior, and how to spot a policy that cannot deliver the requirement it was given. Our scenarios pair each requirement with the policy decision behind it, so you rehearse the judgment the exam actually asks for.
Where do the OSA and ESA encryption flows actually differ?
In the administrative sequence and its dependencies: the exam guide expects you to implement Data-at-Rest Encryption and perform key-management tasks while distinguishing how the flows run on each architecture, not just to define encryption. One architecture's step order does not transplant to the other. Working both flows side by side in practice makes the divergence visible instead of assumed.
What happens if the first attempt falls short of 300?
300 is a point on Broadcom's 100-500 scaled scale — not 300 correct answers and not a published percentage — and VMware policy applies a waiting period between attempts, with the fee payable again for the rebooking. Treat a near-miss scaled score as a domain map, not a coin-flip signal: the score report and practice results point at the objectives worth another pass before you rebook.
Why rehearse the bank as a full mock exam first?
Because pacing is part of the challenge: 60 items in 135 minutes leaves barely two minutes each once interactive formats enter the mix. A full mock exam run at that item count and window exposes which formats slow you down, and reviewing every miss afterward converts the run into a revision list. The bank's detailed explanations are what make the rehearsal worth the clock.
What do the vSAN explanations add after a wrong pick?
Each explanation names the mechanism behind the correct choice and the reason each distractor fails — why a witness belongs in a specific failure domain, why a snapshot does not substitute for a protection schedule. That ties every wrong answer to the objective it came from, so your revision lands on the concepts that carry marks and your preparation works toward passing rather than guessing again.