When setting up an AEM instance, an OSGi configuration needs to be applied that cannot be changed at runtime.
How can the DevOps Engineer achieve this requirement?
Which monitoring practices help ensure AEM's long-term stability? (Choose three)
A DevOps engineer receives a ticket to fix a page that is not displaying the latest data.
The environment consists of an author instance, two publish instances, two dispatcher instances, and a load balancer.
The page is a single page application that uses JSON based resources.
No CDN is being used.
The page is loading properly when directly accessing a publish instance.
Requesting the resource using wget through the load balancer delivers an invalid JSON.
The dispatcher flush agent is working on the publish instance.
The issue is reproducible when accessing the page through the load balancer.
What is the issue?
A DevOps engineer is monitoring an Adobe Managed Services AEM Sites environment. AEM Sites is being run for the customer. During the performance tests conducted via Cloud Manager, the DevOps engineer notices high CPU utilization.
What should the DevOps engineer do?
A customer of multiple Adobe Experience Cloud products, including Analytics, Tags, and AEM as a Cloud Service, recently onboarded a new team for their Technical Documentation site. This team is separate from the team that manages the Marketing site. The Marketing team was the first group to start using AEM, and they originally named their Admin Console group, "AEM Authors".
To enable independent permissions management for both teams, 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 is unable to access the Production environment after being added to the "Marketing AEM Authors" group in Admin Console.
What should the DevOps engineer do?