AD0-E123 Adobe Experience Manager Sites Developer Professional Questions and Answers

In the dispatcher configuration, to allow the caching of requests with an authorization header, the property /cacheAuthorized "true" must be set. By default, the dispatcher does not cache responses to requests that include authorization headers to prevent private or user-specific data from being incorrectly cached and served to other users. Setting this property to true overrides the default behavior, enabling the cache to store and serve responses even for requests that contain an authorization header.

In HTL, the format option in the data-sly-use or data-sly-test attribute can be used to format values according to a pattern. The pattern '-#.##%' indicates that the number should be formatted as a percentage with up to two decimal places. The piValue variable would be the number to format, and in this example, it would convert -3.14 to -314%. The @ symbol is used to denote the use of an option with the variable in HTL.

Options B and C are incorrect because they do not use the correct syntax for the format option in HTL. The use of @ is to specify options and not part of the variable or pattern itself.

AEM service pack release notes typically include information that helps users understand the changes that the service pack will bring to their AEM instance. These release notes commonly include:

A. Deprecated features - This section informs users about the features that are being deprecated with the current release and guides them on migrating away from deprecated features to the recommended alternatives.

B. Known issues - This section provides information about any issues or bugs that are known at the time of the release, which might not yet be fixed. It often includes workarounds for these issues if they are available.

Option C, "Next service pack release date," is not typically included because release dates are subject to change and are usually communicated through official channels closer to the actual release.

Option D, "Download link to AEM jar," is not included in the release notes but is typically available through the Adobe Software Distribution site or Cloud Manager for AEM as a Cloud Service.

In AEM, Lucene is often used for indexing due to its powerful full-text search capabilities, and it also supports asynchronous indexing. Asynchronous indexing allows the system to handle other tasks while indexing is being processed in the background, which can improve performance and scalability. This is especially useful when multiple properties need to be indexed without impacting the immediate response times of the system. Therefore, when a developer needs to enable the indexing of multiple properties asynchronously, a Lucene index is the most suitable choice.

A Java service, which is a backend Java class that encapsulates some business logic or functionality, should be placed in the core Maven module of an AEM project. This module is intended for the Java code that contains OSGi services, servlets, and other Java backend code. By creating the service in the core module, it can be properly compiled, packaged, and deployed as an OSGi bundle within AEM.

When customizing a core component in AEM, setting the sling:resourceSuperType property in the new component's definition allows it to inherit features from an existing core component. This property points to the resource type of the core component that is being extended or customized. By doing so, the new component inherits the core component's logic and rendering scripts but can be customized further according to project-specific requirements.

Option A, sling:resourceType , is used to define the primary resource type for a component and does not indicate inheritance.

Option B, jcr:title , is used to give a human-readable title to a node in the JCR and is unrelated to component inheritance.

In an AEM Single Page Application (SPA) project, the .model.json endpoint is used to expose the properties of a Sling Model as JSON. This is useful for SPAs that need to access component properties dynamically. The front-end developer should check the URL [homepage-path]/model.json to see the JSON output of the Sling Model for the new component. This endpoint provides a tree of the page content as JSON, which includes the Sling Model's exported properties for components included on the page.

In HTL (HTML Template Language), data-sly-element is used to dynamically set the name of a DOM element. The provided option C correctly demonstrates the use of data-sly-element to replace the element name with the value of the titleLevel property of the model. The context 'unsafe' is specified because changing the element name can be a security risk if the value is not properly sanitized since it could lead to script injection vulnerabilities if used with user-provided data.

Options A and B are incorrect because they don't use the data-sly-element attribute, which is necessary to dynamically change the tag name of the element in HTL.

In an AEM as a Cloud Service environment, the preferred approach to clear dispatcher cache of required resources is to use the Replication API along with a replication flush agent. This method allows for programmatic clearing of the cache and is the standard way of invalidating cached content so that the dispatcher can retrieve fresh content from the publish instance.

Option A, "Enable the explicit cache invalidation feature in cloud manager," is not a standard feature available in Cloud Manager.

Option C, "Create a servlet, which will make an HTTP request to the dispatcher," is not advisable as it bypasses the recommended AEM replication and flushing mechanisms and could lead to inconsistencies.

In the Apache Felix Web Console, which is the OSGi management console of AEM, components are managed under the "Components" tab. The provided OSGi component, a servlet in this case, can be disabled by navigating to the "Components" tab, where all the active components are listed. Once the specific servlet is located, it can be disabled by clicking on the "Disable" action button associated with that component. This does not remove the servlet from the system; it simply stops it from being active.

Option A is incorrect because the "Bundle Resource Provider" tab does not deal with enabling or disabling of components.

Option B is also incorrect because the "Services" tab provides information about services but does not provide a direct way to disable them.

In AEM, the Sightly/HTL scripting language is used to develop robust and secure components. To render content conditionally based on the WCM (Web Content Management) mode, the wcmmode object is used. The correct property to check if the current mode is edit is wcmmode.edit . The HTL syntax for testing a condition is data-sly-test followed by the condition in ${} . The option B correctly uses this syntax to test if the WCM mode is edit, and if so, renders "Hello World".

Option A uses wcm.edit which is not the correct object property.

Option C uses wcmmode editor which is not the correct property and the syntax has a typo (should be data-sly-test ).

To create new content fragments programmatically in AEM, a developer would typically use an API provided by AEM for content fragment operations. Among the options given, FragmentTemplate.createFragment() seems to be the most fitting API method call, as it implies the use of a template to create a fragment. In practice, the Content Fragment Java API provides methods to create and manage content fragments in AEM by interacting with the underlying JCR (Java Content Repository). However, without specific API documentation, I'm relying on provided patterns that align with typical AEM Java API usage.