In which of the following scenarios will OceanStor 9000 not trigger data balancing?

Question

Options

• AThe nodes have returned to normal
• BDisable Node
• CNew Road Node
• DEnable node reference

• A
  73% (47)
• B
  16% (10)
• C
  6% (4)
• D
  5% (3)

Explanation

Option A is correct because when nodes simply return to normal after a temporary abnormal state, the data distribution remains unchanged - no structural change has occurred that would require redistribution, so OceanStor 9000 has no reason to trigger a rebalancing event.

Why the distractors are wrong (i.e., they DO trigger balancing):

• B (Disable Node): Taking a node offline changes where data must be accessible, forcing the system to redistribute or re-protect affected data across remaining nodes.
• C (New/Add Node): Adding a new node creates an imbalance because the existing data is spread across fewer nodes than are now available, prompting the system to migrate data onto the new node.
• D (Enable Node Reference): Re-enabling a node reference brings capacity back into the active pool, triggering rebalancing to utilize that newly available resource.

Memory tip: Think of it as "change triggers balancing, restoration does not." B, C, and D all represent configuration changes to the node pool (remove, add, re-enable). Option A is purely a status restoration - the topology didn't change, so there's nothing to rebalance.

No community discussion yet for this question.