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

Answer : C, D

To ensure proper functioning of the Enhanced Connector between AEM and Workfront, it is critical that the firewall allows traffic for Event Subscriptions and Webhooks:

Event Subscriptions: These are necessary for synchronizing events between Workfront and AEM, such as when assets are modified or when metadata is updated.

Webhooks: Webhooks enable real-time data exchange and notifications between the two systems, allowing instant updates to flow between Workfront and AEM.

Option A (Experience Manager Workflows) is relevant within AEM but not directly tied to firewall configuration for the connector. Option B (Single Sign-On) is a security feature but not specifically tied to the Enhanced Connector's data synchronization processes.

Refer to the Workfront Enhanced Connector documentation for details on the processes that rely on Event Subscriptions and Webhooks.

Answer : A

The best practice for managing metadata in this case is to:

Create a document custom form: This form will capture the essential metadata details for the asset, such as title, description, and other key attributes, ensuring that the metadata is structured and managed correctly from the start.

Map the custom form fields along with project details: By mapping this information from Workfront to AEM, the metadata is automatically synchronized, reducing manual work and ensuring consistency across both systems.

Option B, which involves not creating custom forms, would likely lead to the same lack of metadata management as before. Option C suggests creating a project custom form, which is less relevant for capturing specific asset metadata.

Refer to Adobe Workfront Enhanced Connector documentation for more on best practices around metadata management and custom forms.

Answer : C

In this scenario, the calculated field Allowable Days and the Required Delivery Date need to display on the project. To achieve this:

Allowable Days: This is a calculated field, so it should be set up as a calculated field in the project custom form, which references the difference between the Request Entry Date and the Required Delivery Date.

Required Delivery Date: This is a static field and should be displayed as a text field to ensure that the original requested delivery date is retained.

Option B is incorrect because both fields do not need to be calculated. The Required Delivery Date is already a static value and doesn't require calculation.

For more information, refer to the Workfront documentation on setting up calculated fields and text fields in custom forms.

Answer : A

The javax.jcr.PathNotFoundException in this case indicates that the path to the asset /content/dam/projectA/asset.jpg cannot be found. The most likely cause is that the asset does not exist at the specified location, and thus the AssetManager is unable to copy it.

PathNotFoundException: This exception is thrown when the repository path (in this case, the asset path) is not found in the JCR repository, meaning that the asset does not exist or the path is incorrect.

Other possibilities like permissions issues (Option C) would typically result in a PermissionDeniedException, and Option B is incorrect because the issue specifically pertains to the asset path, not the parent folder.

To resolve this, the developer should check if the asset exists at the specified path or if the path is misspelled. For more information, refer to the AEM documentation on handling assets and JCR path exceptions.

Answer : A

To configure the Enhanced Connector in AEM, including features like automatic project-linked folder creation, comment syncing, and automatic publishing of assets, you should navigate to:

Tools > Workfront Tools > Workfront Tools Configuration: This is where you can access and configure the connector settings within AEM. From there, selecting the configuration and choosing Properties in the action bar allows you to adjust the required settings.

Options B and C reference incorrect paths (Cloud Services and Assets), which are not used for the Enhanced Connector configuration.

Refer to AEM's Enhanced Connector documentation for step-by-step instructions on accessing and configuring the connector.

Answer : B

To include the mountain assets in the search results for 'hiking' and ensure they show up at the top of the search, the best approach is to assign the 'hiking' tag to these assets. By using tags, you can enhance the discoverability of the assets without modifying their titles or descriptions. Tags are indexed and have a strong influence on search results in AEM.

Tagging assets is an efficient way to associate them with relevant topics or keywords, such as 'hiking,' which would improve their ranking in search results.

Option A suggests using 'search boosting,' which does not exist in AEM's metadata editor. Option C involves adding 'hiking' to the content and status fields, which isn't the best way to influence search ranking and could clutter the metadata.

Refer to AEM documentation on metadata tagging and search optimization for more details.

Answer : C

The issue of the custom field not displaying correctly on a component is likely because the namespace 'myProject' is not registered in AEM. AEM requires that custom namespaces be registered before they can be used for storing metadata properties. Without registering the myProject namespace, the system cannot properly recognize the custom property, leading to issues displaying the value.

Namespace registration: Custom namespaces like myProject need to be defined in AEM before they can be used to store properties.

Option A is incorrect because the text field should accept special characters, and Option B is incorrect unless there is already a conflicting property name, which is not indicated in this scenario.

Refer to AEM documentation on namespace registration for steps on how to register a custom namespace in AEM.