AD0-E137 Adobe Experience Manager Sites Developer Expert Free Practice Exam Questions (2025 Updated)

AEM package files follow a standard naming convention in CRX Package Manager:

--.zip

Thus, with the package name aem-package, group aem_group, and version 1.0, the correct package name is aem-package-aem_group-1.0.zip. Option B is invalid because group names and content paths are not combined in filenames. Option C omits the group name, making it incomplete. Adobe documentation emphasizes this naming convention for easier package identification and dependency management across environments.

Explanation (Adobe Docs Reference):

Assets in AEM are stored as dam:Asset nodes, not nt:base or cq:image.

Metadata like cq:lastModified is stored under jcr:content/metadata.

Therefore, the correct query must use [dam:Asset] with the proper metadata path.

Options A and C are invalid because they use wrong node types or incorrect property paths.

Adobe Documentation:

“Assets are represented as dam:Asset nodes. Metadata such as lastModified is stored under jcr:content/metadata and can be queried using JCR-SQL2.”

— AEM Assets – Querying Assets

The recommended way to generate a new AEM project is by using the official Adobe AEM Maven Archetype. Developers must specify the correct groupId (com.adobe.aem) and artifactId (aem-project-archetype). The archetypeVersion should match the latest stable archetype version (e.g., 50 for AEM 6.5). The groupId of the project should be set to the organization’s package, in this case com.mysite. The appId defines the project name and should match the intended application (mysite). The version is defined as 2.0 to represent the project version, while aemVersion=6.5 ensures compatibility with AEM 6.5. Option A is invalid because the archetype groupId is incorrect and the values are mismatched. Option C contains placeholders and an invalid groupId. Adobe’s official documentation for generating projects specifies option B as the valid approach.

The correct approach is to use the Query Debugger in AEM, which provides detailed insights into query performance, including query cost, traversal warnings, and which indexes are being used. The Explain Query tool is a lower-level utility but does not provide the same AEM-specific integration and insights as the Query Debugger. Updating Lucene indexes (Option C) might eventually be needed, but the first step is always to analyze query performance and confirm whether the issue is due to indexing. Adobe documentation emphasizes using the Query Debugger under /libs/granite/operations/content/diagnosistools/queryPerformance to identify query inefficiencies and missing index configurations before applying fixes.

Text pre-extraction is recommended during reindexing of existing Lucene indexes that have binary extraction enabled. Binary extraction is the process where text content is extracted from binary files (such as PDFs or Word documents) for indexing. During reindexing, extracting text repeatedly from large binaries can cause performance degradation. Pre-extraction allows text to be extracted once and reused during indexing, significantly reducing reindexing time and system load. Option B is incorrect because small repositories don’t require pre-extraction optimization. Option C is also incorrect, as images generally don’t involve binary text extraction unless paired with OCR. Adobe highlights pre-extraction as a performance optimization technique for reindexing scenarios involving binary text content.

In AEM’s Template Editor, there are multiple modes that allow template authors to configure different aspects of templates. The Structure mode defines static and editable areas in templates. The Page Policy allows defining rules such as which components are available for use. However, the Layout mode is specifically designed for defining grid settings for different devices. With Layout mode, template authors can configure responsive layouts and grid behavior across breakpoints such as desktop, tablet, and mobile. This ensures consistent responsive design and adaptability across devices. Adobe documentation specifies that “Layout mode allows authors to configure responsive grid layouts for different breakpoints, ensuring that pages render appropriately on devices of varying screen sizes.” This mode is essential for enabling adaptive and responsive designs in AEM projects. Options B and C do not allow for device-specific grid settings and thus are not correct.

The issue in this case is that the title field is declared but not annotated with @Inject. In Sling Models, all fields that should be populated from the resource or request must be annotated appropriately (@Inject, @ValueMapValue, or @Self). Without this annotation, the Sling Model cannot populate the field when adapting from the resource, resulting in the model not functioning as expected. Option A is incorrect because Resource.class is a valid adaptable for Sling Models. Option C does not apply because the problem is not with hard-coded paths but with injection. Option D is also incorrect because while @PostConstruct must be properly annotated, the root issue here is missing injection on the field. Adobe’s Sling Models documentation emphasizes correct use of injection annotations as a core requirement.

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

When querying with QueryBuilder API:

type=cq:Page ensures only AEM pages are selected.

property=jcr:content/cq:template filters by the template path.

property.value=/conf/geometrixx/templates/homepage ensures only pages created with the homepage template are returned.

p.hits=selective restricts returned properties.

p.properties=jcr:title ensures only the jcr:title is returned.

Options B, C, and D are invalid due to wrong property paths (jcr:title/cq:template, cq:template, or jcr:content/template) or typos (jrc:title).

Adobe Documentation:

“The property parameter can be used to restrict results based on template usage. Use jcr:content/cq:template to filter by template and p.properties with p.hits=selective to return specific fields.”

— AEM QueryBuilder API Guide

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.

Explanation (Adobe Docs Reference):

The correct OSGi Declarative Services (DS) implementation in AEM:

Must use implements (not extends).

Must register the service interface (SimpleService.class).

Should return an implementation for getMessage().

Option D is the correct implementation.

Options A, B, C are wrong because:

A incorrectly uses extends.

B and C register the wrong service type (MySimpleService).

Adobe Documentation:

“An OSGi service implementation must implement its interface and be annotated with @Component(service=Interface.class) to register the service.”

— OSGi Services in AEM

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 correct approach to implementing an OSGi service in AEM is to use the Declarative Services annotation @Component(service = Interface.class). This ensures that the OSGi container properly registers the service against its interface, making it available for injection into other services, Sling Models, or servlets. In this case, the service is required to fetch store locations from an external API. Using an HTTP client within the OSGi service is the appropriate method to manage these requests. Option A is invalid because @OSGIService is not a valid annotation for service declaration. Option C is incorrect because @Service is not an OSGi Declarative Services annotation in this context. Adobe emphasizes encapsulating external API logic in OSGi services so that components and Sling Models can consume the data in a decoupled manner. This promotes separation of concerns and reusability.

Modern AEM projects often include front-end build processes for handling CSS, JavaScript, and component-specific assets. Webpack is the recommended tool for managing dependencies, bundling code, minification, transpilation (e.g., ES6+ to ES5), and optimizing assets. It integrates with the AEM Maven build process and supports workflows like Single Page Applications (SPA) and client libraries. Option B, Apache Sling, is the underlying web framework for AEM, not a front-end tool. Option C, Maven, manages project builds and back-end dependencies but not front-end asset pipelines. Option D, the AEM Sites Console, is for authoring and managing pages, not development builds. Adobe documentation for SPA Editor and modern AEM projects consistently demonstrates Webpack as the standard tool for front-end optimization.