Question 350
A production maintenance plan must handle this scenario: An installed FortiManager package looks synchronized immediately after deployment but becomes modified again within hours. What preventive step is most appropriate?
Explanation
Correct Answer
This preparation reduces the risk that repeated unseen local modifications can continuously undo central package consistency. Check the resulting system state: A monitored comparison stays synchronized after the underlying drift mechanism is corrected.
Incorrect Answers
That precaution addresses another failure: old ADOM package identifiers cannot be assumed valid after a managed device move. This separate concern does not meet the requested action for Coordinate local management privileges and scheduled jobs.
That precaution addresses another failure: installing a valid package on an unrelated gateway leaves the real enforcement point unchanged. The current action instead turns on Coordinate local management privileges and scheduled jobs.
That precaution addresses another failure: a corrupted database or file system can break imports and installations even when the GUI loads. The primary requirement remains Coordinate local management privileges and scheduled jobs, not that separate capability.