Free AD0-E137 Practice Test Questions and Answers (2026)

This JCR-SQL2 query correctly retrieves the requested data. It specifically targets nodes of type dam:Asset, which is the standard primary node type for all digital assets, including images, stored in the AEM Digital Asset Manager (DAM). The isdescendantnode() function correctly constrains the search to the specified /content/dam/folder1 path. The WHERE clause accurately filters for assets where the cq:lastModified property (located on the jcr:content sub-node) is greater than or equal to the specified date and time, using the CAST function for proper date-type comparison. This query is both syntactically correct and efficient.

A. Using nt:base is functionally possible but highly inefficient. It forces the query to evaluate every single node under the path, regardless of type, leading to poor performance, which is against AEM query best practices.
C. This option is incorrect for two reasons. First, cq:image is not a valid primary node type for assets in the DAM. Second, the property path syntax jcr:content.[cq:lastModified] is invalid in a JCR-SQL2 WHERE clause.

1. Adobe Experience Manager as a Cloud Service Documentation, "Query and Indexing Best Practices": This document emphasizes the importance of query performance. Under the "Restrict Queries with Node Types" section, it states, "Restrict queries with node types whenever possible. This allows the query engine to narrow the search to a smaller subset of nodes." This supports why dam:Asset (Option B) is superior to nt:base (Option A).

2. Adobe Experience Manager as a Cloud Service Documentation, "JCR-SQL2 Cheat Sheet": This guide provides syntax examples for JCR-SQL2. It shows the correct usage of dam:Asset as the node type for querying assets, the isdescendantnode() function for path restrictions, and the CAST function for date/time comparisons (e.g., ...[jcr:created] > CAST('2013-01-01T00:00:00.000Z' AS DATE)). It also confirms the relative property path syntax [jcr:content/cq:lastModified].

3. JCR 2.0 Specification (JSR 283), Section 6.7.19, "PropertyInPath": The official JCR specification defines the syntax for referencing a property on a descendant node within a WHERE clause. The correct syntax is [path/to/property], validating the structure used in Option B and invalidating the dot notation in Option C.

The Adobe Experience Manager (AEM) Dispatcher configuration is managed through a set of text files using a proprietary format with the .any extension. The main configuration file, dispatcher.any, defines various sections, including /cache, which controls caching behavior. For modularity and maintainability, it is a standard practice to separate sections into different files and include them using the $include directive. The file path /etc/httpd/conf.dispatcher.d/cache/cache.any correctly reflects this convention, using the standard .any file extension and a logical location for cache-specific rules.

A. /etc/httpd/conf.dispatcher.d/cache/cache.xml This is incorrect because AEM Dispatcher configuration files do not use the XML format. The required format uses the .any extension.
C. /etc/httpd/conf.dispatcher.d/cache/cache.config This is incorrect as .config is not the standard file extension for AEM Dispatcher configurations. The correct and required extension is .any.

1. Adobe Experience Manager 6.5 Documentation, "Configuring the Dispatcher": This official documentation describes the structure of the dispatcher.any file and its properties. It explicitly states, "The Dispatcher configuration is stored in the dispatcher.any text file." It also details the /cache section, which is the subject of the question. The use of .any files is fundamental to all Dispatcher configuration.

Reference: Adobe Experience Manager 6.5 Documentation, Deploying > Dispatcher > Configuring the Dispatcher > The dispatcher.any File.

2. Adobe Experience Manager as a Cloud Service Documentation, "Dispatcher in the Cloud": This documentation outlines the standard file structure for Dispatcher configurations in AEM as a Cloud Service, which is generated by the AEM Project Archetype. It shows that configurations are split into multiple .any files within the conf.dispatcher.d directory, including a dedicated cache subdirectory for caching rules (e.g., cache/rules.any). This confirms the practice of using separate .any files for cache configuration.

Reference: Adobe Experience Manager as a Cloud Service Documentation, Development > Developing for Dispatcher > Dispatcher in the Cloud > File Structure.

In Adobe Experience Manager (AEM), content is stored in the Java Content Repository (JCR). When querying large data sets, the performance is critically dependent on proper indexing. Failing to create custom Oak indexes for common query properties forces the JCR to traverse large sections of the content tree to find matching nodes. This repository traversal is extremely resource-intensive, consuming significant CPU and I/O, which leads to slow query execution and severe application-wide performance degradation. This is one of the most frequently encountered and impactful performance issues in AEM development.

