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

Answer : B

To synchronize comments on linked documents from Adobe Workfront to Adobe Experience Manager, you need to enable Workfront Event Subscriptions in the enhanced connector configuration properties. Event Subscriptions allow AEM to track changes and updates from Workfront, including comment synchronization.

Workfront Event Subscriptions ensure that comments made in Workfront on linked documents are automatically synced to AEM.

Option A incorrectly references the Advanced tab, and Option C incorrectly states 'Unable' instead of 'Enable' Comment Sync.

Refer to AEM Enhanced Connector documentation on Event Subscriptions for step-by-step configuration.

Answer : C

The features requested by the customer, such as automatic folder creation, synchronization of Workfront document custom form values to AEM asset metadata, and automatic publication of assets to Brand Portal upon project completion, rely on Event Subscriptions in the enhanced connector configuration.

Event Subscriptions are triggered when certain events occur, such as project completion or updates to custom form values, ensuring that the correct actions (like folder creation or asset publication) happen automatically.

Option A (Workflows) would be used for content approval processes but not for these specific automatic actions. Option B (Webhooks) can handle external notifications but is not directly relevant for these tasks within AEM and Workfront.

For more information, refer to AEM Enhanced Connector documentation on Event Subscriptions and their use in automating processes.

Answer : A

The Author permission role is necessary for the design team members who need to edit the proofs before they are sent for review by legal and financial teams. This role allows them to make changes directly to the proof and upload new versions, which is essential for their work in this multi-stage automated workflow.

Author role: Grants permission to edit and manage the proof, which includes uploading new versions and making changes to the existing proof content.

Options B (Reviewer) and C (Approver) are more restrictive roles that do not allow for editing proofs.

Refer to Workfront Proofing roles and permissions documentation for more information on the different proof roles.

Answer : C

In this case, since the user is reviewing a legal document where all changes are related to written copy, the most efficient way to highlight and provide comments is by using the Text Select tool. This tool allows the user to select specific text in the document and attach comments directly related to the text, making it easier for others to understand the context of the feedback.

The Text Select tool is specifically designed for making text-based comments, which is ideal for written copy changes.

Options A (Freehand tool) and B (Box tool) are better suited for graphical annotations or drawing attention to areas of images, not text-specific feedback.

For more details, refer to Workfront Proofing documentation on proofing tools and their use cases.

Answer : B

In AEM, when you need to manage access control (ACL) permissions, including setting specific permissions (like WRITE) for a service user on child nodes without affecting the parent node, the Permission Console is the appropriate tool.

The Permission Console allows you to set fine-grained permissions at both node and subnode levels, which is crucial for scenarios where access needs to be applied only to children nodes, not the parent node itself.

Option A (User Management Console) is used for managing user details, and Option C (Group Management Console) manages group settings, but neither of these are used for setting node-level permissions.

Refer to AEM's User and Group Access Management documentation for more information on using the Permission Console to manage ACLs effectively.

Answer : A

The requirement is to deploy the com.myCompany.ui.content package specifically to the AEM Cloud Service author environment. The key here is ensuring that the package is targeted correctly to the author instance, without affecting other environments.

Option A uses the following target:

<target>/apps/my-company-packages/content/install.author</target>

The use of install.author ensures that the package will only be installed on the author environment of AEM as a Cloud Service, meeting the developer's requirement. This is a common approach in AEM Cloud Service projects, where you differentiate between environments using the appropriate subfolder (in this case, author).

Option B (author.install) and Option D are similar but incorrect because they are not standard for specifying the exact environment, while Option C (install/) is too generic and could apply to both author and publish environments.

Refer to the AEM Cloud Service documentation on deployment and package management for more details on targeting specific environments such as author during content deployment.

Answer : B

In this scenario, the user is managing a marketing campaign in Workfront and wants to use an existing asset from AEM Assets. Since the enhanced connector is already installed and configured, the user can go to the Documents area within the Workfront project, click Add new, and then select the Experience Manager integration.

This integration allows the user to browse assets stored in AEM and select the required asset, which will be linked to the Workfront project without the need to download and re-upload the file.

This seamless integration between Workfront and AEM Assets enhances workflow efficiency by enabling users to directly access and use assets from AEM within their Workfront environment.

For more information, refer to the documentation on Workfront and AEM Asset Integration, which covers the process of selecting and using AEM-stored assets within Workfront.