Refer to the exhibit. An administrator uses SSH to log into a vSAN ESA host and runs the esxcli vsan debug object overview command. The administrator notices the Healthy Components column, the last…

Question

Exhibits

Options

• ANew physical disks have been claimed and a rebalance operation is underway.
• BThe applied Storage policy has been updated.
• CNew VMDKs have been added to multiple VMs, but the storage policy has not finished applying.
• DOne host is in maintenance mode with ensure accessibility.

• A
  4% (2)
• B
  15% (7)
• C
  9% (4)
• D
  72% (34)

Explanation

When a host enters maintenance mode with Ensure Accessibility, vSAN only guarantees objects remain readable/writable - it does not fully evacuate data components off that host. Those components sitting on the maintenance-mode host become absent/degraded, so the Healthy Components column drops below the expected count even though the objects are still accessible. The host is "there but not participating," leaving affected objects in a partially degraded state.

Why the distractors are wrong:

• A (Rebalance): A rebalance shuffles data between disks but keeps all components healthy throughout; no component goes absent during this operation.
• B (Policy updated): Changing a storage policy triggers a compliance check or re-provisioning, but existing components remain healthy while the policy propagates - they don't drop to an unhealthy state.
• C (New VMDKs, policy not finished): Newly provisioned VMDKs may be in a syncing state, but this is a transient provisioning status on new objects, not a degraded health state on existing components.

Memory tip: Associate "Ensure Accessibility" → "Accept Missing Pieces." It's the most permissive maintenance mode option - vSAN accepts that some components are temporarily gone, which is exactly what the health column reflects. If you see degraded-but-accessible in vSAN, think host in maintenance.

No community discussion yet for this question.