Question 500
An IPv4 extended ACL allows employee HTTPS traffic to a public service but must block requests originating in guest subnet 192.168.248.0/21. The ACL currently begins with `permit ip any any` and later denies that guest range. Why is the guest deny ineffective?
Explanation
Correct Answer
IOS ACL conditions are processed top-down; the first matching entry determines the packet result. `permit ip any any` matches the guest source and target before the more-specific deny can be considered. Order the guest deny ahead of that permit or narrow the broad permission to retain the intended security boundary.
Incorrect Answers
Extended ACLs can match source and destination addresses and protocol fields. The issue is rule ordering, not an inability to filter guest sources.
It is within RFC 1918 192.168.0.0/16 and is a valid /21 boundary. The configuration error is that an earlier rule already permits it.
An implicit deny applies only when no prior ACE matches. Here the explicit all-traffic permit matches first and stops further evaluation.