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

Option B is the final rendered html output for the code snippet. The code snippet uses the data-sly-list block statement to iterate over the child pages of the current page. The data-sly-list statement assigns each child page to a variable named page and provides an index variable named i. The code snippet then uses the data-sly-test block statement to check if the index is odd or even and applies a different CSS class accordingly. The code snippet also uses the data-sly-element block statement to create an HTML element with the name specified by the elementName variable. The code snippet also uses the data-sly-attribute block statement to add an attribute with the name specified by the attrName variable and the value specified by the attrValue variable. The code snippet also uses the data-sly-resource block statement to include a resource with the path specified by the page.path variable and the resourceType specified by the resourceType variable. References: https://experienceleague.adobe.com/docs/experience-manager-htl/using-htl/htl-block-statements.html?lang=en

The com.day.cq.workflow.exec.ParticipantStepChooser interface is intended for implementations that will define the participant dynamically. This interface replaces the deprecated com.day.cq.workflow.exec.ParticipantChooser interface. The method getDynamicParticipant returns the dynamically resolved Principal id based on the work item, workflow session and metadata map parameters. References: https://developer.adobe.com/experience-manager/reference-materials/cloud-service/javadoc/com/day/cq/workflow/exec/ParticipantStepChooser.html

The correct tool to use for looking up Adobe Identity Management System (IMS) users by email and returning their IMS IDs is the IMS Lookup Tool. This tool is specifically designed to interact with the Adobe Identity Management System (IMS) and provides functionality to search for user details using various criteria such as email addresses.

Steps to use the IMS Lookup Tool:

Access the IMS Lookup Tool : Navigate to the IMS Lookup Tool interface. This tool is typically available through the Adobe Admin Console or as a part of Adobe's suite of administrative tools.

Authenticate : Ensure that you have the necessary permissions to use the tool. Authentication may be required, often through your Adobe ID and associated admin privileges.

Search by Email : Enter the email address of the user you want to look up in the search field.

Retrieve IMS ID : The tool will return the IMS ID associated with the provided email address.

This tool is essential for managing user identities and integrating with various Adobe services that rely on IMS for authentication and authorization.

References:

Adobe IMS Documentation

Adobe Admin Console

The /enableTTL “1” configuration must be applied to enable re-fetching of cached items based on Cache Headers sent by AEM. This configuration enables the Time To Live (TTL) feature of dispatcher, which allows dispatcher to check the Cache-Control and Expires headers of the cached files and re-fetch them from AEM if they are expired. References: https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/page-invalidation.html?lang=en#time-based-cache-invalidation

An experience fragment is a group of one or more components including content and layout that can be referenced within pages. Experience fragments allow authors to create variations for different channels and modify them for specific time periods. Experience fragments also support versioning and restoring previous versions. References: https://experienceleague.adobe.com/docs/experience-manager-65/authoring/authoring/experience-fragments.html?lang=en

Maximum Parallel Jobs is a configuration property that controls how many workflows can run concurrently on an AEM instance. Reducing this value can help to avoid overloading the server with too many workflows.

AEM Assets HTTP API is a RESTful API that allows access to content fragments in JSON format without any customization. The API supports CRUD operations on content fragments and their variations, as well as querying and searching for content fragments based on metadata or full-text search. References: https://experienceleague.adobe.com/docs/experience-manager-65/assets/extending/assets-api-content-fragments.html?lang=en

JUnit and Mockito are two unit testing dependencies that are generated by AEM archetype. JUnit is a framework for writing and running unit tests in Java. Mockito is a framework for creating and using mock objects in unit tests. AEM archetype also adds Apache Sling Mocks and AEM Mocks Test Framework by io.wcm as dependencies for unit testing. References: https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-wknd-tutorial-develop/project-archetype/unit-testing.html?lang=en https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/archetype/using.html?lang=en

The /cacheroot property under /cache in the dispatcher.any file identifies the directory where cached files are stored. It is a relative or absolute path to the cache root directory. The dispatcher creates a subdirectory for each virtual host under this directory and stores the cached files there. References: https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-configuration.html?lang=en#cache

The Apache Sling Logging Logger Configuration and Apache Sling Logging Writer Configuration are the OSGi configurations that the developer should use to create a Logger and Writer pair for the company’s application logging. The Logger Configuration defines the log level and the log file name for a given logger name or category. The Writer Configuration defines the file size, number of files, and file location for a given log file name. References: https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/configure-logging.html?lang=en#configuring-log-files

