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").