AD0-E137 Sample Questions Answers

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

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.

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

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

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 AEM, multi-site management allows centralized content updates to be pushed across different localized or departmental sites. The “Partial” option on the rollout configuration ensures that only specific components or regions designated for shared updates are synchronized, while leaving local content intact. This fits the described requirement where a portion of each school’s homepage must receive university updates without affecting school-specific content. Option A, Experience Fragments, could be used but are better suited for shared fragments of design/content, not controlled rollout scenarios. Option C requires manual inheritance restoration per page, which is inefficient. Option D, implementing custom rollout logic, is not needed when the built-in “Partial Rollout” option fulfills the requirement. Adobe emphasizes using partial rollout in multi-site configurations to balance central control with localized autonomy.

By default, when saving dialog values, AEM stores them as String types in the JCR unless a type hint is provided. To ensure a checkbox is stored as a Boolean, developers must add a hidden TypeHint field to the dialog. This informs Sling Post Servlet about the correct JCR type when persisting values. Option A, using a JCR Event Listener, is inefficient and adds unnecessary complexity. Option C, using a Switch, would still result in a String unless the TypeHint is specified. Adobe documentation specifies that TypeHint fields should be added whenever developers need precise control over how values are stored, especially for Boolean, Long, or Date properties.

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.

In AEM, fine-grained access control is managed using JCR Access Control Entries (ACEs). To grant access only to a specific node but exclude all child nodes, the correct approach is to set the rep:glob = "" property. This ensures that permissions apply strictly to the node itself and not recursively. Option B, rep:globs = "**", would apply access recursively to all descendants. Option C, rep:glob = "child", is invalid and does not represent a valid configuration. Adobe recommends precise use of rep:glob patterns to restrict user access according to security requirements, ensuring least-privilege principles.

The segment store in AEM grows as new content versions are created and retained. If not managed, this can result in significant performance degradation and increased storage size. To address this, the Version Purge maintenance task should be scheduled daily. This task removes old, unused versions of nodes and ensures that the repository remains healthy and compact. Option A, Audit Log Purge, cleans old audit entries but does not significantly affect segment store size. Option B, Lucene Binaries Cleanup, targets binary references but is not the main factor behind large segment store growth. Adobe recommends running Version Purge regularly as part of AEM maintenance to balance data retention needs and performance optimization.

Explanation (Adobe Docs Reference):

When configuring SAML SSO with AEM, the dispatcher must allow POST requests to the saml_login endpoint. If blocked, AEM redirects endlessly back to the IDP. This is done by allowing the POST request in filters.any.

Adobe Documentation:

“For SAML authentication to work with AEM behind a Dispatcher, you must configure the dispatcher filter to allow POST requests to /saml_login. Otherwise, authentication attempts will loop infinitely.”

— AEM Dispatcher and SAML Authentication Configuration

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.