AD0-E124 Questions and Answers

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.

When migrating an existing AEM code base to AEM as a Cloud Service (AEMaaCS), the structure and rules are strictly enforced by the Cloud Manager pipeline. Before pushing code, a DevOps engineer must validate the code locally against the AEM as a Cloud Service SDK to ensure OSGi bundles resolve and mutable/immutable content separations are respected (Option B). Additionally, the Dispatcher configuration has migrated from an Apache-based structure to a strict AEMaaCS format. Running the local Dispatcher Validator CLI tool (Option C) is mandatory to ensure there are no syntax or structural errors in the dispatcher configurations, which would otherwise immediately fail the Cloud Manager build pipeline.

If a customer only wants published content on their new AEM as a Cloud Service Production instance, the cleanest source of truth is the legacy Publish instance, as it natively contains only activated content. To execute this, the Content Transfer Tool (CTT) should be installed on the legacy Publish instance. From there, the data must be ingested into both the new Target Publish instance (so the website works) and the new Target Author instance (so authors can continue editing the live content). Therefore, the DevOps engineer must extract from the source publish and ingest to both target environments.

To automate user and group management between an enterprise directory (like Azure AD) and AEM as a Cloud Service, direct LDAP connections to AEM are no longer supported. Instead, identity is managed centrally in the Adobe Admin Console. The DevOps engineer must deploy the Adobe User Sync Tool (UST) on a secure corporate server (Option E). The UST automatically syncs AD groups to the Admin Console. Furthermore, to ensure these federated users can actually log into AEM, the engineer must map a catch-all Azure AD group to the baseline "AEM Users" Product Profile within the Admin Console (Option B).

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.

If a Cloud Manager build requires dependencies from a private, password-protected corporate artifact repository, the DevOps engineer must provide Cloud Manager with a custom Maven settings file to handle the authentication. This is done by placing a file at .cloudmanager/maven/settings.xml in the root of the AEM Git repository. Because hardcoding Basic Authentication credentials in Git is a massive security risk, the credentials inside the settings.xml should reference environment variables. The DevOps engineer then uses the Adobe I/O CLI (aio cloudmanager:set-pipeline-variables) to inject the actual username and password as secure pipeline secrets.

In both AEM On-Premise/Managed Services and AEM as a Cloud Service, routine repository maintenance tasks (like Version Purge, Workflow Purge, and Audit Log Purge) are configured natively within the AEM author UI. The DevOps engineer navigates to the Maintenance Dashboard via Tools > Operations > Dashboard > Maintenance to configure the daily and weekly maintenance windows and schedule which tasks run inside them.

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.

AEM as a Cloud Service enforces a strict separation between mutable content (e.g., /content, /conf) and immutable content (e.g., /apps, /libs). Immutable areas are packaged into the read-only base image during the build process and cannot be modified at runtime. When a Repoinit script (which executes when the repository initializes) attempts to create nodes or set ACLs on paths beneath /libs or /apps, the Jackrabbit Oak repository rejects the change with an UnsupportedOperationException: This builder is read only, subsequently crashing the Sling Repository service and failing the deployment.

Adobe Support has strict Service Level Agreement (SLA) definitions for priority levels.

P1 (Critical): The production application is completely down and unavailable to end-users (e.g., Publish tier is crashed).

P2 (Serious): A core, business-critical function is down for all users, causing severe revenue or operational impact.

P3 (Interruption to normal operations): The application is functional, but specific users are experiencing degraded performance or feature loss (like a broken authoring workflow).

Even though the business has a deadline (a product launch within 24 hours), the fact that the live production site is still up and only two authors are currently reporting an inability to activate pages categorizes this strictly as a P3 issue according to standard Adobe support guidelines.