Examine this MySQL Shell command: dba.rebootClusterFromCompleteOutage() Which two statements are true? (Choose two.)

Question

Options

• AIt reconfigures InnoDB Cluster if the cluster was stopped.
• BIt performs InnoDB Cluster instances rolling restart.
• CIt only starts all InnoDB Cluster instances.
• DIt is not mandatory that all instances are running and reachable before running the command.
• EIt stops and restarts all InnoDB Cluster instances and initializes the metadata.
• FIt only stops and restarts all InnoDB Cluster instances.
• GIt picks the minimum number of instances necessary to rebuild the quorum and reconfigures

• A
  21% (9)
• B
  56% (24)
• C
  12% (5)
• E
  7% (3)
• F
  2% (1)
• G
  2% (1)

Explanation

dba.rebootClusterFromCompleteOutage() performs a rolling restart (B) - it brings cluster instances back online sequentially, electing a new primary and rejoining members one by one, rather than requiring a simultaneous startup. It is also correct that not all instances need to be reachable (D) before invoking the command; it works with whatever subset of instances it can contact and will skip or warn about unreachable ones.

Why the distractors are wrong:

• A is too vague - "reconfigures" misrepresents the operation; the cluster topology/metadata is preserved, not reconfigured.
• C and F are wrong because "only starts" or "only stops and restarts" understates what happens - the command orchestrates Group Replication recovery logic, not a plain start/stop.
• E is wrong because the command does not reinitialize metadata; it reuses the existing metadata to restore the cluster.
• G describes dba.forceQuorumUsingPartitionOf(), which repairs a partial outage by rebuilding quorum from a minimum partition - a different command entirely.

Memory tip: Associate rebootClusterFromCompleteOutage with a "power-failure recovery" - you don't need every machine back online first (D), and recovery happens node-by-node in a rolling fashion (B), not all at once.

No community discussion yet for this question.