AD0-E123 Practice Questions

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 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 AEM, when you need to extend a dialog from a core component but want to hide or exclude one

tab or part of the dialog, you can use the sling:hideResource property. This property allows you to

selectively hide resources (like a tab in a dialog) inherited from a super type (the core component) in

your overlay or custom component.

In Adobe Experience Manager (AEM), when dealing with live copies, a content author must be aware

of various factors related to the synchronization of content between the source (blueprint) and the

live copies. Option A is correct because when inheritance is re-enabled on a live copy page,

synchronization with the blueprint page occurs, which may include automatic updates to the live

copy page's content. Option D is also correct because local changes made to a component marked as

a container are protected during rollouts, meaning that these local changes will not be overwritten

by content from the blueprint. The container concept in AEM allows for more granular control over

which parts of the page are updated during synchronization.

For Option B, the term 'paragraph system' seems incorrect. It should likely refer to 'paragraph

systems' as in the ParSys (Paragraph System), a component that allows authors to add components to

a page. There is no automatic restoration of the order of components from the blueprint upon re-

enabling canceled inheritance; instead, components are managed according to the rules set in the

rollout configurations.

Option C is incorrect because the cancel and suspend actions can be applied to individual child

components within a container. When inheritance is canceled for a container, the inheritance status

of child components within that container can be controlled individually.

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 Sling Models, the @DefaultInjectionStrategy annotation is used to specify the strategy for injecting

fields into the model. When setting it to DefaultInjectionStrategy.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 because requiredInjectionStrategy is not a valid annotation property in Sling

Models.

Option C is incorrect because injectionStrategy is not specified at the class level; it is used on the field

level with the @Inject annotation.

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 CQ_JVM_OPTS parameter in an AEM start script is used to set options for the Java Virtual

Machine (JVM). The setting '-agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n'

enables the Java Debug Wire Protocol (JDWP) agent for the JVM, allowing a debugger to attach to it.

The suspend=n flag means the JVM will not suspend at the start but will wait for a debugger to

connect on port 8000. This effectively runs the AEM instance in debug mode, which is useful for

development and troubleshooting.

Option B is incorrect because the suspend=n setting means the JVM does not suspend on start-up.

Option C is incorrect because this parameter is for debug mode, not for specifying the run mode of

the AEM instance.

The "Multi Resource Support" property is used in custom workflow models in AEM to allow a single

workflow instance to handle multiple resources, such as assets or pages. When this property is set to

true, if multiple assets or pages are selected and the workflow is initiated, AEM will start only one

workflow instance instead of individual instances for each item. This is useful for bulk processing of

resources, improving efficiency, and managing workflows better.

Option B, "Multi Resource Enable," is not a standard AEM workflow property.

Option C, "Transient Workflow," refers to workflows that do not persist their data and are not related

to handling multiple resources in a single instance.

Sling Models is an AEM feature that allows developers to map JCR data to Java objects. It is a part of

the Sling framework, which AEM is built on top of. Sling Models facilitate the decoupling of content

from the rendering layer, making it easier to work with data in AEM components. By defining simple

POJOs (Plain Old Java Objects) with annotations, developers can map properties from the JCR (Java

Content Repository) to fields in a Java class, enabling a straightforward and type-safe way to handle

the content. This is especially useful when creating components such as 'Hello World', where

dynamic data needs to be fetched from the JCR and rendered on the page.

HTL and Dialogs (Option A) are used for rendering components and creating editable fields in the

component dialogs, respectively, but do not facilitate data mapping to Java variables.

Client-Side Libraries (Option B) are used to manage client-side resources like JavaScript and CSS but

are not involved in JCR to Java variable mapping.