vSphere Lifecycle Management →mediumMultiple Choice

VCP-DCV vSphere Lifecycle Management Practice Question

Exhibit

{
  "host": "esxi-02.vsphere.local",
  "compliance_status": "non-compliant",
  "differences": [
    {
      "component": "ESXi",
      "desired_version": "8.0.0-123456",
      "current_version": "7.0.0-123456"
    }
  ]
}

Refer to the exhibit. What is the cause of the non-compliance?

⚠ Common exam trap

The trap is conflating firmware compliance with ESXi version compliance — candidates see 'non-compliant' and pick firmware, but the exhibit's version mismatch specifically points to an older ESXi build.

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

✓

The host is running an older ESXi version than desired

In vSphere Lifecycle Manager (vLCM) image-based compliance, a host is marked non-compliant when its installed ESXi version does not match the version specified in the desired image. The exhibit shows a version mismatch between the host's current ESXi build and the target image, which is the direct cause of non-compliance. Firmware, scan failures, and hardware support are separate checks that would produce different error indicators.

Answer analysis

Option-by-option breakdown

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

✗
The host has an outdated firmware version
Why it's wrong here
Firmware version is not the attribute the exhibit flags as non-compliant; the displayed check concerns a different host property. Outdated firmware is tempting because it commonly triggers vSphere Lifecycle Manager drift, but only when the baseline specifically includes firmware components.
✗
The compliance scan failed
Why it's wrong here
A failed scan is a symptom, not the cause shown in the exhibit; the displayed compliance result reflects an assessed host state rather than scan execution. This distracts when scan scheduling or connectivity issues genuinely prevent results, but here the host's own attributes drive the non-compliance.
✗
The host's hardware is not supported
Why it's wrong here
Unsupported hardware would appear as an incompatibility against the vSphere Compatibility Guide, not as the specific compliance failure shown. It is tempting because unsupported devices genuinely block cluster remediation, yet the exhibit's flagged attribute is unrelated to hardware support status.
✓
The host is running an older ESXi version than desired
Why this is correct
Compliance against a desired-state baseline fails when the host's actual ESXi build does not match the specified target version. Running an older ESXi version than the image requires is precisely the drift that marks the host non-compliant.

Go deeper

VCP-DCV vSphere Lifecycle Management Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question