AD0-E911 Questions and Answers

To create a custom report in Workfront that focuses on issues logged to projects, the project manager needs to create a new Issue report from the Reports page. By applying a filter based on the Project Owner ID and grouping the report by project name, they can track all the issues associated with the projects they own. This approach provides clear visibility into project-related issues​​.

In Adobe Workfront, the Workload Balancer is the correct tool for reviewing resource utilization across multiple projects and making staffing decisions. Adobe documentation explains that the Workload Balancer helps users visualize and manage people’s workloads and demand in one view, at the global, project, or team level. This makes it useful for resource managers who need to see whether team members are overallocated, underutilized, or available for more work across different projects. Adobe’s best-practice guidance also states that the Workload Balancer provides a clear visual mapping of overallocation and underutilization, helping managers determine which team members have bandwidth to complete tasks or issues on time. Scenario Planner is used for high-level planning scenarios and job-skill forecasting, not day-to-day staffing review. Timesheets are used to track and submit time worked, but they do not provide the same forward-looking workload and capacity view. Therefore, the correct answer is C. Workload Balancer .

In Workfront, custom data fields created for projects are typically found within the " Business Case " section, specifically under " Project Info. " This area houses key project information and unique custom fields that are relevant to the project ' s setup. The " Project Details " section is more focused on task-related information and the overall summary of the project​​.

The team lead should create a report in the Reports area to see all hours logged by the home team during the current month. By using filters for Home Team ID and Entry Date , and grouping the results by Project Name , the team lead can view hours logged in a project-based format for the entire home team during the selected time period​​.

In Workfront, if a task that is part of the critical path is delayed, it affects the overall project schedule. Even though the task is not overdue yet, Workfront ' s automated system flags the project as " At Risk " if there is a delay in progress that could impact the project ' s timeline. This " At Risk " condition acts as a warning to project managers and stakeholders that immediate attention is needed​​.

In Adobe Workfront, the Critical Path feature in the Gantt chart helps a project manager understand which tasks can affect the project timeline when delays occur. Adobe documentation explains that Workfront automatically identifies a sequence of tasks that have the potential to impact the project’s timeline and flags those tasks as Critical Path tasks. It also states that any delay in a task on the Critical Path directly impacts the project’s projected completion date because there is no float on the critical path. In the Gantt chart, Critical Path tasks are visually marked, making it easier for the project manager to see which delayed work can affect successor or downstream tasks and the overall schedule. Actual Dates show when work actually started or completed, and % Complete shows progress on a task, but neither is specifically designed to show schedule impact across dependent tasks. Therefore, the correct answer is C. Critical Path .

=========

Adobe Workfront uses Teams as a work-assignment structure for tasks and issues. A task or issue can be assigned to users, job roles, or teams, and Workfront documentation states that assignments can include more than one resource at a time. For issues, Adobe’s documentation specifically says that the assignment field can include users, job roles, or teams, and that multiple resources can be assigned at the same time. For tasks, Adobe similarly explains that tasks can be assigned to users, job roles, or teams, including multiple resources. This makes Team the best answer because it is the Workfront collection designed to receive task or issue assignments and route that work to a set of people. A Group is mainly an administrative structure for organizing users, permissions, preferences, and governance. A Project Team represents users associated with a specific project, but it is not the general collection used to assign a task or issue to multiple people. Therefore, the verified answer is A. Team .

In Workfront, when the projected completion date exceeds the planned completion date and the task is only 50% complete by May 19, it is automatically flagged as " At Risk. " This alerts the project manager that the task is not progressing according to the original plan, potentially causing delays in the project timeline​​.

In Adobe Workfront, the default task constraint for new tasks depends mainly on the project’s schedule mode and the system or group task-start-date preference. Adobe documentation states that As Soon As Possible places the start time of a task as close to the beginning of the project as possible. It is the default constraint when the project uses a schedule mode of Schedule from Start Date and the default start date for a new task is based on the project planned date. This fits the question because the project owner created the project with Schedule Mode set to Start Date. As Late As Possible is normally the default for projects scheduled from Completion Date, not Start Date. Must Start On is a fixed-date constraint used when a task must begin on one specific date, so it is not the standard default for new tasks in a start-date scheduled project. Therefore, the correct answer is A. As Soon As Possible .

=========

In Workfront, approval processes are designed to handle scenarios where certain team members must give formal approval before work can proceed. In this case, the project manager should set up a customized approval process that routes the request through the necessary stakeholders (management team) for their sign-off. This ensures proper governance and tracking​​.

To meet the team ' s request for highlighting new tasks, the most effective solution is to create a View that uses Column Rules . These rules allow for conditional formatting based on task criteria, such as highlighting new tasks in a specific color for easy identification. This approach enhances visibility without requiring the creation of filters or new reports, and it makes it easier for users to see relevant tasks within their existing task lists​​.

The best way to display milestone statuses for projects in a portfolio, while excluding completed projects, is to create a Project Report . By setting filters to exclude completed projects and selecting the appropriate Portfolio Owner ID , the report will display the relevant data. Additionally, enabling the Milestone view in the report ensures that the portfolio owner can easily track project progress and statuses​​.

