Question 670
Original Fortinet NSE5_SSE_AD-7.6 educational scenario: A service team sees tunnels up between branch and FortiSASE but application sessions fail because the FortiGate has a restrictive destination firewall policy. Which observable result would best verify the correction?
Explanation
Correct Answer
In this situation, a service team sees tunnels up between branch and FortiSASE but application sessions fail because the FortiGate has a restrictive destination firewall policy. The relevant technical mechanism is: Tunnel health alone does not establish application-level permission across policy boundaries. The most direct diagnostic or implementation action is: Inspect tunnel routing and security policy for the exact permitted application flow. A useful verification is: Authorized traffic reaches the protected app while disallowed sources remain blocked. An ongoing safeguard is: Test positive and negative access cases after link integration. This is the INTENDED choice for the strongest verification evidence. The issuer documents define the topic and product background, not the truth of this item-level intended key.
Incorrect Answers
That test belongs to another control with this basis: Identity success and branch network integration depend on different components. In the current case, the governing reason is: Tunnel health alone does not establish application-level permission across policy boundaries. The direct verification is “Authorized traffic reaches the protected app while disallowed sources remain blocked”.
This observation would test a different technical dependency: Forward overlay reachability is insufficient if the application side cannot return to the user source. The current issue is governed by: Tunnel health alone does not establish application-level permission across policy boundaries. Its decisive check is “Authorized traffic reaches the protected app while disallowed sources remain blocked”.
That test belongs to another control with this basis: Successful authentication does not establish correct authorization group membership. In the current case, the governing reason is: Tunnel health alone does not establish application-level permission across policy boundaries. The direct verification is “Authorized traffic reaches the protected app while disallowed sources remain blocked”.