nerdexam
Broadcom-VMware

2V0-621 · Question #135

What are two reasons why a local flash device would be unavailable for use with Virtual SAN? (Choose two.)

The correct answer is A. It has a VMFS datastore present. B. It is in use by the vFlash Read Cache feature. A local flash device cannot be contributed to Virtual SAN if it is already claimed by a VMFS datastore or actively used by the vFlash Read Cache feature, because VSAN requires unclaimed, unformatted capacity devices.

Section 3 – Configure and Administer vSphere 6.x Storage

Question

What are two reasons why a local flash device would be unavailable for use with Virtual SAN? (Choose two.)

Options

  • AIt has a VMFS datastore present.
  • BIt is in use by the vFlash Read Cache feature.
  • CIt is smaller than the minimum capacity required for Virtual SAN usage.
  • DIt does not have any partitions created.

How the community answered

(31 responses)
  • A
    74% (23)
  • C
    16% (5)
  • D
    10% (3)

Why each option

A local flash device cannot be contributed to Virtual SAN if it is already claimed by a VMFS datastore or actively used by the vFlash Read Cache feature, because VSAN requires unclaimed, unformatted capacity devices.

AIt has a VMFS datastore present.Correct

Virtual SAN requires that flash devices be in an unclaimed state with no existing partitions or file systems; the presence of a VMFS datastore means the device is already partitioned and claimed by the storage stack, making it unavailable for VSAN disk groups.

BIt is in use by the vFlash Read Cache feature.Correct

The vFlash Read Cache feature exclusively claims a flash device at the host level to use as a read cache tier; a device already claimed by vFlash cannot simultaneously be contributed to a VSAN disk group.

CIt is smaller than the minimum capacity required for Virtual SAN usage.

While VSAN has minimum capacity recommendations, a device being below a soft threshold does not automatically make it 'unavailable' in the UI; the device would still appear as a candidate and the correct answers involve claimed/in-use states.

DIt does not have any partitions created.

The absence of partitions is actually the desired state for a VSAN candidate disk; an unpartitioned device is eligible to be claimed by VSAN, so lacking partitions does not make it unavailable.

Concept tested: Virtual SAN flash device eligibility requirements

Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan.doc/GUID-C9D07B99-2B74-4E5E-B14E-75E8CC6C7DC6.html

Topics

#Virtual SAN#flash device#vFlash Read Cache#VMFS datastore conflict

Community Discussion

No community discussion yet for this question.

Full 2V0-621 Practice