Adobe AD0-E134 Adobe Experience Manager Developer Exam Exam Practice Test

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

In AEM as a Cloud Service, the OSGi configuration values that can be used include Inline, secret, and environment-specific. These configurations provide flexibility and security for managing environment-specific settings and sensitive information.

Inline Configurations: Inline configurations are directly embedded within the code and are typically used for straightforward configurations.

Secret Configurations: Secret configurations are used to securely store sensitive information, such as passwords and API keys. These configurations are managed separately to ensure security.

Environment-Specific Configurations: Environment-specific configurations allow you to tailor settings for different environments (e.g., development, staging, production) without changing the underlying codebase.

Example of using these configurations:

Inline Configuration:

{

"service.url": "https://api.example.com"

}

 Secret Configuration: Managed through Adobe IMS and not directly embedded in the code.

 Environment-Specific Configuration:

{

"runmode": "dev",

"service.timeout": "30"

}

References:

Managing OSGi Configurations in AEM

Adobe IMS for Secrets Management

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

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

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

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. References:https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-configuration.html?lang=en#filter-rules

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.

AEM as a Cloud Service does not support custom OSGi configuration runmodes, such as “config.author.staging”. Only 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 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

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

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.References: https://sling.apache.org/documentation/development/sling-testing-tools.html https://wcm.io/testing/aem-mock/usage.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

maven-surefire-plugin

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

The recommended path to override /libs standard functionality is /apps. The /apps folder contains application-specific code and configuration that can extend or override the default functionality provided by /libs. The /apps folder has precedence over the /libs folder, meaning that if there are two resources with the same path under both folders, the one under /apps will be used. References: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/aem-project-content-package-structure.html?lang=en#repository-restrictions https://experienceleague.adobe.com/docs/experience-manager-learn/foundation/development/set-up-a-local-aem-development-environment.html?lang=en#the-aem-repository

An AEM Developer should add a front-end dependency in the package.json file. The package.json file is a standard configuration file for managing dependencies in JavaScript projects, including those using npm or Yarn as package managers.

Here’s how to add a front-end dependency:

Open the package.json File: This file is typically located at the root of your project.

Add the Dependency: Add the required front-end dependency under the dependencies or devDependencies section. For example, to add lodash as a dependency:

{

"name": "my-aem-project",

"version": "1.0.0",

"dependencies": {

"lodash": "^4.17.21"

}

}

Install the Dependency: Run the following command to install the new dependency:

npm install

Verify Installation: Ensure that the dependency has been added to the node_modules directory and is listed in the package-lock.json file.

The package.json file is the central place to manage all front-end dependencies, making it easy to track, update, and share dependencies across the development team.

References:

npm Documentation

Managing Dependencies in AEM Projects

These steps ensure that the front-end dependencies are managed efficiently and consistently within the AEM project.

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 thelogic of the custom process step. References: https://developer.adobe.com/experience-manager/reference-materials/6-5/javadoc/com/adobe/granite/workflow/exec/WorkflowProcess.html https://experienceleague.adobe.com/docs/experience-manager-learn/forms/adaptive-forms/custom-process-step-aem-workflow.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.

In AEM as a Cloud Service, one notable change that developers should be aware of is the removal of replication agents. Instead of the traditional replication agents used in on-premise or AEM Managed Services environments, AEM as a Cloud Service uses a different mechanism to distribute content.

Key points about this change:

Content Distribution:

In AEM as a Cloud Service, content distribution is managed through automated processes that do not rely on manually configured replication agents.

The cloud infrastructure handles the replication and distribution of content to publish instances.

Publishing Model:

The publishing process is designed to be more seamless and integrated within the cloud environment, leveraging the underlying cloud services for scalability and efficiency.

Developers and administrators do not need to manually manage replication agents, simplifying the content deployment process.

Benefits:

This change reduces the complexity of content distribution in AEM projects.

It ensures higher reliability and performance by leveraging the capabilities of the cloud infrastructure.

References:

AEM as a Cloud Service Documentation

Content Distribution in AEM as a Cloud Service

By understanding this change, developers can effectively manage content distribution in AEM as a Cloud Service and leverage the new mechanisms provided by the cloud platform.

Option C is the correct implementation for the Sling Model. Option C 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 C also uses the @Inject annotation with the name parameter set to “./name” and “./occupations” to inject the values of the name and occupations properties into the name and occupations fields. Option C also uses the @Named annotation with the value parameter set to “byline” to specify the name of the Sling Model that can be used in HTL scripts. 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

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

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

To resolve the domain name by the dispatcher, you should configure it in the vhosts file. The vhosts file is part of the Apache HTTP server configuration and allows you to define how requests for different domain names are handled. This is crucial for setting up virtual hosts, which is essential for resolving domain names and directing them to the appropriate content served by your AEM instance.

Here are the detailed steps to configure domain name resolution in the vhosts file:

Locate the vhosts file: The file is typically located in the conf directory of your Apache HTTP server installation. Common paths are:

/etc/httpd/conf/httpd.conf (on many Linux systems)

/usr/local/apache2/conf/httpd.conf (if installed from source)

Edit the vhosts file: Open the file with a text editor. You might need superuser permissions to edit this file.

Add a VirtualHost directive: Define a new VirtualHost block for your domain. For example:

ServerName www.example.com

ServerAlias example.com

DocumentRoot "/path/to/your/document/root"

# Dispatcher configuration

SetHandler dispatcher-handler

ModMimeUsePathInfo On

AllowOverride None

Options FollowSymLinks

Require all granted

 ServerName specifies the primary domain name.

ServerAlias allows you to specify additional names that should resolve to the same content.

DocumentRoot specifies the directory from which the content should be served.

The section includes the Dispatcher handler configuration.

 Restart Apache: After saving the changes to the vhosts file, restart the Apache server to apply the changes.

sudo systemctl restart httpd

# or

sudo service apache2 restart

References:

Adobe Experience Manager Dispatcher Configuration

Apache HTTP Server Documentation on VirtualHost

Backward Compatibility with the previous AEM Version is out of scope for the Pattern Detector tool, while doing an AEM upgrade. The Pattern Detector tool is a tool that scans an existing AEM code base and identifies patterns that are incompatible with AEM as a Cloud Service or newer versions of AEM on-premise. The tool does not check for backward compatibility with older versions of AEM, as this is not a requirement for upgrading. References: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/moving/cloud-migration/pattern-detector.html?lang=en https://experienceleague.adobe.com/docs/experience-manager-cloud-service/moving/cloud-migration/pattern-detector/patterns-detected.html?lang=en