Free AD0-E903 Practice Test

Workfront's reporting capabilities allow for flexible data visualization and organization. Calendar reports are a standard report type that can be configured to display objects based on various date fields, including planned start and completion dates. This provides a time-based visual of schedules and deadlines. Additionally, Workfront reports are highly customizable; users can apply filters to narrow the dataset to specific criteria while simultaneously using groupings, including complex custom groupings created in text mode, to structure and aggregate the filtered data. These two features, filters and groupings, work in conjunction to create powerful, specific reports.

A. A chart report that references a multi-select custom field: Workfront charts cannot be grouped by fields that allow multiple selections, such as a multi-select custom field, because there is no single value to plot for a given record.
D. An object name with more than 500 characters: Workfront has a system-wide character limit of 255 characters for most object names (e.g., Project Name, Task Name). Therefore, an object with a name exceeding 500 characters cannot exist.

1. Correct Option B: Adobe Workfront Documentation, "Create a calendar report." In the section "Configure what displays on the calendar," it details how to select the "Start Date" and "End Date" fields, which can be set to planned dates like "Planned Start Date" and "Planned Completion Date."

2. Correct Option C: Adobe Workfront Documentation, "Create a custom grouping in a report." This article explains how to build custom groupings for reports. These groupings are applied to lists of objects, which can be simultaneously filtered using the report's filter rules. The "Filters" tab and "Groupings" tab are separate but complementary functions in the report builder.

3. Incorrect Option A: Adobe Workfront Documentation, "Add a chart to a report." Under the "Chart limitations" section, the documentation explicitly states, "You cannot group a chart by a field that allows for multiple selections (for example, a multi-select drop-down custom field or the Assignments field)."

4. Incorrect Option D: Adobe Workfront Documentation, "System-wide character limits." This page lists the character limits for various fields. For "Project Name," "Task Name," and "Issue Name," the specified limit is 255 characters.

Using a project template is the best practice for standardizing processes for future projects. By adding the required approval process to the marketing team's project template, you ensure that every new project created from that template automatically inherits the correct approval workflow. This method enforces consistency, eliminates the need for manual setup on each project, and significantly reduces the risk of human error, thereby guaranteeing that the Project Sponsor's review occurs before project closure.

A. A global approval process is available system-wide but does not automatically attach to specific projects. It would still require a manual step or a template to be applied consistently.
B. Creating a single-use approval process on each individual project is inefficient, time-consuming, and highly susceptible to being forgotten, making it the opposite of a reliable best practice.

1. Adobe Workfront Documentation, "Create a project template." This document states, "A project template is a predefined set of tasks and settings that you can use over and over to create projects." It emphasizes that templates are the primary tool for standardizing project creation and ensuring consistent processes are applied.

2. Adobe Workfront Documentation, "Attach an approval process to a Workfront object." In the section "Attach an approval process to a template," the documentation explicitly states: "When you attach an approval process to a template, any object created from that template automatically has the approval process attached." This directly supports the chosen answer as the correct implementation method.

3. Adobe Workfront Documentation, "Create an approval process for a work item." This source distinguishes between single-use and reusable approval processes. It clarifies that single-use approvals are for unique, ad-hoc situations, whereas reusable processes, which can be attached to templates, are intended for standardized, repeatable workflows, making option B an incorrect approach for a recurring requirement.

In Adobe Workfront, the project's 'Condition' reflects its overall health, while the 'Progress Status' measures its timeliness against the planned completion date. Workfront can be configured to automatically update the Condition based on the Progress Status. When a project's Progress Status becomes 'At Risk' (projected to finish after the planned date) or 'Behind' (projected to finish significantly after the planned date), the system automatically sets the project's Condition to 'At Risk'. This serves as an early warning indicator to stakeholders that the project requires attention to prevent further delays.

A. Late: "Late" is a value for the 'Progress Status' field, indicating the project's planned completion date has passed, not a value for the 'Condition' field.
C. In Trouble: The "In Trouble" condition typically represents a more severe state of project health and is usually set manually by a project manager rather than being the default automatic condition for a 'Behind' or 'At Risk' status.

1. Adobe Experience League. (2024). Update the Condition for a project. Adobe Workfront Documentation. Retrieved from https://experienceleague.adobe.com/docs/workfront/using/projects/manage-projects/update-project-condition.html.

