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

Fortinet Exam NSE5_FSM-6.3 Topic 6 Question 7 Discussion

Actual exam question for Fortinet's NSE5_FSM-6.3 exam
Question #: 7
Topic #: 6
[All NSE5_FSM-6.3 Questions]

In FortiSIEM enterprise licensing mode, it the link between the collector and data center FortiSlEM cluster is down, what happens?

Show Suggested Answer Hide Answer
Suggested Answer: D

Enterprise Licensing Mode: In FortiSIEM enterprise licensing mode, collectors are deployed in remote sites to gather and forward data to the central FortiSIEM cluster located in the data center.

Collector Functionality: Collectors are responsible for receiving logs, events (e.g., syslog), and performance metrics from devices.

Link Down Scenario: When the link between the collector and the FortiSIEM cluster is down, the collector needs a mechanism to ensure no data is lost during the disconnection.

Event Buffering: The collector buffers the events locally until the connection is restored, ensuring that no incoming events are lost. This buffered data is then forwarded to the FortiSIEM cluster once the link is re-established.

References: FortiSIEM 6.3 User Guide, Data Collection and Buffering section, explains the behavior of collectors during network disruptions.


Contribute your Thoughts:

Lajuana
10 days ago
I wonder if the exam writers are trying to trick us with these options. Gotta stay on our toes!
upvoted 0 times
...
Renea
11 days ago
Option B sounds a bit too extreme. I can't imagine the collector would just stop processing events entirely if the link goes down.
upvoted 0 times
Aretha
22 hours ago
A) The collector drops incoming events like syslog, but stops performance collection.
upvoted 0 times
...
...
Leigha
20 days ago
I'm not sure, but I think D) The collector buffers events could also be a possibility.
upvoted 0 times
...
Jillian
21 days ago
I bet the correct answer is Option A. Dropping incoming events but still doing performance collection sounds like it would maintain some functionality.
upvoted 0 times
Aliza
7 days ago
I think you're right, Option A does seem like the correct answer.
upvoted 0 times
...
...
Sherron
22 days ago
I disagree, I believe the answer is C) The collector continues performance collection of devices, but stops receiving syslog.
upvoted 0 times
...
Julian
27 days ago
Hmm, I'm not sure. Option C seems a bit strange - why would it stop receiving syslog but continue performance collection?
upvoted 0 times
...
Shawna
30 days ago
Option D seems like the logical choice. The collector should buffer events until the link is restored, right?
upvoted 0 times
Valentin
4 days ago
A) The collector drops incoming events like syslog. but stops performance collection.
upvoted 0 times
...
Pura
22 days ago
A) The collector drops incoming events like syslog. but stops performance collection.
upvoted 0 times
...
...
Audry
1 months ago
I think the answer is A) The collector drops incoming events like syslog, but stops performance collection.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77