VCP-DCV vSphere Lifecycle Management Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  Upgrade all hosts simultaneously to complete faster.

  Why it's wrong here

  Upgrading every host at once takes the entire vSAN cluster offline, so no fault domain remains to rebuild data from and downtime is total. Sequential host upgrades with full data evacuation are the correct approach; simultaneous upgrading suits stateless compute clusters without shared storage.

• ✗

  Upgrade vCenter Server first, then upgrade all hosts at once.

  Why it's wrong here

  Upgrading vCenter first is required, but then upgrading all hosts at once still removes every vSAN fault domain simultaneously, causing full outage. The stem demands minimising downtime, which sequential remediation with data evacuation provides; the all-at-once portion is what breaks it.

• ✓

  Place each host in maintenance mode, evacuate vSAN data, upgrade, and rejoin the cluster.

  Why this is correct

  Maintenance mode with full data evacuation maintains vSAN availability throughout the upgrade, satisfying the no-downtime constraint. Each host's data is migrated to remaining cluster members before remediation, and the host rejoins once upgraded, avoiding any storage outage.

• ✗

  Use Quick Boot feature to speed up the upgrade process.

  Why it's wrong here

  Quick Boot only shortens a single host's reboot by skipping firmware initialisation; it does not preserve vSAN availability, so hosts still need sequential evacuation and reboot. It is a valid accelerator within a rolling upgrade, not the approach that minimises downtime across the cluster.

Go deeper

Related to this question