Question 1

A developer needs to create a workflow custom process step in AEM. In a custom process step, an
OSGi component needs to implement the WorkflowProcess interface.
Which method should the developer implement?

Accepted Answer

C

Explanation: The WorkflowProcess interface is the interface to be used for automatic workflow steps implemented in Java. Classes implementing this interface define Java based processes that can be attached to a WorkflowNode and executed by the workflow engine. The method execute takes a WorkItem, a WorkflowSession and a MetaDataMap as parameters and performs the logic of the custom process step. Reference: https://developer.adobe.com/experience-manager/referencematerials/6-5/javadoc/com/adobe/granite/workflow/exec/WorkflowProcess.html https://experienceleague.adobe.com/docs/experience-manager-learn/forms/adaptiveforms/custom-process-step-aem-workflow.html?lang=en

Question 2

An AEM environment is cloned, and the domain and IPs ate changed. What must be reconfigured for content activation to work?

Accepted Answer

B

Explanation: When an AEM environment is cloned and the domain and IPs are changed, it is crucial to reconfigure the Transport URI of both the flush and replication agents to ensure content activation works correctly. Here’s the step-by-step process to reconfigure these settings: Access the AEM Tools Console: Log into your AEM instance and navigate to Tools > Deployment > Replication. Update Replication Agents: Go to the "Agents on author" section. Select each replication agent (usually named "default" or based on your custom setup). Edit the agent configuration. Update the Transport URI to reflect the new domain and IP address. Save the configuration. Update Flush Agents: Navigate to the dispatcher flush agents. Select each flush agent. Edit the agent configuration. Update the Transport URI with the new domain and IP address. Save the configuration. Test the Configuration: After updating the URIs, test the content activation process to ensure that the replication and flushing mechanisms are working correctly with the new settings. These steps ensure that the communication paths for content replication and cache flushing are correctly established, thereby maintaining the integrity and functionality of content activation. Reference: AEM Replication Documentation Dispatcher Configuration Documentation

Question 3

A development team is starting a new AEM project that is going to integrate with the Adobe
Commerce platform. The developer needs to create a new AEM project using the Maven command
line interface.
How can the 'mvn -B archetype:generate' command help the developer with the integration
between AEM and Adobe Commerce?

Accepted Answer

C

Explanation: The includeCommerce property is a boolean flag that indicates whether to include Commerce Core Components in the project or not. If set to y, the command will generate a commerce module that contains specific Commerce Core Components and their dependencies. These components can be used to integrate AEM with Adobe Commerce platform or other commerce solutions. Reference: https://experienceleague.adobe.com/docs/experience-manager-corecomponents/using/developing/archetype/using.html?lang=en#properties https://experienceleague.adobe.com/docs/experience-manager-corecomponents/using/components/commerce.html?lang=en

Question 4

A developer is on an AEM application that is being used to calculate an employee's salary. The
calculation is done in an OSGi service called CalculationService. This service class has a dependency
on one other service, called the EmployeeService.
How should the developer make sure that the critical code in the CalculationService has a high unit
test coverage?

Accepted Answer

C

Explanation: A mock framework is a tool that allows creating mock objects that simulate the behavior of real objects in a controlled way. A mock framework can be used in a unit test to inject the EmployeeService dependency into the CalculationService and verify its interactions. This way, the unit test can focus on testing the logic of the CalculationService without relying on the actual implementation of the EmployeeService. Reference: https://sling.apache.org/documentation/development/sling-testing-tools.html https://wcm.io/testing/aem-mock/usage.html

Question 5

A developer is working on a project based on core components. The client requests that text pasted
inside the Text component should be stripped of all styling and formatting.
The developer needs to override RTE plugin implementation and change the default paste (CTRL+V)
behavior.
Which paste option should the developer add to achieve this?

Accepted Answer

B

Explanation: To ensure that text pasted inside the Text component in AEM is stripped of all styling and formatting, you need to override the RTE (Rich Text Editor) plugin implementation and change the default paste behavior. The correct option to achieve this is defaultPasteMode=plaintext. Steps to configure the RTE plugin for plain text pasting: Locate the RTE Configuration: Find the existing configuration for the RTE or create a new one in the /apps directory of your AEM project. Modify the Plugin Configuration: Add or update the configuration to include the defaultPasteMode parameter. The configuration might look something like this: { "jcr:primaryType": "nt:unstructured", "features": "[text]", "defaultPasteMode": "plaintext" } Apply the Configuration: Ensure that this configuration is applied to the Text component. This typically involves updating the component dialog or design dialog to reference the updated RTE configuration. Test the Configuration: In the AEM author instance, open the page with the Text component and paste text using CTRL+V. The pasted text should now be stripped of all styling and formatting, adhering to the plaintext mode. By setting defaultPasteMode to plaintext, you ensure that the RTE only accepts plain text input, removing any formatting that might come from external sources. Reference: AEM Rich Text Editor (RTE) Documentation Configuring the Rich Text Editor in AEM

