Question 460
During an independent network handover at the Cedar Valley branch of Nova Valley Transit, the monitored service is regional payroll for clients in 10.52.8.0/23; incident reference is DC-8875. The on-duty analyst documents this symptom before proposing any configuration: An interface ACL blocks return traffic for a service because the filter is applied inbound on the wrong routed boundary. 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 ACL hit counters and configuration shadowing after edits. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: An interface ACL blocks return traffic for a service because the filter is applied inbound on the wrong routed boundary. This alternative addresses a different issue (acl rule ordering). The decisive distinction is: Audit interface-to-ACL bindings and denied-flow logs.
This alternative addresses a different issue (dhcp address pool depletion). The option would address: Track active leases, allocation errors and address-conflict alarms. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: An interface ACL blocks return traffic for a service because the filter is applied inbound on the wrong routed boundary.
Monitor NAT allocation failures and per-address port utilization. This alternative addresses a different issue (pat address exhaustion). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: An interface ACL blocks return traffic for a service because the filter is applied inbound on the wrong routed boundary. The decisive distinction is: Audit interface-to-ACL bindings and denied-flow logs.
The on-duty analyst documents this symptom before proposing any configuration: An interface ACL blocks return traffic for a service because the filter is applied inbound on the wrong routed boundary. That points to this explanation: Audit interface-to-ACL bindings and denied-flow logs.