Free Adobe AD0-E137 Practice Exam with Questions & Answers

Explanation (Adobe Docs Reference):

Replication agents in AEM are responsible for transferring content and digital assets from the author instance to the publish instance (or to other targets like Dispatcher flush agents). This ensures that authored and approved content becomes available on the public site.

Options B and C are incorrect:

User permissions are not replicated by agents; they are managed by user synchronization.

Core Components are provided via Maven dependencies and not transferred via replication agents.

Adobe Documentation:

“Replication agents are central to AEM; they are used to publish (activate) content from an author to a publish environment, or to clear content from the dispatcher cache.”

— AEM Replication Agents

The Retry Delay setting in a replication agent specifies the interval (in milliseconds) to wait before retrying a failed replication request. This ensures that temporary network or system issues don’t permanently block replication, as the agent will automatically attempt to resend content at the configured delay interval.

From Adobe Documentation:

“Retry Delay: The time (in milliseconds) to wait before attempting to retry a failed replication. This helps ensure that replication requests are retried at regular intervals if initial delivery fails.”

— Adobe AEM 6.5 & AEMaaCS – Replication Agent Configuration

Explanation (Adobe Docs Reference):

The SAML Authentication Handler in AEM requires the following key properties:

path: Defines the content path where this handler applies (here /content/siteB).

idpUrl: The Identity Provider’s SAML endpoint (here https://www.idpB.com).

Other properties like serviceProviderEntityId and assertionConsumerServiceURL are also required in a real-world setup but the correct basic mapping in this scenario is option B.

Adobe Documentation:

“The SAML authentication handler is configured by setting path to the protected resource root and idpUrl to the Identity Provider endpoint.”

— Adobe AEM 6.5 – SAML Authentication Handler

Explanation (Adobe Docs Reference):

Unit tests for Sling Models using wcm.io AEM Mocks (AemContext) require test content to be loaded into the mock JCR repository. This is usually done with:

ctx.load().json("/path/to/test-content.json", "/content");

Without loading node data, ctx.currentResource("/content/bar") won’t resolve anything, causing adaptTo(Flarp.class) to return null.

A is wrong: AemContext is correct for Sling Models in AEM.

B is wrong: @Rule applies to JUnit4, but the test uses JUnit5 with @ExtendWith.

C is correct: Loading JSON test content is required.

Adobe/WCM.IO Documentation:

“Use context.load().json() to load test content into the JCR repository for unit tests. Then set context.currentResource(path) to adapt resources to Sling Models.”

— wcm.io AEM Mocks Documentation

Workflow launchers in AEM are designed to monitor changes in specific repository paths such as /content, /content/dam, and /conf. However, changes under certain system-level paths, including /var, do not trigger workflows. This restriction is intentional, as /var is used for system-generated and internal data such as workflow instances, audit logs, and temporary nodes. Triggering workflows on changes under /var could result in recursive or unintended behavior. Option A is unrelated because Workflow Process Legacy Mode refers to backwards compatibility. Option B is incorrect, as AEM does allow system nodes under /var, but they are not workflow-launcher enabled. Adobe documentation makes clear that workflow launchers must be configured under supported content paths for them to execute correctly.

In AEM, multi-site management allows centralized content updates to be pushed across different localized or departmental sites. The “Partial” option on the rollout configuration ensures that only specific components or regions designated for shared updates are synchronized, while leaving local content intact. This fits the described requirement where a portion of each school’s homepage must receive university updates without affecting school-specific content. Option A, Experience Fragments, could be used but are better suited for shared fragments of design/content, not controlled rollout scenarios. Option C requires manual inheritance restoration per page, which is inefficient. Option D, implementing custom rollout logic, is not needed when the built-in “Partial Rollout” option fulfills the requirement. Adobe emphasizes using partial rollout in multi-site configurations to balance central control with localized autonomy.

In AEM as a Cloud Service, dedicated preview service endpoints are configured under publish run modes. The correct configuration folder for a UAT preview service is config.publish.uat within the ui.config project. Option A incorrectly places the configuration under author run mode, which is unrelated to preview endpoints. Option C misorders the naming convention, using config.uat.author instead of the proper config.publish.uat. Adobe’s guidance specifies that preview service configuration is a publish-tier responsibility, requiring config.publish. folders in the configuration project.

The Dispatcher should be configured to cache static pages like .html, but when query parameters are present (used for personalization, targeting, or dynamic rendering), the dispatcher must invalidate or bypass cache to prevent stale or incorrect content delivery.

Option A is correct → balances performance (cache static .html) and personalization (invalidate with query strings).

Option B is incorrect → POST requests should never be cached, as they modify content.

Option C is incorrect → disabling cache for all .html removes performance benefits.

Adobe Documentation:

“The dispatcher can be configured to cache .html responses while invalidating the cache when query string parameters are present. This ensures efficient caching while supporting personalization and dynamic content.”

— AEM Dispatcher Caching Guidelines

When unit testing a service that depends on JCR queries, the best practice is to use mocking frameworks (such as Mockito) to mock the Query and QueryResult objects. The purpose of a unit test is to isolate the service under test and not rely on a real JCR repository or SlingContext persistence layer, which moves testing into integration testing territory. By mocking the Query object and using the when(...).thenReturn(...) pattern, developers can control query results and validate how the service behaves under different scenarios. This ensures that the test runs quickly, without dependency on repository setup or external data. Option B is incorrect because currentResource() is used in Sling Model tests rather than for query-driven services. Option C with SlingContext and JCR_OAK would be used in integration or functional tests, not in lightweight unit tests. Adobe documentation highlights that JCR queries should be mocked in unit tests to ensure isolation and speed.

Explanation (Adobe Docs Reference):

In AEM SPA Editor, the MapTo function is used in the React (or Angular) component to map a frontend component to its corresponding AEM component resource type (Sling Model). This ensures data from the Sling Model is properly bound to the SPA component.

Correct: React component implements MapTo with the AEM component resource type.

Incorrect: The AEM Component or Sling Model itself does not implement MapTo.

Adobe Documentation:

“SPA components must call MapTo in the JavaScript app to map a frontend component to an AEM component resource type. This enables the Sling Model data to be injected into the SPA component.”

— AEM SPA Editor – MapTo Function