Reference Point: The section "How Workfront sets the project Condition automatically" states

"Workfront can automatically set the Condition of a project to At Risk when its Progress Status becomes At Risk or Behind."

2. Adobe Experience League. (2024). Overview of Project Progress Status. Adobe Workfront Documentation. Retrieved from https://experienceleague.adobe.com/docs/workfront/using/projects/manage-projects/project-progress-status.html.

Reference Point: This document defines the different Progress Statuses

including 'At Risk'

'Behind'

and 'Late'

distinguishing them from the project 'Condition'.

3. Adobe Experience League. (2024). Overview of Project Condition and Condition Type. Adobe Workfront Documentation. Retrieved from https://experienceleague.adobe.com/docs/workfront/using/projects/manage-projects/project-condition-and-condition-type.html.

Reference Point: This document defines the default project Conditions as 'On Target'

'At Risk'

and 'In Trouble'

clarifying the purpose of each.

In Adobe Workfront, associating a task with a milestone step can be done directly from the project's task list. The most common methods are using in-line editing by adding the "Milestone" column to the view, which allows for quick, single-task updates. For efficiency when multiple tasks need to be linked to the same milestone step, the bulk-editing functionality is used. A user can select several tasks from the list and assign them to a milestone step in a single action.

B. The Milestone View is a visualization tool used to track the progress of the milestone path; it does not provide functionality to associate tasks with milestone steps.
D. The "Settings" section within a task's details page contains configurations like task constraints and duration type, not the field for associating the task to a milestone step.

1. Adobe Workfront Documentation - Associate tasks with milestones: This document explicitly details the two primary methods.

For In-line Editing (A): Under the section "Associate a task with a milestone in a list

" it states

"You can associate a task with a milestone when editing it in a list of tasks... Add the Milestone column to your task view. Click the Milestone column for the task you want to associate with a milestone

then start typing the name of the milestone."

For Bulk-Editing (C): Under the same section

it describes the bulk edit process: "Select multiple tasks in a task list... Click the Edit icon... In the Edit Tasks box that displays

scroll to the Milestone field and start typing the name of the milestone."

2. Adobe Workfront Documentation - Edit tasks: This document clarifies the different editing areas for a task. The "Milestone" field is located in the "Task Details" section of the Edit Task dialog box

not in the "Settings" section

confirming why option D is incorrect.

3. Adobe Workfront Documentation - Milestone view: This source confirms the purpose of the Milestone View. It states

"The Milestone view provides a simple

easy-to-read

visual representation of the milestone path on your project

" confirming it is for visualization

not for editing task associations

which makes option B incorrect.

In Adobe Workfront, the project's "Condition" is an automatic health indicator based on the progress of its tasks, particularly those on the critical path. A critical path task is one that directly impacts the project's finish date. Although the task is not yet overdue, the lack of progress by the fourth day of a five-day window represents a significant risk to the project timeline. Workfront's system is designed to proactively flag such risks. This scenario is a classic trigger for the system to automatically change the project's condition to "At Risk," alerting the project manager to a potential delay before it becomes critical.

A. The next team member cannot start his task. This describes a potential consequence of the delay (a successor dependency), not the project's overall progress status indicator within Workfront, which is what the question asks for.
B. No impact as the task is not overdue. This is incorrect. Tasks on the critical path have zero float, meaning any delay in their completion directly delays the entire project. The lack of progress is a significant risk and has an immediate impact on the project's health status.

1. Adobe Workfront Documentation, "Overview of the project Condition": This document explicitly states, "The Condition of a project is determined by the progress status of the tasks on the critical path." It defines "At Risk" as the condition when the project is in danger of not meeting its Planned Completion Date. The scenario described directly endangers the timeline. (Adobe Experience League, Workfront for Project Managers section).

2. Adobe Workfront Documentation, "Track progress on the critical path": This guide explains that Workfront highlights tasks on the critical path because their timeliness is essential for on-time project completion. A lack of progress on such a task, as described in the question, would cause the project's Projected Completion Date to slip, triggering a change in the project's Condition. (Adobe Experience League, Workfront for Project Managers section).

