NSE7_SSE_AD-25 · Question #25
Refer to the exhibits. A FortiSASE administrator has configured FortiSASE as a spoke to a FortiGate hub. The tunnel is up to the FortiGate hub. However, the remote FortiClient is not able to access…
The correct answer is D. The server subnet BGP route was not received on FortiSASE. The FortiSASE BGP learned routes do not include the 10.160.160.0/24 subnet (server network). Although the FortiGate hub is advertising this route (10.160.160.0/24) to FortiSASE, it is not visible in the FortiSASE BGP route table - indicating a routing issue. Without this route…
Question
Refer to the exhibits. A FortiSASE administrator has configured FortiSASE as a spoke to a FortiGate hub. The tunnel is up to the FortiGate hub. However, the remote FortiClient is not able to access the web server hosted behind the FortiGate hub. Based on the exhibits, what is the reason for the access failure?
Exhibits
Options
- AA private access policy has denied the traffic because of failed compliance
- BThe hub is not advertising the required routes.
- CThe hub firewall policy does not include the FortiClient address range.
- DThe server subnet BGP route was not received on FortiSASE.
How the community answered
(18 responses)- A6% (1)
- B6% (1)
- C11% (2)
- D78% (14)
Explanation
The FortiSASE BGP learned routes do not include the 10.160.160.0/24 subnet (server network). Although the FortiGate hub is advertising this route (10.160.160.0/24) to FortiSASE, it is not visible in the FortiSASE BGP route table - indicating a routing issue. Without this route, FortiSASE cannot forward traffic from FortiClient to the server.
Topics
Community Discussion
No community discussion yet for this question.