Question 210
During an independent network handover at the Harborcrest branch of Ivory Cloud Services, the monitored service is payroll approval for clients in 10.91.44.0/24; incident reference is DC-8450. The on-duty analyst documents this symptom before proposing any configuration: Hosts in VLAN 40 can communicate locally but cannot reach other campus subnets because the VLAN gateway interface is down. 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 port-to-VLAN inventory drift and incorrect DHCP scope allocation on access ports. This alternative addresses a different issue (access port vlan membership). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: Hosts in VLAN 40 can communicate locally but cannot reach other campus subnets because the VLAN gateway interface is down. The decisive distinction is: Monitor SVI state, gateway ARP, and permitted inter-VLAN service checks.
The decisive evidence is: The on-duty analyst documents this symptom before proposing any configuration: Hosts in VLAN 40 can communicate locally but cannot reach other campus subnets because the VLAN gateway interface is down. Monitor SVI state, gateway ARP, and permitted inter-VLAN service checks.
Monitor STP root changes, path costs and convergence events. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: Hosts in VLAN 40 can communicate locally but cannot reach other campus subnets because the VLAN gateway interface is down. This alternative addresses a different issue (stp root bridge placement). The decisive distinction is: Monitor SVI state, gateway ARP, and permitted inter-VLAN service checks.
This alternative addresses a different issue (trunk allowed vlans). The option would address: Track trunk VLAN membership, VLAN pruning events and voice endpoint connectivity after changes. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: Hosts in VLAN 40 can communicate locally but cannot reach other campus subnets because the VLAN gateway interface is down.