Adobe AD0-E134 Practice Test - Questions Answers, Page 3

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. Reference: https://experienceleague.adobe.com/docs/experience-manager- 65/assets/extending/assets-api-content-fragments.html?lang=en

The embed property of the cq:ClientLibraryFolder node allows embedding code from a client library into another client library. At runtime, the generated JS and CSS files of the embedding library include the code of the embedded library. This reduces the number of network calls and improves performance. Embedding code is useful for providing access to libraries that are stored in secured areas of the repository. Reference: https://experienceleague.adobe.com/docs/experience-managercloud- service/content/implementing/developing/full-stack/clientlibs.html?lang=en#embed

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/embed-propertyin- client-libs/m-p/426858

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. Reference:

https://experienceleague.adobe.com/docs/experience-manager-corecomponents/ using/developing/data-layer.html?lang=en https://github.com/adobe/adobe-clientdata- layer

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

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 vers a. 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. Reference:

https://sling.apache.org/documentation/bundles/models.html

https://sling.apache.org/documentation/bundles/mime-type-support-commons-mime.html

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

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-manager- 65/developing/introduction/clientlibs.html?lang=en#embedded-files

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. Reference:

https://sling.apache.org/documentation/bundles/models.html

https://sling.apache.org/documentation/bundles/models.html#optional-injection

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. Reference:

https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-wkndtutorial- develop/project-archetype/unit-testing.html?lang=en

https://experienceleague.adobe.com/docs/experience-manager-corecomponents/ using/developing/archetype/using.html?lang=en