The correct answer is D .
In the exhibit, get router info routing-table database shows both static default routes:
* 0.0.0.0/0 [20/0] via 100.64.2.254, port2
* 0.0.0.0/0 [10/0] via 100.64.1.254, port1
But get router info routing-table all shows only:
* 0.0.0.0/0 [10/0] via 100.64.1.254, port1
The study guide explains that get router info routing-table all displays the routes that make it to the FIB
- the best active routes . It also says that this command doesn't show standby or inactive routes , which can remain only in the routing table database. It gives the exact rule: "when two static routes to the same destination subnet have different distances, the one with the lower distance is installed in the routing table, and the one with the higher distance is installed in the routing table database." The study guide also shows the route selection process:
* Most specific route
* Lowest distance
* Lowest metric (dynamic routes)
* Lowest priority (static routes)
* ECMP
So the port2 default route is absent from the second output because its distance is 20 , while the port1 default route has distance 10 . The lower-distance route is installed in the active routing table/FIB.
Why the other options are wrong:
* A is wrong because the exhibit does not indicate port2 is down or disabled.
* B and C are wrong because priority is checked only after distance for static routes. Here, the routes already differ by distance , so priority is not the deciding factor.
So the verified answer is: D .

The correct answers are A and B .
The Network Security Support Engineer 7.6 Study Guide states under OSPF Troubleshooting :
"Follow these steps to troubleshoot an OSPF problem between two peers:
* Check that the local router can reach the remote peer. IP addresses must be in the same subnet and have the same subnet mask.
* Ensure that IP protocol 89 is not blocked.
* Hello and dead intervals must match.
* The OSPF router ID for each peer must be unique. Duplicate router IDs are not allowed.
* Do the MTUs match?
* If authentication is enabled, the type and password must match on both sides."** The same page also summarizes the troubleshooting tips as:
* "Do peers have an IP address within the same subnet?"
* "Is IP protocol 89 blocked?"
This directly confirms:
* A is correct
* B is correct
Why the other options are wrong:
* C is wrong because TCP port 179 is used by BGP , not OSPF. OSPF uses IP protocol 89 , as the study guide explicitly notes
* D is wrong because the study guide's OSPF adjacency troubleshooting checklist does not require an active static route to the peer. OSPF neighbors form adjacency on directly reachable networks, and the guide instead focuses on same subnet, protocol 89, intervals, router ID, MTU, and authentication matching So the verified answers are: A, B .

The correct answer is C. 64.26.151.37 .
The study guide explains the FortiGuard flags shown by diagnose debug rating:
* D = Default
* I = Initial
* T = Timing
* F = Failed and specifically: "F = The server is down"
So even though 121.111.236.179 has the lowest RTT in the exhibit, it has the F flag, meaning FortiGate considers that server failed/down , so it will not be chosen.
To determine which active server is selected, the FortiOS administration guide states:
"The server list is sorted first by weight. The server with the smallest RTT appears at the top of the list regardless of weight. ... Therefore the top position in the list is selected based on RTT while the other positions are based on weight." Among the valid, non-failed choices in the exhibit:
* 64.26.151.37 # RTT 45
* 209.22.147.36 # RTT 103
* 96.45.33.65 # RTT 144
* 208.91.112.194 # RTT 107
The active server with the lowest RTT is 64.26.151.37 , so that is the server FortiGate will choose.
So the verified answer is: C .

The study guide identifies this exact output as an expectation session created by the FTP session helper :
* "run helper-ftp" indicates the FTP helper is in use.
* "FortiGate created an expectation session and opened the pinhole port for the expected return traffic" It also explains why this exists:
* "Another important function of the session helper is to temporarily create an expected session (or pinhole) for the data channel connection that comes from the server."
* "The session helper automatically creates the session and opens the door for the incoming connection."
* "These incoming TCP sessions use random TCP port numbers."
That directly proves C is correct.
For A , the exhibit shows expire=23. The study guide explains the expire field as the length of time until the session expires if no matching traffic arrives, and the FortiOS guide states for expectation sessions:
* "Expectation sessions usually have a timeout value of 30 seconds. If the communication from the server is not initiated within 30 seconds the expectation session times out and traffic will be denied." So with expire=23, FortiGate will allow that expected traffic only for the remaining 23 seconds; after that, it times out and the traffic is denied. That makes A correct.
Why the other options are wrong:
* B is not supported . The study guide describes expectation sessions as being created by the session helper from the control-session negotiation, not as independent objects unaffected by the master session.
* D is wrong as stated. Even though the output contains policy_id=25, the study guide explicitly says the incoming expected connection is allowed by the expected session itself, "even when no firewall policy allows it."