An administrator is preparing maintenance on a host in a vSAN cluster, and the maintenance is expected to take less than one hour. The administrator is considering using the "Full Data Migration"…

Question

Options

• AUse maintenance mode with "No Data Migration".
• BUse maintenance mode with "Ensure Accessibility".
• CUse maintenance mode with "Ensure Accessibly", and increase the vSAN object repair timer to
• DTake an outage window when users are less likely to be working.

• A
  76% (35)
• B
  2% (1)
• C
  15% (7)
• D
  7% (3)

Explanation

"No Data Migration" is correct because the maintenance is short-term (under one hour), so there's no need to move data off the host at all - vSAN simply tolerates the temporary unavailability, and data remains accessible from other hosts in the cluster without any capacity or performance overhead.

• Option B ("Ensure Accessibility") only guarantees one accessible copy of each object, not full redundancy - it still migrates some data, which partially addresses the concern but doesn't fully eliminate the capacity/performance overhead, making it a worse fit than No Data Migration for a sub-one-hour window.
• Option C is a distractor that conflates two separate concepts: "Ensure Accessibility" mode doesn't benefit from extending the repair timer in this context, and the option is also incomplete/misspelled in the question, signaling it's a trap.
• Option D avoids the technical problem rather than solving it - taking an outage window doesn't eliminate the data migration concern; it just shifts when it happens.

Memory tip: Think of the three vSAN maintenance modes on a spectrum of how much data moves - "No Data Migration" moves nothing (fastest, lowest overhead), "Ensure Accessibility" moves minimal data (one accessible copy), and "Full Data Migration" moves everything (slowest, highest overhead). Match the mode to the outage duration: short outage = No Migration, long outage = Full Migration.

No community discussion yet for this question.