3. Adobe Workfront Documentation, "Configure system-wide project preferences": This documentation details how system administrators can define the automatic triggers for condition changes. Default settings typically flag projects as "At Risk" based on deviations between the Planned and Projected Completion Dates, which are directly affected by delays on the critical path. (Adobe Experience League, Workfront for Administrators section).

To generate a report that lists individual issues, the report's primary object must be "Issue." The requirement is to show issues only from projects the user owns. This is achieved by creating an "Issue" report and applying a filter based on a field from the parent object (Project). The correct filter is "Project Owner ID," which can be set to the current user's ID. Starting the process from the main "Reports" page is the standard procedure in Workfront. Grouping the results by "Project Name" logically organizes the list of issues.

A. This is incorrect because it filters by "Issue Owner ID." The request is to filter by the project's owner, not the owner of the individual issue.
B. This is incorrect because a "Project" report lists projects as its primary object. It cannot display a detailed list of individual issues, only aggregated data about them in columns.

1. Adobe Workfront Documentation

"Create a custom report": This guide outlines the initial steps for report creation. It specifies beginning in the Reports area and then selecting the object for the report (in this case

Issue).

Source: Adobe Experience League

Workfront Documentation. Section: "Create a custom report".

2. Adobe Workfront Documentation

"Add a filter to a report": This document explains how to apply filters. When building an Issue report

the filter builder allows you to access fields from related objects. You can select the Project object and then its Owner ID field to filter the issues based on who owns the project they belong to.

Source: Adobe Experience League

Workfront Documentation. Section: "Add a filter to a report"

subsection "Build a filter".

3. Adobe Workfront Documentation

"Create and customize groupings in a report": This resource details how to organize report data. For an Issue report

adding a grouping for the Project Name (accessed via Project:Name) will structure the results as required

listing issues under their respective project headings.

Source: Adobe Experience League

Workfront Documentation. Section: "Create and customize groupings in a report".

This approach correctly addresses all requirements. Creating a Project report is the correct starting point. Adding the 'Actual Cost' column and sorting it in descending order fulfills the request to see the most expensive projects first. Most importantly, adding a prompt for 'Portfolio Name' from the Report Settings is the specific function that allows a user to select a single, specific portfolio each time the report is run. This makes the report reusable for any portfolio as requested by the executive.

B. Grouping and summarizing by SUM would show the total cost for all portfolios, not the individual project costs within a single, selected portfolio as requested.
C. Grouping by Portfolio Name displays all portfolios in the same report, which does not meet the requirement to select and view a single, specific portfolio.

1. Adobe Experience League Documentation - Create a custom report: This document outlines the initial steps for report creation. The scenario starts with creating a new Project report, which is the foundational step. (See section "Create a report").

2. Adobe Experience League Documentation - Add a prompt to a report: This source details how to add prompts, which are essential for user-selectable criteria. The document states, "You can add a prompt to a report to allow people who view the report to specify a filter for the information they see." This directly supports using a prompt for 'Portfolio Name'. (See section "Add a prompt to a report").

3. Adobe Experience League Documentation - Edit report settings: This guide explains how to access the settings to modify a report, including adding prompts. The path described in option A, "From the Reporting Settings dropdown, add a prompt," aligns with the UI described here. (See section "Report Settings area").

4. Adobe Experience League Documentation - Sort information in a list: This document confirms the ability to sort columns in reports. It explains how to apply a descending sort to a column like 'Actual Cost' to list the highest values at the top. (See section "Sort by one column").

The sequence of tasks highlighted in red on the Gantt chart represents the Critical Path. In project management, the Critical Path is the longest sequence of dependent tasks that must be completed on time for the entire project to finish by its deadline. These tasks have zero "float" or "slack," meaning any delay in a task on this path will directly result in a delay of the project's final completion date. Project management software, such as Adobe Workfront, commonly uses red highlighting on the Gantt chart to visually distinguish the tasks that constitute the Critical Path, immediately drawing attention to the activities that are most critical to the project's schedule.

B. Baselines: A baseline is a fixed, saved version of the project schedule used as a benchmark for tracking performance, not a sequence of tasks that drives the timeline.
C. Milestones: A milestone represents a significant point or event in a project's lifecycle and typically has zero duration. It is not the entire path of critical tasks.

