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

Answer : A, B

When configuring metadata mapping between Adobe Workfront custom form fields and Adobe Experience Manager metadata properties, you can use Issue and Document custom forms to define these mappings. These types of forms are commonly used for tracking and managing work items and documents, both of which need to have their metadata synchronized between the two systems.

Issue custom forms: Used for tracking work requests, such as issues or tasks.

Document custom forms: Specifically used for managing metadata related to documents, which can be mapped directly to AEM assets.

Options C (Portfolio) and D (Program) are not typically used for metadata mapping related to assets or documents.

Refer to Workfront Enhanced Connector documentation for more information on mapping custom forms to AEM metadata properties.

Answer : A

In this scenario, the workflow launcher is configured to trigger a workflow for assets in the path /content/dam/projects/en/designs. However, to ensure that the workflow only triggers for image assets, the condition must be updated to filter the relevant asset types. The condition should be modified to dc:format==image/*, which ensures that only assets with an image format trigger the workflow.

Condition 'dc

==image/*': This filters assets based on their format (MIME type), ensuring that the workflow is only triggered for images, which matches the use case of working with assets such as JPGs or PNGs.

Option B suggests modifying the path, but the existing path (/content/dam/projects/en/designs) is correct for the project structure. Option C suggests changing the node type to nt:file, which is incorrect since the node type for assets in AEM is typically dam:Asset.

For more information, refer to AEM documentation on workflow launchers and DAM metadata properties.

Answer : A, D

There are two possible reasons for receiving the 'Unable to edit properties' error when trying to save metadata properties in AEM:

Insufficient Modify Permission: The user needs to have Modify permissions for the folder or assets within the folder to be able to edit the metadata. Without this permission, changes to metadata cannot be saved.

Invalid Metadata Path: If a metadata property in the schema is mapped to an invalid JCR path, AEM will not be able to save the changes. The system requires valid paths in the JCR to store metadata properties correctly, and any invalid path will result in an error.

Option B, involving asset locking, would prevent editing altogether rather than giving an error during property saving. Option C, mapping two properties to the same path, would result in overwriting issues rather than an error about saving properties.

For more details, refer to AEM's Metadata Schema documentation and permissions management.

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

To upload a new version of a document and ensure it is available in AEM Assets, the user must select the New Version option in Workfront. This triggers the version control process where the updated file can be uploaded.

By choosing the Experience Manager integration after selecting New Version, the system ensures that the latest version of the document is sent to AEM Assets, where it will replace the previous version without losing version history.

This workflow supports maintaining version control between Workfront and AEM, ensuring that the most current version of the asset is always available in both systems.

Refer to the Workfront-AEM Enhanced Connector Guide for further details on version control and document updates between Workfront and AEM.

Answer : B

When metadata mappings between Adobe Workfront and AEM are configured, the process of sending a document along with its metadata from Workfront to Adobe Experience Manager (AEM) Assets is streamlined. The user selects the document in Workfront, clicks 'Send to,' and chooses the Experience Manager integration.

The metadata fields that have been mapped are automatically synchronized along with the document. There is no need for manual selection of metadata at this stage, as the integration ensures that all configured mappings are applied.

This functionality is part of the enhanced connector, which simplifies the workflow between Workfront and AEM Assets by automating the synchronization of mapped metadata fields during the document transfer.

For more details, refer to Adobe's documentation on Workfront for Experience Manager Enhanced Connector, which outlines how automatic metadata synchronization works during document transfers.