A new user who is a member of the content-authors group needs to access the AEM web console. The new user should not be added to the administrator's group. What should the Business Practitioner…

Question

Options

• AGive additional permissions to content-authors group
• BUpdate the IMS configuration
• CUpdate the OSGi configuration
• DGive additional permissions to the new user

• A
  9% (3)
• B
  74% (26)
• C
  14% (5)
• D
  3% (1)

Explanation

Updating the IMS (Identity Management System) configuration is correct because, in AEM as a Cloud Service, user access to tools like the web console is governed by IMS product profiles - not by AEM-internal group membership alone. By assigning the appropriate product profile through IMS, the user gains web console access without being elevated to the administrators group, preserving the principle of least privilege.

Why the distractors are wrong:

• A - Modifying the content-authors group permissions affects all group members, violating least-privilege and creating unnecessary security exposure.
• C - OSGi configuration governs framework and service behavior, not user identity and access management.
• D - Granting permissions directly to an individual user bypasses the centralized IMS governance model and doesn't scale; AEM Cloud best practice is to manage access through IMS product profiles.

Memory tip: Think "IMS = the front door." In AEM as a Cloud Service, before a user can touch anything - including the web console - they must be provisioned through IMS. When access needs to change without touching AEM group membership, the answer is almost always the front door (IMS).

No community discussion yet for this question.