QuestionQ16
Security, Access, and PermissionsA customer uses several Adobe Experience Cloud products, including Analytics, Tags, and AEM as a Cloud Service, and has recently onboarded a new team for its Technical Documentation site. This team is distinct from the team that manages the Marketing site. The Marketing team was the first team to use AEM and originally named its Admin Console group, “AEM Authors.”
To allow both teams to manage permissions independently, the Admin Console Administrator renames the “AEM Authors” group to “Marketing AEM Authors” and adds a separate group for the Technical Documentation authors.
The DevOps engineer receives a report from the Marketing team that a new team member cannot access the Production environment after being added to the “Marketing AEM Authors” group in Admin Console.
What should the DevOps engineer do?
- A Using repoinit, migrate the user accounts from the "Marketing AEM Authors" group to the "AEM Authors" group.
- B In AEM, rename the "AEM Authors" group to "Marketing AEM Authors" to match the Admin Console group name.
- C Using repoinit, change the rep:externalId property for the "AEM Authors" group to "Marketing AEM Authors;ims".
- D In AEM, make the "Marketing AEM Authors" group a member of the same group as the "AEM Authors" group.
Community Discussion