AEM as a Cloud Service does not support custom OSGi configuration runmodes, such as “config.author.staging”. Only < service > specific OSGi configuration runmodes, such as “config.author” or “config.publish”, are supported. These runmodes are used to apply configurations to specific services, such as author or publish. The < service > specific runmodes can be combined with environment variables to achieve different configurations for different environments. References: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/deploying/configuring-osgi.html?lang=en#run-modes https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/deploying/environment-variables.html?lang=en

In AEM as a Cloud Service environment, the repository areas /apps and /libs are considered as immutable, meaning that they cannot be modified at runtime by any means. These areas contain application code and configuration that are deployed via Cloud Manager and are read-only for security and performance reasons. Any changes to these areas require a new deployment via Cloud Manager. References: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/deploying/overview.html?lang=en#repository-restrictions https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/aem-project-content-package-structure.html?lang=en#repository-restrictions

For AEM as a Cloud Service, the correct format to use for OSGi configuration files is .cfg.json. This format is specifically designed for use in AEM as a Cloud Service and supports both structured and unstructured data, making it versatile for various configuration needs.

Steps to create and deploy OSGi configurations in .cfg.json format:

Create Configuration File : Create a .cfg.json file in your codebase, typically under the apps directory, for example:

/apps/myproject/config/org.apache.sling.commons.log.LogManager.cfg.json

Define Configuration : Add your configuration properties in JSON format:

{

"org.apache.sling.commons.log.level": "debug",

"org.apache.sling.commons.log.file": "logs/error.log"

}

Deploy to AEM : Deploy the configuration along with your code package to AEM as a Cloud Service. The configuration will be applied automatically.

References:

AEM as a Cloud Service - OSGi Configuration

The MapTo() method is used to map a SPA component to an AEM component by specifying the sling:resourceType of the AEM component as an argument. The MapTo() method should be called on the SPA component and not on a string. The second argument of the MapTo() method is optional and can be used to provide an edit configuration for the SPA component.

Adobe Client Data Layer is a JavaScript library that provides a standardized way to collect, structure, and manage data on a web page. It can be used to implement an event-driven data layer for analytics solutions. It integrates with Core components and allows authors to configure data layer properties for each component. It also supports custom events and data sources. References: https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/data-layer.html?lang=en https://github.com/adobe/adobe-client-data-layer

The Auto Replicate via On Off Trigger Configuration is a feature that allows content to be replicated as soon as the On Time and Off Times are reached. This feature can be enabled by creating an OSGi configuration for the com.day.cq.wcm.core.impl.servlets.OnOffTimeServlet service. This service listens for changes in the On Time and Off Time properties of pages and triggers replication accordingly. References: https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/replication.html?lang=en#on-off-time https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/replication.html?lang=en#auto-replication

To generate a test coverage report for an AEM project using the latest archetype, the correct plugin to use is the maven-surefire-plugin (Option A). The maven-surefire-plugin is a part of the Maven ecosystem and is widely used to run unit tests within a Maven project. This plugin can be configured to generate detailed test reports, including HTML versions, which can be easily shared with clients.

Here’s how to configure the maven-surefire-plugin to generate test coverage reports:

Add the Plugin to the POM File : Add the maven-surefire-plugin configuration in your pom.xml file:

< plugin >

< groupId > org.apache.maven.plugins < /groupId >

< artifactId > maven-surefire-plugin < /artifactId >

< version > 2.22.2 < /version >

< configuration >

< reportsDirectory > ${project.build.directory}/surefire-reports < /reportsDirectory >

< reportFormat > html < /reportFormat >

< trimStackTrace > false < /trimStackTrace >

< /configuration >

< /plugin >

Execute the Maven Command : Run the following command to execute the tests and generate the coverage report:

mvn clean test

Locate the Report : The HTML test coverage report will be generated in the target/surefire-reports directory of your project.

References:

Maven Surefire Plugin Documentation

The @Component(service = ConfigurationFactory.class) @Designate(ocd = ConfigurationFactorylmpl.Config.class,factory=true) option is recommended for creating a multi-tenancy configuration and binding multiple configurations to it. This option uses the OSGi R6 annotations to define a component that provides a service of type ConfigurationFactory and designates a class that contains the configuration properties. The factory=true attribute indicates that multiple configurations can be created for this component. References: https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/osgi-configuration-settings.html?lang=en#creating-factory-configurations