Free AD0-E911 Practice Test Questions and Answers (2026)

In Adobe Workfront, an approval path dictates the workflow for a work item requiring authorization. When a project is submitted for approval and an approver denies the request, the system is configured to update the project's status to reflect this outcome. The 'Rejected' status is a system-default status specifically designed to indicate that an item has failed to gain the necessary approval and cannot proceed. This status change halts the project's progression and clearly communicates the decision to all stakeholders.

B. Current: This status indicates a project has been approved and is actively in progress. A rejection is the opposite of this outcome.

C. Requested: This is typically the initial status of a project when it is first created or submitted, pending a decision from the approval process.

1. Adobe Workfront Documentation - System project statuses: This document explicitly defines the 'Rejected' status. It states

"Rejected: The project was not approved. You cannot change the status of a project from Rejected to any other status." This confirms 'Rejected' is the terminal status for a denied project.

Source: Adobe Experience League

"System project statuses

" in Workfront > Get Started > Administration and setup > Project preferences.

2. Adobe Workfront Documentation - Create an approval process for work items: This guide explains how approval processes are configured. In the section "Configure a status for an approval

" it details that administrators can define what status an object is set to when it is approved or rejected. The default and logical status for a rejection is 'Rejected'.

Source: Adobe Experience League

"Create an approval process for work items

" in Workfront > Get Started > Administration and setup > Review and approval.

The Project Condition in Adobe Workfront is an automatic indicator of a project's health. For projects in a conceptual or pre-planning stage, where no work has commenced and no progress can be measured, Workfront assigns a default neutral condition. The "Idea" status represents the earliest phase of a potential project, before it is approved or planned. Consequently, Workfront automatically sets the Project Condition for any project with the "Idea" status to “On Time,” as there are no metrics to indicate it is at risk or in trouble.

B. Planning: While projects in "Planning" status also default to "On Time," the "Idea" status represents the most fundamental pre-project stage where this default is applied.

C. On Hold: This status does not default the condition to "On Time." Instead, it preserves the project's last known condition from before it was paused.

1. Adobe Workfront Documentation

"Overview of Project Condition and Condition Type."

Section: "How the Project Condition is updated"

Quote/Paraphrase: The documentation explicitly states

"The Condition of a project with a status of Idea is automatically set to On Time." It also notes that for a status equating with "On Hold

" the condition is not updated automatically but is preserved. This directly supports 'A' as correct and 'C' as incorrect. The same document confirms that "Planning" status also defaults to "On Time."

The scenario describes a potential scheduling conflict that may affect the project's completion date. In project management terminology, a potential, uncertain event that could impact a project is defined as a risk. Adobe Workfront provides specific functionality to log and manage risks. These risks are often documented within the project's Business Case to assess their potential impact on the project's overall objectives and justification. Logging an issue is incorrect as an issue is a problem that is currently happening, not a potential one. Creating a task is for assigning work, not for documenting a risk.

B. Log an issue on the project and explain that the completion date is at risk.

An issue in Workfront represents an unexpected problem or event that has already occurred, whereas a risk is a potential future event.

C. Create a task in the project and set the Planned Completion Date for 2 weeks.

Creating a task is for scheduling and assigning work to be done. This action does not document the risk itself, but might be a response to mitigate it later.

1. Adobe Workfront Documentation

"Create and edit risks on a project": This document defines a risk as "a potential event that can jeopardize the success of your project." It further explains that you can create risks for a project to track these potential events. The process involves navigating to a project

clicking the Risks section

and creating a new risk

which aligns with the action in option A. (See section: "Create a risk").

2. Adobe Workfront Documentation

"Create a Business Case for a project": This source details the components of a project's Business Case in Workfront. It explicitly shows a "Risks" tab as part of the Business Case section

confirming that logging risks is an integral part of defining the project's justification and potential challenges. (See section: "Edit information in the Business Case Summary").

3. Adobe Workfront Documentation

"Create issues": This document clarifies the definition of an issue: "Issues are often entered to report bugs or unexpected problems that arise during the course of a project." This directly contrasts with the definition of a risk

supporting why option B is incorrect. (See the introductory paragraph).

The Planned Start Date in Adobe Workfront is calculated based on a sequence of factors, including task predecessors, task constraints, and resource availability. In this scenario, the predecessor and constraint indicate the task can start on Tuesday. However, the Workfront scheduling engine then checks the schedule of the primary task owner. If the primary owner has time off logged for Tuesday, Wednesday, and Thursday, the system will automatically push the Planned Start Date to the next available working day for that user, which is Friday. This is the most common reason for a planned date to differ from the date suggested by dependencies alone.

B. The team needs to review the task before confirming the start date.

This describes a manual business process, not an automated scheduling behavior within Workfront that would change the Planned Start Date.

C. The task duration and planned hours are set to begin on Friday.

Task duration and planned hours define the length and effort of a task, respectively; they do not have their own start date setting that overrides the task's schedule.

1. Adobe Experience League

"Overview of the Task Planned Start Date": This document outlines the factors that influence the Planned Start Date. It states

