AD0-E906 Exam Questions & Answers

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.

When handling high-volume content ingestion in AEM, transient workflows are a key factor for optimizing performance. Transient workflows do not persist workflow data in the JCR repository, which greatly reduces the load on the repository and improves overall performance. Since content ingestion typically involves processing a large number of assets, using transient workflows prevents unnecessary data accumulation in the repository.

Transient workflows are ideal for operations where you don't need to keep historical data about each workflow instance, such as ingestion processes, thereby making the system faster and more efficient.

Option A (using schedulers) is not related to workflow performance, and Option B (allocating more RAM) is a generic solution but not directly tied to optimizing workflow efficiency.

For further guidance, refer to AEM's documentation on workflow optimization and transient workflows.

When a new metadata profile is applied to a folder in AEM, it only affects new assets added to that folder after the profile is applied. Existing assets that were already in the folder or subfolders prior to the profile being assigned will retain the metadata profile that was previously applied.

To update the metadata of existing assets with the new profile, you would need to either manually update the assets or run a script to reapply the metadata profile to those assets.

Option B is incorrect because the profile applies to all assets in the folder, not just direct children. Option C is incorrect because if there were invalid field values, you would likely see an error or warning, rather than a silent failure.

For more details, refer to AEM's documentation on managing and applying metadata profiles.

For a workflow where a task assignee must upload a document, have it reviewed and marked up with annotations, and then have it approved by the director and customer, the best option is to upload the document with a proofing approval workflow attached. Proofing workflows allow for:

Annotations: Reviewers can mark up the document with comments and annotations.

Approvals: Once the document is reviewed, it can go through the necessary approval stages, including the director and customer.

Option A (using approvals under document details) does not allow for the same level of markup and annotation as a proofing workflow. Option C (uploading to a subtask) is not an ideal way to manage the review and approval process with annotations.

Refer to Workfront's proofing documentation for more information on setting up proofing workflows with annotations and approvals.

The requirement is to allow users to select a resource (Creative Manager) from a list of existing users in the Workfront application. The appropriate solution is to use a Typeahead field with the User object type.

Field type - Typeahead: This field allows users to start typing the name of an individual, and the system will auto-suggest matching users from the Workfront database. This is ideal for scenarios where you need to assign a specific role, like a Creative Manager, from a list of existing users.

Object type - User: By using the User object type, the field will link directly to Workfront's user directory, ensuring that the selection is limited to valid, active resources in the system.

This combination of field and object type is the most efficient for assigning roles based on existing users, as it prevents errors and ensures data consistency by utilizing Workfront's internal user directory.

Options B and C are not suitable because a calculated field is not required, and checkboxes do not allow selection from a list of user names.

For further reference, consult the Custom Fields and Typeahead Fields sections in Workfront's documentation, which outline how to configure these fields to enable user selection from the organization's resource pool.