What is the command to configure an extended ACL entry specifying protocol, source, and destination IP?

The command to configure an extended Access Control List (ACL) entry involves specifying the action (permit or deny), the protocol being used, as well as the source and destination IP addresses. The correct syntax for an extended ACL would start with the command access-list, followed by a unique number that defines the ACL, then the action to take (either permit or deny), and finally the specified protocol along with the source and destination IP addresses.

In this context, the provided response captures the required structure. It showcases the use of access-list, clearly indicating that it’s setting up an ACL, before detailing the protocol and the associated IP addresses. This structure is essential for Cisco devices, as it allows for granular control over traffic passing through a network based on more than just IP address—extending to protocols as well.

In contrast, the other choices either lack necessary components or do not fit the correct command syntax for establishing extended ACLs. For instance, omitting access-list or not including the number makes the command incomplete, while the mention of ip access-list extended is more related to a different syntax used for named ACLs rather than numbered ones. Thus, the first option provides the complete command structure required for effective ACL configuration in