Correct Answer: D

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

Explanation: 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=enhttps://experienceleague.adobe.com/docs/experience-manager- 65/assets/fragments/content-fragments.html?

lang=en

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

Explanation: 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 Experience Cloud 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-responsibilitieshttps://

experienceleague.adobe.com/docs/experience-manager-cloud- service/implementing/using-cloud-manager/cloud-manager-user-roles.html?lang=en

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

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

Correct Answer: B

Explanation: 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=enhttps://experienceleague.adobe.com/docs/experience-manager- cloud-service/moving/cloudmigration/pattern-detector/patterns-detected.html?lang=en

Correct Answer: A

Explanation: 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. Reference: 1 Using Core Components section 2 Create Proxy Component in AEM section 3 AEM- Create Proxy Component section 4 Proxy Components in AEM 6.4 section 5 AEM Proxy Component Pattern and Component Versioning section

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