Question 6

Which practice should be used to push a code fix to make it into the current release candidate?

Accepted Answer

D

Explanation: To push a code fix into the current release candidate, the best practice is to cherry-pick the fix commit into the release candidate branch. Cherry-picking allows you to apply specific changes from one branch to another, ensuring that only the necessary fixes are included without introducing unrelated changes. Here’s how to cherry-pick a commit: Identify the Commit: Locate the commit hash of the fix you need to apply. This can be found in your version control system (e.g., Git). Checkout the Release Candidate Branch: git checkout release-candidate-branch Cherry-pick the Commit: git cherry-pick Resolve Conflicts (if any): If there are conflicts, resolve them manually and then continue the cherry- pick process: git add git cherry-pick --continue  Test the Changes: Ensure that the changes are tested thoroughly in the release candidate environment to confirm the fix works as expected.  Push the Changes: git push origin release-candidate-branch Cherry-picking ensures that only the required changes are applied to the release candidate, maintaining the stability and integrity of the codebase. Reference: Git Cherry-pick Documentation

Question 7

A customer adds third-party client libraries to add some features in an existing AEM application, which will significantly reduce performance. How should the developer optimize the site?

Accepted Answer

A

Explanation: Embedding client libraries is a technique that allows combining code from multiple client libraries into a single file. This reduces the number of network requests and improves performance. Embedding client libraries can be done by using the embed property of the cq:ClientLibraryFolder node and specifying the categories of the client libraries to be embedded. Reference: https://experienceleague.adobe.com/docs/experience-manager-cloudservice/content/implementing/developing/full-stack/clientlibs.html?lang=en#embed https://experienceleague.adobe.com/docs/experience-manager65/developing/introduction/clientlibs.html?lang=en#embedded-files

Question 8

An AEM application requires LDAP Service integration to synchronize users/groups. Which two OSGi configuration are required for LDAP integration in AEM? (Select Two.)

Accepted Answer

Explanation: The Apache Jackrabbit Oak External Login Module and Apache Jackrabbit Oak Default Sync Handler are the two OSGi configurations that are required for LDAP integration in AEM. The External Login Module defines how AEM connects to the LDAP server and authenticates users against it. The Default Sync Handler defines how AEM synchronizes users and groups from the LDAP server to the repository. Reference: https://experienceleague.adobe.com/docs/experience-manager65/administering/security/ldap-config.html?lang=en#ldap-integration

Question 9

An AEM Developer needs to build out a project. That contains only the required modules. Which most recent AEM Archetype module is optional?

Accepted Answer

B

Explanation: When building out a project using the most recent AEM Archetype, the ui.frontend module is optional. The ui.frontend module is typically used for integrating front-end build processes, such as those involving npm, Webpack, or other front-end tooling. If your project does not require such front-end tooling, you can omit this module. Here is a breakdown of the archetype modules: it.launcher: This module is used for integration tests and is required if you need to run automated tests as part of your build process. ui.frontend: This module includes front-end tooling and build processes. It is optional and can be omitted if your project does not involve complex front-end development. ui.tests: This module includes unit and integration tests for the UI part of your AEM project. It is often required for testing purposes. ui.content: This module includes the content structures and initial content for your AEM project. It is generally required to set up the content for your project. Reference: AEM Project Archetype AEM Development Best Practices

Question 10

A developer has to create a Logger and Writer pair for the company's application logging. Which OSGi configurations should the developer use?

Accepted Answer

C

Explanation: 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. Reference: https://experienceleague.adobe.com/docs/experience-manager65/deploying/configuring/configure-logging.html?lang=en#configuring-log-files

Question 11

A developer needs to create a dynamic participant step where the participant is selected
automatically at run time.
The developer decides to develop an OSGi service, which needs to implement the
com.day.cq.workflow.exec.ParticipantStepChooser interface.
Which method should the developer implement from the
com.day.cq.workflow.exec.ParticipantStepChooser interface?

Accepted Answer

C

Explanation: 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. Reference: https://developer.adobe.com/experience-manager/referencematerials/cloud-service/javadoc/com/day/cq/workflow/exec/ParticipantStepChooser.html

Question 12

A client is having issues with some query results:
• Many of the client's industry terms have the same meaning, and users do not always search the
exact wording
• Many users search by typing in short phrases instead of exact keywords, ex:// "cats and dogs"
What index analyzers should the AEM developer recommend?

Accepted Answer

D

Explanation: A Synonym filter can help to map different terms that have the same meaning, such as “cat” and “feline”. A LowerCase filter can help to normalize the case of the terms, so that “cats and dogs” and “Cats and Dogs” are treated the same. Reference:1Lucene Analyzers section

Question 13

