Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Fortinet NSE8_812 Exam - Topic 1 Question 17 Discussion

Refer to the exhibit showing a FortiView monitor screen.After a Secure SD-WAN implementation a customer reports that in FortiAnalyzer under FortiView Secure SD-WAN Monitor there is No Device for selection.What can cause this issue?
A) Upload option from FortiGate to FortiAnalyzer is not set as a real time.
B) Extended logging is not enabled on FortiGate.
C) ADOM 1 is set as a Fabric ADOM.
D) sla-fail-log-period and sla-pass-log-period on FortiGate health check is not set.

Fortinet NSE8_812 Exam - Topic 1 Question 17 Discussion

Actual exam question for Fortinet's NSE8_812 exam
Question #: 17
Topic #: 1
[All NSE8_812 Questions]

Refer to the exhibit showing a FortiView monitor screen.

After a Secure SD-WAN implementation a customer reports that in FortiAnalyzer under FortiView Secure SD-WAN Monitor there is No Device for selection.

What can cause this issue?

Show Suggested Answer Hide Answer
Suggested Answer: A

A is correct because using network-overlay id allows you to configure multiple ADVPN tunnels on a single interface with a single IP address on the DC FortiGate. This is explained in the FortiGate Administration Guide under ADVPN > Configuring ADVPN > Configuring ADVPN on the hub. References: https://docs.fortinet.com/document/fortigate/7.4.0/administration-guide/978793/advpn https://docs.fortinet.com/document/fortigate/7.4.0/administration-guide/978793/advpn/978794/configuring-advpn


by Garry at Mar 08, 2024, 01:27 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Dacia
9 months ago
Surprised no one mentioned the health check settings, option D could be it!
upvoted 0 times
...
Karl
9 months ago
I heard option A can cause issues too, real-time uploads matter.
upvoted 0 times
...
Shanda
9 months ago
Wait, could it really be option C? Fabric ADOMs are tricky.
upvoted 0 times
...
Glynda
10 months ago
Definitely agree with that, logging is crucial for monitoring!
upvoted 0 times
...
Della
10 months ago
I think it's option B, extended logging needs to be enabled.
upvoted 0 times
...
Deane
10 months ago
I don't recall much about the sla-fail-log-period settings. Could that really affect device visibility in FortiView?
upvoted 0 times
...
Karina
10 months ago
I'm not entirely sure, but I feel like the ADOM settings could be causing this. We discussed Fabric ADOMs in class.
upvoted 0 times
...
Pok
10 months ago
I think extended logging might be the key here. We practiced a similar question where logging was the issue.
upvoted 0 times
...
Dominic
11 months ago
I remember something about the upload settings; could it be that the real-time option isn't enabled?
upvoted 0 times
...
Amie
11 months ago
Ah, this is a good one. I bet it has to do with the real-time upload or the health check settings. I'll make sure to review those carefully.
upvoted 0 times
...
Mira
11 months ago
Hmm, the lack of a device in FortiAnalyzer could be due to a few different issues. I'll need to consider the configuration settings on both the FortiGate and FortiAnalyzer.
upvoted 0 times
...
Belen
11 months ago
This seems like a tricky one. I'll need to carefully review the options and think through the potential causes.
upvoted 0 times
...
Dominga
11 months ago
Okay, let's see. I'm thinking it might be related to the logging configuration or the ADOM settings. I'll need to double-check those areas.
upvoted 0 times
...
Rebbecca
11 months ago
I'm pretty sure the api logs are located in $FWDIR/log/api.elg, but I'll double-check the options just to be sure.
upvoted 0 times
...
Jade
11 months ago
I'm a little confused by all the options. Software Restriction Policies and Active Directory Federated Services don't seem to match the requirements very well. I'm leaning towards either Dynamic Access Control or Azure Rights Management, but I'll need to review the details of each one to make a final decision.
upvoted 0 times
...
Sheridan
11 months ago
This question seems pretty straightforward. I think the key is to understand the differences between intradomain and interdomain multicast routing.
upvoted 0 times
...
Felicitas
11 months ago
The build array function in a While loop sounds interesting, but I'm not familiar with that approach. I'll need to research it more to see if it's really the most efficient method.
upvoted 0 times
...
Linn
1 year ago
Hey, at least the question didn't ask about configuring the SD-WAN 'Mood Swing' feature. That one's always a doozy!
upvoted 0 times
Jaclyn
1 year ago
C) ADOM 1 is set as a Fabric ADOM.
upvoted 0 times
...
Ozell
1 year ago
B) Extended logging is not enabled on FortiGate.
upvoted 0 times
...
Tiera
1 year ago
A) Upload option from FortiGate to FortiAnalyzer is not set as a real time.
upvoted 0 times
...
...
Lilli
1 year ago
Ah, the joys of troubleshooting Secure SD-WAN! I bet the answer is hidden in the 'extended logging' setting, like a needle in a haystack.
upvoted 0 times
Ernestine
1 year ago
C) ADOM 1 is set as a Fabric ADOM.
upvoted 0 times
...
Kimbery
1 year ago
B) Extended logging is not enabled on FortiGate.
upvoted 0 times
...
Carmelina
1 year ago
A) Upload option from FortiGate to FortiAnalyzer is not set as a real time.
upvoted 0 times
...
...
Marcelle
1 year ago
Hmm, I think I'll have to go with A. If the real-time upload from FortiGate to FortiAnalyzer is not set, that would explain the missing device data.
upvoted 0 times
Melvin
1 year ago
User 4: Let's double check that setting to see if that resolves the missing device data.
upvoted 0 times
...
Herminia
1 year ago
User 3: It's important to have that connection between FortiGate and FortiAnalyzer for accurate monitoring.
upvoted 0 times
...
Thad
1 year ago
User 2: Maybe we should check the settings to make sure the real-time upload is enabled.
upvoted 0 times
...
Maryln
1 year ago
User 1: I agree, A seems like the most likely cause for the issue.
upvoted 0 times
...
...
Crista
1 year ago
I'm going with C. Setting the ADOM as a Fabric ADOM could definitely cause this issue with the Secure SD-WAN monitor.
upvoted 0 times
...
Dannie
1 year ago
D sounds like the right choice to me. If the health check logging periods are not set, the SD-WAN data may not be making it to FortiAnalyzer.
upvoted 0 times
Mozelle
1 year ago
User 2: Yeah, if the health check logging periods are not set, the SD-WAN data may not be making it to FortiAnalyzer.
upvoted 0 times
...
Dorathy
1 year ago
User 1: I think D is the correct answer.
upvoted 0 times
...
...
Annmarie
1 year ago
Option B seems to be the correct answer. Extended logging needs to be enabled on the FortiGate for the Secure SD-WAN data to be visible in FortiAnalyzer.
upvoted 0 times
...
Laine
1 year ago
I believe it could also be related to the ADOM 1 being set as a Fabric ADOM.
upvoted 0 times
...
Annmarie
1 year ago
I agree with Amos, that could be causing the problem.
upvoted 0 times
...
Amos
1 year ago
I think the issue might be with the upload option not set as real time.
upvoted 0 times
...

Save Cancel