Free Practice Questions for the Adobe Experience Manager AD0-E128 Exam (2026 Updated)

Comprehensive Explanation

Adobe Experience Manager provides SAML 2.0 authentication functionality through its Adobe Granite SAML Authentication Handler.

To investigate authentication failures, assertion validation errors, certificate problems, or identity-provider integration issues, developers can configure a dedicated Apache Sling logger targeting the SAML authentication package.

Adobe explicitly documents the logger name as:

com.adobe.granite.auth.saml

The recommended diagnostic configuration uses the Apache Sling Logging Logger Configuration with the logging level set to DEBUG .

A dedicated file, such as logs/saml.log , can be configured to isolate authentication-related messages.

Option A is correct because it matches the Java package associated with the Adobe Granite SAML Authentication Handler.

Option B is incorrect because com.adobe.granite.debug.auth.saml is not the documented logger category.

Option C is incorrect because the SAML authentication handler uses the Adobe Granite namespace rather than the proposed com.adobe.sling.auth.saml namespace.

Diagnostic messages can reveal problems involving invalid assertion signatures, incorrect certificates, unavailable private keys, and authentication configuration mismatches.

Operational consideration: DEBUG logging may expose sensitive authentication-related diagnostic information and generate additional log volume. It should be enabled only for the required troubleshooting period and disabled afterward.

Official Adobe Reference: SAML 2.0 Authentication Handler — Configure a Logger for SAML; Configuring OKTA with AEM — DEBUG Logging.

Comprehensive Explanation

Content Fragments provide structured, reusable, presentation-independent content within Adobe Experience Manager.

A Content Fragment is created from a Content Fragment Model, which defines its data structure using fields such as single-line text, multiline text, numbers, dates, Boolean values, enumerations, and references to other content.

This model-driven architecture makes Content Fragments suitable for managing structured information independently of the visual components used to display it.

For example, an e-commerce application can define a Content Fragment Model representing product information, including product names, specifications, descriptions, and related assets. The resulting content can be reused across AEM Sites pages, mobile applications, and external systems.

Option A refers to a component dialog, which provides an authoring interface for configuring component properties rather than representing a reusable structured-content entity.

Option B refers to Experience Fragments, which combine content and presentation to create reusable visual experiences.

Option C refers to design dialogs, which historically controlled component design properties in static-template implementations.

Content Fragments are specifically intended for structured and channel-neutral content management. They also integrate with AEM's GraphQL API, enabling applications to query and retrieve model-defined information.

Official Adobe Reference: Working with Content Fragments; Content Fragments and Experience Fragments.

Comprehensive Explanation

Adobe Experience Manager Multi Site Manager (MSM) enables organizations to maintain a centrally managed content source while distributing localized variations across multiple regional websites.

For this scenario, the appropriate implementation is to establish a primary French-language site and create Live Copies for Chad, Ivory Coast, and Senegal.

The primary French site serves as the content source, while individual country sites inherit common information through MSM Live Copy relationships. Rollout configurations determine when and how changes are synchronized between the source and regional destinations.

Each country can maintain localized information, including currency, shipping conditions, payment methods, promotional offers, and country-specific regulatory disclosures. Inheritance can be suspended where localized content must differ from the central version.

Option A is less appropriate because MSM does not perform language translation itself. Adobe recommends using translated language masters as sources for regional sites that share the same language.

Option C incorrectly emphasizes copying templates rather than managing Live Copies of content pages. Option D creates unnecessary duplication and weakens centralized content governance.

Using a French language master therefore provides consistent content management while preserving the flexibility required for country-specific localization.

Official Adobe Reference: Multi Site Manager and Translation; Reusing Content: Multi Site Manager and Live Copy.

Comprehensive Explanation

Adobe Experience Manager Multi Site Manager applies a defined configuration-resolution hierarchy when determining the rollout configuration for a Live Copy.

When a Live Copy page does not explicitly define a rollout configuration, AEM checks whether its associated blueprint source page specifies one. If a configuration exists on the blueprint source, AEM applies that configuration to the Live Copy.

This behavior ensures that synchronization policies defined at the source can govern associated Live Copies without requiring every individual page to maintain a duplicate configuration.

Adobe documents the resolution order as follows: an explicit Live Copy configuration takes precedence; otherwise, the blueprint source configuration is considered. If neither specifies a configuration, AEM checks the Live Copy parent page. Finally, the system default applies when no configuration is available through the preceding levels.

Option A is incorrect because the system default is a fallback, not the immediate choice. Option C is incorrect because the absence of an explicit configuration does not automatically cause a publication error. Option D describes a later fallback condition.

Therefore, option B correctly identifies the configuration that takes precedence in the scenario.

Official Adobe Reference: Configuring Live Copy Synchronization — Specifying the Rollout Configurations to Use.

Comprehensive Explanation

