The correct sequence is to create the extended ACL named HTTP_ONLY, remove the existing PERMIT_ALL ACL from the interface, and apply the new ACL inbound on GigabitEthernet0/0. This is correct because the extended ACL must explicitly permit TCP port 80 (HTTP) from source 192.168.1.0/24 to destination 10.0.0.0/30, and the implicit deny at the end of every ACL automatically blocks all other IP traffic, so no explicit deny statement is needed. On the CCNA 200-301 v2 exam, this question tests your ability to configure and place extended ACLs with precise traffic filtering, a core skill for securing network access. A common trap is forgetting to remove the old ACL with the `no ip access-group` command before applying the new one, as the exam explicitly requires correcting an overly permissive configuration. Remember the mnemonic “Remove before you restrict” to avoid leaving a permissive ACL active while applying a new one.
CCNA Network Services and Security Practice Question
This 200-301 practice question tests your understanding of network services and security. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Network Topology
You are connected to R1. Configure an extended ACL on R1 to permit HTTP traffic from the 192.168.1.0/24 network to the 10.0.0.0/30 network, and deny all other IP traffic. Apply the ACL inbound on the interface facing the 192.168.1.0/24 network. The current configuration has an ACL that is too permissive; you must explicitly remove the existing ACL before applying the new one. Correct the configuration.
R1# show running-config | section interface GigabitEthernet0/0
interface GigabitEthernet0/0
ip address 192.168.1.1 255.255.255.0
ip access-group PERMIT_ALL in
!
R1# show running-config | section ip access-list
ip access-list extended PERMIT_ALL
permit ip any any
A
ip access-list extended HTTP_ONLY
permit tcp 192.168.1.0 0.0.0.255 10.0.0.0 0.0.0.3 eq 80
interface gigabitEthernet0/0
no ip access-group PERMIT_ALL in
ip access-group HTTP_ONLY in
This configuration creates an extended ACL that permits TCP port 80 (HTTP) from the 192.168.1.0/24 network to the 10.0.0.0/30 network, and implicitly denies all other traffic. The ACL is applied inbound on the correct interface after removing the overly permissive ACL.
B
ip access-list extended HTTP_ONLY
permit tcp 192.168.1.0 0.0.0.255 10.0.0.0 0.0.0.3 eq 80
deny ip any any
interface gigabitEthernet0/0
no ip access-group PERMIT_ALL in
ip access-group HTTP_ONLY in
Why wrong: This is incorrect because the explicit 'deny ip any any' is unnecessary; extended ACLs have an implicit deny at the end. Adding it does not change functionality but is redundant and not the best practice.
C
ip access-list extended HTTP_ONLY
permit tcp 192.168.1.0 0.0.0.255 10.0.0.0 0.0.0.3 eq 80
interface gigabitEthernet0/0
ip access-group HTTP_ONLY in
Why wrong: This is incorrect because it fails to remove the existing overly permissive ACL (PERMIT_ALL) from the interface. Without removing it, both ACLs would be applied, and the order of evaluation could allow unwanted traffic.
D
ip access-list extended HTTP_ONLY
permit tcp 192.168.1.0 0.0.0.255 10.0.0.0 0.0.0.3 eq 80
permit ip any any
interface gigabitEthernet0/0
no ip access-group PERMIT_ALL in
ip access-group HTTP_ONLY in
Why wrong: This is incorrect because the second permit statement 'permit ip any any' allows all IP traffic, making the ACL just as permissive as the original PERMIT_ALL. It does not restrict traffic to only HTTP.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
ip access-list extended HTTP_ONLY
permit tcp 192.168.1.0 0.0.0.255 10.0.0.0 0.0.0.3 eq 80
interface gigabitEthernet0/0
no ip access-group PERMIT_ALL in
ip access-group HTTP_ONLY in
The existing ACL PERMIT_ALL allows all IP traffic, which must be replaced by a new ACL that permits only TCP port 80 (HTTP) from 192.168.1.0/24 to 10.0.0.0/30 and denies everything else. Because the requirement specifies explicit removal of the old ACL, you must first issue 'no ip access-group PERMIT_ALL in' under the interface before applying the new ACL. The extended ACL has an implicit deny at the end, so no separate deny statement is needed. Therefore, the correct sequence is: create the ACL HTTP_ONLY with the permit statement, enter the interface, remove the old ACL, and apply the new one inbound.
Key principle: ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
ip access-list extended HTTP_ONLY
permit tcp 192.168.1.0 0.0.0.255 10.0.0.0 0.0.0.3 eq 80
interface gigabitEthernet0/0
no ip access-group PERMIT_ALL in
ip access-group HTTP_ONLY in
Why this is correct
This configuration creates an extended ACL that permits TCP port 80 (HTTP) from the 192.168.1.0/24 network to the 10.0.0.0/30 network, and implicitly denies all other traffic. The ACL is applied inbound on the correct interface after removing the overly permissive ACL.
Related concept
Standard ACLs match source addresses.
✗
ip access-list extended HTTP_ONLY
permit tcp 192.168.1.0 0.0.0.255 10.0.0.0 0.0.0.3 eq 80
deny ip any any
interface gigabitEthernet0/0
no ip access-group PERMIT_ALL in
ip access-group HTTP_ONLY in
Why it's wrong here
This is incorrect because the explicit 'deny ip any any' is unnecessary; extended ACLs have an implicit deny at the end. Adding it does not change functionality but is redundant and not the best practice.
✗
ip access-list extended HTTP_ONLY
permit tcp 192.168.1.0 0.0.0.255 10.0.0.0 0.0.0.3 eq 80
interface gigabitEthernet0/0
ip access-group HTTP_ONLY in
Why it's wrong here
This is incorrect because it fails to remove the existing overly permissive ACL (PERMIT_ALL) from the interface. Without removing it, both ACLs would be applied, and the order of evaluation could allow unwanted traffic.
✗
ip access-list extended HTTP_ONLY
permit tcp 192.168.1.0 0.0.0.255 10.0.0.0 0.0.0.3 eq 80
permit ip any any
interface gigabitEthernet0/0
no ip access-group PERMIT_ALL in
ip access-group HTTP_ONLY in
Why it's wrong here
This is incorrect because the second permit statement 'permit ip any any' allows all IP traffic, making the ACL just as permissive as the original PERMIT_ALL. It does not restrict traffic to only HTTP.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 200-301 exam frequently reuses these exact scenarios with slightly different constraints.
✓ip access-list extended HTTP_ONLY
permit tcp 192.168.1.0 0.0.0.255 10.0.0.0 0.0.0.3 eq 80
interface gigabitEthernet0/0
no ip access-group PERMIT_ALL in
ip access-group HTTP_ONLY inCorrect answer▾
Why this is correct
This configuration creates an extended ACL that permits TCP port 80 (HTTP) from the 192.168.1.0/24 network to the 10.0.0.0/30 network, and implicitly denies all other traffic. The ACL is applied inbound on the correct interface after removing the overly permissive ACL.
✗ip access-list extended HTTP_ONLY
permit tcp 192.168.1.0 0.0.0.255 10.0.0.0 0.0.0.3 eq 80
deny ip any any
interface gigabitEthernet0/0
no ip access-group PERMIT_ALL in
ip access-group HTTP_ONLY inWrong answer — click to see why▾
Why this is wrong here
The explicit deny is not required and may cause confusion; the implicit deny already blocks all other traffic.
Why candidates choose this
Candidates may think they need to explicitly deny all other traffic to ensure security, not realizing the implicit deny exists.
✗ip access-list extended HTTP_ONLY
permit tcp 192.168.1.0 0.0.0.255 10.0.0.0 0.0.0.3 eq 80
interface gigabitEthernet0/0
ip access-group HTTP_ONLY inWrong answer — click to see why▾
Why this is wrong here
The existing ACL PERMIT_ALL must be removed before applying the new ACL; otherwise, the interface may have multiple ACLs or the old one still in effect.
Why candidates choose this
Candidates may forget to remove the old ACL, thinking that applying a new one overwrites the previous, but Cisco IOS does not automatically replace ACLs on an interface.
✗ip access-list extended HTTP_ONLY
permit tcp 192.168.1.0 0.0.0.255 10.0.0.0 0.0.0.3 eq 80
permit ip any any
interface gigabitEthernet0/0
no ip access-group PERMIT_ALL in
ip access-group HTTP_ONLY inWrong answer — click to see why▾
Why this is wrong here
Adding 'permit ip any any' after the HTTP permit allows all other traffic, defeating the purpose of restricting to HTTP only.
Why candidates choose this
Candidates might think they need to explicitly allow all other traffic to avoid blocking necessary traffic, but the requirement is to deny all other IP traffic.
Analysis generated from the official 200-301blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Common exam traps
Common exam trap: ACLs stop at the first match
ACLs are processed top to bottom. The first matching entry wins, and an implicit deny usually exists at the end.
Detailed technical explanation
How to think about this question
ACL questions test precision: source, destination, protocol, port and direction. A generally correct ACL can still fail if it is applied on the wrong interface or in the wrong direction.
KKey Concepts to Remember
Standard ACLs match source addresses.
Extended ACLs can match source, destination, protocol and ports.
The first matching ACL entry is used.
There is usually an implicit deny at the end.
TExam Day Tips
→Check inbound versus outbound direction.
→Read the ACL from top to bottom.
→Look for a broader permit or deny above the intended line.
Key takeaway
ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.
Real-world example
How this comes up in practice
A security administrator must allow nursing staff to reach a patient records server while blocking access from the guest Wi-Fi VLAN. After applying an extended ACL, traffic is still blocked from nursing workstations. The ACL was applied outbound instead of inbound on the wrong interface. Questions like this test ACL direction and placement rules.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this 200-301 question in full detail.
Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related 200-301 ACL questions on filtering logic and placement.
Network Services and Security — This question tests Network Services and Security — Standard ACLs match source addresses..
What is the correct answer to this question?
The correct answer is: ip access-list extended HTTP_ONLY
permit tcp 192.168.1.0 0.0.0.255 10.0.0.0 0.0.0.3 eq 80
interface gigabitEthernet0/0
no ip access-group PERMIT_ALL in
ip access-group HTTP_ONLY in — The existing ACL PERMIT_ALL allows all IP traffic, which must be replaced by a new ACL that permits only TCP port 80 (HTTP) from 192.168.1.0/24 to 10.0.0.0/30 and denies everything else. Because the requirement specifies explicit removal of the old ACL, you must first issue 'no ip access-group PERMIT_ALL in' under the interface before applying the new ACL. The extended ACL has an implicit deny at the end, so no separate deny statement is needed. Therefore, the correct sequence is: create the ACL HTTP_ONLY with the permit statement, enter the interface, remove the old ACL, and apply the new one inbound.
What should I do if I get this 200-301 question wrong?
Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related 200-301 ACL questions on filtering logic and placement.
What is the key concept behind this question?
Standard ACLs match source addresses.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which TWO statements are true regarding the configuration and placement of standard and extended ACLs on a router?
medium
A.Standard ACLs are typically placed closest to the source of the traffic.
✓ B.Extended ACLs are typically placed closest to the source of the traffic.
✓ C.A wildcard mask of 0.0.0.0 in an ACL matches all bits of the IP address.
D.A wildcard mask of 255.255.255.255 in an ACL matches all bits of the IP address.
E.Extended ACLs should be placed on the interface closest to the destination to filter traffic before it reaches the final segment.
Why B: Option B is correct because extended ACLs evaluate multiple criteria (source/destination IP, port, protocol), so placing them closest to the source prevents unwanted traffic from consuming bandwidth across the network. Option C is correct because a wildcard mask of 0.0.0.0 means all 32 bits must match, matching a single host. Option A is incorrect—standard ACLs are placed closest to the destination, not the source. Option D is incorrect—a wildcard mask of 255.255.255.255 matches any address (ignores all bits), not all bits. Option E is incorrect—extended ACLs placed near the destination would not conserve bandwidth; they should be near the source.
Variation 2. Drag and drop the following steps into the correct order to configure and apply an extended IPv4 ACL on a Cisco router to block Telnet traffic from subnet 192.168.1.0/24 to host 10.0.0.1 and permit all other IP traffic.
medium
✓ A.Identify the traffic to filter (deny Telnet from 192.168.1.0/24 to 10.0.0.1) and determine that the ACL should be applied inbound on interface GigabitEthernet0/1.
✓ D.Add the permit statement: access-list 100 permit ip any any
✓ E.Enter interface configuration mode for GigabitEthernet0/1.
✓ F.Apply the ACL inbound: ip access-group 100 in
✓ G.Verify the ACL is active: show ip interface GigabitEthernet0/1 | include access list
Why A: Correct order: 1) Identify the traffic to filter and the interface/direction because this planning determines all subsequent configuration choices. 2) Enter global configuration mode to access ACL definition. 3) Configure the deny statement first — ACLs are processed top-down, so the specific deny must precede the general permit to actually block the unwanted traffic. 4) Add the permit statement after the deny to allow everything else. 5) Enter interface configuration mode to attach the ACL to a specific port. 6) Apply the ACL with the correct direction (inbound) using the ip access-group command, which activates the filtering. 7) Verify the ACL is correctly applied to confirm the configuration is functioning as intended.
Last reviewed: Jun 6, 2026
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This 200-301 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-301 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.