Adobe Experience Manager Sites Developer Professional AD0-E123 Exam Practice Test

Answer : C

Global project properties in a Maven project are typically defined in the section of the parent pom.xml file. This allows these properties to be shared across all modules of the project, ensuring consistency and easy maintenance of project-wide settings such as versions of dependencies, plugin configurations, and other properties that are common across multiple modules of the project.

Answer : C

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.

Answer : A

When modifications are made to a workflow model in AEM, they must be saved and synchronized with the running instance of AEM. If a user starts a workflow and does not see the recent changes or workflow steps, it could be because the workflow model was not synced in runtime. This means the running instance of AEM is not yet aware of the changes, and as a result, the workflow instance uses the old version of the workflow model.

Option B is incorrect because permissions would not cause the recent changes to be unavailable; they would more likely prevent the user from starting the workflow at all.

Option C is also incorrect because while errors in subsequent steps could potentially stop the workflow from proceeding, they would not prevent new steps from appearing in the workflow instance if they were properly saved and synced.

Answer : A

Experience Fragments in AEM can be exported to Adobe Target, and the default format for this export is HTML. When Experience Fragments are exported to Adobe Target, they are typically used for personalization and A/B testing. HTML is the format that is readily usable within Adobe Target to create variations of a page or a component for these testing purposes.

XML (Option B) and JSON (Option C) are not the default formats for exporting Experience Fragments to Adobe Target. While they can represent structured data, for the purposes of visual personalization in Adobe Target, the HTML format is used because it can directly represent the markup required for the content to be rendered in a browser.

Answer : A

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.

Answer : 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.

Answer : 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.