Adobe Experience Manager stores its standard application log files within the crx-quickstart/logs directory of a local installation.

When an AEM Quickstart instance is started, the runtime creates the necessary directory structure for repository storage, configuration, application execution, and diagnostic logging.

The default log directory includes several files used for troubleshooting, such as error.log , request.log , and access.log .

The full path to the standard application error log is:

< aem-installation-directory > /crx-quickstart/logs/error.log

Option B is correct because it identifies the directory containing the standard AEM error log.

Option A is incorrect because crx-quickstart/metrics/logs is not the documented default directory for application error logging.

Option C is incorrect because crx-quickstart/bin normally contains startup scripts and related runtime-management files.

Option D is incorrect because crx-quickstart/conf/error/logs is not a standard AEM Quickstart logging directory.

The error.log file is particularly important for investigating Java exceptions, OSGi failures, Sling Models, repository queries, and component-rendering problems.

Developers can monitor the file continuously using an appropriate operating-system utility or inspect historical entries to correlate errors with affected requests.

Adobe confirms that local AEM SDK environments use the same fundamental crx-quickstart/logs directory structure.

Official Adobe Reference: Monitoring and Maintaining Your AEM Instance — Finding the Log Files; AEM as a Cloud Service Development Guidelines — Logs.

Comprehensive Explanation

Adobe Experience Manager provides configurable logging through Apache Sling's logging infrastructure, which supports defining dedicated loggers and log writers for individual services or Java packages.

The principal benefit of assigning a separate log file to a particular service is the ability to isolate its diagnostic messages from general application logging.

For example, a developer investigating a custom OSGi service can configure an Apache Sling Logging Logger Configuration that targets the service's package and directs its messages to a dedicated log file.

A corresponding Apache Sling Logging Writer Configuration determines the physical output file, rotation behavior, and retention settings.

This arrangement makes troubleshooting more efficient because developers can review service-specific events without filtering through unrelated messages generated by the rest of the AEM application.

Option A is incorrect because increasing log-file size is not the purpose of creating a dedicated writer.

Option B is incorrect because the requirement emphasizes isolating one service rather than consolidating messages from multiple services.

Option C is incorrect because configuring a separate writer does not inherently enable asynchronous logging.

Adobe explicitly documents that service-specific logging is particularly useful during development and testing, when additional diagnostic detail may be required.

Dedicated logging also allows a service-specific log level to be configured without increasing logging verbosity across the entire application.

Official Adobe Reference: Logging — Loggers and Writers for Individual Services; Creating Your Own Loggers and Writers.

Comprehensive Explanation

Adobe Experience Manager supports exposing structured component data through the Sling Model Exporter, which serializes Sling Model properties into JSON representations.

In an AEM Single Page Application (SPA) implementation, the frontend application consumes exported component data to render the user interface.

The .model.json selector provides access to the JSON representation generated by the Sling Model Exporter.

For example, a homepage located at /content/mysite/en/home.html can expose its exported model through:

/content/mysite/en/home.model.json

The developer can inspect this response to determine whether the custom component and its expected property are included in the exported model.

Option A correctly uses the .model.json selector.

Option B is incorrect because /sling.json is not the documented endpoint for the page's Sling Model Exporter representation.

Option C is incorrect because /sling-model.json does not follow the required selector structure.

If the property is absent, the developer should inspect the Sling Model's exported getters, annotations, implementation, component resource type, and the frontend component mapping.

The developer must also confirm that the relevant component is present in the page model and that the exported property is not explicitly excluded from JSON serialization.

This diagnostic method allows the frontend and backend implementations to be evaluated independently.

Official Adobe Reference: Sling Model Exporter — JSON Serialization; AEM SPA Editor and Model Exporter.

Comprehensive Explanation

The HTML Template Language (HTL) provides the data-sly-element block statement for dynamically replacing an HTML element's tag name during server-side rendering.

This functionality is particularly useful when building configurable heading components. A Sling Model can expose a property named titleLevel containing values such as h1 , h2 , or h3 . HTL evaluates that property and replaces the host element's original tag name with the specified heading level.

For example, the valid implementation is:

< h1 data-sly-element="${titleLevel}" >

Page Heading

< /h1 >

If titleLevel evaluates to h2 , the rendered element becomes an h2 heading.

Option B is incorrect because data-sly-attribute dynamically assigns HTML attributes rather than changing the element name. Option C is incorrect because data-sly-use provides access to backing objects, such as Sling Models, instead of replacing HTML elements.

Source accuracy note: Option A contains malformed syntax: @context-'unsafe' appears outside the HTL expression. Moreover, disabling escaping is unnecessary because HTL automatically validates element names using its elementName security context. The corrected implementation above is the appropriate solution.

Official Adobe Reference: Getting Started with HTL — Element and Attribute Names; HTML Template Language Specification — Element Statement.

