AD0-E134 Adobe Experience Manager Developer Exam Questions and Answers

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

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

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

The Deployment Manager is a role that can configure or run pipelines in Cloud Manager. The Deployment Manager can create and edit programs and environments, configure pipelines, start and cancel pipeline executions, and approve or reject deployments to production. The Deployment Manager role requires an IMS ID that is associated with the Adobe ExperienceCloud product profile. References: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/using-cloud-manager/adding-users-to-programs-and-environments.html?lang=en#roles-and-responsibilities https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/using-cloud-manager/cloud-manager-user-roles.html?lang=en

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

The inability to run the Best Practice Analyzer (BPA) in AEM is most commonly due to the AEM Developer not having the necessary administrative rights. The Best Practice Analyzer is a tool that requires certain permissions to execute, typically administrative privileges.

Here’s a detailed explanation:

Administrator Rights Requirement: The Best Practice Analyzer tool needs access to various parts of the AEM system, including configuration settings and repository data, which require administrator-level permissions. Without these permissions, the tool cannot run properly.

Permissions Check: Verify that the AEM Developer has admin rights. This can be done by checking the user roles in the AEM User Management console. Ensure that the user is part of the "administrators" group or has equivalent privileges.

Running BPA: Once the correct permissions are in place, the developer can navigate to the Best Practice Analyzer tool in AEM and execute it. The BPA will then analyze the AEM instance for compliance with best practices.

Version Compatibility: Note that while this specific issue is related to permissions, it’s also important to ensure that the BPA tool version is compatible with the AEM version being used. In this case, the BPA supports AEM version 6.4 and above.

Steps to assign admin rights:

Log into AEM: As an existing admin, log into the AEM instance.

Navigate to User Management: Go to Tools > Security > Users.

Add User to Admin Group: Find the user and add them to the "administrators" group.

Save and Log Out: Save the changes and ask the user to log out and log back in to acquire the new permissions.

References:

Adobe Best Practice Analyzer Documentation

AEM User Management Documentation

These steps should resolve the issue and enable the AEM Developer to run the Best Practice Analyzer tool successfully.

The order of resolution for OSGi configurations at runtime in AEM is as follows:

Web Console Configuration:

Changes made through the OSGi Web Console take immediate effect and have the highest precedence. This is because these configurations are considered the most direct way to adjust OSGi settings at runtime.

References:OSGi Configuration in AEM

/apps Configuration:

Configurations in the /apps directory take precedence over those in the /libs directory. This allows custom configurations to override the default configurations provided by AEM.

References:AEM Project Structure

/libs Configuration:

Configurations in the /libs directory are the default configurations provided by AEM. They are overridden by any configurations in the /apps directory.

References:AEM Configuration

By understanding this order, developers can effectively manage and prioritize their OSGi configurations to ensure the desired behavior of their AEM instances.

The developer should add the defaultInjectionStrategy = DefaultInjectionStrategy property to the @Model Class annotation to fix the snippet. The defaultInjectionStrategy property defines how the Sling Model handles missing or null values for the injected fields. By default, the Sling Model uses the REQUIRED injection strategy, which means that all fields must have a non-null value or else an exception is thrown. By setting the defaultInjectionStrategy property to OPTIONAL, the Sling Model allows null values for the injected fields and does not throw an exception. This way, if the page field is null because the resource is not a page, the Sling Model can still work without errors.References: https://sling.apache.org/documentation/bundles/models.html https://sling.apache.org/documentation/bundles/models.html#optional-injection

When multiple configurations for the same PID are applicable, the configuration with the highest number of matching runmodes is applied. This is because the runmodes act as a filter to select the most specific configuration for a given environment. If there is a tie between two or more configurations with the same number of matching runmodes, the one that occurs first in the repository is applied.References:https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/configure-runmodes.html?lang=en#configuring-osgi-settings-per-runmode

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

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.

References:

AEM Project Archetype

AEM Development Best Practices

A proxy component is a site-specific component that inherits from a core component and allows customization of the component name, group, dialog, and behavior. A proxy component can refer to any version of the core component by changing the sling:resourceSuperType property. A custom sling model can be used to implement the logic for adding the page title as prefix to the text property. A component template can be used to define the layout of the component.

The aemanalyser-maven-plugin is a Maven plugin that checks if all the requirements declarations made in OSGi bundles are satisfied by the capabilities declarations of other bundles included in the Maven project. This plugin ensures that the OSGi bundles are consistent and can be resolved at runtime. The plugin also checks for other issues such as API compatibility, package versioning, and bundle start order. References: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/aem-project-content-package-structure.html?lang=en#build-analyzer-maven-plugin https://github.com/adobe/aemanalyser-maven-plugin

To enable JSON export on any component after defining a Sling Model, you need to annotate the Sling Model interface with @Exporter annotation. This annotation is part of the Sling Model Exporter framework which allows Sling Models to be exported in JSON format.

Here is the detailed step-by-step explanation:

Define the Sling Model: Define your Sling Model with the necessary annotations and methods. For example:

@Model(adaptables = Resource.class)

public class MyModel {

@Inject

private String title;

public String getTitle() {

return title;

}

}

Annotate with @Exporter: Annotate the Sling Model class with @Exporter to enable JSON export. The @Exporter annotation configures the model to be exported as JSON.

@Model(adaptables = Resource.class)

@Exporter(name = "jackson", extensions = "json")

public class MyModel {

@Inject

private String title;

public String getTitle() {

return title;

}

}

Access the JSON Output: Once annotated, the JSON representation of the model can be accessed through the .model.json extension. For example, if your component is at /content/mysite/en, you can access the JSON output at:

http://localhost:4502/content/mysite/en.model.json

This approach leverages the Sling Model Exporter framework to seamlessly convert Sling Models to JSON format, making it easy to integrate with front-end frameworks and other systems that consume JSON data.

References:

Adobe Sling Model Exporter

AEM Core Components JSON Export

To create Sling Models that can export data in a human-readable yaml format, the following steps are required:

Create Sling models to export as yaml. Sling models are Java classes that can be used to represent resources in AEM. Sling models can use annotations to define how they can be adapted from a resource and how they can export data in different formats. To export data in yaml format, the Sling model class needs to use the @Model annotation with the resourceType parameter set to the resource type of the resource that the model represents. The Sling model class also needs to implement the org.apache.sling.models.annotations.Exporter annotation with the name parameter set to “jackson” and the extensions parameter set to “yaml”. The Sling model class also needs to use the @JsonProperty annotation on the fields or methods that need to be exported in yaml format.

Configure mime type in Apache Sling MIME Type Service. The Apache Sling MIME Type Service is an OSGi service that maps file extensions to MIME types and vice versa. To enable the yaml format for Sling models, the MIME Type Service needs to be configured with a new entry for the yaml extension and its corresponding MIME type, which is “application/x-yaml”. This can be done by creating an OSGi configuration for the org.apache.sling.commons.mime.internal.MimeTypeServiceImpl service and adding the entry “yaml=application/x-yaml” to the mime.types property. References: https://sling.apache.org/documentation/bundles/models.html https://sling.apache.org/documentation/bundles/mime-type-support-commons-mime.html

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:

org.apache.maven.plugins

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

2.22.2

${project.build.directory}/surefire-reports

html

false

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

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

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.

References:

Adobe Experience Manager - Core Components

Sling Models Documentation