AD0-E906 Exam Questions Tutorials

In AEM, to limit the number of concurrent workflows running at the same time, you need to adjust theMaximum Parallel Jobssetting in the OSGI console. This setting controls how many workflow jobs can be processed simultaneously, and reducing this number will lower the load on the server by limiting the number of workflows that can run concurrently.

This setting can be found under theDay CQ Workflow - Workflow Engineconfiguration in the OSGI Web Console.

Options B and C refer to specific workflows and threads, but they do not directly address the overall system limit on concurrent workflow executions.

Refer to theAEM documentation on workflow scaling and performancefor more information on how to adjust these settings in the OSGI configuration.

For a multi-faceted holiday promotion involving several teams and unique workflows, the best way to track the associated assets is to:

Establish the holiday promotion as a Program: This allows all related projects, each corresponding to a specific marketing platform (e.g., social media, email), to be grouped under a single program for easy tracking.

Associate each project with the Program: This ensures that all related assets and workflows are linked to the holiday promotion and can be reported on collectively.

Create a Project-level Custom Form Field: This will capture specific details related to the holiday promotion for each project, allowing for more tailored reporting.

Create a Project Report filtered to the holiday promotion: This report will enable leadership and stakeholders to track the progress of all assets related to the promotion and ensure on-time delivery.

Option A involves creating a Program for each platform, which adds unnecessary complexity. Option B is similar but lacks the specific tracking of custom fields at the project level.

Refer toWorkfront’s documentation on managing Programs and custom formsfor details on setting up and reporting on large campaigns.

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 aTypeahead fieldwith theUser 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 acalculated fieldis not required, andcheckboxesdo not allow selection from a list of user names.

For further reference, consult theCustom FieldsandTypeahead Fieldssections in Workfront’s documentation, which outline how to configure these fields to enable user selection from the organization’s resource pool.

TheAuthorpermission role is necessary for the design team members who need toedit the proofsbefore they are sent for review by legal and financial teams. This role allows them to make changes directly to the proof and upload new versions, which is essential for their work in this multi-stage automated workflow.

Author role: Grants permission to edit and manage the proof, which includes uploading new versions and making changes to the existing proof content.

Options B (Reviewer) and C (Approver) are more restrictive roles that do not allow for editing proofs.

Refer toWorkfront Proofing roles and permissions documentationfor more information on the different proof roles.