Diagnose Issues Using Configuration and Revision History NSE6-FORTIMANAGER-ADMINISTRATOR Practice Questions (Page 5)

Questions 21–25

1. 21application · medium

   After a firewall policy change, users at a remote site lost access to a critical SaaS application. The administrator identified the faulty change in the latest revision. The device is currently in a normal (non-bypass) state. What is the correct way to restore the known-good configuration using FortiManager?

   • AUse the FortiGate CLI to upload a backup file that was saved locally on the FortiGate before the change.
   • BSelect the device, open Revision History, right-click the previous good revision, and choose 'Rollback' to restore that configuration.
   • CDelete the current revision from FortiManager so the device automatically reverts to the previous one.
   • DManually edit the current policy in the device's policy package to match the old settings, then install the policy package.
   Reveal Solution Discussion Select an answer first
2. 22foundation · easy

   How does FortiManager structure revision history for a managed device?

   • AAs a database of only the differences between configurations, without full snapshots
   • BAs a single overwritable file that holds only the latest configuration
   • CAs a chronological list of configuration snapshots, each with a timestamp and revision number
   • DAs a log file that records only the commands executed by administrators
   Reveal Solution Discussion Select an answer first
4. 23expert · hard

   A FortiManager administrator needs to roll back a FortiGate to a revision from two weeks ago. However, the device has been in 'bypass' mode for the last three days due to a network issue. What is the most important consideration before performing the rollback?

   • AThe rollback will be queued and applied automatically when the device returns to normal mode.
   • BThe rollback will fail because FortiManager cannot access a device that is in bypass mode.
   • CThe rollback will restore the configuration, but the device must be taken out of bypass mode for the change to take effect and be verified.
   • DThe rollback will automatically disable bypass mode as part of the configuration restore.
   Reveal Solution Discussion Select an answer first
5. 24expert · hard

   After rolling back a FortiGate to a previous revision, the administrator notices that the device's interface IP addresses are correct, but the device is not passing traffic. The revision history shows the rollback was successful. What is the most likely cause of the traffic failure?

   • AThe rollback was not applied correctly because the device was in bypass mode during the rollback.
   • BThe rollback restored the configuration, but the device's routing table or ARP cache may be stale; a reboot or clearing the ARP cache may be needed.
   • CThe previous revision was corrupt, and the rollback restored a broken configuration.
   • DThe FortiGate needs a new license after the rollback because the revision was from before a license renewal.
   Reveal Solution Discussion Select an answer first
6. 25foundation · easy

   How can revision history help diagnose a configuration issue on a managed device?

   • ABy providing real-time monitoring of device performance
   • BBy generating a list of all devices with similar configurations
   • CBy correlating the time of a reported issue with configuration changes made around that time
   • DBy automatically reverting the device to a known-good configuration
   Reveal Solution Discussion Select an answer first