An AEM development team is working on a new multi-country application using AEM as a Cloud Service. A developer has been assigned the task for building the integration with a third-party web service. A secret key is needed to connect with this web service. The website creators will provide this key. The key is different for each type of environment (dev, stage and production)
What is the recommended way to make the secret key available in the AEM application?
The recommended way to make the secret key available in the AEM application is to use an environment variable which is then consumed by an OSGi configuration. This way, the secret key is not stored in the code base or in the repository, but rather in a secure and encrypted way in the Cloud Manager environment variables. The OSGi configuration can use a placeholder to reference the environment variable and inject its value at runtime. Reference: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/deploying/configuring-osgi.html?lang=en#environment-variables https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/deploying/environment-variables.html?lang=en
An AEM as a Cloud Service implementation customer wants content to be replicated as soon as the On Time and Off Times are reached.
What must the developer configure?
The Auto Replicate via On Off Trigger Configuration is a feature that allows content to be replicated as soon as the On Time and Off Times are reached. This feature can be enabled by creating an OSGi configuration for the com.day.cq.wcm.core.impl.servlets.OnOffTimeServlet service. This service listens for changes in the On Time and Off Time properties of pages and triggers replication accordingly. Reference: https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/replication.html?lang=en#on-off-time https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/replication.html?lang=en#auto-replication
The OSGi configuration is added to a runmode specific configuration "config.author.staging" in AEM as a Cloud Service. The application fails to read the configuration.
What is a possible cause of this issue?
AEM as a Cloud Service does not support custom OSGi configuration runmodes, such as ''config.author.staging''. Only <service> specific OSGi configuration runmodes, such as ''config.author'' or ''config.publish'', are supported. These runmodes are used to apply configurations to specific services, such as author or publish. The <service> specific runmodes can be combined with environment variables to achieve different configurations for different environments. Reference: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/deploying/configuring-osgi.html?lang=en#run-modes https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/deploying/environment-variables.html?lang=en
Which AEM as a Cloud Service role can configure or run pipelines?
The Deployment Manager is a role that can configure or run pipelines in Cloud Manager. The Deployment Manager can create and edit programs and environments, configure pipelines, start and cancel pipeline executions, and approve or reject deployments to production. The Deployment Manager role requires an IMS ID that is associated with the Adobe Experience Cloud product profile. Reference: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/using-cloud-manager/adding-users-to-programs-and-environments.html?lang=en#roles-and-responsibilities https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/using-cloud-manager/cloud-manager-user-roles.html?lang=en
A customer who is running an AEM application on premise reports that the application is slowing down over time and even crashes The issues seem to start occurring after a new production deployment. The AEM developer knows that the described symptoms could be caused by a memory leak.
Which two steps should be taken after confirming the problem is related to a memory issue? (Choose two.)
Creating a heap dump and a thread dump are two steps that should be taken after confirming the problem is related to a memory issue. A heap dump is a snapshot of the memory usage of the Java Virtual Machine (JVM) at a given point in time. A heap dump can be used to identify memory leaks, memory consumption patterns, and objects that occupy large amounts of memory. A thread dump is a snapshot of the state of all threads that are part of the JVM process. A thread dump can be used to identify deadlocks, blocked threads, and CPU-intensive threads. Reference: https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/memory-analysis.html?lang=en https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/thread-dump-analysis.html?lang=en