A. Implementing recursive function calls without considering potential stack overflow errors This is a general programming error that typically causes a StackOverflowError and application crash, not a gradual performance degradation, which is the focus of the question.
B. Using static variables extensively to store application state across multiple requests This is a poor practice in a multi-threaded environment like AEM, leading to data inconsistency and concurrency bugs, but it is not a primary or common cause of performance degradation.
D. Overusing synchronized blocks to manage concurrent access to shared resources While excessive synchronization can cause thread contention and performance bottlenecks, un-indexed JCR queries are a far more common and severe source of performance degradation specific to the AEM platform.

1. Adobe Experience Manager as a Cloud Service Documentation, "Queries and Indexing": "Queries are a way to access content in AEM. Every developer will need to write queries for their component. If not designed properly, a single query can have a high impact on the AEM system performance. An un-indexed query will read many more content nodes from the repository into memory. This can put a strain on the system and impact other users."

Source: Adobe Experience Manager Documentation, Queries and Indexing, Section: "When to use queries".

2. Adobe Experience Manager 6.5 Documentation, "Best Practices for Queries and Indexing": "One of the most common problems in AEM deployments is the performance of queries. They can be easy to write in your components, but without considering their impact and how they are optimized, a whole AEM deployment can be brought to a halt."

Source: Adobe Experience Manager 6.5 Documentation, Developing User Guide, Section: "Best Practices for Queries and Indexing".

3. Adobe Experience Manager as a Cloud Service Documentation, "Query and Indexing Best Practices": "AEM provides a Query Performance tool that helps to debug and optimize queries. A key feature is the Explain Query functionality, which provides details on how AEM is executing the query, including which index is used, and the estimated number of nodes that will be traversed. This is critical for determining if an index is being properly leveraged."

Source: Adobe Experience Manager Documentation, Development Best Practices, Section: "Query and Indexing Best Practices".

The recommended query language for the Oak query engine is JCR-SQL2. In the context of the available options, "SQL" represents JCR-SQL2. This language is preferred over others like XPath because it is more expressive, powerful, and generally performs better. The Oak query engine often converts XPath queries into JCR-SQL2 before execution, which can introduce a slight performance overhead. Writing queries directly in JCR-SQL2 bypasses this conversion step and provides more direct control over the query execution plan, making it the recommended choice for developers working with AEM and the Oak repository.

A. JCR-SQL: This is the older, deprecated query language from the JCR 1.0 specification. It has been superseded by the more powerful and standardized JCR-SQL2 and is not recommended.
C. XPath: While XPath is supported and can be convenient for simple, path-based queries, it is not the recommended language. XPath queries are typically converted to JCR-SQL2 by the query engine, which can add unnecessary overhead.

1. Adobe Experience Manager as a Cloud Service Documentation, "Query and Indexing Best Practices": In the section "Prefer JCR-SQL2 over XPath," the documentation explicitly states, "JCR-SQL2 is the recommended query language for AEM." It further explains that XPath is converted to SQL2 by the query engine, and using SQL2 directly avoids this overhead.

Source: Adobe Experience League, AEM as a Cloud Service Documentation, Develop > Content > Query and Indexing Best Practices.

2. Adobe Experience Manager 6.5 Documentation, "Best Practices for Queries and Indexing": This document reinforces the recommendation. In the section "JCR-SQL2 versus XPath versus JCR-JQOM," it states, "The general recommendation is to use JCR-SQL2 for queries as it is the most robust and fully featured query language from a JCR perspective."

Source: Adobe Experience League, AEM 6.5 Documentation, Developing > Platform > Queries and Indexing > Best Practices for Queries and Indexing.

3. Apache Jackrabbit Oak Documentation, "Oak Query Engine": The official Oak documentation details the query processing flow. It describes how XPath queries are parsed and then converted into an internal SQL-2 representation for execution, confirming the underlying mechanism that makes direct JCR-SQL2 usage more efficient.

Source: Apache Jackrabbit Oak Documentation, Section: Query > Query Languages.

The Layout mode in the AEM Template Editor is specifically designed for managing the responsive behavior of a template. It allows a template author to define the responsive grid, set component widths, and control component visibility across various device breakpoints (e.g., desktop, tablet, and mobile). This mode is essential for ensuring that the page content adapts correctly to different screen sizes, which directly addresses the developer's need to define grid settings for different devices.

