AD0-E134 Online Practice Questions and Answers

Correct Answer: D

Explanation: 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

Correct Answer: C

Explanation: 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.htmlhttps://experienceleague.adob e.com/docs/experience-manager-htl/using-htl/htl-block-statements.html?lang=en#use

Correct Answer: AC

Explanation: Code Quality testing and UI testing are two types of testing that are available OOB in AEM Cloud Manager Pipeline. Code Quality testing checks the code quality of the project using SonarQubeand reports any issues or

vulnerabilities. UI testing checks the functionality and usability of the project using Selenium WebDriver and reports any errors or failures.

References: https://experienceleague.adobe.com/docs/experience-manager- cloud-service/implementing/testing/testing-overview.html?lang=en#testing-types https://experienceleague.adobe.com/docs/experience-manager-cloud- service/

implementing/testing/code-quality-testing.html?lang=enhttps://experienceleague.adobe.com/docs/experience-manager-cloud- service/implementing/testing/ui-testing.html?lang=en

Correct Answer: D

Correct 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. References: https://developer.adobe.com/experience-manager/reference-materials/6- 5/javadoc/com/adobe/granite/workflow/exec/WorkflowProcess.htmlhttps://experienceleagu e.adobe.com/docs/experience-manager-learn/forms/adaptiveforms/custom-process-step- aem-workflow.html?lang=en

Correct Answer: B

Explanation: 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

Correct Answer: B

https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/spa-editor/react/map-components.html?lang=en

Correct Answer: D

Explanation: The configuration in DNS (Domain Name System) should be used to resolve the domain name by dispatcher. The DNS resolves the domain names to the IP address of the web server that hosts the dispatcher. The dispatcher then matches the incoming request URL with the cached files or the AEM publish instances. References:https://experienceleague.adobe.com/docs/experience-manager- dispatcher/using/configuring/dispatcher-domains.html?lang=en#client-requests

Correct Answer: D

Explanation: 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-pluginhttps://github.com/adobe/aemanalysermaven-plugin

Correct Answer: AB

Explanation: 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#propertieshttps://experiencel eague.adobe.com/docs/experience-manager-cloud-service/

implementing/developing/aem- as-a-cloud-service-sdk.html?lang=en#sdk-versions