AD0-E124 Adobe Experience Manager DevOps Engineer Expert Questions and Answers

In Adobe Experience Manager, replication agents are environment and runmode-specific. Author instances use agents located under /etc/replication/agents.author to send content to publish instances. Publish instances, on the other hand, use agents under /etc/replication/agents.publish to send flush requests to the Dispatcher. If a flush agent is created on the Publish instance but placed under the .author path, the publish instance will ignore it when replication events occur, meaning the Dispatcher cache will never be invalidated.

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.

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.

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 AEM search results are outdated and the LastIndexedTime metric is stalled, it indicates that the Oak Asynchronous Indexer has failed or is stuck on a corrupted node. To diagnose Oak indexing issues, you must create a specific logger in AEM OSGi configurations for the Java package responsible for Oak indexing: org.apache.jackrabbit.oak.plugins.index. Setting this logger to DEBUG or TRACE will output detailed information into the logs, revealing the exact path or query causing the indexer to fail.

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.

For headless, service-to-service integrations via Adobe I/O (Adobe Developer Console), JWT (JSON Web Tokens) was historically the standard. However, Adobe officially deprecated the Service Account (JWT) credentials in favor of the new OAuth 2.0 Server-to-Server credential implementation. Because Adobe exams are updated to reflect current platform deprecations and best practices, OAuth 2.0 is the correct, modern standard for programmatic authentication without a user interface.

To secure multiple domains or subdomains efficiently using a single certificate upload in Adobe Cloud Manager, DevOps engineers should use either a SAN (Subject Alternative Name) certificate or a Wildcard certificate. A SAN certificate allows multiple distinct hostnames (e.g., example.com, shop.example.com, example.org) to be protected by a single certificate. A Wildcard certificate (e.g., *.example.com) protects a single domain and all its subdomains. Both are officially supported in the Cloud Manager UI for SSL deployment.

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 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 Cloud Manager for AEM as a Cloud Service, environments are automatically updated to newer AEM versions by Adobe. If an environment is updated but the pipeline itself is still holding a reference to a previous AEM release, version mismatch errors will occur during the deployment step. The Cloud Manager UI provides an "Update" option on the environment card to synchronize the environment and the pipeline to the latest expected release. Once synchronized, re-running the pipeline will resolve the version conflict.

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.