B. Structure: This mode is used to define the permanent components of the template and to configure the allowed components within content containers (parsys), not for managing the responsive grid layout.
C. Page Policy: This is a configuration, not a mode. It is used to define properties for the page template as a whole, such as required client-side libraries (CSS/JS), but not the responsive grid itself.

1. Adobe Experience Manager as a Cloud Service Documentation, "Creating Page Templates":

Section: Template Editor Modes -> Layout

Quote: "Define the template layout for a range of devices... The layouting for a template is done using the responsive grid. This allows you to interactively resize the components and define their layout across different devices and orientations." This directly confirms that Layout mode is used for defining grid settings for different devices.

2. Adobe Experience Manager 6.5 Documentation, "Creating Page Templates":

Section: Modes -> Layout

Quote: "The Layout mode is used to position the content within a responsive grid... The layouting for a template is done using the responsive grid. The responsive grid allows you to define different layouts for different window sizes." This reinforces the purpose of the Layout mode for responsive grid configuration.

To configure the SAML Authentication Handler for a specific site path, the path property must be set to that content path (e.g., /content/siteB). This ensures the handler is only invoked for requests under that path. The idpUrl property must be configured with the URL of the Identity Provider (IDP) to which AEM will send authentication requests. Option B correctly uses these two essential properties to meet the customer's requirement of scoping a specific IDP to a particular site within AEM.

A. The assertionConsumerServiceURL is the endpoint on AEM (the Service Provider) that receives the SAML response from the IDP; it should not be the IDP's URL.
C. The serviceProviderEntityId is the unique identifier for the AEM instance itself, not the URL of the Identity Provider. The userIntermediatePath specifies where user nodes are created, it does not scope the handler.

1. Adobe Experience Manager 6.5 Documentation, Security Guide, SAML 2.0 Authentication Handler: This official guide details the configuration properties for the SAML handler.

Section: "Configuring the SAML 2.0 Authentication Handler"

Details: The documentation explicitly states:

Path (path): "Repository path for which this authentication handler should be used by Sling. If this is empty, the authentication handler is disabled." This confirms its use for scoping the handler to /content/siteB.

IDP URL (idpUrl): "URL of the IDP where the SAML Authentication Request is sent." This confirms its value should be https://www.idpB.com.

Assertion Consumer Service URL (assertionConsumerServiceURL): "URL on the SP which will receive the SAML response." This confirms it is an AEM-side URL, invalidating option A.

Service Provider Entity ID (serviceProviderEntityId): "The ID which uniquely identifies this service provider with the IDP." This confirms it is the AEM instance's ID, invalidating option C.

To meet the client's requirements, a developer must address two separate areas of AEM. First, to control which components are available to authors on a page, the developer defines a Policy for the layout container within the editable template. This policy specifies the exact component group or individual components that can be used. Second, to enforce data integrity for Content Fragments, validation rules are configured directly within the Content Fragment Model. For each field (data type), properties such as 'Required' or 'Validation' (using regular expressions) can be set, ensuring that all created content fragments adhere to the defined schema.

A. Editable templates control page structure and component policies, not the validation rules for fields within a separate Content Fragment Model.
C. Workflows are used for automating processes like content review and approval, not for controlling the availability of components in the authoring interface.
D. "Dynamic templates" is a general term; the specific AEM feature for controlling components in an editable template is the Policy configuration.

1. Adobe Experience Manager as a Cloud Service Documentation, "Editable Page Templates," Section: Policies. This section states, "Policies define the design properties of a component... For example, the components available in the component browser..." This directly supports option E, as policies are the designated mechanism for controlling allowed components.

2. Adobe Experience Manager as a Cloud Service Documentation, "Content Fragment Models," Section: Data Types and Properties. This documentation details the properties available for each data type in a model. For the "Single-line text" data type, it lists properties like "Required" and "Validation Type," which can be set to a predefined or custom regex. This directly supports option B for enforcing validation rules.

3. Adobe Experience Manager as a Cloud Service Documentation, "Applying Workflows to Pages." This document describes how workflows are used to manage content lifecycles (e.g., review, approval, publishing), confirming that their purpose is process automation, not real-time component filtering in the editor, making option C incorrect.

To override the default JSON export behavior for specific AEM components, a developer should create a Sling Model that implements the ComponentExporter interface. This model must be adaptable from the component's SlingHttpServletRequest or Resource. When the AEM SPA framework serializes the component model, it checks for a custom ComponentExporter implementation associated with the component's resource type. If found, it uses this custom implementation to generate the JSON output. For components without a custom ComponentExporter, AEM falls back to the default serialization mechanism, thus meeting the requirement to only override the exporter for a subset of components.

