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

When creating a custom query in AEM's JCR (Java Content Repository), the query's performance is highly dependent on the indexing configuration. For the given query that selects all nodes with a 'status' property equal to 'STARTED' from the 'nt:base' node type, the index must be set up correctly:

Option A, "nt:base index rule", is correct. The index rule for 'nt:base' must be added to define which properties of nodes of this type are indexed.

Option D, "status property with propertyIndex = true", is also correct. This index ensures that queries filtering on the 'status' property are executed efficiently. The property index should be set to true, which means that this property is indexed and the query will use this index to filter the results.

Option B is incorrect because setting the property index to false would mean that the property is not indexed, making the query less efficient since the repository would need to scan each node to find matches.

Option C, "nt:base aggregate", is not mandatory. Aggregates are used to include properties of related nodes in the index, but they are not required for a simple property match like the one in the given query.

In Adobe Experience Manager (AEM), a transient workflow is designed for short-lived workflows that do not persist their state information in the repository, which means they are faster and do not leave a footprint in the repository. However, if a Process Step in a transient workflow creates a sling job, it defeats the purpose of the transient workflow because sling jobs are persisted in the repository and could generate error messages in the log files if they are not executed immediately or if there are issues with the job queue. Therefore, to maintain the transient nature of the workflow, Process Steps that create sling jobs should be avoided.

• The Container Step (Option A) is used to group other workflow steps and does not inherently create sling jobs.
• The Goto Step (Option B) is used for branching logic and also does not create sling jobs.

When customizing a core component in AEM, setting thesling:resourceSuperTypeproperty 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 Sling Models, the@DefaultInjectionStrategyannotation is used to specify the strategy for injecting fields into the model. When setting it toDefaultInjectionStrategy.OPTIONAL, it indicates that all injected fields in the Sling Model are optional and the model will not fail to instantiate if a field cannot be injected. This is a class-level annotation that affects the default injection behavior of all fields within the Sling Model.

• Option B is incorrect becauserequiredInjectionStrategyis not a valid annotation property in Sling Models.
• Option C is incorrect becauseinjectionStrategyis not specified at the class level; it is used on the field level with the@Injectannotation.

In AEM, OSGi configurations are typically managed within theui.appsMaven module. This module is responsible for the application code that comprises the components, templates, and OSGi configurations among other things. By placing OSGi configurations within theui.appsmodule, a developer can ensure that these configurations are deployed to the JCR repository and become part of the application package.

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 totrueoverrides the default behavior, enabling the cache to store and serve responses even for requests that contain an authorization header.

In a Maven project, the<version>property is used to specify the version of the project itself. This version can include the version of the AEM project being built if that's the convention used in the project's versioning strategy. It's typically specified in thepom.xmlfile at the root of the project and is inherited by all the modules of the project unless they specify a different version locally in their respectivepom.xmlfiles.

Given the dispatcher configuration snippet provided in the image, we can understand the URL patterns that will be ignored (not cached) by the dispatcher. The configuration under/ignoreUrlParamsshows patterns to match query parameters in the URLs:

• /0001 { /glob "*" /type "deny" } means that by default, all query parameters are ignored (not cached).
• /0002 { /glob "search" /type "allow" } specifically allows caching for URLs with the 'search' parameter.
• /0003 { /glob "order" /type "allow" } specifically allows caching for URLs with the 'order' parameter.

Based on this, let's evaluate the options:

A. /myproduct/myrecipe.html?search=searchparam — This URL will not be cached because the 'search' parameter is allowed, but the actual value 'searchparam' does not match any allow pattern. B. /myproduct/myrecipe.html?search=s&order=asc&brand=ad — This URL will not be cached because although 'search' and 'order' parameters are allowed, the 'brand' parameter is not allowed according to the configuration. C./myproduct/myrecipe.html?brand=mybrand — This URL will be cached because there are no allowed parameters, so the default deny does not apply, and the page can be cached without considering the 'brand' parameter.

Therefore, the page that will be cached on the dispatcher is the one in option C, as it does not contain any of the explicitly allowed query parameters ('search' or 'order'), and all other parameters are ignored by default.

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.

The correct logger to be created for debugging SAML (Security Assertion Markup Language) within AEM (Adobe Experience Manager) is the one pertaining to the Granite platform, which is part of AEM’s internal framework dealing with authentication. The Granite framework provides services that include user, group, and permission management, and is integral to AEM's SAML authentication process. Thus, the loggercom.adobe.granite.auth.samlis the appropriate logger that should be created and configured to capture and display debug logs related to SAML authentication processes.

The recommended approach to use AEM Core Components is by creating proxy components. Proxy components are essentially wrapper components within your own project that reference the core components. This practice allows developers to inherit functionality from the core components while being able to override and extend it as necessary. By using proxy components, developers can ensure that any custom styles and configurations are preserved even when the core components are updated in the future.

In HTL, theformatoption 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. ThepiValuevariable 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.