View all questions & answers for the NSE 6 - FortiManager 7.6 Administrator Exam Materials exam
NSE 6 - FortiManager 7.6 Administrator Exam Materials - Question #25 Discussion
Community Explanations & Comments (7)
Saeed Abd El Halim Hamada
1 year ago
Selected: A, C
Correct Answer: A & C
Omar Ahmed ([email protected])
1 year ago
Selected: A, D
➤ dev-db: not modified
This means no local changes have been made to the device-level database in FortiManager.
BUT "cond: pending" indicates that some action is still pending — possibly a mismatch or update needed.
➤ conf: in sync
The FortiGate's configuration and FortiManager are in sync.
However, "cond: pending" means something is queued (like policy package or template changes not yet pushed).
➤ template: [modified]default
The device is using the default system template, but it has been modified, which implies changes in the system template that will override device-specific settings when installed.
This means no local changes have been made to the device-level database in FortiManager.
BUT "cond: pending" indicates that some action is still pending — possibly a mismatch or update needed.
➤ conf: in sync
The FortiGate's configuration and FortiManager are in sync.
However, "cond: pending" means something is queued (like policy package or template changes not yet pushed).
➤ template: [modified]default
The device is using the default system template, but it has been modified, which implies changes in the system template that will override device-specific settings when installed.
Brave-Dumps.com Admin
11 months ago
Selected: A, C
A&C is the correct option
Mehdi
7 months ago
Selected: A, C
A : The revision history shows "not modified" for the device database, meaning the latest changes on FortiGate do NOT match what's in FortiManager's device-level database
C : Since "conf: in sync" and "dm: installed," the latest revision DOES match the FortiManager policy database (ADOM level)
dev-db: not modified - The device database hasn't been changed
conf: in sync - The configuration is synchronized between FortiGate and FortiManager
cond: pending - There's a pending condition (changes waiting to be installed)
dm: installed - Device Manager (policy) is installed
template:[modified]default - The default template has been modified
C : Since "conf: in sync" and "dm: installed," the latest revision DOES match the FortiManager policy database (ADOM level)
dev-db: not modified - The device database hasn't been changed
conf: in sync - The configuration is synchronized between FortiGate and FortiManager
cond: pending - There's a pending condition (changes waiting to be installed)
dm: installed - Device Manager (policy) is installed
template:[modified]default - The default template has been modified
Anonymous User
7 months ago
Selected: B, D
A is show revisiehistorie is a match
Brave-Dumps.com Admin
6 months ago
Selected: A, C
We edited the question, it is confirmed A,C
ALI HASAN
4 months ago
Selected: A, C
why D is wrong:
pkg:[Imported]
Policies and objects were imported from FortiGate into FortiManager using the 'Import' action, and the action was successful.
Why B is wrong:
cond: pending
This status indicates device-level settings have been made on the FortiManager, and changes are yet to be installed on the FortiGate.
so: AC are right.
https://community.fortinet.com/fortimanager-27/technical-guide-understanding-fortimanager-core-operations-and-device-database-status-policy-package-status-with-examples-227625
pkg:[Imported]
Policies and objects were imported from FortiGate into FortiManager using the 'Import' action, and the action was successful.
Why B is wrong:
cond: pending
This status indicates device-level settings have been made on the FortiManager, and changes are yet to be installed on the FortiGate.
so: AC are right.
https://community.fortinet.com/fortimanager-27/technical-guide-understanding-fortimanager-core-operations-and-device-database-status-policy-package-status-with-examples-227625
Which two statements about the output are true? (Choose two answers)
Brave-Dump Community Votes