Question 880
At the Dartwood LAN operations group, a sensitive service remains reachable despite a deployed ACL and the operator does not know if rules match. Which setting or practice should be reviewed in future?
Explanation
Correct Answer
This control works beyond the initial remediation because it requires the team to monitor ACL policy hits after every security rule change.
Incorrect Answers
Monitor switch system resource trends during peak hours is not the primary recurring safeguard for this problem. The team should monitor ACL policy hits after every security rule change. For the Dartwood LAN operations group, the direct corrective action is to read supported ACL hit counters and policy attachment scope for the target packet path.
The suggested preventive check is: Document expected split-interface port states for monitoring. Its technical scope concerns: An intentionally standby split-interface link may not forward until failover. This question asks how to sustain control over: A filter with no matching hits may be incorrectly ordered attached or classified. The more targeted safeguard is: Monitor ACL policy hits after every security rule change.
Confirm address and VLAN bindings at the start of a capture. That safeguard would help prevent recurrence of: An overly narrow or outdated filter can hide valid traffic from the analyst. The risk being reviewed here is instead: A filter with no matching hits may be incorrectly ordered attached or classified. The matching ongoing control is: Monitor ACL policy hits after every security rule change.