A customer's infrastructure is set up to use both primary and secondary gateway clusters on the SSID profile based on best practices. Why do they have an equal split of their 144 APs across the…

Question

Options

• AThe secondary gateway cluster is a heterogeneous cluster with four nodes.
• BThe primary and secondary gateway clusters are up, and the cluster preemption is enabled.
• CThe primary and secondary gateway clusters are up, but the cluster preemption is not enabled.
• DThe secondary gateway cluster is a homogeneous cluster with six nodes.

• A
  14% (4)
• B
  29% (8)
• C
  50% (14)
• D
  7% (2)

Explanation

Option C is correct because when both clusters are operational but cluster preemption is disabled, APs that originally failed over to the secondary cluster during a primary outage will remain on the secondary even after the primary recovers. This produces the observed equal 72/72 split - half the APs never migrated back, because nothing forced them to.

Why the distractors fail:

• B is the near-miss trap: if preemption were enabled, APs would automatically return to the primary once it recovered, and you'd see a heavily primary-weighted distribution, not an equal split.
• A and D are red herrings about cluster composition (heterogeneous/homogeneous, node counts). Cluster type and node count influence capacity and redundancy, but they don't govern whether APs rebalance after a failover - that's preemption's job.

Memory tip: Think of cluster preemption like a "return flight home." If it's enabled, your APs automatically fly back to primary after recovery. If it's disabled, they're stranded at the backup gateway until manually moved - explaining why you end up with a permanent equal split across both clusters.

No community discussion yet for this question.