NSE4 Question #240: Real Exam Question with Answer & Explanation

Question

A network administrator connects his PC to the INTERNAL interface on a FortiGate unit. The administrator attempts to make an HTTPS connection to the FortiGate unit on the VLAN1 interface at the IP address of 10.0.1.1, but gets no connectivity. The following troubleshooting commands are executed from the DOS prompt on the PC and from the CLI. C:\>ping 10.0.1.1 Pinging 10.0.1.1 with 32 bytes of data: Reply from 10.0.1.1: bytes=32 time=1ms TTL=255 Reply from 10.0.1.1: bytes=32 time<1ms TTL=255 Reply from 10.0.1.1: bytes=32 time<1ms TTL=255 Reply from 10.0.1.1: bytes=32 time<1ms TTL=255 user1 # get system interface == [ internal ] name. internal mode. static ip: 10.0.1.254 255.255.255.128 status: up netbios-forwarD. disable type. physical mtu-override. disable == [ vlan1 ] name. vlan1 mode. static ip: 10.0.1.1 255.255.255.128 status: up netb ios-forward. disable type. vlan mtu-override. disable user1 # diagnose debug flow trace start 100 user1 # diagnose debug ena user1 # diagnose debug flow filter daddr 10.0.1.1 10.0.1.1 id=20085 trace_id=274 msg="vd-root received a packet(proto=6, 10.0.1.130:47927- >10.0.1.1:443) from internal." id=20085 trace_id=274 msg="allocate a new session-00000b1b" id=20085 trace_id=274 msg="find SNAT: IP-10.0.1.1, port-43798" id=20085 trace_id=274 msg="iprope_in_check() check failed, drop" Based on the output from these commands, which of the following explanations is a possible cause of the problem?

Options

• AThe Fortigate unit has no route back to the PC.
• BThe PC has an IP address in the wrong subnet.
• CThe PC is using an incorrect default gateway IP address.
• DThe FortiGate unit does not have the HTTPS service configured on the VLAN1 interface.
• EThere is no firewall policy allowing traffic from INTERNAL-> VLAN1.