Exam NSE5_FMG-7.2 topic 1 question 51 discussion

A&B are correct. The admins can lock one or more policies each and can work on the same ADOM! C is nonsense cuz nothing is disabled unless one admin has locked an ADOM!

B and C

B. Correct. In normal workspace mode, an administrator can lock multiple ADOMs or projects for editing simultaneously. This allows for flexibility in managing various parts of the network without being restricted to a single ADOM at a time. C. Correct. This is in line with the idea of locking in workspace mode. While in normal mode, concurrent read-write access is indeed disabled, ensuring that only the administrator who has locked the ADOM can make changes. This prevents conflicts and overwrites in configurations.

B and C

B & C A - wrong they do not refer to policy lock so is just workspace mode normal. Once a user locks the ADOM that particular ADOM appers with a red lock to any other user. I put that in a lab. b - Correct the user can lock more than one ADOMs. Put that is a lab too c - seems correct as that justifies to what I say for option A. d - doent make sense

I would say this is BC Question shows Workspace-mode normal - it's not stating policy locking is enabled, so i assume it is disabled. A - With workspace mode you have to lock the ADOM, which prevents other admins from using the ADOM. -- Incorrect B - An Admin can lock multiple ADOMs at the same time - Correct C. Once workspace is enabled (not policy locking) and the Admin has locked an ADOM. Then no other Admins can make changes to that ADOM until it's been unlocked by the original Admin - Correct D. Syslog servers can be enabled for event logs, but it's not what the questions looking for. So I'd say incorrect.

Ingore my previous answer, copy and past did not work... 7.4 study guide, pg 205 policy locking and workflow Policy locking is available in workspace normal and per-ADOM modes. Policy locking allows administrators to work on, and lock, sing policy package instead of locking the whole ADOM. In order to use policy locking, you must set workspace-mode to normal. You can lock either the whole ADOM or a specific policy package. So, this: A) two or more administrators in the same ADOM (correct - policy locking) B) does not prevent being in multiple ADOMS (correct) C) Incorrect - Concurrent RW access to ADOM is disabled (policy locking allows this per ADOM) D) Incorrect - obviously not an answer for this question. Nothing to do with authentication

7.4 study guide, pg 205 policy locking and workflow ADOM revision history allows you to maintain a revision of the policy packages, objects, and VPN console settings in an ADOM.

Answer AB for my. Page 239 Study Guide Policy locking is available in workspace normal mode only. Policy locking allows administrators to work on, and lock, a single policy package instead of locking the whole ADOM. In order to use policy locking, you must set workspace-mode to normal. You can lock either the whole ADOM or a specific policy package. Policy locking is an extension of ADOM locking, which allows multiple administrators to work on separate policy packages on the same ADOM at the same time.