Question 780
During an independent network handover at the Fox River branch of Pineview Hospitality, the monitored service is facility access control for clients in 172.20.54.0/24; incident reference is DC-9419. The on-duty analyst documents this symptom before proposing any configuration: A campus relies on one distribution gateway, and every VLAN loses remote connectivity when that switch fails. The branch requires an auditable explanation, a narrowly staged change, and a rollback plan that preserves its working services. Which ongoing operational check is most relevant to recognizing recurrence of this failure?
Answer and explanations
Monitor campus dependency mapping and failure blast radius. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: A campus relies on one distribution gateway, and every VLAN loses remote connectivity when that switch fails. This alternative addresses a different issue (access distribution hierarchy). The decisive distinction is: Track active gateway role, failover events and application recovery times.
This alternative addresses a different issue (access poe capacity planning). The option would address: Monitor switch PoE budget headroom and denied power requests. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: A campus relies on one distribution gateway, and every VLAN loses remote connectivity when that switch fails.
Retest representative campus paths and change success metrics after rollout. This alternative addresses a different issue (campus acceptance and rollback). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: A campus relies on one distribution gateway, and every VLAN loses remote connectivity when that switch fails. The decisive distinction is: Track active gateway role, failover events and application recovery times.
The on-duty analyst documents this symptom before proposing any configuration: A campus relies on one distribution gateway, and every VLAN loses remote connectivity when that switch fails. That points to this explanation: Track active gateway role, failover events and application recovery times.