nerdexam
Broadcom-VMware

2V0-622D · Question #88

An administrator needs to configure a storage solution for a vSphere 6.x implementation with these characteristics: - Snapshot support - vMotion Capability - Clustering across multiple ESXi hosts - Da

The correct answer is C. A Virtual Mode Raw Device Mapped LUN. Virtual Mode RDM is the only option that satisfies all five requirements simultaneously, including snapshot support, vMotion, guest OS clustering for a database workload, and vFlash Read Cache.

Section 3 – Configure and Administer vSphere 6.5 Storage

Question

An administrator needs to configure a storage solution for a vSphere 6.x implementation with these characteristics:

  • Snapshot support
  • vMotion Capability
  • Clustering across multiple ESXi hosts
  • Database application with high transaction count
  • vFlash Read Cache

Which solution meets all of the stated requirements?

Options

  • AA vmdk located on a Shared VMFS datastore
  • BA Physical Mode Raw Device Mapped LUN
  • CA Virtual Mode Raw Device Mapped LUN
  • DA Virtual SAN-based vmdk

How the community answered

(47 responses)
  • A
    19% (9)
  • B
    9% (4)
  • C
    68% (32)
  • D
    4% (2)

Why each option

Virtual Mode RDM is the only option that satisfies all five requirements simultaneously, including snapshot support, vMotion, guest OS clustering for a database workload, and vFlash Read Cache.

AA vmdk located on a Shared VMFS datastore

A VMFS-based vmdk does not natively support shared-disk guest OS clustering (e.g., MSCS) across multiple ESXi hosts without a multi-writer flag, which introduces its own significant limitations.

BA Physical Mode Raw Device Mapped LUN

Physical Mode RDM bypasses hypervisor abstraction entirely, which means snapshots and vFlash Read Cache are not supported, failing two of the stated requirements.

CA Virtual Mode Raw Device Mapped LUNCorrect

Virtual Mode RDM presents the LUN to the guest OS through a virtual SCSI controller while the hypervisor retains management control, enabling snapshot support, vMotion compatibility, shared-disk guest OS clustering (such as MSCS across ESXi hosts), and vFlash Read Cache - covering every requirement listed in the scenario.

DA Virtual SAN-based vmdk

Virtual SAN uses its own distributed caching layer that is architecturally incompatible with vFlash Read Cache, so it cannot satisfy all stated requirements.

Concept tested: Virtual Mode RDM capabilities versus other vSphere storage types

Source: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.storage.doc/GUID-9E0F57B3-B9B0-4F61-9A56-F52E28EB2F65.html

Topics

#RDM#virtual mode RDM#vFlash Read Cache#storage requirements

Community Discussion

No community discussion yet for this question.

Full 2V0-622D Practice