Important Adobe AD0-E906 Exam Questions

Answer: A

Explanation:

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

Explanation:

If the multi-value text field is being populated unexpectedly, the most likely cause is that another field in the metadata schema is mapped to the same property. When multiple fields are mapped to the same property in AEM, any updates to either field will overwrite or modify the property, leading to the unexpected population of values.

This can happen due to schema misconfiguration, where fields unintentionally share the same JCR property path.

Option B is incorrect because the value being required would not cause it to be populated automatically. Option C suggests simultaneous updates by different users, which is unlikely to cause the issue described.

Check the metadata schema configuration to ensure fields are mapped to distinct properties.

Answer: C

Explanation:

Given that the company only occasionally needs to upload documents for approval and does not require advanced features like markup or electronic validation, the Document approvals feature in Workfront is the best choice.

Document approvals allow users to upload documents, assign approvers, and receive approval/rejection responses without the need for advanced proofing or signing functionality.

Options A (Workfront Proof) and B (AdobeSign) provide more advanced capabilities like markup, commenting, and e-signatures, which are unnecessary for this use case.

Refer to Workfront's document management features for more information on basic approval workflows.

Answer: A

Explanation:

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

Explanation:

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.