Question 610
A production maintenance plan must handle this scenario: An administrator needs to modify one rule in a very large shared policy package without granting broad concurrent editing rights. What preventive step is most appropriate?
Explanation
Correct Answer
This preparation reduces the risk that assuming rule-level locking is always enabled can produce unauthorized or conflicting edits. Check the resulting system state: The designated policy is locked to its editor and unrelated rules remain protected.
Incorrect Answers
That precaution addresses another failure: locking the entire ADOM for a narrow change can unnecessarily block other valid administrators. That does not establish the case-specific action: Verify that the selected FortiManager and ADOM.
That precaution addresses another failure: focusing only on the latest rule can miss shared-object changes that altered effective access. This separate concern does not meet the requested action for Verify that the selected FortiManager and ADOM.
That precaution addresses another failure: an overly broad destination object expands access beyond the authorized service even with the correct port. The current action instead turns on Verify that the selected FortiManager and ADOM.