The Adobe Experience Manager Sites Developer Expert (AD0-E137)

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

Run mode-specific configurations in AEM follow a strict naming convention under the osgiconfig folder. The folder structure defines both the run mode (author or publish) and the environment (e.g., dev, stage, uat, prod). For UAT author environments, the correct structure is config.author.uat. Option C follows this convention correctly. Option A and B use incorrect naming patterns, which would prevent AEM from loading the configuration under the desired run mode. Adobe emphasizes the importance of placing OSGi configs in the correct folder paths within the ui.apps project or ui.config project depending on deployment structure.

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.

Explanation (Adobe Docs Reference):

AEM provides Generic Analytics Snippet functionality to allow marketing/analytics teams to manage third-party tracking scripts directly through the AEM UI, without needing a development release cycle. This enables non-developers to add or update scripts (e.g., analytics tags, marketing pixels) safely.

Option A is incorrect: Hardcoding the script in HTL means dev releases are required for every change.

Option B is incorrect: Page policies control design configurations and allowed components, not scripts.

Option C is correct: Generic Analytics Snippet is designed for this scenario.

Adobe Documentation:

“AEM provides a generic analytics snippet component that allows administrators to add and manage third-party tracking codes outside of the development cycle.”

— AEM Sites – Generic Analytics Snippet

Explanation (Adobe Docs Reference):

Editable templates + Policies : Editable templates allow developers to restrict which components are available by defining policies that control allowed components for layout containers.

Content Fragment Model validation : Developers can define validation rules (e.g., regex, required fields, min/max length) directly in the content fragment model.

Options A, C, and D are incorrect:

Field validation is not configured in editable templates (A is wrong).

Workflows are not used for enforcing component usage (C is wrong).

Dynamic templates are deprecated in favor of editable templates (D is wrong).

Adobe Documentation:

“Editable templates support defining policies to determine which components can be used in the layout container.”

— AEM Templates – Defining Policies

“Content Fragment Models can include validation rules to ensure data integrity, including regex patterns, length restrictions, and required fields.”

— AEM Content Fragment Models – Validation Rules

When defining component style options in AEM, authors can select from pre-defined CSS classes by configuring them in the component’s cq:editConfig node under /cq:style. The correct properties are:

cq:styleClasses : Defines the list of CSS classes that authors can apply.

cq:styleLabel : Defines the label displayed in the authoring dialog for the style selection.

Options B, C, D are incorrect because they use invalid property names (cssClasses, styleLabel, cssStyles, cssLabel) which are not recognized by AEM.

From Adobe Documentation:

“Component styles can be defined using the cq:editConfig node. Authors can choose between style variations configured under cq:styleClasses with a descriptive cq:styleLabel.”

— AEM 6.5 – Defining Component Styles with cq:editConfig

— AEM Core Components – Style System

The correct approach to display external API results using server-side rendering in AEM is to separate responsibilities across three layers. First, create an OSGi component that encapsulates the logic for making external API calls using an HTTP client. This ensures reusability and central management of integration code. Second, create a Sling Model that references this OSGi service. Sling Models provide a resource-adaptable layer that connects AEM components to backend services, making it easier to expose data to HTL scripts. Finally, bind this Sling Model to an AEM component, which displays the fetched data in server-rendered HTML. This is aligned with Adobe’s guidance that integration logic should be handled within OSGi services, with Sling Models bridging content and services for components. Options B and C incorrectly assign responsibilities to Servlets or components, which violates best practices for modularity.

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. < env > folders in the configuration project.

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.