vSphere Lifecycle Management →mediumMultiple ChoiceObjective-mapped

VCP-DCV vSphere Lifecycle Management Practice Question

Exhibit

Refer to the exhibit.

Exhibit: vSphere Lifecycle Manager Hardware Compatibility Check Output
{
  "image": {
    "esx_version": "8.0.0",
    "vendor": "VMware"
  },
  "hosts": [
    {
      "host_name": "esx-01.vmware.com",
      "status": "COMPATIBLE",
      "firmware_required": false
    },
    {
      "host_name": "esx-02.vmware.com",
      "status": "INCOMPATIBLE",
      "firmware_required": true,
      "reason": "Network card driver version 1.2.3 is not in the image."
    }
  ]
}

An administrator sees the above output from a vLCM pre-check prior to remediation. The administrator wants to remediate all hosts in the cluster with the image. What should the administrator do first?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Add the required network card driver component to the image.

The vLCM pre-check output indicates that the host esx-02 is incompatible due to a missing network card driver. To remediate all hosts with the image, the administrator must add the required driver component to the image. Option A is incorrect because removing the host does not address the missing driver; it only avoids the issue. Option B is incorrect because the firmware requirement is not the problem. Option D is incorrect because the host does not need a firmware update, and rebooting will not add the missing driver.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Remove the incompatible host from the cluster.
Why it's wrong here
Unnecessary; the host can be fixed.
✗
Change the image firmware requirement to false.
Why it's wrong here
Firmware requirement is not the cause of incompatibility.
✓
Add the required network card driver component to the image.
Why this is correct
Adding the driver to the image will make the host compatible.
✗
Reboot the host esx-02 to apply a firmware update.
Why it's wrong here
The issue is a missing driver, not firmware.

Go deeper

VCP-DCV vSphere Lifecycle Management Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question