nerdexam
Broadcom-VMware

2V0-622D · Question #295

An administrator has a large boot from SAN cluster and wants to ensure consistent configuration by using host profiles. What special considerations are required for boot from SAN hosts?

The correct answer is C. Verify that the boot LUN is correctly identified as the boot device in the host profile.. Boot from SAN hosts require that the host profile correctly identifies the SAN LUN as the designated boot device to prevent misconfiguration when the profile is applied cluster-wide.

Section 3 – Configure and Administer vSphere 6.5 Storage

Question

An administrator has a large boot from SAN cluster and wants to ensure consistent configuration by using host profiles. What special considerations are required for boot from SAN hosts?

Options

  • AHost profiles are incompatible with boot from SAN hosts.
  • BChange the "Device is shared clusterwide" setting to "false" in the host profile.
  • CVerify that the boot LUN is correctly identified as the boot device in the host profile.
  • DThe boot from SAN device must report as a local device.

How the community answered

(33 responses)
  • A
    3% (1)
  • B
    6% (2)
  • C
    76% (25)
  • D
    15% (5)

Why each option

Boot from SAN hosts require that the host profile correctly identifies the SAN LUN as the designated boot device to prevent misconfiguration when the profile is applied cluster-wide.

AHost profiles are incompatible with boot from SAN hosts.

Host profiles are fully supported and commonly used with boot from SAN environments; they are not incompatible.

BChange the "Device is shared clusterwide" setting to "false" in the host profile.

Setting 'Device is shared clusterwide' to false would be incorrect for a SAN LUN used in a cluster, as it is a shared resource and should remain marked as shared clusterwide.

CVerify that the boot LUN is correctly identified as the boot device in the host profile.Correct

When a host profile is captured from a boot from SAN host, it records storage device assignments including which device is the boot target. Verifying that the boot LUN is correctly flagged as the boot device in the profile is critical - if misidentified, applying the profile to other hosts can result in incorrect boot device assignments and potential boot failures across the cluster.

DThe boot from SAN device must report as a local device.

Boot from SAN devices are remote SAN-attached LUNs, not local devices; no requirement exists for them to report as local for host profile compatibility.

Concept tested: Host profile boot device identification for boot from SAN

Source: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-host-profiles/GUID-59B5A48F-E5E7-4C1A-88E1-5DA6B6BAE80F.html

Topics

#boot from SAN#host profiles#boot device#SAN configuration

Community Discussion

No community discussion yet for this question.

Full 2V0-622D Practice