AD0-E911 Adobe Workfront Project Manager Certified Professional Questions and Answers

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 .

=========

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​​.

Even if the task shows 100% complete, the Status of the task may still be listed as something other than " Done. " Workfront requires that both the Status and the Percent Complete indicate the task is fully completed before the project can be marked as complete. The Project Owner can filter for tasks that are not marked as " Done " and update their statuses accordingly​​.

The best approach is to generate a Project Report in Workfront, where the report filters the Actual Completion Date for the past year and groups projects by the Sponsor and the month of completion. This allows the sponsor to see exactly which projects they sponsored and when they were completed within the selected timeframe. Grouping by month provides a clear visual of the completion timeline​​.

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 Adobe Workfront, Planned date-based calendar reports are commonly used to visualize project timelines, milestones, and deadlines. They help teams plan and manage workloads based on dates and other time-related factors.

Filters with custom grouping allow users to customize their reports by organizing data in a meaningful way, tailored to specific project or team requirements. Custom groupings enhance the clarity of reports by categorizing data based on selected criteria.

The other options are not correct because Workfront does not support reports that reference multi-select custom fields in a chart format, nor does it allow object names longer than 500 characters​​.

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, when creating a Milestone Step within the Setup area, the Key field is essential as it serves as a unique identifier for each milestone step. It is used to define the specific step within a milestone path that can be associated with tasks in a project. The Status and Description fields are not used for creating the milestone step itself but are more relevant for defining attributes or metadata​​.

In Adobe Workfront, the later system-calculated dates described in the question are Projected Dates . Adobe documentation explains that when a task is first created, Planned, Projected, and Estimated Dates often match. However, Projected Dates can change as work progresses or when schedule conditions change. Adobe specifically states that predecessor delays can cause projected dates for dependent tasks to move, and that a task assignee’s Commit Date can also affect the projected completion date. This matches the scenario where predecessors slipped and the assignee changed a completion commitment. Planned Dates represent the schedule established in the project plan, such as planned start and planned completion, and they do not automatically become the later forecast just because delays occur. Milestone Path Dates relate to milestone tracking, not the general forecasted start and finish of a task. Therefore, the dates that reflect Workfront’s current schedule forecast are Projected Dates , making the correct answer B .

=========

To help the marketing team manage incoming work requests, the most effective reports would focus on the priority and entry date of requests. These reports would allow the team to quickly view what requests are new, in progress, or completed, enabling them to prioritize work accordingly. A report that tracks the " entry date " helps in monitoring how long a request has been waiting, while status-based reports help in identifying the current stage of each request​​.

In Adobe Workfront, the correct wildcard to filter for a project completion date greater than 1 month from the current date is CURRENTDATE + 4w . This wildcard ensures that the filter captures projects scheduled to be completed more than four weeks (or one month) from the current day. Workfront uses such wildcards for dynamic date filtering in reports​​.

In Workfront, tasks are governed by several factors such as task duration, planned hours, and predecessors. In this case, the most likely reason for the task starting later than expected is due to the task ' s duration and planned hours being configured to start on Friday. Even though the predecessor may suggest an earlier start, task settings such as constraints and assigned hours can override the default scheduling. Additionally, task constraints, like " Fixed Start " or " Fixed Finish, " can influence when tasks appear on the schedule​​​.

A Burndown Chart is a visual representation of work remaining versus time in a Scrum iteration. It is unique to agile methodologies like Scrum and is used to track the team ' s progress during a sprint. The chart helps teams visualize how much work is left to complete the sprint goal, making it a critical tool in Scrum​​.

For the art director to only receive email notifications about new proofs or versions, the option " Disabled and Notify recipients about this proof is selected " is the correct choice. This ensures that they are not inundated with notifications about every comment or decision made but are alerted when a new proof or version is uploaded for review.

