In static-priority arbitration mode, if the active-active relationships are functioning, but all replication links between storage arrays are down. What will happen?

Question

Options

• AServices stop at the preferred-site while they continue at the non-preferred site
• BServices continue at the preferred site while they stop at the non-preferred site
• CService stop at both the preferred and non-preferred sites
• DService continues at both the preferred and non-preferred sites

• A
  15% (9)
• B
  77% (46)
• C
  2% (1)
• D
  7% (4)

Explanation

In static-priority arbitration mode, the preferred site is designated to "win" any conflict, including the loss of all replication links. When links go down, the non-preferred site fences itself off (stops I/O) to prevent split-brain data divergence, while the preferred site continues serving workloads uninterrupted - making B correct.

Why the distractors are wrong:

• A reverses the logic - the preferred site has priority and survives, not the non-preferred one.
• C describes a full outage, which would defeat the purpose of having a priority designation at all; static-priority exists precisely so one site can survive link loss.
• D describes what happens in uniform arbitration (or when links are healthy), but allowing both sites to proceed independently with broken links causes split-brain and data corruption - the non-preferred site must stop to prevent this.

Memory tip: Think "Preferred = Protected." In static-priority mode, the preferred site is always protected and keeps running; the non-preferred site sacrifices itself whenever a tiebreaker is needed.

No community discussion yet for this question.