Adobe AD0-E906 Adobe Workfront for Experience Manager Enhanced Connector Expert Exam Practice Test

Answer : C

When handling high-volume content ingestion in AEM, transient workflows are a key factor for optimizing performance. Transient workflows do not persist workflow data in the JCR repository, which greatly reduces the load on the repository and improves overall performance. Since content ingestion typically involves processing a large number of assets, using transient workflows prevents unnecessary data accumulation in the repository.

Transient workflows are ideal for operations where you don't need to keep historical data about each workflow instance, such as ingestion processes, thereby making the system faster and more efficient.

Option A (using schedulers) is not related to workflow performance, and Option B (allocating more RAM) is a generic solution but not directly tied to optimizing workflow efficiency.

For further guidance, refer to AEM's documentation on workflow optimization and transient workflows.

Answer : B

In this case, the solutions consultant needs to limit the legal team's access to read-only for all content in AEM. Since the legal team will be working in Workfront and accessing AEM via the enhanced connector, the best way to manage their access is to apply Access Control Entries (ACEs) to the wf-workfront-users user group.

ACEs allow you to specify detailed permissions for a group or user in AEM, such as granting read-only access to specific resources or folders within the DAM.

Options A and C would either grant too much access (as in the case of the Everyone user group) or allow contributions, which is beyond the requirement of just reading access.

Refer to AEM Access Control Management documentation to learn more about setting up ACEs and managing permissions.

Answer : C

To search for assets that are expiring within the next week, the most efficient way is to configure the search rail using the Relative Date Predicate. This predicate allows for dynamic filtering based on a relative date range, such as 'next week.'

The Relative Date Predicate automatically adjusts to search for assets within a specific upcoming time frame, such as the expiration date.

Option A and B are more rigid and require specific date or range configurations, which may not be as flexible or user-friendly as the relative date search.

Refer to AEM's Assets Admin Search Rail configuration documentation for more information on predicates and their use in filtering search results.

Answer : B, C

To enable the search of products by SKU number in AEM, two main configurations are required:

Multi Value Property Predicate: By using a Multi Value Property Predicate, users can search for multiple SKU numbers at once. This is crucial if product owners need to query for multiple products simultaneously.

Single Line Text Field for SKU: SKU numbers are typically unique, so adding a Single Line Text field to the image metadata schema for SKU numbers ensures that each image has its own SKU field for accurate identification during searches.

Option D is incorrect because SKUs are usually single, unique identifiers, so a Multi Value Text field isn't necessary for each SKU.

Refer to AEM's documentation on customizing metadata schemas and Assets Admin Search to implement these features.

Answer : A

In AEM, to limit the number of concurrent workflows running at the same time, you need to adjust the Maximum Parallel Jobs setting in the OSGI console. This setting controls how many workflow jobs can be processed simultaneously, and reducing this number will lower the load on the server by limiting the number of workflows that can run concurrently.

This setting can be found under the Day CQ Workflow - Workflow Engine configuration in the OSGI Web Console.

Options B and C refer to specific workflows and threads, but they do not directly address the overall system limit on concurrent workflow executions.

Refer to the AEM documentation on workflow scaling and performance for more information on how to adjust these settings in the OSGI configuration.

Answer : B

In Workfront, the best way to ensure that all documents within a project are shared with a designated team is to share the entire project. By sharing the project, all documents and related assets within that project are automatically made available to the designated team members according to the project's access permissions.

Option C is incorrect because sharing one document does not automatically inherit the same access levels for the other documents. Option A suggests linking documents from AEM, but the question pertains to sharing documents within Workfront itself.

Refer to Workfront's documentation on document sharing for detailed instructions on how to share all project-related assets with teams.

Answer : C

In AEM, for a custom workflow process to be available for selection in the dropdown menu of a process step, the process.name property must be set in the @Component annotation. This property defines the unique name under which the custom workflow process will be registered and visible in the workflow model editor.

Here is an example of how this should be added to the existing code:

@Component(service = WorkflowProcess.class,

property = {'process.label=Custom Workflow Process', 'process.name=customWorkflowProcess'})

process.label: This is the label that appears in the workflow model editor dropdown.

process.name: This is the internal identifier used by AEM to register the workflow process.

Options A and B would define other properties but will not resolve the issue of the custom workflow not appearing in the dropdown. The key property needed here is process.name.

For more details, refer to the AEM documentation on creating custom workflows and annotating components.