"Workfront uses the following items to calculate the Planned Start Date of a task... The schedule of the Primary Assignee of the task

including their time off." This directly supports that the primary owner's time off is a key factor in the calculation.

(Reference: Adobe Experience League > Workfront > Get Started > Understand objects in Adobe Workfront > Understand projects > Project Timelines > Overview of the Task Planned Start Date)

2. Adobe Experience League

"Configure user time off": This article explains how time off impacts scheduling. It clarifies

"When a user is assigned to a task

Adobe Workfront uses the user's schedule to determine the planned dates of the task. If the user has time off scheduled... Workfront schedules the task to start on the next available business day for the user." This confirms the behavior described in the correct answer.

(Reference: Adobe Experience League > Workfront > Administer and set up Workfront > Set up the system > Create and manage schedules > Configure user time off)

A Work Item report in Adobe Workfront is the most appropriate choice because it is the only report type that consolidates both tasks and issues into a single list. The term "assignments" encompasses all work allocated to team members, which includes both planned work (tasks) and unplanned work (issues). Using a Work Item report ensures the project manager can provide a comprehensive overview of every piece of work assigned to everyone on the team, fulfilling the manager's request completely.

A. Task: A Task report is incomplete because it would only show planned work (tasks) and would completely omit any assignments related to issues (unplanned work).

C. Issue: An Issue report is too specific and would only display unplanned work items. It would fail to include the planned tasks that are also part of the team's assignments.

1. Adobe Experience League Documentation - Create a Work Item report: "A Work Item report is a custom report that lists both tasks and issues in the same list. This is the only area in Adobe Workfront where you can display both objects in the same list." This source directly confirms that the Work Item report is the unique tool for viewing all assigned work (tasks and issues) together.

Source: Adobe Workfront Documentation

"Create a Work Item report

" Section: "Overview of a Work Item report."

2. Adobe Experience League Documentation - Reporting elements: This document outlines the various objects you can report on. It distinguishes between Task reports

Issue reports

and the combined Work Item report

clarifying their distinct purposes. A Work Item report is presented as the solution for a unified view of work.

Source: Adobe Workfront Documentation

"Reporting elements: filters

views

and groupings

" Section: "Understand the objects in Adobe Workfront."

In Adobe Workfront, a matrix report is designed to display aggregated or summarized data, not individual row-level details. For a column to appear in the matrix view, it must be configured with a summarization function (e.g., Sum, Count, Average, Min, Max). If a column is added to the report's view but is not set to be summarized, Workfront will not display it in the final matrix output. The project manager's issue stems from failing to apply this necessary aggregation to the column.

B. Update the grouping using text mode: Text mode is an advanced method for editing report elements. The core requirement is to summarize the column, which can be done through the standard user interface without needing text mode.

C. Update the conditional formatting of the column: Conditional formatting alters the visual appearance of data (like color or style) based on specific criteria. It does not control the visibility or inclusion of a column in a matrix report.

1. Adobe Experience League Documentation - Create a matrix report:

Section: "Understand how columns work in a matrix report"

Content: "In a matrix report

any column that you want to display information must be aggregated. If a column is not aggregated

it does not display in the matrix view

although it is still a column in the report. For example

if you want to display the Planned Hours on a project

you must summarize the column by selecting Sum as the aggregator for this column." This directly confirms that summarization is required for a column to be visible.

In Adobe Workfront, the "Assignments" field is specifically designed to display a complete list of all entities assigned to a work item, including all users, job roles, and teams. The "Assigned To" field, in contrast, is used to display only the single Primary Assignee. To view all assignees for a task, the project manager must reference the "Assignments" field in a view, report, or on the task details page.

A. Assigned To: This field displays only the Primary Assignee for the task, not the complete list of all assignees.

C. Assigned: This is not a standard, default field name in Adobe Workfront for listing the individuals assigned to a task.

1. Adobe Experience League Documentation - Overview of the Assignments field on an object:

Section: "Overview of the Assignments field on an object"

Content: "The Assignments field on an object lists the names of all users

job roles

and teams assigned to the object. You can view the Assignments field in a list of objects or in the header of an object." This directly confirms that "Assignments" is the correct field for viewing all assignees.

2. Adobe Experience League Documentation - Assign tasks:

Section: "The Assignments section in the task header"

Content: The documentation illustrates the "Assignments" section in the task details

showing where multiple users

roles

or teams can be added. It also separately describes how to designate one of those as the "Primary Assignee

" which populates the "Assigned To" field

reinforcing the distinction between the two fields.

3. Adobe Experience League Documentation - Glossary of Adobe Workfront terminology:

Term: "Assignment"

Content: Defines an assignment as "The association between a work item and the resource (user

role

or team) that is designated to complete the work." The field that lists these associations is logically named "Assignments."

In Adobe Workfront, task completion can be blocked by specific dependencies and hierarchical rules. A parent task cannot be marked as "Complete" if any of its subtasks are still open; all child tasks must be completed first. Similarly, if the project settings enforce predecessor relationships, a successor task cannot be completed until its predecessor task's status is "Complete." An "In Progress" status for a predecessor does not meet this requirement, thus blocking the completion of the dependent task.

