Adobe AD0-E134 Online Practice Questions and Exam Preparation

Adobe AD0-E134 Online Questions & Answers

• Question 11:

  Which notable change should the developer be aware of in order to distribute content in AEM as a Cloud Service?

  A. Removal of publish content tree workflow
  B. Removal of replication agents
  C. Removal of tree activation
  D. Removal of touch Ul
  B. Removal of replication agents

• Question 12:

  The OSGi configuration is added to a runmode specific configuration "config.author.staging" in AEM as a Cloud Service. The application fails to read the configuration.

  What is a possible cause of this issue?

  A. The custom OSGi configuration runmode used (i.e., "config.author.staging") is not supported in AEM as a Cloud service.
  B. OSGi configuration runmodes cannot be installed automatically on AEM as a Cloud Service. We need to install them as a package using the Package manager.
  C. AEM as a Cloud service does not support OSGi configuration runmodes.
  D. Only specific OSGi configuration runmodes like "config.author" or "config.publish" are supported in AEM as a Cloud service.
  C. AEM as a Cloud service does not support OSGi configuration runmodes.

  ---

  The correct answer is C: AEM as a Cloud service does not support OSGi configuration runmodes. In AEM as a Cloud service, only the default runmodes (i.e., "config.author" and "config.publish") are supported for OSGi configuration. Runmodes like "config.author.staging" are not supported and cannot be added as a Cloud service. This is because AEM as a Cloud service has specific limitations and configurations that are imposed by the cloud environment itself. The OSGi configuration runmodes are one such limitation, which can only use the default author and publish runmodes.

• Question 13:

  The following anchor tag is not resolving:

  {item.name}

  Upon further inspection the developer notices that the link has no .html appended to the end of the URL

  What could be a potential fix for the issue?

  

  A. Option A
  B. Option B
  C. Option C
  D. Option D
  B. Option B

  ---

  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

• Question 14:

  AEM SPA integration provides various design models. In an application the developer chooses to use AEM as a headless CMS without using the SPA Editor SDK framework.

  What would be an advantage for this design model?

  A. The content author can edit the app using AEM's content authoring experience.
  B. The developer has full control over the app.
  C. The SPA is compatible with the template editor
  D. The developer keeps control over the app by only enabling authoring in restricted areas of the app
  C. The SPA is compatible with the template editor

  ---

  In an application where the developer chooses to use AEM as a headless CMS without using the SPA Editor SDK framework, the advantage would be that the developer keeps control over the app by only enabling authoring in restricted areas of the app. By limiting the use of the SPA Editor SDK, the developer can ensure that content authors do not have access to the entire application code and can only make changes within specific areas or components that have been designated for them. This provides greater security and control over the application while still allowing content authors to make necessary updates and changes to the content. Therefore, the correct answer is D.

• Question 15:

  An AEM application is expected to export a content fragment in JSON format without any customization for a headless implementation.

  What is the recommended approach?

  A. Use AEM Assets HTTP API
  B. Use Core components to export JSON
  C. Use Sling Exporter framework
  A. Use AEM Assets HTTP API

  ---

  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

• Question 16:

  An AEM application must process a high volume of content ingestion on the author server.

  What is a key factor to optimize a design for overall performance gain for implementing workflows?

  A. Use Schedulers to run the workflows only on weekends.
  B. Use Transient workflows.
  C. Allocate more RAM for the content ingestion up front.
  D. Run garbage collection every time content ingestion occurs.
  B. Use Transient workflows.

• Question 17:

  A development team is starting a new AEM project that is going to integrate with the Adobe Commerce platform. The developer needs to create a new AEM project using the Maven command line interface.

  How can the 'mvn -B archetype:generate' command help the developer with the integration between AEM and Adobe Commerce?

  A. Using the property 'commerceModule=AdobeCommerce' can provide a path to an external jar that integrates between the platforms.
  B. Using the property ,aemVersion=cloudl automatically provides a report with integration guidelines.
  C. Using the property 'includeCommerce=y'1 the command will generate specific Commerce Core Components.
  C. Using the property 'includeCommerce=y'1 the command will generate specific Commerce Core Components.

  ---

  The includeCommerce property is a boolean flag that indicates whether to include Commerce Core Components in the project or not. If set to y, the command will generate a commerce module that contains specific Commerce Core Components and their dependencies. These components can be used to integrate AEM with Adobe Commerce platform or other commerce solutions. References: https://experienceleague.adobe.com/docs/experience-manager-corecomponents/using/developing/archetype/using.html?lang=en#propertieshttps://experiencel eague.adobe.com/docs/experience-manager-core- components/using/components/commerce.html?lang=en

• Question 18:

  A customer is having trouble with some search queries and provides the following information:

  The logs show the following warning occurs many times:

  WARN* Traversed 1000 nodes with filter Filter (query=select...)

  The client has more than 100,000 pages stored in their AEM instance

  The client uses a custom page property to help search for pages of a given type

  What should the AEM Developer do to help resolve the client's issue?

  A. Create a custom Oak index for the custom page property.
  B. Set the reindex flag to true for node oak:index/cqPageLicen
  C. Use the Index Manager to validate the cqPageLicence index is enabled.
  A. Create a custom Oak index for the custom page property.

• Question 19:

  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?

  A. import org.apache.felix.scr.annotations.Component; @Component(label = "My configuration", metatype = true, factory= true)
  B. import org.osgi.service.component.annotations.Component; @Component(service = ConfigurationFactory.class)
  C. import 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)
  D. @Component(service = ConfigurationFactory.class) @Designate(ocd = ConfigurationFactorylmpl.Config.class, factory=true)

  ---

  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. References:https://experienceleague.adobe.com/docs/experience-manager- 65/deploying/configuring/osgi-configuration-settings.html?lang=en#creating-factory- configurations

• Question 20:

  An AEM Developer needs to create a new component to help support a new product launch.

  The client is on AEM 6.5 on-premise with the latest version of WCM Core Components The component must include text, image, and a link The component must support multiple designs

  Which process should the AEM Developer use to support the launch?

  A. 1. Extend the Teaser Component from Core Components 2. Create style variations to be used in the Style System
  B. 1. Create a new component by extending the Text Component from Core Components 2. Add dialog properties and modify HTL to support images
  C. 1. Extend the Text Component from Core Components 2. Enable image manipulations for the Text Component via policy
  D. 1. Create a new Image with Text component that exposes the Core Components authoring dialogs for those components 2. Add a policy to define which designs are used
  A. 1. Extend the Teaser Component from Core Components 2. Create style variations to be used in the Style System

  ---

  Extend the Teaser Component from Core Components Create style variations to be used in the Style System** Comprehensiveof Correct Answer Only: The Teaser Component from Core Components is a component that allows authors to display a title, description, image and link for a teaser item. The component supports multiple designs and can be extended to add custom features or logic. The Style System allows authors to define style variations for components without requiring code changes or new templates. References: https://experienceleague.adobe.com/docs/experience- manager-core-components/using/components/teaser.html?lang=en https://experienceleague.adobe.com/docs/experience-manager-core- components/using/components/ style-system.html?lang=en