Comprehensive Explanation

Adobe Experience Manager provides the wcmmode object within HTL to identify the current Web Content Management rendering mode.

The wcmmode.edit property evaluates to true when a page is rendered in AEM's Edit mode. This enables developers to conditionally display authoring-specific markup without including that markup in normal published-page output.

The data-sly-test block statement evaluates a Boolean expression and renders its host element only when the expression is true.

The correct implementation is:

< p data-sly-test="${wcmmode.edit}" >

Hello World

< /p >

When an author opens the page in Edit mode, the paragraph is rendered. In other modes where wcmmode.edit evaluates to false, the paragraph is omitted.

Option A is incorrect because wcm.edit is not the documented HTL property for detecting the current authoring mode.

Option B is incorrect because wcmmode.editor is not the recognized mode property.

Adobe also documents wcmmode.preview for conditions that must apply specifically to Preview mode.

A common practical application involves displaying component placeholders when a component has no configured content. Such placeholders help authors identify and select components that would otherwise appear empty.

The wcmmode.edit condition is therefore the correct mechanism for rendering content exclusively in Edit mode.

Official Adobe Reference: Adobe Experience Manager Components — The Basics, Component Placeholders; Components Reference Guide — Authoring Mode.

Comprehensive Explanation

Editable templates in Adobe Experience Manager separate template configuration into Structure, Initial Content, Content Policies, and Layout.

The Structure section defines components that must remain consistent across pages created from the template. Components placed in this section can be locked to prevent page authors from modifying, moving, or deleting them.

When a component is locked in the template structure, it remains visible on resulting pages but cannot be edited directly by ordinary page authors.

This capability is particularly useful for mandatory page elements such as standardized headers, regulatory notices, branding elements, and structural containers.

Option A is incorrect because removing a component from the allowed-components policy restricts its availability for insertion; it does not establish an existing, non-editable component.

Option B is incorrect because Initial Content provides starting content that authors can subsequently modify on individual pages.

Option C does not provide the required template-level editing restriction.

The appropriate implementation is therefore to place the component in the editable template's Structure section and maintain it in a locked state.

Adobe's editable-template documentation explicitly distinguishes locked structure components from editable initial content, establishing the correct behavior for this requirement.

Official Adobe Reference: Editable Templates — Structure and Initial Content; Templates to Create Pages That Are Editable with the Page Editor.

Comprehensive Explanation

Adobe Experience Manager Dispatcher controls external HTTP request access through the /filter section of its farm configuration. This section can permit or reject requests according to their HTTP method, URL, selectors, extensions, and query strings.

When Dispatcher rejects a request containing query parameters, the developer should inspect its access-filter rules to determine whether an appropriate /query condition has been configured.

For example:

/filter {

/0001 {

/type "allow"

/method "GET"

/url "/content/site/*"

/query "q=*"

}

}

This rule permits matching GET requests containing the designated query parameter.

Option A controls the AEM rendering instances and does not determine whether query strings are permitted. Option B generally refers to cache rules, which govern cache eligibility. Option C controls caching behavior, including /ignoreUrlParams , rather than request authorization.

Technical qualification: The actual Dispatcher configuration directive is /filter , not /filters . Therefore, option D contains a naming error.

Additionally, if the problem concerns pages with query parameters bypassing the cache rather than being rejected, option C would be relevant because /cache/ignoreUrlParams controls query-parameter caching behavior.

For requests being denied, D identifies the intended configuration area.

Official Adobe Reference: Configure Dispatcher — Restrict Query Strings and Ignore URL Parameters.

Comprehensive Explanation

Adobe Experience Manager maintains an HTTP request log that records incoming requests and their corresponding responses, including response times.

The request.log file is particularly useful for identifying slow page requests, diagnosing performance problems, and evaluating application responsiveness.

Each request receives an identifier that associates the incoming HTTP request with its corresponding response. The response record includes the HTTP status code, content type, and processing time.

For example:

09:43:41 [66] - > GET /content/site/en.html HTTP/1.1

09:43:41 [66] < - 200 text/html 797ms

In this example, AEM required 797 milliseconds to process the request.

Option A is incorrect because audit.log primarily records auditing information, such as content-related administrative and moderation activities.

Option B is incorrect because stdout.log captures standard-output messages, including startup-related information, rather than providing the dedicated request timing records.

Option C is correct because request.log provides a direct mechanism for analyzing HTTP response times.

Adobe recommends using request-log analysis to identify slow pages, evaluate request concurrency, and diagnose application performance bottlenecks.

For extensive performance investigations, developers can aggregate response times by URL and correlate slow requests with thread dumps, repository query performance, and application logs.

Official Adobe Reference: Monitoring and Maintaining Your AEM Instance — Interpreting the request.log; Examples of request.log Analysis.