How do standard and extended ACLs differ on Cisco devices?

Study for the Router and Routing Basics Test with interactive quizzes. Tackle multiple choice questions, explore hints, and review explanations. Prepare for your exam effectively!

Multiple Choice

How do standard and extended ACLs differ on Cisco devices?

Explanation:
Standard ACLs look at where the traffic is coming from—the source IP address—and don’t consider the destination, protocol, or port numbers. Extended ACLs are more flexible: they can filter based on both the source and destination IP addresses, the protocol (such as TCP, UDP, or ICMP), and even specific port numbers. That combination lets you allow or deny very particular kinds of traffic, like web traffic from one host to a specific server, or blocking a particular service between networks. So the correct description matches that standard ACLs filter by source IP only, while extended ACLs filter by source and destination IP plus protocol and ports. The other statements misrepresent what standard and extended ACLs examine (for example, mentioning hostname filtering or assigning a strict inbound/outbound constraint to one type only), which isn’t how Cisco ACLs are defined.

Standard ACLs look at where the traffic is coming from—the source IP address—and don’t consider the destination, protocol, or port numbers. Extended ACLs are more flexible: they can filter based on both the source and destination IP addresses, the protocol (such as TCP, UDP, or ICMP), and even specific port numbers. That combination lets you allow or deny very particular kinds of traffic, like web traffic from one host to a specific server, or blocking a particular service between networks.

So the correct description matches that standard ACLs filter by source IP only, while extended ACLs filter by source and destination IP plus protocol and ports. The other statements misrepresent what standard and extended ACLs examine (for example, mentioning hostname filtering or assigning a strict inbound/outbound constraint to one type only), which isn’t how Cisco ACLs are defined.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy