AD0-E134 Adobe Experience Manager Developer Exam Questions and Answers

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. References:https://experienceleague.adobe.com/docs/experience-manager-65/administering/security/ldap-config.html?lang=en#ldap-integration

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.

References:

Git Cherry-pick Documentation

The issue arises because the anonymous user does not have the necessary read permissions for the /content directory. When using Sling context-aware configurations, access to the configuration resource is required. If the anonymous user lacks read permissions, the configuration cannot be retrieved, resulting in a null value.

To fix this issue, you need to grant read permissions to the anonymous user for the /content directory.

Steps to apply read permissions:

Access CRXDE Lite: Log into your AEM instance and navigate to CRXDE Lite (http://localhost:4502/crx/de).

Navigate to the /content Directory: In the CRXDE Lite interface, browse to the /content directory.

Set Permissions:

Right-click on the /content directory and select "Permissions".

Add the anonymous user (if not already present).

Grant read permissions to the anonymous user.

Save Changes: Apply the changes and ensure that they are saved correctly.

Test the Configuration: Log out of the AEM instance and test the context-aware configuration as an anonymous user to ensure that the configuration resource can now be retrieved.

By granting read permissions to the anonymous user for the /content directory, you allow access to the necessary configuration resources, resolving the issue.

References:

Adobe Experience Manager Security Permissions

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 aemVersion property specifies the target AEM version for the project. To create a project based on AEM as a Cloud Service SDK, the value should be set to cloud. The sdkVersion property specifies the AEM as a Cloud Service SDK version to use for local development. To use a specific SDK version, the value should be set to the exact version number, such as 2022.5.7575.20220530T152407Z-220401. References: https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/archetype/using.html?lang=en#properties https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/aem-as-a-cloud-service-sdk.html?lang=en#sdk-versions

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

Option C is the AEM dependency that provides APIs for all AEM environments. Option C uses the uber-jar dependency with the provided scope and the classifier set to apis. The uber-jar dependency contains all the public Java APIs that are available in AEM. The provided scope indicates that the dependency is not required for runtime, as it is already provided by the AEM platform. The apis classifier indicates that only the API classes are included in the dependency, not the implementation classes. References: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/aem-project-content-package-structure.html?lang=en#project-dependencies https://helpx.adobe.com/experience-manager/6-4/sites/developing/using/htl/eclipse-setup.html

Option B is a potential fix for the issue. Option B uses the data-sly-attribute block statement to add the href attribute to the anchor tag. The data-sly-attribute statement uses an expression to append “.html” to the item.path value. This way, the link will have the correct extension and will resolve to the corresponding page. References:https://experienceleague.adobe.com/docs/experience-manager-htl/using-htl/htl-block-statements.html?lang=en#data-sly-attribute

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 ui.config project, (/config/…/config.) folder is the location where the OSGi configuration should be created for a runmode-specific configuration for an AEM as a Cloud Service implementation. The ui.config project contains OSGi configurations that are deployed to /apps in the repository. The config. folder specifies the runmode for which the configuration is applicable, such as author or publish. References:https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/deploying/configuring-osgi.html?lang=en#project-structure

A content fragment is a reusable piece of content that can be authored and managed independently from a page. Content fragments are based on structured data models that define the elements and data types of the content. Content fragments can be delivered as JSON using various APIs, such as Assets HTTP API, Content Fragments REST API, or Content Fragments GraphQL API. Content fragments are suitable for creating multi-channel applications that use AEM as a headless CMS. References: https://experienceleague.adobe.com/docs/experience-manager-learn/foundation/headless/introduction-to-headless.html?lang=en https://experienceleague.adobe.com/docs/experience-manager-65/assets/fragments/content-fragments.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 thecached files there. References:https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-configuration.html?lang=en#cache

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.

Creating a heap dump and a thread dump are two steps that should be taken after confirming the problem is related to a memory issue. A heap dump is a snapshot of the memory usage of the Java Virtual Machine (JVM) at a given point in time. A heap dump can be used to identify memory leaks, memory consumption patterns, and objects that occupy large amounts of memory. A thread dump is a snapshot of the state of all threads that are part of the JVM process. A thread dump can be used to identify deadlocks, blocked threads, and CPU-intensive threads. References: https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/memory-analysis.html?lang=en https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/thread-dump-analysis.html?lang=en

Extend the Teaser Component from Core Components

Create style variations to be used in the Style System** Comprehensive Explanation of Correct Answer Only: The Teaser Component from Core Components is a component that allows authors to display a title, description, image and link for a teaser item. The component supports multiple designs and can be extended to add custom features or logic. The Style System allows authors to define style variations for components without requiring code changes or new templates. References: https://experienceleague.adobe.com/docs/experience-manager-core-components/using/components/teaser.html?lang=en https://experienceleague.adobe.com/docs/experience-manager-core-components/using/components/style-system.html?lang=en

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

Option B and Option D are two implementations that will support the HTL snippet. Option B uses the @Model annotation with the adaptables parameter set to Resource.class. This allows the Sling Model to adapt from a resource object and access its properties using the ValueMap interface. Option B also uses the @Inject annotation with the name parameter set to “./text” to inject the value of the text property into the text field. Option D uses the @Model annotation with the defaultInjectionStrategy parameter set to OPTIONAL. This allows the Sling Model to use optional injection for all fields and avoid null pointer exceptions if a property is missing. Option D also uses the @Inject annotation without any parameters to inject the value of the text property into the text field, using the field name as the default property name. References: https://sling.apache.org/documentation/bundles/models.html https://experienceleague.adobe.com/docs/experience-manager-htl/using-htl/htl-block-statements.html?lang=en#use

To design a workflow that collects data from the participant and then determines the reviewer/approver branch to proceed further, the developer should use theDynamic 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.

References:

Adobe Experience Manager Workflow

AEM Dynamic Participant Step