AD0-E124 Dumps with Practice Exam Questions Answers

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.

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.

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.