A customer's infrastructure is set up to use both primary and secondary gateway clusters on the SSID profile based on best practices. What is a valid cause for having an equal split in APs connected…

Question

Options

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

• A
  3% (2)
• B
  8% (5)
• C
  13% (8)
• D
  76% (47)

Explanation

Option D is correct because when both clusters are operational but cluster preemption is disabled, APs that previously failed over to the secondary cluster have no mechanism to automatically return to the primary. This results in a persistent, roughly equal split where some APs remain anchored to the secondary cluster indefinitely, rather than migrating back.

Why the distractors fail:

• A - The secondary cluster being heterogeneous (mixed node types) has no bearing on how APs distribute themselves between clusters; cluster composition doesn't drive AP affinity.
• B - Similarly, the primary cluster being homogeneous (uniform node types) is irrelevant to AP distribution logic between primary and secondary.
• C - With preemption enabled, APs that connected to the secondary cluster during an outage will actively migrate back to the primary once it recovers, so you'd expect the primary to dominate - not an equal split.

Memory tip: Think of cluster preemption as a "snap back" feature. When it's ON, APs snap back to primary when it's healthy. When it's OFF, APs are "sticky" - they stay wherever they landed, which is what produces an equal split if half the APs previously failed over to secondary.

No community discussion yet for this question.