Master Adobe AEM Sites Developer Pro AD0-E123: Your Career Catalyst

Correct : A, D

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.

Correct : C

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.

Correct : A, B

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.

Correct : C

When working with custom workflow steps in AEM, metadata associated with the workflow session can be programmatically accessed and manipulated. The MetaDataMap object serves as a container for this data. The correct way to access and modify this metadata in Java would be:

Option C, MetaDataMap wfd = WorkItem.getWorkflow().getWorkflowData().getMetaDataMap(); wfd.put('mykey', 'My Step Value'); This snippet correctly retrieves the MetaDataMap from the WorkflowData of the current Workflow session. It then uses the put method to store a new key-value pair, where 'mykey' is the key and 'My Step Value' is the value to be saved.

Options A and B do not properly chain the method calls to access the MetaDataMap associated with the current workflow session and are therefore incorrect.

Correct : A, D

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.