An enterprise organization deploys two Layer 3 core switches, Core-A and Core-B, to provide default gateway redundancy for VLAN 10 () using VRRPv3. Core-A is configured as the VRRP Master with a priority of 110, while Core-B acts as the Backup with a priority of 100. Preemption is enabled on both routers. To prevent black-holing traffic if Core-A loses its WAN connection, an interface tracking object is configured on Core-A to decrement its VRRP priority by 20 upon WAN uplink failure. Core-A is also manually configured as the Spanning Tree Protocol (STP) Primary Root Bridge for VLAN 10.
During a WAN link failure test on Core-A, tracking successfully decrements Core-A's priority to 90, and Core-B transitions to the VRRP Master state. However, telemetry shows that outbound host traffic from VLAN 10 experiences significant path latency and traverses the inter-switch trunk twice before leaving the network.
Which of the following root causes best explains why traffic is traversing the inter-switch trunk redundantly following the failover?
- Core-A remains the STP Root Bridge for VLAN 10, forcing access switches to continue forwarding Layer 2 traffic to Core-A first, which must then relay frames across the trunk to Core-B.Cevap
- BThe host endpoints on VLAN 10 were statically assigned Core-A's physical interface IP address as their default gateway rather than the VRRP virtual IP address.
- CCore-B was configured with a higher numerical STP priority value than Core-A, causing Core-B to place its trunk interface into an STP Blocking state.
- DA native VLAN mismatch on the inter-switch trunk between Core-A and Core-B caused VRRP advertisement packets to be dropped, resulting in a dual-Master state.