Question 400
A Fortinet team is working on this situation: a customer wants PoPs to function as SD-WAN spokes while reusing an existing secure WAN. It attempted: Integrate FortiSASE using PoP-to-hub IPsec overlay service connections. Expected evidence (Check that PoPs appear as peers/routes within the hub-spoke network) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
Explanation
Correct Answer
Repair the service connection or peering before deploying redundant public direct-access policies. The missing evidence (check that PoPs appear as peers/routes within the hub-spoke network) points to a problem with the implementation of integrate FortiSASE using PoP-to-hub IPsec overlay service connections. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
Resolve license or location-capacity mismatches before adding new site tunnels addresses a different operational issue: a design requires a separate on-ramp subscription for multiple remote offices. This situation calls for repair the service connection or peering before deploying redundant public direct-access policies because the missing result relates to check that PoPs appear as peers/routes within the hub-spoke network.
Correct the misconfigured additional tunnel rather than deleting the functioning first device addresses a different operational issue: a branch-on-ramp deployment needs to support more than one IPsec router in one location. This situation calls for repair the service connection or peering before deploying redundant public direct-access policies because the missing result relates to check that PoPs appear as peers/routes within the hub-spoke network.
Correct the LAN gateway or edge tunnel before distributing unnecessary endpoint VPN profiles addresses a different operational issue: a campus plans to connect devices with ordinary LAN gateway settings rather than desktop VPN software. This situation calls for repair the service connection or peering before deploying redundant public direct-access policies because the missing result relates to check that PoPs appear as peers/routes within the hub-spoke network.



Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests