Question 520
During an independent network handover at the Coastal Haven branch of Lakefront Regional Archives, the monitored service is laboratory instrument upload for clients in 172.18.14.0/24; incident reference is DC-8977. The on-duty analyst documents this symptom before proposing any configuration: New guest laptops fail to obtain IPv4 leases while existing devices retain working addresses; the DHCP scope shows no available leases. 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 NAT allocation failures and per-address port utilization. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: New guest laptops fail to obtain IPv4 leases while existing devices retain working addresses; the DHCP scope shows no available leases. This alternative addresses a different issue (pat address exhaustion). The decisive distinction is: Track active leases, allocation errors and address-conflict alarms.
This alternative addresses a different issue (acl direction and placement). The option would address: Audit interface-to-ACL bindings and denied-flow logs. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: New guest laptops fail to obtain IPv4 leases while existing devices retain working addresses; the DHCP scope shows no available leases.
Monitor ACL hit counters and configuration shadowing after edits. This alternative addresses a different issue (acl rule ordering). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: New guest laptops fail to obtain IPv4 leases while existing devices retain working addresses; the DHCP scope shows no available leases. The decisive distinction is: Track active leases, allocation errors and address-conflict alarms.
The on-duty analyst documents this symptom before proposing any configuration: New guest laptops fail to obtain IPv4 leases while existing devices retain working addresses; the DHCP scope shows no available leases. That points to this explanation: Track active leases, allocation errors and address-conflict alarms.