C. The task is a predecessor to another task.

A task's status as a predecessor for a future task does not prevent its own completion; in fact, it must be completed to allow the next task to start.

D. The task is assigned to a job role and not an individual user.

Assigning a task to a job role is a valid configuration for planning and does not prevent a user with appropriate permissions from marking the task as complete.

E. The project is “Active.”

An "Active" project status is the normal, required state for tasks to be worked on and completed. It is an enabler, not a blocker.

1. For option B (Subtasks):

Adobe Experience League

Workfront Documentation. "Create subtasks." Section: "Considerations when creating subtasks." It states

"You cannot complete a parent task until all of its subtasks are complete."

Reference Identifier: Adobe Workfront Documentation > Get started with Workfront > Projects > Create and manage projects > Create subtasks.

2. For option A (Predecessors):

Adobe Experience League

Workfront Documentation. "Set predecessor enforcement." This document explains that when predecessor tasks are enforced

successor tasks cannot be started before the predecessor is completed. By extension

a task that cannot be started (or is in progress) cannot be marked as complete if its predecessor is not yet complete.

Reference Identifier: Adobe Workfront Documentation > Get started with Workfront > Projects > Manage projects > Manage task predecessors > Set predecessor enforcement.

3. For option E (Project Status):

Adobe Experience League

Workfront Documentation. "System project statuses." This document describes the "Active" status as one that allows users to work on the project

which is contrary to it being a blocker.

Reference Identifier: Adobe Workfront Documentation > Set up Workfront > Projects > Create custom statuses and approval processes > System project statuses.

In Adobe Workfront, a Team is a specific collection of users created for the purpose of work assignment. When a task or issue is assigned to a Team, it appears in the work queue for all members of that team. Any member of the team can then self-assign or claim the work item to complete it. This functionality is designed to distribute workload and ensure tasks are addressed without being dependent on a single individual's availability.

B. Group: A Group in Workfront is an administrative construct used to manage user access, permissions, layout templates, and system-wide preferences, not for direct assignment of work items.

C. Project Team: A Project Team consists of all users assigned to a specific project. However, tasks are assigned to individuals or roles within the project team, not to the entire Project Team as a single, assignable entity.

1. Adobe Experience League Documentation - Teams Overview: "A team is a group of users that can be assigned to work items. When a work item is assigned to a team

any member of the team can claim the work item and complete it."

Source: Adobe Workfront Documentation

"Teams overview

" Section: "How teams are used in Workfront."

2. Adobe Experience League Documentation - Assign work to a team: "You can assign a task or an issue to a team when you want to make it available to a group of users and let them decide who on the team should work on it."

Source: Adobe Workfront Documentation

"Assign work to a team."

3. Adobe Experience League Documentation - Groups Overview: "Groups in Adobe Workfront are organizational units that help you manage your users. You can use groups to establish an administrative hierarchy and manage settings such as user access

project preferences

and timesheet profiles."

Source: Adobe Workfront Documentation

"Groups overview."

This combination of elements provides a comprehensive toolkit for monitoring an active project's progress within Adobe Workfront. The Gantt chart offers a visual representation of the project timeline, task dependencies, and completion status. The project Condition is a key qualitative indicator that summarizes the project's overall health (e.g., On Target, At Risk). Metrics, such as Percent Complete, Planned vs. Actual Hours, and cost variance, provide the essential quantitative data needed to measure performance against the project baseline. Together, these three elements allow a project manager to effectively track and report on project progress from multiple perspectives.

B: Risks are potential future problems, not measures of current progress. Planned hours are a baseline, and resource utilization tracks team member workload, not task completion.

C: Project status (e.g., Current, Complete) indicates a lifecycle phase, not granular progress. Updates and Sharing are communication and permission tools, not monitoring instruments.

1. Gantt Chart: Adobe Experience League. (n.d.). Get started with the Gantt Chart. "The Gantt Chart is a visual project timeline that is useful for planning and scheduling your projects

as well as tracking their progress." (Section: "Overview of the Gantt Chart")

2. Project Condition: Adobe Experience League. (n.d.). Overview of Project Condition and Condition Type. "The Condition of a project indicates the current state of the project in relation to its planned progress. Project managers manually update the project Condition to reflect whether the project is on schedule to meet its Planned Completion Date." (Paragraph 1)

3. Metrics (Percent Complete): Adobe Experience League. (n.d.). Project Percent Complete overview. "The Project Percent Complete indicates the progress of a project. Adobe Workfront calculates the Project Percent Complete based on the duration or the planned hours of the parent tasks." (Paragraph 1)

4. Risks vs. Progress: Adobe Experience League. (n.d.). Create and edit risks on a project. "Risks are any potential events that could negatively impact your project's timeline

budget

or scope." (Section: "Overview of project risks") This defines risks as potential future events

distinct from tracking current progress.