1. Adobe Experience League - Workfront Documentation: "The critical path is a sequence of tasks that cannot be delayed without delaying the completion of the entire project. ... In Workfront, tasks on the critical path are outlined in red in a Gantt chart when you view the project in the Gantt chart." (Source: Overview of the Critical Path in Workfront, Section: "How Workfront calculates the Critical Path").

2. Adobe Experience League - Workfront Documentation: "The Gantt Chart is a visual project management tool that illustrates a project schedule. ... It can also display the critical path of the project, dependencies between tasks, and the progress of each task." (Source: Gantt Chart overview, Section: "Gantt Chart overview").

3. MIT OpenCourseWare: In project scheduling, the Critical Path Method (CPM) is used to identify the sequence of activities that determines the project's duration. "The critical path is the longest path through the network... Activities on the critical path have zero slack." (Source: MIT OpenCourseWare, 1.040 Project Management, Fall 2009. Lecture 6: Project Scheduling, Page 11, "Critical Path Method").

A project report is the most appropriate tool for viewing detailed information about individual projects. Grouping this report by portfolio organizes the projects according to strategic initiatives, which is ideal for an executive audience. The columns for project condition (health), project priority (importance), and custom data for business goals directly address the executive team's need for visibility into health, importance, and strategic alignment. This combination provides a comprehensive, strategically-oriented overview for data-driven decision-making, precisely matching the request.

B: Grouping by team provides an operational view, which is less relevant for strategic executive decisions compared to grouping by portfolio. C: This option is incorrect because it provides program health, whereas the executive team specifically requested visibility into the health of individual active projects.

1. Adobe Workfront Documentation, "Create a project report": This guide details how to build reports using the Project object. It confirms that fields like Condition, Priority, and custom data fields can be added as columns, and that reports can be grouped by Portfolio. This supports using a project report to meet the specified requirements. (See section: "Build a project report").

2. Adobe Workfront Documentation, "Portfolios in Adobe Workfront": This document explains that portfolios are used to manage a collection of projects that align with the strategic objectives of an organization. Grouping a project report by portfolio, therefore, directly supports the need for visibility into strategic alignment. (See section: "The portfolio management process").

3. Adobe Workfront Documentation, "Overview of project Condition": This article defines Project Condition as the "overall health of the project." This directly links the project condition field to the executive's requirement for visibility into project "health." (See section: "How project Condition is calculated").

In Adobe Workfront, the "Project Details" section is the specific area where a project manager can find and manage the core financial attributes of a project. This includes the dedicated fields for "Fixed Cost" and "Fixed Revenue." These fields are designed to hold predefined, non-variable amounts that are factored into the project's overall financial calculations, such as Planned Cost and Planned Revenue. While this information may originate from the Business Case during the project's approval phase, its operational location for an active project is within the Project Details.

A. Business Case: The Business Case is used during the project initiation and approval phases to outline planned costs and planned benefits, but the final, operational fixed values are stored on the project object itself.
B. Billing Records: Billing Records are used to track and manage actual, billable time and expenses as they are incurred, not the predetermined fixed financial figures of the project.

1. Adobe Workfront Documentation - Glossary of Adobe Workfront terminology:

Fixed Cost: "A cost associated with a project that is independent of the number of hours worked on the project. The Fixed Cost of a project is specified in the Project Details."

Fixed Revenue: "A fixed amount of money that a project is expected to generate. The Fixed Revenue of a project is specified in the Project Details."

Source: Adobe Experience League. "Glossary of Adobe Workfront terminology". Accessed October 2023.

2. Adobe Workfront Documentation - Project Financials:

The formula for calculating the total Planned Cost of a project is explicitly stated as: Project Planned Cost = SUM(Task Planned Costs) + Project Fixed Cost. This confirms that "Project Fixed Cost" is a distinct field at the project level

found within its details.

Source: Adobe Experience League. "Calculate Planned Cost". Section: "How Workfront calculates project Planned Cost". Accessed October 2023.

3. Adobe Workfront Documentation - Business Case vs. Project Details:

The documentation on creating a Business Case explains that it is a tool for justifying a project

containing information like proposed costs and anticipated benefits. When a project is created from an approved Business Case

this information populates fields on the project

including those in the Project Details section. This establishes the Business Case as the source

but Project Details as the location for the active project's data.

Source: Adobe Experience League. "Create a Business Case for a project". Section: "Understand the Business Case". Accessed October 2023.