Adobe AD0-E134 Exam Practice Test Instant Access

Question 1

An AEM application wants to set up multi-tenancy using Adobe-recommended best practices and bind multiple configurations to it. Which of the following options is recommended?

Aimport org.apache.felix.scr.annotations.Component; @Component(label = 'My configuration', metatype = true, factory= true)

Bimport org.osgi.service.component.annotations.Component; @Component(service = ConfigurationFactory.class)

Cimport org.osgi.service.metatype.annotations.AttributeDefinition;
import org.osgi.service.metatype.annotations.ObjectClassDefinition;
@ObjectClassDefinition(name = 'My configuration')

D@Component(service = ConfigurationFactory.class)
@Designate(ocd = ConfigurationFactorylmpl.Config.class, factory=true)

Answer : D

The @Component(service = ConfigurationFactory.class) @Designate(ocd = ConfigurationFactorylmpl.Config.class,factory=true) option is recommended for creating a multi-tenancy configuration and binding multiple configurations to it. This option uses the OSGi R6 annotations to define a component that provides a service of type ConfigurationFactory and designates a class that contains the configuration properties. The factory=true attribute indicates that multiple configurations can be created for this component. Reference: https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/osgi-configuration-settings.html?lang=en#creating-factory-configurations

Question 2

Which type of Cloud Manager tests are enabled for all Cloud Manager production pipelines and cannot be skipped?

ACode Quality Testing

BExperience Audit Testing

CUl Testing

DFunctional Testing

Answer : A

Code Quality Testing is a type of Cloud Manager tests that are enabled for all Cloud Manager production pipelines and cannot be skipped. Code Quality Testing checks the code quality of the project using SonarQube and reports any issues or vulnerabilities. Code Quality Testing can fail the pipeline if the code quality does not meet the minimum standards defined by Adobe. Reference: 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=en

Question 3

A developer needs to create a new Title component. The requirements are:

1. The layout must be the same as the Title core component

2. The text property must have the page title as prefix (e.g., Page Title - )

3. The component must be reusable

Which approach is recommended?

A1. Create a Proxy Component of Title core component
2. Create a Custom Sling Model that overrides the default behavior
3. Customize the component template
B, 1. Create a custom component from scratch
2. Create a Custom Sling Model for the component that follows the requirement
3. Create a Model Exporter

C1. Create a Proxy Component from Title core component
2. Create a Custom Sling Model that overrides the default behavior

Answer : A

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.

Question 4

Which configuration must be applied to enable re-fetching of cached items based on Cache Headers sent by AEM?

A/autolnvalidate true

B/autolnvalidate '1'

C/enableTTLtrue

D/enableTTL '1'

Answer : D

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. Reference: https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/page-invalidation.html?lang=en#time-based-cache-invalidation

Question 5

In an AEM as a Cloud Service environment, which repository areas are considered as immutable?

A/content and /libs

B/content and /etc

C/apps and /libs

D/apps and /content

Answer : C

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

Question 6

A developer needs to create sling models for two fields name and occupations. The dialog has two fields, name - a single value field, and occupations - a multi value field.

The following code is included in sling models inherited from interface com.adobe.aem.guides.wknd.core.models.Byline