A network administrator is troubleshooting an issue where an application host with IPv4 address cannot transmit HTTPS management data to a target server at . Diagnostic tests reveal that the host can successfully ping its default gateway (), but a traceroute to stops at . Inspecting the gateway router shows the following configuration details:
text
ip route 10.200.5.0 255.255.255.0 192.168.4.1
access-list 105 permit udp host 192.168.4.25 host 10.200.5.50 eq 514
Which TWO of the following factors explain why HTTPS traffic (TCP port 443) fails to reach the destination? (Select TWO.)
- The static route entry uses the gateway router's local LAN IP address as the next hop rather than the upstream router's IP address.Cevap
- The access control list lacks an explicit permit rule for TCP port 443, resulting in the traffic being blocked by the implicit deny.Cevap
- CThe host IP address and its configured default gateway IP address reside on different usable subnets.
- DThe destination IP address belongs to the same VLAN broadcast domain and must be reached via Layer 2 switching without routing.
Cevap
The routing failure occurs because the static route incorrectly references the local gateway's own interface IP address () as the next hop, and the Access Control List lacks a permit statement for TCP port 443, causing HTTPS packets to be dropped by the ACL implicit deny.
The issue stems from two distinct network layer misconfigurations: first, pointing a static route next hop to the router's own inbound interface IP address prevents proper forwarding to the next router; second, ACL 105 only permits UDP port 514 traffic, meaning TCP port 443 traffic hits the implicit deny rule at the end of the ACL.
Adım Adım Çözüm
Anahtar Kavram
Troubleshooting Static Routes and ACL Rules