Practice Free AD0-E124 Adobe Experience Manager DevOps Engineer Expert Exam Questions Answers With Explanation

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.

When troubleshooting routing or Virtual Host configurations on a Dispatcher (which is typically an Apache or Nginx web proxy), the proxy relies on the Host HTTP header to determine which farm or server block should process the request. Using cURL, you can bypass DNS layers and test the origin server directly by specifying the target IP or default hostname (e.g., origin-mysite.adobeqms.com) while explicitly passing the desired Virtual Host name via the Host header (-H "Host: mysite.com"). This forces the Dispatcher to process the request as if it were traffic coming for mysite.com.

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.

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.

The Dispatcher relies on the /virtualhost section of the farm configuration to route incoming HTTP requests based on the Host header. If a page renders correctly on www.domain.com but returns a blank or default response on domain.com, it strongly indicates that the bare domain (non-www) has not been added to the /virtualhost array for that specific site's farm configuration. The Dispatcher does not know how to handle the request for the missing host and drops or misroutes it.

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.

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.

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.

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, the number of provisioned environments (especially Development, Stage, and Production environments) is strictly governed by the customer's commercial license and contract. If the "Add Environment" button is disabled or missing in Cloud Manager, it means the organization has reached its licensed limit. Technical teams cannot bypass this via the UI or OSGi. The DevOps engineer must advise the business to contact their Adobe Account Executive or Customer Success Engineer to procure and provision additional cloud environments.