A new component called Page Headline needs to be implemented. The only difference to the title component delivered by Adobe's WCM core components is that the text needs to be taken from the current page title instead of jcr.title. How should a developer implement this request? A) 1. Create custom component 2. Implement Sling Modal as follows https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/Adobe_AD0-E134/page_52_img_1.jpg B) 1. Create proxy component from the core title component 2. Implement sling Model as follows https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/Adobe_AD0-E134/page_52_img_2.jpg C) https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/Adobe_AD0-E134/page_52_img_3.jpg 1. Create proxy component from the core title component 2. Implement Sling Model as follows https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/Adobe_AD0-E134/page_52_img_4.jpg

Accepted Answer

C

Explanation: To implement a new component called "Page Headline" which takes the text from the current page title instead of jcr:title, you should create a proxy component from the core title component and implement a Sling Model accordingly. Option C demonstrates the correct approach to achieve this functionality. Here is a detailed explanation of Option C: Create Proxy Component: Create a new component in your project that will act as a proxy to the core title component. This involves creating a new component node in the repository that inherits from the core title component. Example path: /apps/myproject/components/pageHeadline with sling:resourceSuperType set to core/wcm/components/title/v2/title. Implement Sling Model: Implement a Sling Model that adapts from SlingHttpServletRequest and Title.class, ensuring it overrides the text fetching logic to retrieve the title from the current page's title. The model will use @ScriptVariable to inject the current page and @Self to access the core title component's logic. @Model(adaptables = SlingHttpServletRequest.class, adapters = Title.class, resourceType = "myproject/components/pageHeadline") public class PageHeadline implements Title { @ScriptVariable private Page currentPage; @Self @Via(type = ResourceSuperType.class) private Title title; @Override public String getText() { return currentPage.getTitle(); } @Override public String getType() { return title.getType(); } } @Model Annotation: Specifies that this class is a Sling Model and adapts from SlingHttpServletRequest. It is also an adapter for Title.class and applies to the myproject/components/pageHeadline resource type. @ScriptVariable: Injects the current Page object, which allows access to the current page's properties. @Self @Via(type = ResourceSuperType.class): Injects the core title component, allowing the reuse of existing logic. getText() Method: Overrides the getText() method to return the title from the current page instead of the jcr:title. getType() Method: Delegates to the core title component's getType() method to maintain existing functionality. This approach leverages the power of Sling Models and the core components to extend functionality while keeping the implementation clean and maintainable. Reference: Adobe Experience Manager - Core Components Sling Models Documentation

Question 14

An AEM developer is assigned a task to design a workflow. The workflow is supposed to collect data
from the participant and then determine the reviewer/approver branch to proceed further.
Which workflow step should be used by the developer?

Accepted Answer

D

Explanation: To design a workflow that collects data from the participant and then determines the reviewer/approver branch to proceed further, the developer should use the Dynamic Participant Step. This workflow step allows for dynamic determination of participants based on the data collected or any other logic implemented in the workflow. Here’s how to implement a Dynamic Participant Step in AEM: Create the Workflow Model: In AEM, navigate to Tools > Workflow > Models. Create a new workflow model or edit an existing one. Add Dynamic Participant Step: Drag and drop the Dynamic Participant Step into your workflow model. Configure the Dynamic Participant Step: Click on the Dynamic Participant Step and configure it by specifying the participant chooser class. This class should implement the logic to determine the next participant. @Component(service = ParticipantStepChooser.class, property = { "service.description=Dynamic Participant Chooser" }) public class CustomParticipantStepChooser implements ParticipantStepChooser { @Override public String getParticipant(WorkItem workItem, WorkflowSession workflowSession, MetaDataMap metaDataMap) { // Custom logic to determine the participant based on workflow data String reviewer = // logic to determine reviewer return reviewer; } } Implement Participant Chooser Logic: The CustomParticipantStepChooser class should contain the logic to determine the next participant based on the workflow data. This can include reading workflow variables, making decisions based on conditions, or any other custom logic. Deploy and Test: Save the workflow model and test it by starting a new workflow instance. Ensure that the dynamic participant determination works as expected. By using the Dynamic Participant Step, you can create flexible workflows that adapt to the data and context, ensuring that the appropriate participants are chosen dynamically. Reference: Adobe Experience Manager Workflow AEM Dynamic Participant Step

Question 15

Which attribute must be present in all filter rules in AEM dispatcher configuration?

Accepted Answer

D

Explanation: The /glob attribute is mandatory for all filter rules in the dispatcher configuration. It specifies a pattern that is matched against the incoming request URL. If the pattern matches, the rule is applied. The /glob attribute can use wildcards (*) and placeholders ($1, $2, etc.) to match parts of the URL. Reference: https://experienceleague.adobe.com/docs/experience-managerdispatcher/using/configuring/dispatcher-configuration.html?lang=en#filter-rules

Free Adobe AD0-E134 Actual Exam Questions