Question 90
A support ticket describes this FortiManager problem: A policy import reports an object name collision where FortiManager and the managed FortiGate define the same name differently. Which risk is most directly involved?
Explanation
Correct Answer
This mechanism explains the problem. The appropriate correction is: Review the conflicting object values and choose an explicit supported reconciliation in the import workflow.
Incorrect Answers
That risk arises in a different situation: A security group needs to track change owner and application classification on FortiManager policy objects for audit reports. This separate concern does not meet the requested risk for Blindly accepting one conflicting object can change.
That risk arises in a different situation: Several policies use nearly identical lists of approved application server IP addresses and must remain consistent. The current risk instead turns on Blindly accepting one conflicting object can change.
That risk arises in a different situation: A FortiManager team enables workflow mode, but operators try to edit policies without opening an eligible change session. The primary requirement remains Blindly accepting one conflicting object can change, not that separate capability.