In Adobe Workfront, when a project is set to " In Progress, " the default project condition is marked as " On Target. " This reflects that the project is actively being worked on and progressing as expected without any significant issues or delays. The " On Target " condition is designed to signal that the project is meeting the planned timelines and performance metrics.

The New and Idea statuses are preliminary stages where active progress or development has not started yet, and thus these statuses would not set the project condition to " On Target. " Instead, they may represent an early phase of consideration or planning, where progress and targets have not been set in motion.

This is an essential feature within Workfront for project management, allowing teams to understand at a glance whether a project is moving as planned or if it requires attention based on predefined thresholds for performance or timing.

For further detailed information, please refer to the Adobe Workfront documentation on project statuses and conditions, which elaborates on how different statuses affect project tracking and reporting​​​.

In Adobe Workfront, risks associated with a project should be logged as part of the project business case. The " Risk " section within the business case allows stakeholders to document any potential threats to the project timeline, scope, or resources. Identifying this risk as a " schedule " risk helps communicate the potential delay to the project stakeholders and allows it to be tracked and mitigated effectively​​.

In Adobe Workfront, the Project Details section is where you can find critical information about the financial aspects of a project, including the fixed revenue and costs. This section includes details such as budgets, financials, and other related data. The Business Case primarily contains the justification or rationale for the project, while Billing Records pertain to invoicing and payment tracking, not necessarily fixed project costs and revenue.

For accurate financial tracking and reporting, the Project Details page is the go-to source for project managers to monitor and update financial data​​.

In Adobe Workfront, Condition is the reportable variable that is determined by the relationship between the Planned , Projected , and Estimated Dates . The Condition field reflects whether a project is On Target , At Risk , or In Trouble based on how its actual progress aligns with the planned schedule and dates. It allows project managers and stakeholders to quickly assess the health of the project​​.

In Workfront, when adjusting user access, it’s important to ensure that Program Manager A only has the necessary level of access to their own program. To rectify the over-access issue, the portfolio manager must share the relevant program with Program Manager A with the correct Manage access and remove their broader Manage access to the portfolio. This restricts their control to only their specific program​​.

In Adobe Workfront, task Duration represents the time frame available for a task to be completed. Adobe documentation states that task duration is the difference between the task’s Planned Start Date and Planned Completion Date , and that planned task dates affect the overall project timeline. When a project is behind schedule and must still meet a requested completion date, reducing task durations is a valid scheduling action because shorter durations can move planned completion dates earlier and compress the project timeline. Applying a Must Start On constraint to all tasks is not the best approach because that constraint forces each task to start on a specified date and can reduce Workfront’s ability to calculate the schedule dynamically. Adjusting all Planned Start Dates to the same day is also inappropriate because it ignores task sequence, predecessors, dependencies, and realistic resource planning. Workfront recommends using durations and predecessor relationships to establish project timelines rather than relying on manually forced constraints. Therefore, the correct action is B. Reduce the durations of the tasks .

=========

The best combination of elements to monitor an active project ' s progress in Adobe Workfront is Gantt chart , project Condition , and Metrics . The Gantt chart provides a visual timeline of task dependencies and durations, the Condition field shows the project’s current health (On Target, At Risk, etc.), and Metrics offer quantitative data to measure progress. Together, these provide a comprehensive view of a project ' s performance​​.

In Adobe Workfront, Planned Dates are the dates that project managers can manually modify. These dates represent the schedule that the project is expected to follow and can be adjusted based on project needs. Estimated and Projected Dates are automatically calculated by the system based on task progress and dependencies, and these cannot be manually modified directly by a project manager. The Projected date is influenced by changes in the actual completion rate of tasks, whereas the Planned Date is the baseline schedule​​.

In Adobe Workfront, the best way to assign tasks across multiple projects without opening each project individually is to use Bulk Assignments in the Workload Balancer. Adobe documentation explains that work can be assigned in the Workload Balancer from the Resourcing area, project area, or team area. It also states that multiple items can be assigned at the same time through the Bulk Assignments option, where users can define rules to assign work to multiple users at once. When accessed from the Resourcing area or a team, the Bulk Assignments panel allows the project manager to filter and select one or more projects and then select tasks for assignment. Drag-and-drop assignment is useful for assigning or reassigning individual work items, but it is not the best method for assigning tasks across projects at scale. Resource Planner focuses more on resource planning and budgeting, not direct bulk task assignment. Therefore, the correct answer is C. Assign work in bulk .

=========

In Adobe Workfront, a matrix report displays report data in a table format based on matrix groupings. When a report uses a matrix grouping, the values that appear in the matrix depend on whether the relevant columns are configured to be summarized. Adobe’s documentation for creating a matrix report states that, in the Columns (View) tab, the user must select the column and use the Summarize this column by setting to choose an available summary option. Adobe specifically notes that if this option is not selected, the information from that column is not displayed correctly in the matrix report. This directly matches the scenario where one of the columns is not showing after the project manager created a matrix grouping. Text mode is not required just to make a standard matrix column appear, and conditional formatting only changes how values are visually styled. Therefore, the project manager forgot to summarize the columns , making the correct answer A .

=========

In Workfront, the connector lines in a Gantt chart represent the predecessor relationships between tasks. These lines show how one task depends on another, indicating the order in which tasks need to be completed. This helps project managers visualize task dependencies and how changes in one task can affect others in the timeline​​.