Cyber Monday 2024! 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 Exam NSE5_FMG-7.2 Topic 2 Question 14 Discussion

Actual exam question for Fortinet's NSE5_FMG-7.2 exam
Question #: 14
Topic #: 2
[All NSE5_FMG-7.2 Questions]

Which two conditions trigger FortiManager to create a new revision history? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: B, C

by Tandra at Jul 08, 2024, 03:11 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Sheron
4 months ago
This is a good question. I think the key is understanding what triggers FortiManager to create a new revision - the database changes and reverting to previous versions. Gotta stay on top of that revision history!
upvoted 0 times
Gennie
3 months ago
D) When a configuration revision is reverted to a previous revision in the revision history
upvoted 0 times
...
Yuonne
3 months ago
I agree, it's important to keep track of those triggers for revision history.
upvoted 0 times
...
Johnna
3 months ago
C) When FortiManager installs device-level changes on a managed device
upvoted 0 times
...
Julian
4 months ago
A) When FortiManager is auto-updated with configuration changes made directly on a managed device
upvoted 0 times
...
...
Rochell
4 months ago
I believe it's A and C because those actions involve changes being made on FortiManager.
upvoted 0 times
...
Jani
5 months ago
Haha, I'm just hoping I don't accidentally revert to a previous revision and erase all my hard work! But yeah, B and D sound right to me.
upvoted 0 times
...
Dong
5 months ago
I'm not sure, I think it might be B and D.
upvoted 0 times
...
Paul
5 months ago
I agree with Alva. B and D are the correct answers. Revision history is important for tracking configuration changes.
upvoted 0 times
Carmelina
4 months ago
C) When FortiManager installs device-level changes on a managed device
upvoted 0 times
...
Ashley
4 months ago
B) When changes to the device-level database are made on FortiManager
upvoted 0 times
...
Rima
4 months ago
A) When FortiManager is auto-updated with configuration changes made directly on a managed device
upvoted 0 times
...
Cary
4 months ago
C) When FortiManager installs device-level changes on a managed device
upvoted 0 times
...
Rima
4 months ago
B) When changes to the device-level database are made on FortiManager
upvoted 0 times
...
Nada
4 months ago
A) When FortiManager is auto-updated with configuration changes made directly on a managed device
upvoted 0 times
...
...
Alva
5 months ago
I'm pretty sure it's B and D. Anytime changes are made to the device-level database or a previous revision is reverted, it creates a new revision history.
upvoted 0 times
Jolanda
4 months ago
I'm pretty sure it's B and D. Anytime changes are made to the device-level database or a previous revision is reverted, it creates a new revision history.
upvoted 0 times
...
Rikki
4 months ago
I think it's A and C. When FortiManager is auto-updated with configuration changes or installs device-level changes, it creates a new revision history.
upvoted 0 times
...
...
Walton
5 months ago
I agree with Deangelo, those two conditions make sense.
upvoted 0 times
...
Deangelo
5 months ago
I think it's A and C.
upvoted 0 times
...

Save Cancel