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

Answer : B

In this case, the customer wants to define the linked folder structure based on the Workfront Portfolio name, Program name, Project name, and Project Type. The Project Type is a custom form field with specific choices like 'Campaign,' 'Product Launch,' etc.

The correct format to define the folder structure in AEM based on these elements would be:

Portfolio, Program, Name, projectType: This structure will create a hierarchical folder system in AEM where the folders are nested by Portfolio, Program, Project Name, and Project Type (which is pulled from the custom form field).

Option A includes an incorrect syntax with 'DE

,' which is not necessary, and Option C repeats the 'Program' and misorders the fields.

Refer to Workfront Enhanced Connector documentation for further guidance on defining folder structures using custom form fields.

Answer : B

When configuring the Workfront Enhanced Connector in AEM, Workfront users who will use the connector are automatically added to a corresponding AEM user group via the connector. This automatic process ensures that permissions and group assignments are correctly synced between Workfront and AEM without manual intervention.

Option A (using the Import People option in Workfront) refers to importing users into Workfront, not syncing users to AEM. Option C (from the Adobe Admin Console) is related to managing users in the Adobe platform but not specifically for the Enhanced Connector.

Refer to AEM and Workfront Enhanced Connector documentation for more information on user synchronization and group management.

Answer : C

When configuring allowed HTTP request methods for /bin/workfront-tools on the AEM dispatcher, the safest and most appropriate methods to allow are GET, POST, and PUT. These methods cover the basic operations for retrieving data (GET), submitting data (POST), and updating data (PUT), which are typically required for the Enhanced Connector functionality.

GET: Used to retrieve data from the server.

POST: Used to send data to the server.

PUT: Used to update resources on the server.

Options A (DELETE) and B (HEAD, DELETE) are riskier and less commonly needed for this use case, and DELETE should be restricted unless absolutely necessary to prevent unintended deletions.

Refer to Adobe documentation on Dispatcher security for best practices regarding allowed HTTP methods.

Answer : A

To ensure that changes in metadata in Adobe Experience Manager (AEM) are synced back to Workfront for the fields Content Type and Effort, the correct property assignment should map the Workfront custom form fields to the corresponding paths in the AEM JCR repository.

In Option A:

CUSTOM FORMS

is mapped to /jcr:content/metadata/content-type

CUSTOM FORMS

is mapped to /jcr:content/metadata/effort

This configuration ensures that changes made in AEM's content-type and effort metadata properties will be reflected in the respective custom fields in Workfront.

Options B and C use incorrect prefixes (e.g., 'DE:') and would not map the properties correctly for synchronization between Workfront and AEM.

Refer to the Workfront Enhanced Connector documentation for detailed instructions on configuring metadata synchronization between AEM and Workfront.

Answer : A

To implement conditional automatic publishing of assets from Workfront to AEM based on the value of the custom form field, you should:

Check the option 'Automatically publish assets when sent from Workfront': This ensures that the assets will be automatically published to AEM when they are sent from Workfront.

Use the custom form field ('auto_publish_assets'): The system needs to check the value of this custom form field, and if it is set to 'Yes', the assets will be automatically published.

Set the Custom Form Field Value to 'Yes': In the configuration, you'll specify that automatic publishing only occurs when the field value is 'Yes.'

Option B incorrectly refers to 'Workflow' instead of 'Workfront,' and Option C refers to publishing to Brand Portal, which is irrelevant since the customer does not have Brand Portal.

Refer to Workfront for AEM Enhanced Connector documentation for step-by-step guidance on configuring conditional automatic asset publishing.

Answer : B

When adding the required packages for the Enhanced Connector in AEM, they should be added to the Embedded section of the pom.xml for all subprojects. The Embedded section is used to define dependencies that need to be bundled with the AEM project, ensuring that the connector's functionality is included in the deployment.

Option A (Tools) is incorrect because this section is used for development tools, not dependencies. Option C (Servers) refers to server configurations, which is unrelated to package embedding.

Refer to AEM Maven project documentation for more details on embedding packages in the pom.xml file.

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.