This approach optimizes the notification settings based on the user ' s request, providing a more focused and less overwhelming email experience, which is often crucial for roles such as creative directors who manage multiple proofs and versions​​.

When uploading reference materials, such as a statement of work, to a project in Adobe Workfront, it should be uploaded as a Document . The " Document " option is appropriate for files intended to serve as reference or informational materials within the project. Documents in Workfront allow users to access, share, and manage files related to tasks, projects, and issues.

The " Proof " option is used for files that need collaborative reviews and feedback, such as marketing materials or design files, where multiple stakeholders need to comment and approve. " Approval " refers to a specific status for documents or tasks requiring formal acknowledgment or acceptance but is not directly tied to the method of uploading files​​.

In Adobe Workfront, to configure tasks according to the requirement of the second task beginning 5 business days after the first task, you need to set the appropriate " Duration " and use " Finish-Start " dependencies. The task ' s duration is key to determining the time allowed for its completion. The " Finish-Start " dependency ensures that the second task begins only after the first is finished, and a lag can be set to introduce a delay, such as 5 business days. Setting a " Finish-Start " dependency with a lag allows for proper scheduling of tasks in sequence without overlapping.

To create a task report that shows the logged-in user all tasks they are assigned to as the primary task owner, USER.ID is the correct wildcard. USER.ID dynamically filters tasks based on the unique identification of the logged-in user, ensuring that only tasks assigned to them are displayed. USER.NAME would not uniquely identify the logged-in user, and USER.roleID is related to roles rather than task assignments​​.

In Workfront, billing rates can be customized for individual projects. To apply a negotiated rate for the Video Editor role within a specific initiative, the project manager can add a new billing rate at the project level. This ensures that the rate is applied only to tasks within the project and does not affect the default system-wide rate for other projects​​.

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 field a user should review to determine whether a task is pending approval is Status . Adobe documentation explains that approval processes for work items, including tasks, can be triggered when an item is moved to a specific status. When a project, task, or issue is pending approval, the approval information appears on the object, and the Status represents the current status of the item that is waiting for approval. Adobe also provides reporting guidance for listing objects with a pending approval process by using the object’s pending status , including task pending status. This confirms that pending approval is communicated through status-related information, not through scheduling or prioritization fields. Critical Path identifies tasks that affect the project timeline and completion date, while Priority indicates relative importance or urgency. Neither field confirms whether an approval process is pending. Therefore, the correct task field to review is A. Status .

=========

In Workfront, the " As Late As Possible " task constraint ensures that tasks are scheduled as close to the project’s end date as possible. This is useful when specific start dates are not necessary, but tasks need to happen near the end of the project timeline. This constraint allows for flexibility while still ensuring that the tasks are completed within the required time frame​​.

In Workfront, when a task owner is unavailable due to time off, they can update the Commit Date to reflect when they are available to work on the task. This prevents delays and ensures the task is completed within a revised timeline. The Commit Date feature is designed to accommodate personal schedules and ensure tasks are accurately tracked without putting the task " At Risk " unnecessarily​​.

In Adobe Workfront, the Progress Status of a project is determined by the project’s progression across its timeline . Adobe documentation states that Workfront determines project Progress Status by evaluating how the project is progressing against its timeline, including comparisons between planned, projected, and estimated completion dates. This is why project Progress Status can appear as values such as On Time , At Risk , Behind , or Late depending on how the current forecast relates to the planned completion date. Critical Path is important because it identifies the sequence of tasks that can affect the project timeline, but it is not the direct field or aspect that determines Progress Status. Milestone Tasks are used to mark important points or phases in a project and can help with milestone reporting, but they also do not determine the overall Progress Status by themselves. Therefore, the correct answer is A. Timeline .

=========

In Workfront, Teams are operational entities that can be assigned to tasks, while Groups are organizational entities that are not assignable to tasks. Additionally, work requests can be routed to both Groups and Teams, depending on how the organization is structured and how the routing is set up​​.