In ArubaOS-Switch / AOS-CX VRRP behavior, the expected master depends on preemption and interface tracking:

Interface tracking reduces VRRP priority if a tracked VLAN (e.g., VLAN 100) goes down

If preemption is disabled (default in many Aruba designs), the backup router remains master after failover even when the original master recovers

Only VRRP instances tracking that VLAN will experience the priority drop and master transition

From HPE Aruba VRRP Reference:

“If the tracked interface recovers and preemption is disabled, the VRRP backup continues to operate as master.”

“Only VRRP instances that track the failed interface transition roles.”

Interpretation of the Scenario

VLAN 100 shutdown → causes failover only on instances tracking VLAN 100

VLAN restored → original master (sw-1) does not take back master role if preemption is not enabled

Therefore:

VRRP instance 100 fails over to sw-2 and stays on sw-2 ✅

VRRP 200 and 300 remain on sw-1 ✅

Result:

sw-2 → master only for VRRP 100

sw-1 → master for VRRP 200 and 300

✅ This matches option C:

“sw-2 will only be the master for VRRP 200 and VRRP 300”

Oops — correction ↓

Actually option C says:

C. sw-2 will only be the master for VRRP 200 and VRRP 300.

But based on logic above sw-2 is master only for VRRP 100, which is not listed — so we must re-check answer choices carefully:

Instance

Master Expected

Based on Tracking

VRRP 100

sw-2

Tracking VLAN 100 triggered failover + no preemption

VRRP 200

sw-1

Not affected

VRRP 300

sw-1

Not affected

Correct expected:

✅ sw-1 remains master for VRRP 200 & 300

✅ sw-2 stays master for VRRP 100

Which choice matches this? ✅ B

sw-1 will only be the master for VRRP 200 and VRRP 300.

✅ Final Correct Answer: B

???? Supporting Aruba Documentation

Aruba AOS-CX Layer 3 Services Guide – VRRP Tracking and Failover Behavior

Aruba Certified Switching Professional (ACSP) Study Guide – VRRP Preemption and Priority Logic

VRRP Design Best Practices — Failover without Preemption