An administrator has been tasked with deploying a new VMware Cloud Foundation (VCF) environment that includes a Management Domain and two workload domains. Compliance regulations require that production and non-production workloads reside in separate failure domains, with the production workload environment using low-latency block storage and the non-production environment relying on high-capacity file-based storage.
Which combination of supported non-vSAN storage solutions should the administrator recommend to meet these requirements?

• A. Management domain on local VMFS datastores, production workload domain on iSCSI, and non- production workload domain on NFS v3
• B. Management domain on VMFS over Fibre Channel, production workload domain on VMFS over NVMe/FC, and non-production workload domain on NFS v4.1
• C. Management domain on vSAN ESA, production workload domain on vSAN HCI Mesh, and non- production workload domain on vSAN File Services
• D. Management domain on vVols over NFS, production workload domain on VMFS over iSCSI, and non- production workload domain on SMB

解説: (CertJuken メンバーにのみ表示されます)

Select the storage capabilities supported for use with persistent volumes in the VMware Kubernetes Service (VKS) in VMware Cloud Foundation (VCF).
Drag and drop the five supported capabilities from the vSphere Storage Capabilities list on the left and place them into the Supported Storage Capabilities list on the right in any order. (Choose five.)

Explanation:
Full Clone from Volume Snapshot
4kn Support
Online Volume Expansion
Offline Volume Expansion
Static Persistent Volume
VMware Kubernetes Service persistent volumes use vSphere storage integrations such as CNS and pvCSI to provide Kubernetes storage services backed by vSphere datastores and storage policies. The supported persistent volume capabilities include Static Persistent Volume, which allows pre-existing storage to be consumed by Kubernetes workloads; Offline Volume Expansion and Online Volume Expansion, which allow persistent volumes to be resized depending on workload and filesystem state; Full Clone from Volume Snapshot, which enables a new volume to be created from an existing snapshot; and 4kn Support, which supports modern 4K native storage devices where the underlying stack supports them. Storage vMotion with attached Persistent Volumes is not supported because moving an attached Kubernetes persistent volume while it is in active use can break attachment and consistency assumptions. Storage DRS is also not a supported persistent volume capability in this VKS context. Flash Read Cache is not part of the supported VKS persistent-volume capability set. Reference topics: VMware Kubernetes Service Storage, CNS, pvCSI, Persistent Volume Capabilities, Volume Expansion, Volume Snapshot Clone.

A VMware Cloud Foundation (VCF) environment runs mixed workloads (Online Transaction Processing (OLTP) + analytics), with the following vSAN configuration:
* 8 hosts (all-flash), ESA enabled.
* Each host: 2 x 3.2 TB NVMe devices.
* Compression is Enabled.
* Checksum is Enabled.
* Storage Policy: FTT=1 (RAID-5/6), Failures to Tolerate = 1 and Object Space Reservation = 0%.
During peak OLTP load, vSAN resync I/O and backend congestion increase latency despite having sufficient network bandwidth.
What is the direct action the administrator can perform to improve write performance while maintaining data protection compliance?

• A. Disable checksums to reduce metadata writes on NVMe devices.
• B. Increase object reservation to 100% to pre-allocate capacity and prevent log-structuring overhead.
• C. Increase FTT to 2 with RAID-5/6 and disable compression.
• D. Convert policy to RAID-1 (FTT=1) for latency-sensitive workloads while keeping compression enabled.

解説: (CertJuken メンバーにのみ表示されます)

An administrator is working on a VMware Cloud Foundation (VCF) Workload Domain that was configured to use vSAN for principal storage. The administrator wishes to create and configure a datastore cluster to host tenant VMs using that vSAN backed storage across multiple clusters, mixed OSA and ESA, in the domain.
What should the administrator consider?

• A. A datastore cluster can combine different storage types, such as vSAN, FC, and NFS datastores, as long as they are in the same vCenter; Storage DRS will treat them uniformly.
• B. When using vSAN as the underlying datastore, an administrator must create the datastore cluster via vCenter APIs, include the vSAN datastore(s) in it, enable Storage DRS, and ensure the VM Storage Policies reference the appropriate vSAN-capable datastore.
• C. vSAN OSA and ESA based datastores must be added to a datastore cluster tag and then selected as part of a single storage policy.
• D. When using vSAN datastores, Datastore Clusters are not supported. Each VM must be placed manually on the vSAN datastore.

To respect the application criticality, an administrator is configuring the Recovery Priority of protected Virtual Machines (VMs).
What does VMware Live Site Recovery leverage to mark a recovery priority as completed?

• A. Virtual machines are successfully recovered.
• B. VMware Tools heartbeat are present.
• C. Virtual machines are registered.
• D. Virtual machines are powered on.
• E. Final replication is complete.

解説: (CertJuken メンバーにのみ表示されます)