nerdexam
Broadcom-VMware

2V0-622 · 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 is unavailable for Virtual SAN when it is already committed to another vSphere feature such as an existing VMFS datastore or the vFlash Read Cache.

Section 3 – Configure and Administer vSphere 6.5 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

(38 responses)
  • A
    79% (30)
  • C
    8% (3)
  • D
    13% (5)

Why each option

A local flash device is unavailable for Virtual SAN when it is already committed to another vSphere feature such as an existing VMFS datastore or the vFlash Read Cache.

AIt has a VMFS datastore present.Correct

If a flash device hosts an existing VMFS datastore, ESXi treats it as in use and will not allow Virtual SAN to claim it; the datastore must be removed and the device wiped before it can join a vSAN disk group.

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

A flash device configured for the vFlash Read Cache feature is already allocated to that service and cannot simultaneously serve as a Virtual SAN caching or capacity tier device.

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

While very small flash devices may be impractical for vSAN, the absence of a minimum capacity threshold does not make a device categorically unavailable the way an already-in-use device is blocked.

DIt does not have any partitions created.

Virtual SAN claims and partitions raw devices itself during disk group configuration, so the absence of pre-existing partitions is the expected state and does not make a device unavailable.

Concept tested: Virtual SAN flash device eligibility and conflicts

Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan-planning.doc/GUID-18E96C56-CC75-4B27-A7D2-3D0ED91E82B1.html

Topics

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

Community Discussion

No community discussion yet for this question.

Full 2V0-622 Practice