An engineer wants to modify the user information on the Agile Controller, but finds that it cannot be modified. What is the possible reason? (Multiple choice)

Question

Options

• AThe engineer's Agile Controller account has insufficient permissions
• BUser information is synchronized from the AD directory server
• CAgile Controller created the same user information
• DThe relevant user information in the AD directory server is deleted

• A
  80% (16)
• C
  10% (2)
• D
  10% (2)

Explanation

A is correct because access control is fundamental - if the engineer lacks write/admin permissions on the Agile Controller, the system will simply block any edits to user information, regardless of what they're trying to change.

B is correct because when user accounts are synchronized from an external AD (Active Directory) directory server, those accounts become read-only on the Agile Controller side. The source of truth is AD, so modifications must be made there - the controller only mirrors what AD provides.

C is wrong because having a duplicate user locally doesn't prevent modification; it might cause a conflict error, but it doesn't make existing records uneditable in the same way.

D is wrong because deleting a record in AD would typically cause the synced account to disappear or become orphaned on the controller, not become locked/uneditable - it's the opposite direction of the problem.

Memory tip: Think "who owns the data?" - if AD owns it (sync source), only AD can change it (B); if you don't have the keys to the door, you can't open it (A). Both answers are about authority - either organizational (permissions) or architectural (data ownership).

No community discussion yet for this question.