Adobe AD0-E137 - Adobe Experience Manager Sites Developer Expert

Custom components built on Core Components should use the sling:resourceSuperType property to inherit functionality. When upgrading from v1 to v2 Core Components, the developer updates the sling:resourceSuperType property of the custom component to reference the new v2 implementation. This allows the custom component to inherit all new features and bug fixes introduced in v2 while retaining its customizations. Option A is incorrect because sling:resourceType defines the resource type of the component itself, not inheritance. Option B is incorrect because there is no automatic upgrade mechanism in AEM; developers must explicitly update the inheritance path. Adobe documentation clearly states that upgrading Core Components is achieved by re-pointing sling:resourceSuperType to the new version.

In Dispatcher configuration, request filtering is handled through the filters.any file. To deny access to specific content types or formats (like .json and .xml) for certain paths, the configuration must explicitly match both the extension and the path using correct syntax. The valid approach uses:

/0001 { /type "deny" /extension "(xml|json)" /path "(/path2|/path3)/*" }

Options A and B contain syntax errors. Option A incorrectly uses JSON/* instead of paths, and Option B mixes array-style brackets instead of regex or path expressions. Option C follows the correct pattern of specifying deny rules with /extension and /path. Adobe recommends always explicitly denying unwanted selectors or extensions to prevent exposure of sensitive content through JSON or XML requests.

When workflows require complex conditional logic or integration with external systems, Adobe recommends writing custom workflow process steps in Java. By implementing the WorkflowProcess interface, developers can evaluate metadata dynamically and invoke APIs or services as needed. Option A is too limited because out-of-the-box workflow steps support simple operations but cannot manage advanced branching or integrations. Option C is not suitable because content fragments are intended for structured content authoring, not for managing asset workflows. Adobe’s documentation states that workflows should remain modular, with custom steps encapsulating business-specific logic, while the Workflow Model defines the process flow. This ensures extensibility, testability, and clean separation between workflow orchestration and implementation logic.

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):

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