Free Practice Questions for Adobe AD0-E124 Exam

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.

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.

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.

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.

Role-Based Access Control (RBAC) in Adobe Cloud Manager is strictly managed via the Adobe Admin Console. The "Developer" role grants read-only access to environments and pipelines, allowing the user to view execution steps, download logs, and access the Developer Console to push Git commits. However, the Developer role cannot initiate, override, or cancel pipeline executions. To trigger a build (making the Build button visible and active), the user must be assigned the "Deployment Manager" role within the Admin Console.

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.

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.

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.

The Oak Segment NodeStore (TarMK) includes an "estimation phase" before running Revision Garbage Collection (Compaction). This phase calculates if enough "garbage" (unreferenced data) has accumulated to justify the heavy I/O cost of compaction. If the size delta doesn't meet the threshold, it skips the process to save resources. If a DevOps engineer must force the compaction to run regardless of the delta, they must configure the OSGi configuration for the "Apache Jackrabbit Oak Segment NodeStore Service" and disable the "Estimation Phase" by unchecking/toggling the appropriate property.