A network administrator is troubleshooting an intermittent reachability issue affecting a Linux web server located in a corporate DMZ subnet (). Internal workstations on the LAN () can ping their local default gateway (), but cannot reach the web server at on TCP port 443. The administrator executes diagnostic commands and observes the following output:
text C:\Users\admin> traceroute 10.50.100.45 traceroute to 10.50.100.45, 30 hops max, 60 byte packets 1 192.168.10.1 (192.168.10.1) 1.102 ms 0.985 ms 0.950 ms 2 10.200.1.1 (10.200.1.1) 3.421 ms 3.211 ms 3.105 ms 3 * * * 4 * * *
A inspect of the gateway router () inbound Access Control List (ACL) on the interface facing the core router reveals:
text 10 permit tcp 192.168.10.0 0.0.0.255 10.50.100.0 0.0.0.255 eq 80 20 permit icmp 192.168.10.0 0.0.0.255 10.50.100.0 0.0.0.255 30 deny ip any any
Additionally, direct diagnostic checks on the web server () show its IPv4 address is configured as with a default gateway configured as .
Which TWO of the following underlying issues are preventing workstation connections to the web server over HTTPS?
- The Access Control List on the gateway router lacks a rule permitting TCP port 443 traffic, causing HTTPS packets to trigger the implicit or explicit deny rule.Cevap
- The web server's default gateway IP address resides on a different IP subnet than its assigned interface address, preventing it from routing return packets.Cevap
- CThe traceroute utility failed because ICMP Echo Request traffic is strictly blocked by line 20 of the router's inbound Access Control List.
- DThe web server is automatically assigning itself an APIPA address because the gateway router is unable to act as a DHCP relay agent.