AD0-E137 Questions and Answers

The correct HTL syntax combines the page path and the suffix in a structured format where the final .html extension appears at the end of the generated URL. In AEM, links must resolve to valid Sling resources that end in .html for pages, and suffixes can be appended before the extension. Option B correctly creates the path /content/testsite/en/page1/product/test1.html, which is a valid and Sling-resolvable path. Option A incorrectly places .html too early, producing an invalid URL that AEM cannot resolve. Option C inverts the intended relationship between the path and suffix. Adobe documentation for HTL and URL construction highlights that Sling requires .html as the standard extension for page rendering, and suffixes should precede this extension.

Explanation (Adobe Docs Reference):

AEM supports basic multi-tenancy through separation by content paths, ACLs, and templates. However, this is not true multi-tenancy. For strict isolation with no code/content overlap, separate AEM instances per tenant is required. Adobe’s official recommendation for true isolation (zero cross-tenant knowledge or sharing) is to run dedicated AEM environments per tenant.

Adobe Documentation:

“AEM supports multi-tenancy by allowing separation of content trees, ACLs, and components. However, for strict tenant isolation (true multi-tenancy), each tenant must be deployed on separate AEM environments.”

— Adobe AEM Multi-tenancy Concepts

developer documents: Vanity URLs in Adobe Experience Manager (AEM) allow authors to define custom, shorter, or more user-friendly URLs for pages directly in the page properties, which are then published and handled by the Dispatcher for caching and security. To enable Dispatcher to dynamically fetch and allow these vanity URLs without manually updating filters for each one, a specific configuration section must be defined in the Dispatcher configuration file (typically dispatcher.any). This section instructs Dispatcher on how to retrieve the list of vanity URLs from the AEM publish instance, store them locally, and automatically permit requests matching those URLs to bypass certain deny rules.

The correct property for defining this configuration is /vanity_urls, which is a child block under the /farms section in the Dispatcher configuration. This block contains sub-properties such as:

/url: The endpoint on the AEM publish instance to fetch the vanity URL list (e.g., "https://publish.example.com/libs/granite/dispatcher/content/vanityUrls.html ").

/file: The local file path where Dispatcher caches the fetched vanity URL list (e.g., "/tmp/vanity_urls"). Dispatcher requires write access to this file.

/delay: The interval (in seconds) between periodic fetches of the vanity URL list from AEM (default is 60 seconds).

/loadOnStartup: A boolean (0 or 1) to load the vanity URLs immediately when Dispatcher starts (default is 1).

For the vanity URL feature to function:

Install the VanityURLS-Components package on the AEM publish instance(s) from Adobe's Software Distribution to enable the /libs/granite/dispatcher/content/vanityUrls.html servlet.

Ensure Dispatcher filters deny vanity URL paths by default (e.g., via a rule like { /type "allow" /method "GET" /url "/libs/granite/dispatcher/content/vanityUrls.*" /extension "html" } to allow the fetch, but deny the vanity paths themselves).

Add the /vanity_urls block under /farms/{farmname}.

Restart the Apache web server after configuration changes.

If not configured correctly, errors like "Vanity URL file (/tmp/vanity_urls) not found, fetching..." may appear in Dispatcher logs, followed by failures if the AEM endpoint is unreachable.

Exact Extracts from Adobe Experience Manager (AEM) Sites Developer Documents:

From "Configure AEM Dispatcher": "Add the /vanity_urls section below /farms. Restart Apache web server. ... The value of this property must be '/libs/granite/dispatcher/content/vanityUrls.html'. /file: The path to the local file where Dispatcher stores the list of vanity URLs. Make sure that the Dispatcher has write-access to this file. /delay: (Seconds) The time between calls to the vanity URL service. ... If your render is an instance of AEM, you must install the VanityURLS-Components package from Software Distribution to enable the vanity URL service."

From "AEM Dispatcher vanity URLs feature": "For this reason, the Dispatcher module has a feature to auto-allow anything listed as a vanity in the content tree. ... Simple Dispatcher has an auto-filter allow mechanism and you have to install an AEM package and then configure the Dispatcher to point to that package page."

From "AEM Dispatcher Common Logs": "Thu Sep 27 17:40:29 2018 D pid 21844 Checking vanity URLs Thu Sep 27 17:40:29 2018 D pid 21844 Vanity URL file (/tmp/vanity_urls) not found, fetching... Thu Sep 27 17:40:29 2018 D pid 21844 Loaded 18 vanity URLs from file /tmp/vanity_urls"

To optimize queries against DAM assets with custom properties, developers must extend the existing damAssetLucene index. The correct method is to add the custom property under:

oak:index/damAssetLucene/indexRules/dam:Asset/properties. This ensures that the property is indexed for all assets and avoids traversal queries. Option B refers to a non-existent lucene index path, and Option C incorrectly suggests adding a property value (Hello) instead of the property name. Adobe’s indexing guidelines specify that extending existing Lucene indexes such as damAssetLucene is the standard approach for asset-related queries. This ensures queries remain efficient, scalable, and compatible across environments.

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.

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.

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

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.

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

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