What must the DevOps engineer do to initial onboarding of users who need admin privileges to the AEM as Cloud Service instances?

What must the DevOps engineer do to initial onboarding of users who need admin privileges to the AEM as Cloud Service instances?

• A. Add users to the AEM Administrators-xxx product profile via the Admin Console.
• B. Add users to the Administrators group via the Oak LDAP synchronization.
• C. Add users to the Administrators group on the AEM instances.
• D. Configure the AEM cloud service user directory.

Answer: (A)

Admin privileges in AEM as Cloud Service are granted through product profiles in the Admin Console. Adding a user to the AEM Administrators-xxx product profile gives them the admin capabilities across Cloud Service environments, which is the centralized and supported way to onboard admins. LDAP synchronization, instance-level groups, or simply configuring the user directory don’t confer those broad admin rights on Cloud Service. The user directory defines who can sign in, but the Admin Console product profile determines what they can do, so placing the user into the Administrators-xxx profile is the correct approach.

Admin privileges in AEM as Cloud Service are granted through product profiles in the Admin Console. Adding a user to the AEM Administrators-xxx product profile gives them the admin capabilities across Cloud Service environments, which is the centralized and supported way to onboard admins. LDAP synchronization, instance-level groups, or simply configuring the user directory don’t confer those broad admin rights on Cloud Service. The user directory defines who can sign in, but the Admin Console product profile determines what they can do, so placing the user into the Administrators-xxx profile is the correct approach.