Question 160
A change reviewer anticipates problems with this requirement: A FortiManager device revision changed overnight with no corresponding central change ticket. What should be checked before rollout?
Explanation
Correct Answer
This preparation reduces the risk that an unexplained revision may be a local change, automated retrieval or an unauthorized modification. Check the resulting system state: The relevant revision record identifies the changed settings and associated management event.
Incorrect Answers
That precaution addresses another failure: an overall task completion status can conceal device-specific failures. That does not establish the case-specific action: Keep revision retention and operator attribution enabled.
That precaution addresses another failure: generic reachability tests alone may miss protocol-level authentication or keepalive failures. The current action instead turns on Keep revision retention and operator attribution enabled.
That precaution addresses another failure: repeated unseen local modifications can continuously undo central package consistency. The primary requirement remains Keep revision retention and operator attribution enabled, not that separate capability.