Fortinet Exam FCSS_SASE_AD-24 Topic 1 Question 5 Discussion

Actual exam question for Fortinet's FCSS_SASE_AD-24 exam

Question #: 5
Topic #: 1

Refer to the exhibits.

A FortiSASE administrator is trying to configure FortiSASE as a spoke to a FortiGate hub. The tunnel is up to the FortiGale hub. However, the administrator is not able to ping the webserver hosted behind the FortiGate hub.

Based on the output, what is the reason for the ping failures?

AThe Secure Private Access (SPA) policy needs to allow PING service.

BQuick mode selectors are restricting the subnet.

CThe BGP route is not received.

DNetwork address translation (NAT) is not enabled on the spoke-to-hub policy.

Show Suggested Answer

Suggested Answer: C

by Cassie at Mar 06, 2025, 06:49 AM

Limited Time Offer

25%

Off

Get Premium FCSS_SASE_AD-24 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Brice

2 months ago

I'm gonna go with C. The BGP route not being received seems like the culprit here. Though I'm also tempted to blame the webserver for being too shy to come out and play. Maybe it's just camera-shy.

upvoted 0 times

Judy

29 days ago

C: I'm gonna go with C. The BGP route not being received seems like the culprit here.

upvoted 0 times

...

Viola

1 months ago

B: I disagree, I believe it's D. NAT needs to be enabled on the spoke-to-hub policy.

upvoted 0 times

...

Gertude

1 months ago

A: I think it might be A. The SPA policy needs to allow PING service.

upvoted 0 times

...

Berry

2 months ago

Ooh, option B is intriguing. Those quick mode selectors can be real tricky. It's like trying to fit a square peg in a round hole, but with IP subnets. Gotta watch out for those!

upvoted 0 times

...

Fannie

2 months ago

Option D sounds juicy. Maybe the NAT settings are messing things up. You know what they say, 'If in doubt, check the NAT!' Or was it, 'When in NAT, do as the NATs do'? I can never remember.

upvoted 0 times

Ronny

1 months ago

User 3: That could be the issue. NAT settings need to be double-checked for sure.

upvoted 0 times

...

Lauran

1 months ago

User 2: Yeah, NAT can be tricky. Maybe the administrator forgot to enable it on the spoke-to-hub policy.

upvoted 0 times

...

Kanisha

2 months ago

User 1: I think you might be onto something with option D. NAT settings can definitely cause ping failures.

upvoted 0 times

...

Dean

2 months ago

I'm going with option C. If the BGP route isn't being learned, that would explain why the webserver can't be reached. Gotta make sure those routing ducks are in a row.

upvoted 0 times

Mayra

2 months ago

User3: Agreed, ensuring the BGP route is received is crucial for proper connectivity in this setup.

upvoted 0 times

...

Kristeen

2 months ago

User2: Yeah, that could definitely be causing the problem with reaching the webserver.

upvoted 0 times

...

Krissy

2 months ago

User1: I think option C makes sense. If the BGP route isn't received, that could be the issue.

upvoted 0 times

...

Wendell

3 months ago

Hmm, the BGP route not being received sounds like the most likely issue. I mean, if the tunnel is up, the ping should work, right? Unless there's something funky going on with the routing.

upvoted 0 times

Rosio

2 months ago

Hmm, the BGP route not being received sounds like the most likely issue. I mean, if the tunnel is up, the ping should work, right? Unless there's something funky going on with the routing.

upvoted 0 times

...