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

Answer : A

In Adobe Experience Manager (AEM) as a Cloud Service, deployments are handled through Cloud Manager, and all code, including third-party libraries, must be part of the versioned code repository. To deploy the third-party package provided by the vendor, it needs to be included as part of the AEM project's codebase under the install folder within the repository:

The package should be stored in the <url>file;$(maven.multiModuleProjectDirectory)/install</url> directory.

Once stored, the deployment will be handled through Cloud Manager's deployment pipeline.

This ensures the third-party package is included in the standard deployment process and follows AEMaaCS's immutable infrastructure model, which ensures that changes to environments are made only through deployments using Cloud Manager.

Option B is incorrect because installing a package directly to production via CRX Package Manager is not allowed in AEM as a Cloud Service. Option C would work for self-hosted AEM instances but not for AEMaaCS, where dependencies must be part of the Maven build.

For more information, refer to AEMaaCS deployment best practices and the Cloud Manager documentation.

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 : B

In Workfront, the best way to ensure that all documents within a project are shared with a designated team is to share the entire project. By sharing the project, all documents and related assets within that project are automatically made available to the designated team members according to the project's access permissions.

Option C is incorrect because sharing one document does not automatically inherit the same access levels for the other documents. Option A suggests linking documents from AEM, but the question pertains to sharing documents within Workfront itself.

Refer to Workfront's documentation on document sharing for detailed instructions on how to share all project-related assets with teams.

Answer : A, D

In this scenario, the proofing workflow needs two stages:

Stage 1: This stage routes the proof to the creative director upon proof creation. By selecting 'do not allow this stage to be deleted,' the workflow ensures that the creative director must always review the proof before it is sent to stakeholders. This ensures consistency in the review process and makes sure the creative director is always involved.

Stage 2: This stage activates when all decisions are made on the parent stage (i.e., the creative director's approval). Additionally, since the creative agency only requires one decision from each company, the 'only one decision required' setting is appropriate to speed up the process while ensuring the necessary approvals are gathered.

Option B is incorrect because setting the stage as private may hinder collaboration, and Option C suggests waiting until all decisions are approved, which is not necessary in this scenario.

Refer to Workfront documentation on proofing workflows for details on setting up multi-stage approval processes.

Answer : C

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 : C

In this scenario, the company wants only one department to use a custom metadata schema with a 'verifiedBy' user picker field for image assets. The best approach is to:

Create a new metadata schema for the specific department.

Extend the Coral UI Component to create a custom user picker field, which will allow the department to select users from the list of available users in the system.

Option A suggests modifying the default image metadata schema, which could impact all departments, and Option B involves manually adding users to a dropdown, which is not as efficient as using a user picker field.

Refer to AEM documentation on creating custom metadata schemas and extending Coral UI components for more information.

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.