Question 440
A production maintenance plan must handle this scenario: A policy import reports an object name collision where FortiManager and the managed FortiGate define the same name differently. What preventive step is most appropriate?
Explanation
Correct Answer
This preparation reduces the risk that blindly accepting one conflicting object can change the behavior of unrelated rules using that name. Check the resulting system state: The imported package references approved object definitions without unexpected replacement.
Incorrect Answers
That precaution addresses another failure: installing without examining the diff can overwrite local changes or deploy unexpected object modifications. That does not establish the case-specific action: Diff conflicting addresses and services before merging.
That precaution addresses another failure: object names alone do not capture reliable business metadata for later review. This separate concern does not meet the requested action for Diff conflicting addresses and services before merging.
That precaution addresses another failure: without a recorded ADOM revision it is difficult to restore coherent rule and object relationships. The primary requirement remains Diff conflicting addresses and services before merging, not that separate capability.