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, a task's 'Percent Complete' and its 'Status' are distinct fields. A project cannot be set to 'Complete' if any of its tasks have a status that does not equate to a complete state (e.g., 'In Progress', 'New'), even if those tasks show 100% in the 'Percent Complete' field. The system error occurs because the project's completion is gated by the task status, not just the percentage. The Project Owner must identify tasks that are 100% complete but still have an active status and update their status to 'Complete' or an equivalent. Filtering the task list for incomplete tasks is the correct procedure to locate them.

A. While an incomplete approval can prevent a task's status from being updated, the direct cause of the project-level error is the task's status itself, not the pending approval.

B. This option incorrectly focuses on project issues. The question specifically asks how to determine which tasks are incomplete, not which issues are open.

1. Adobe Workfront Documentation

"Update the status of a project": This document outlines the prerequisites for changing a project's status. It explicitly states

"You cannot mark a project Complete if there are incomplete tasks or open issues on the project." This directly supports the error message received by the user and the core problem. (Source: Adobe Experience League

Workfront Documentation

Projects section).

2. Adobe Workfront Documentation

"Overview of Task Status": This article explains the difference between system statuses. It clarifies that statuses like 'New' and 'In Progress' represent incomplete work

whereas the 'Complete' status signifies that the task is finished. This distinction is central to the question

as a task at 100% can still have an 'In Progress' status. (Source: Adobe Experience League

Workfront Documentation

Tasks section).

3. Adobe Workfront Documentation

"Edit tasks": In the section detailing task fields

the documentation describes 'Percent Complete' and 'Status' as separate

editable fields. It notes that setting a task's status to 'Complete' automatically sets the 'Percent Complete' to 100%. However

the reverse is not a default behavior; setting 'Percent Complete' to 100% does not automatically change the status to 'Complete'

which is the root cause of the scenario in the question. (Source: Adobe Experience League

Workfront Documentation

Tasks section).

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 most direct and accurate method to fulfill the request is by using the dedicated Calendars area in Adobe Workfront. This approach allows for the creation of a calendar view by defining the object type (projects), specifying the date field to be displayed (Planned Dates), applying a filter for the specific project manager (Project Owner ID), and setting a single, static color (purple) for all displayed entries. This process aligns perfectly and efficiently with all the user's requirements.

A: This option is incorrect because it states that the color should be set in the filter ("set the Color ID field to purple"). In Workfront, color is a display property configured in the View settings, not a filterable attribute.

C: This option is incorrect for two reasons: you create a report (not a calendar) on the Reports page, and it incorrectly places the color setting within the filter. It also fails to mention applying the calendar view.

1. Adobe Workfront Documentation

"Get started with Calendars": This document outlines the procedure for creating a calendar directly from the Calendars area. It states

"Go to the Main Menu > Calendars... Click New Calendar." It then details the steps for adding items (like projects)

applying filters

and configuring display options

which includes setting the color for calendar entries. This supports the process described in option B.

2. Adobe Workfront Documentation

"Create a calendar report": This guide details how to apply a calendar view to a standard report. In the section "Customize the calendar view

" it explains how to configure event coloring under "Style events by

" where you can select "A single color for all events." This confirms color is a view setting.

3. Adobe Workfront Documentation

"Create or edit a filter in Adobe Workfront": This source provides a comprehensive list and explanation of available filterable fields. There is no "Color ID" field or any similar attribute that would allow a user to filter objects based on a display color

confirming that the method described in options A and C is not possible.

In Adobe Workfront reporting, date-based wildcards are used to create dynamic filters. The wildcard TODAY represents the current date. To filter for a date one month in the future, you append +1m, where m specifically designates a calendar month. Therefore, TODAY + 1m correctly and precisely represents a date exactly one calendar month from the current date, fulfilling the requirement to filter for projects with a planned completion date greater than this value.

A. TODAY + 1bm: This is incorrect because bm stands for "business month," which may differ from a calendar month depending on the system's fiscal calendar configuration. The question specifies a generic "month."

C. CURRENTDATE + 4w: This is incorrect because 4w represents four weeks (28 days). This is not equivalent to a calendar month, which can have 28, 29, 30, or 31 days, making the filter inaccurate.

1. Adobe Experience League - Workfront Documentation. "Wildcard filter variables". In the section "Date-based wildcards

" the documentation explicitly lists m as the modifier for "month" and provides examples of its usage (e.g.

$$TODAY+1m). It also lists w for "week" and bm for "business month

" clarifying the distinction between the options.

Reference Location: Adobe Experience League > Workfront > Reporting > Create and manage reports > Filters > Wildcard filter variables.