The vSphere Client reports that the state of some components stored on the vSAN datastore are in the reconfiguring state. Which situation causes components to enter this state?

Question

Options

• AA host in the cluster enters maintenance mode.
• BThe cluster is recovering from a vSAN failure.
• CThe applied storage policy is modified.
• DAdditional storage capacity is added to the cluster.

• A
  4% (2)
• B
  11% (6)
• C
  80% (43)
• D
  6% (3)

Explanation

When a storage policy applied to a VM or object on a vSAN datastore is modified, vSAN must reconfigure existing components to satisfy the new policy requirements (e.g., changed FTT, RAID type, or stripe width) - this active restructuring is shown as the reconfiguring state. Option A (maintenance mode) triggers absent or degraded states as components become inaccessible, not reconfiguration. Option B (recovering from failure) puts components into a degraded or resyncing/rebuilding state, not reconfiguring. Option D (adding capacity) may trigger rebalancing, but that is a background rebalance operation - not a policy-driven reconfiguration of components.

Memory tip: Think "reconfiguring = re-policy-ing." The word reconfigure maps directly to a configuration change - and a storage policy IS the configuration. Any time the policy definition changes, vSAN must reconfigure the components to match it.

No community discussion yet for this question.