Question 540
During an independent network handover at the Hollow Creek branch of Xenia Transport, the monitored service is production analytics for clients in 10.115.6.0/24; incident reference is DC-9011. The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. 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 relay request/response counts and per-VLAN lease success. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. This alternative addresses a different issue (dhcp relay across vlans). The decisive distinction is: Track resolver latency, NXDOMAIN spikes and stale address records.
This alternative addresses a different issue (aaa management authentication). The option would address: Track AAA availability, failed logins and emergency account use. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. The decisive distinction is: Track resolver latency, NXDOMAIN spikes and stale address records.
Review ACL range expansion and overbroad rule matches. This alternative addresses a different issue (acl wildcard matching). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. The decisive distinction is: Track resolver latency, NXDOMAIN spikes and stale address records.
The on-duty analyst documents this symptom before proposing any configuration: Clients can ping an application by IP but fail by hostname after a DNS server change. That points to this explanation: Track resolver latency, NXDOMAIN spikes and stale address records.