A. Implement ImplementationPicker service: This service is used to select a specific component implementation (script) to render based on request parameters, not to customize the JSON export model.
C. Implement FallbackComponentImpl service: This is not a standard, documented AEM service or interface related to the Sling Model Exporter framework or SPA component serialization.

1. Adobe Experience Manager as a Cloud Service Documentation, "Sling Model Exporter": This document explains the core framework. It states, "The Sling Model Exporter relies on the @JsonExport annotation on the Sling Model class... The framework also provides a way to use a custom serializer... A Sling Model can also implement the ComponentExporter interface to get full control over the JSON output."

Source: Adobe Experience Manager Documentation > Developing > Developing with CRX > Sling Model Exporter.

2. Adobe Experience Manager as a Cloud Service Documentation, "Customizing the JSON Output": This guide for SPA development explicitly details the method. It notes, "To take full control over the JSON serialization of a component, the component's model can implement the ComponentExporter interface... By implementing the ComponentExporter interface... the component is given full control over its JSON representation."

Source: Adobe Experience Manager Documentation > Developing > Headless and SPA > SPA Editor > Developing SPAs for AEM > Customizing the JSON Output.

3. Javadoc for com.adobe.cq.export.json.ComponentExporter: The official interface documentation defines its purpose: "Interface to be implemented by a Sling Model that wants to define its own JSON export. The Sling Model must be adaptable from a SlingHttpServletRequest or a Resource." This confirms it is the designated mechanism for custom component-level JSON serialization.

Source: Adobe Experience Manager 6.5.0 Javadoc, com.adobe.cq.export.json package summary.

The "Retry Delay" setting in an Adobe Experience Manager (AEM) replication agent specifies the time, in milliseconds, that the agent will wait between consecutive attempts to replicate content after an initial failure. If a replication job fails, the agent enters a retry cycle. This delay prevents the agent from immediately and repeatedly attempting to connect to a potentially unavailable or overloaded target instance, thus managing network traffic and system load. The agent will continue to retry until the replication is successful or the queue is manually cleared.

B. It controls the delay between each replication trigger. This is incorrect. The delay applies only after a replication attempt has failed, not between every triggered replication event.
C. It specifies how long to wait before marking a replication job as failed. This describes a timeout period, which is a different concept. The "Retry Delay" is the interval between retries, not the total time before giving up.
D. It manages the interval at which the replication queue is processed. This is incorrect. This describes a polling mechanism, which is not the primary function of "Retry Delay" for standard push-style replication agents.

1. Adobe Experience Manager 6.5 Documentation, "Configuring your Replication Agents." Under the section "Standard Agent," the "Retry" tab parameters are described. The documentation states for Retry Delay: "The delay (in milliseconds) to wait between two retries." This directly confirms that the setting defines the interval between retry attempts following a failure. (Adobe. (n.d.). Configuring your Replication Agents. Adobe Experience League. Retrieved from the AEM 6.5 documentation, section on Administering -> Operations -> Replication).

The standard naming convention for a generated Adobe Experience Manager (AEM) package file is -.zip. The 'Group' (aemgroup) is a metadata property used for organizational purposes within the AEM Package Manager repository, typically structuring the path as /etc/packages//-.zip. However, the group name is not included in the downloadable ZIP filename itself by default. The 'Content Path' (/content/aem-site) defines the JCR content included in the package, not the package's filename. Therefore, with a package name of aem-package and a version of 1.0, the correct filename is aem-package-1.0.zip.

A. aem-package-aemgroup-1.0.zip: This format is incorrect because the package group is not, by default, appended to the filename of the generated ZIP file.
B. aemgroup-aem-site-aem-package.zip: This is incorrect as it improperly includes the group name and the content path (aem-site) in the filename and lacks the version number.

1. Adobe Experience Manager as a Cloud Service Documentation, "How to Work With Packages": This official guide details the creation and management of packages. The user interface and build process described result in a downloadable file that follows the -.zip convention. The group is shown as a separate metadata field for organization. (See section: "Package Manager UI").

2. Apache Jackrabbit™ FileVault Package Maven Plugin, "filevault-package-maven-plugin: package": This documentation outlines the configuration for building AEM packages within a Maven project. The final ZIP filename is determined by Maven's build configuration (e.g., -.zip), while the package's internal name and group are set via the and configuration parameters respectively. The plugin does not combine these into the filename. (See parameter details for name and group).