VendorsExamsEnterprise
Support
Request an ExamContact UsFAQ

Advanced VMware Cloud Foundation 9.0 Storage Free Sample Questions

Description

Covers HCI versus traditional storage architecture, vSAN OSA and ESA components, designing and sizing vSAN solutions, deploying vSAN and stretched clusters, and troubleshooting vSAN storage.

12 free sample questions150 in the full practice test

Try simulator

3V0-23.25 Sample Questions

  1. Question 1

    Intermediate

    IT Architectures, Technologies, Standards · Differentiate Between Supported Storage Types

    An architect is designing a greenfield VMware Cloud Foundation 9.0 workload domain for a financial institution. The institution has a strict requirement to use their existing high-performance Fibre Channel All-Flash Arrays for the principal storage of the new domain due to regulatory data sanitization standards that their current arrays already meet. Which design decision aligns with VCF 9.0 capabilities?

    Answer and explanation

    Correct answer: B

    In VCF 9.0, Fibre Channel (VMFS on FC) is a supported principal storage model for the management domain and for VI workload domains (Table 23). Hosts are commissioned with the VMFS on FC storage type, the VMFS datastore must already be created and mounted on all hosts before commissioning, and VMFS on FC is then selected on the Storage page of the workload domain creation workflow (run from VCF Operations; the SDDC Manager UI is deprecated in 9.0). Using vSAN as principal with FC only as supplemental does not meet the requirement, and HCI Mesh only shares vSAN datastores.

  2. Question 2

    Advanced

    VMware Cloud Foundation (VCF) Products and Solutions · Differentiate Between vSAN OSA and vSAN ESA

    A storage administrator is evaluating the move from vSAN Original Storage Architecture (OSA) to vSAN Express Storage Architecture (ESA) for a new VCF 9.0 deployment. The environment requires the highest possible storage efficiency for VDI workloads that have high deduplication potential. Which architectural difference in ESA 9.0 directly benefits this scenario compared to OSA?

    Answer and explanation

    Correct answer: D

    vSAN ESA global deduplication (available as limited release in 9.0 P01; generally available in VCF 9.1) uses a cluster-wide deduplication domain at 4 KB granularity and runs as a post-process background task, so duplicate blocks across all hosts in the cluster - common in VDI - are found. vSAN OSA deduplicates only within each disk group. ESA deduplication is not done after encryption at the bottom of the stack, ESA does not support HDDs, and ESA has no cache tier.

  3. Question 3

    Intermediate

    Plan and Design the VMware Solution · Design a vSAN Storage Solution for VCF

    A consultant is designing a vSAN Stretched Cluster for a VCF 9.0 environment spanning two datacenters. The customer requires a solution that can tolerate a complete site failure while maintaining the lowest possible storage overhead. Which vSAN storage policy configuration meets these requirements?

    flowchart LR A["Stretched Cluster Site A + Site B"] --> B{Choose Resilience Strategy} B -->|Maximum Efficiency| C["Dual Site Mirroring RAID-1 across sites + Local RAID-5 (~2.66x OSA / 2.5-3x ESA total)"] B -->|Higher Overhead| D["Dual Site Mirroring RAID-1 across sites + Local RAID-1 (4x total)"] C --> E["Recommended for Cost Optimization"] D --> F["Simpler but Expensive"]
    Answer and explanation

    Correct answer: B

    Tolerating a complete site failure requires the Site disaster tolerance rule 'Dual site mirroring' (Site mirroring - stretched cluster), which keeps a full copy in each data site. The secondary Failures to tolerate rule then protects data within each site; '1 failure - RAID-5' stores that local copy as an erasure code, consuming about 2.66x the VM size on vSAN OSA (4 hosts per site) or 3x/2.5x on vSAN ESA, versus 4x for dual site mirroring with local RAID-1. 'None - keep data on Preferred' does not survive loss of that site, and 'No data redundancy' gives no local resilience.

  4. Question 4

    Intermediate

    Install, Configure, Administrate the VMware Solution · Configure vSAN Encryption

    An administrator needs to enable data-at-rest encryption on a new vSAN ESA cluster within VCF 9.0. The organization has strict security policies requiring the separation of key management from the virtualization platform. Which component must be configured before enabling vSAN data-at-rest encryption on the cluster?

    Answer and explanation

    Correct answer: C

    To meet the requirement of separating key management from the virtualization platform, the administrator must configure a Standard Key Provider that establishes a trust relationship with an external Key Management Server (KMS) compliant with KMIP. The Native Key Provider (NKP) runs within vCenter and does not meet the 'separation' requirement.

  5. Question 5

    Intermediate

    Install, Configure, Administrate the VMware Solution · Deploy a VCF Workload Domain cluster with supported (non-vSAN) Storage

    During the deployment of a new VCF 9.0 Workload Domain, an architect selects NFSv3 as the principal storage. Which prerequisite must be met in VCF for this configuration to succeed?

    Answer and explanation

    Correct answer: C

    Network pools automatically assign static IP addresses to vSAN, NFS, iSCSI and vMotion VMkernel ports. For NFS principal storage the network pool must contain the vMotion and NFS networks, and VCF docs state that to use external NFS or VMFS on FC storage you must create a new network pool. The network pool must exist and support the selected storage type before host commissioning. NFS v3 requires root access to the export (no_root_squash), and jumbo frames are recommended rather than prohibited.

  6. Question 6

    Advanced

    Troubleshoot and Optimize the VMware Solution · Troubleshoot and Resolve Issues with VMware vSAN Storage

    A VCF administrator is troubleshooting a vSAN ESA cluster that is reporting high latency. The cluster uses RAID-6 storage policies. Upon inspection, the administrator notices that the 'Congestion' metric in the vSAN Performance Service is consistently high. What is the most likely cause of this behavior in an ESA architecture?

    Answer and explanation

    Correct answer: A

    vSAN congestion is a backpressure signal from the local storage layer. The VOB esx.problem.vsan.lsom.congestionthreshold is defined as 'vSAN device memory or SSD congestion', and esxcli vsan debug disk list reports Congestion Health per device. Sustained high congestion therefore means the backend devices, or the resources that front them, cannot absorb the incoming write rate, so vSAN slows guest I/O. Network problems show up instead as network latency or packet loss in the performance and network health views, which the I/O Trip Analyzer can separate by layer.

Register free for 6 more questions

Or unlock all 150 3V0-23.25 questions with explanations, timed mode and flashcards.

Related practice tests

All VMware practice exams