AD0-E124 Adobe Experience Manager DevOps Engineer Expert Free Practice Exam Questions (2026 Updated)

Jackrabbit FileVault packages (AEM Content Packages) use a filter.xml file to define the workspace paths being imported and the behavior of the import. The mode attribute on a filter determines how existing nodes are handled.

replace (default): Overwrites existing nodes completely.

merge: Only adds nodes that do not already exist. It explicitly preserves existing content and ignores the updated properties in the incoming package.

If existing pages are not updating upon package deployment, it is because the filter mode is incorrectly set to merge.

This question draws a technical comparison between how scaling works on the legacy Adobe Managed Services (AMS) platform versus the target AEM as a Cloud Service (AEMaaCS) platform. On the current legacy AMS platform, horizontal scaling (adding more instances) requires submitting a ticket to a Customer Success Engineer (CSE) to provision and attach new VMs manually (Option E). By contrast, on AEM as a Cloud Service, publish instances scale automatically (Auto scaling) horizontally via Cloud Manager based on live traffic thresholds, or can be scaled via Cloud Manager logic (Option A represents the target platform's cloud-native scaling methodology, though standard AEMaaCS implies Auto scaling; Cloud Manager orchestrates this).

When an Admin Console (IMS) group is renamed, it synchronizes into AEM as an entirely new group, leaving the old group intact. The new "Marketing AEM Authors" group has no permissions mapped to it inside AEM, which is why the new user cannot access anything. Trying to rename the AEM group or manipulate its backend ID (rep:externalid) can break IMS synchronization. The standard, safest best practice is to take the newly synchronized IMS group ("Marketing AEM Authors") and add it as a member of the existing AEM permission structure (the original "AEM Authors" group, or the underlying AEM content-authors group). This grants the new IMS group all inherited permissions seamlessly.

When adding a custom domain to AEM as a Cloud Service, three things are required from the DNS/IT side:

An SSL Certificate (DV, OV, or EV are all valid, but DV is standard for this context).

A TXT record added to aemverification. < your-domain > to prove domain ownership to Adobe.

A CNAME record that routes the traffic from your custom domain (marketplace.acmecorp.biz) directly to the generic Adobe Fastly CDN edge endpoint (cdn.adobeaemcloud.com, or a specific edge node depending on exact implementation, but cdn.adobeaemcloud.com is the standard architectural target).

Option A correctly identifies the TXT record format and the CNAME target.

To enable Java remote debugging (Java Debug Wire Protocol or JDWP) for any JVM application, including AEM, the correct parameter format in modern Java versions is -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8000. This allows an IDE (like IntelliJ or Eclipse) to attach to the JVM process on port 8000. Option A is used for exposing JMX beans (monitoring), not debugging.

To perform an in-place upgrade of an AEM instance (such as upgrading from AEM 6.4 to 6.5) while preserving version history, workflow instances, and audit logs, the correct approach is an "in-place upgrade." This involves placing the new AEM quickstart JAR file in the existing installation directory, unpacking it using the -unpack command, and then starting the instance. Copying site content using Content Packages (Option C) will move the latest state of the nodes but will lose version history, ACLs (if not included), and running workflow instances.

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 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.

In Adobe Cloud Manager, system-level monitoring metrics and their associated alerting thresholds (like CPU limits, Memory usage, and Segment Store disk space) are managed by Adobe's internal operations team. Standard DevOps engineers and customer administrators do not have the ability to alter these foundational infrastructure thresholds via the Cloud Manager UI or APIs. To request a configuration change to alerting thresholds, the engineer must file a request via their Adobe Customer Success Engineer (CSE) or Adobe Support.

To verify and analyze slow-loading pages in AEM, the correct tool is "Request Performance" located under the Diagnosis Tools (accessible via the AEM Web Console / Operations Dashboard). This tool tracks incoming HTTP requests to the AEM instance, breaks down the execution time of the request across various internal components and scripts, and allows the DevOps engineer to pinpoint exactly which part of the page rendering is causing the delay. Query Performance (Option A) is specifically for slow JCR searches, not necessarily overall page load times.

Similar to Code Coverage, a Security Rating of 'B' in Cloud Manager usually results in a "Partial Pass" state (3-tier rating system where critical vulnerabilities cause outright failures, but lower-tier warnings cause partial passes). Since all critical and mandatory tests passed, the pipeline pauses and waits for user intervention. The DevOps engineer (with the Deployment Manager role) can proceed with the build by navigating to the execution details, selecting the option to "Override failed results," and submitting the decision to resume the pipeline.

In Adobe Experience Manager, environment and runmode-specific OSGi configurations are managed using folder naming conventions. To target a specific runmode, the folder name must be appended with . followed by the runmode name. Therefore, to supply separate configurations for the Author and Publish runmodes, the configurations must reside in /config.author/ and /config.publish/ respectively. Option D uses a nested folder approach (/config/author/) which is not the standard OSGi runmode resolution syntax in AEM.

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.