AD0-E124 Sample Questions Answers

Unclosed JCR sessions are a classic cause of memory leaks in AEM applications. When custom backend code opens a JCR Session or ResourceResolver but fails to close it within a finally block, the garbage collector cannot reclaim that memory. Over time, these open sessions accumulate in the heap memory, causing the system to slow down and eventually leading to unpredictable OutOfMemory (OOM) crashes. Restarting the instance clears the heap, temporarily mitigating the issue until the unclosed sessions build up again. This issue is agnostic of visitor peaks or runmodes (author/publish).

According to Adobe Support ticketing protocols, once a ticket has been marked as resolved and successfully closed (especially after a prolonged period like three weeks), it cannot be re-opened or escalated. The system locks closed tickets. Even if the symptoms appear identical, a recurrence requires the engineer to open a brand new ticket. They should reference the old ticket number in the new ticket's description so the support team can review the historical context and previous resolutions.

When executing Custom UI Tests (Selenium/Cypress) within an AEM Cloud Manager pipeline, the pipeline looks for a specific Maven module typically named ui.tests. During the dedicated UI Testing phase, Cloud Manager injects an environment variable named CM_BUILD. To ensure the tests are properly triggered and executed inside the Cloud Manager docker container, the Maven profile responsible for the tests (often named ui-tests-docker-execution or similar) must be configured in the pom.xml to activate automatically when the env.CM_BUILD property is present.

In the OSGi lifecycle, a bundle goes through states: Installed - > Resolved - > Active. A bundle remains stuck in the "Installed" state when the OSGi framework cannot resolve its dependencies—specifically, the Java packages listed in its Import-Package manifest header. If a required dependency is missing from the container, the bundle cannot transition to "Resolved". Issues inside the actual components (like exceptions during @Activate, missing configs, or unsatisfied @Reference annotations) will allow the bundle itself to become "Active", but the specific component will remain unsatisfied.

A common race condition (timing conflict) occurs when a Dispatcher Flush agent is configured on the Author instance. The Author sends the content to the Publish instance and simultaneously sends a flush request to the Dispatcher. If the flush request arrives before the Publish instance finishes saving the content, the Dispatcher clears the cache, immediately receives a new request, pulls the old content from the still-updating Publish instance, and caches the old content again. To prevent this, the Dispatcher Flush agent must be configured on the Publish instance. This ensures the flush request is only sent to the Dispatcher after the Publish instance has completely saved the new content.

High CPU utilization in a Java application like AEM is typically caused by active threads stuck in infinite loops, recursive calls, or highly intensive processing tasks. A "Thread Dump" takes a snapshot of exactly what every thread in the JVM is executing at that specific millisecond. By taking multiple thread dumps a few seconds apart and comparing them, a DevOps engineer can identify which specific threads (and therefore which Java classes/methods) are constantly active and consuming the CPU resources. (Heap dumps are used for memory issues, not CPU issues).

In AEM as a Cloud Service, direct access to the legacy AEM Web Console (OSGi console) and traditional Diagnosis tools is restricted for security and architecture reasons. Instead, Adobe provides the Cloud Manager Developer Console. Through this Developer Console, authorized developers and DevOps engineers can execute and analyze JCR queries against specific environments (including Stage and Production) using the "Query Performance" tool to identify unindexed, slow, or traversing queries.

In AEM as a Cloud Service, directly deploying packages via the AEM Package Manager UI is severely restricted. You cannot deploy immutable content (code, OSGi configs, or anything under /apps or /libs) via the Package Manager; immutable content must go through the CI/CD pipeline. If a DevOps engineer is forced to use the Package Manager, the package must be strictly limited to mutable content (authorable content, configurations under /conf, /content, /dam). Therefore, they must refactor the package, explicitly set the < packageType > to content, and update the filter.xml to exclude any immutable paths.

In AEM as a Cloud Service, the Preview tier is designed to act as an internal staging ground to verify content exactly as it will look on Publish, but restricted from the general public. By default, the Preview Service is completely blocked from external access via a default IP Allow List. To grant access to specific internal authors or stakeholders, the DevOps engineer must first remove/unbind this default blocking rule, and then create and bind a custom IP Allow List via Cloud Manager that explicitly whitelists the corporate IP addresses or VPN IP ranges of those specific authors.

To allow an external system (like a CI/CD server or custom dashboard) to programmatically interact with Cloud Manager (such as fetching pipeline metrics), you must set up a server-to-server API integration. This is done via the Adobe Developer Console (Adobe I/O). The DevOps engineer must create a new project, add the Cloud Manager API service, and configure authentication using a public/private key pair (typically generating a JWT token for secure, headless authentication). Adding standard user accounts (Option A) is an anti-pattern for system integrations because it relies on interactive logins or brittle basic auth.

Role-Based Access Control (RBAC) in Adobe Cloud Manager is strictly managed via the Adobe Admin Console. The "Developer" role grants read-only access to environments and pipelines, allowing the user to view execution steps, download logs, and access the Developer Console to push Git commits. However, the Developer role cannot initiate, override, or cancel pipeline executions. To trigger a build (making the Build button visible and active), the user must be assigned the "Deployment Manager" role within the Admin Console.

In AEM as a Cloud Service, Sling Content Distribution is responsible for moving content and packages between tiers. If the sling-distribution-importer system user lacks the necessary Access Control Lists (ACLs) to write to specific paths, it will throw an AccessDeniedException during package installation. Because AEMaaCS environments are ephemeral and access to traditional local consoles (like User Admin or CRXDE) is restricted or wiped out during updates, all system user creation and ACL configurations must be declared as code. The DevOps engineer must configure these permissions using OSGi factory configurations containing OSGi Repoinit scripts.