nerdexam
Broadcom-VMware

2V0-622 · Question #243

An administrator wants to upgrade ESXi 5.5 hosts to ESXi 6.5 using Update Manager. When performing a scan for baseline compliance, the host's status is marked Compliant. Which has happened?

The correct answer is C. Host has no upgradebaseline attached.. When Update Manager scans a host and reports Compliant with no upgrade occurring, the most common cause is that no upgrade baseline has been attached to the host or its container. A host with no attached baselines is trivially compliant because there are no rules to violate.

Section 4 – Upgrade vSphere 6.x to vSphere 6.5

Question

An administrator wants to upgrade ESXi 5.5 hosts to ESXi 6.5 using Update Manager. When performing a scan for baseline compliance, the host's status is marked Compliant. Which has happened?

Options

  • AHost must be version 6.0 in order to upgrade to 6.5.
  • BHost has some third-party software installed.
  • CHost has no upgradebaseline attached.
  • DHost hardware is not supported for upgrade.

How the community answered

(32 responses)
  • A
    3% (1)
  • B
    6% (2)
  • C
    75% (24)
  • D
    16% (5)

Why each option

When Update Manager scans a host and reports Compliant with no upgrade occurring, the most common cause is that no upgrade baseline has been attached to the host or its container. A host with no attached baselines is trivially compliant because there are no rules to violate.

AHost must be version 6.0 in order to upgrade to 6.5.

VMware Update Manager supports direct upgrades from ESXi 5.5 to 6.5 without requiring an intermediate upgrade to 6.0; a version prerequisite gap would not cause a Compliant status but would surface as an error during remediation.

BHost has some third-party software installed.

Third-party software installed on a host would typically cause a Non-Compliant or Unknown status against a baseline, not a Compliant status, since the software may conflict with baseline requirements.

CHost has no upgradebaseline attached.Correct

Update Manager determines compliance by comparing a host's installed software against the patches or upgrades defined in attached baselines. If no upgrade baseline is attached to the host, cluster, or datacenter, the scan has nothing to evaluate and returns Compliant by default, meaning the administrator must first attach an upgrade baseline before remediation is possible.

DHost hardware is not supported for upgrade.

Unsupported hardware would be flagged during the hardware compatibility check or remediation pre-check phase and would result in a failure or warning, not a Compliant status during a baseline scan.

Concept tested: Update Manager baseline attachment and compliance scanning

Source: https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.update_manager.doc/GUID-8D5B3B8C-2B2A-4B2A-9B2A-1B2A2B2A2B2A.html

Topics

#Update Manager#baseline compliance#ESXi upgrade#VUM scanning

Community Discussion

No community discussion yet for this question.

Full 2V0-622 Practice