AD0-E911 Sample Questions Answers

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, cross-project predecessors allow dependencies between tasks across different projects. To ensure that Task 1 in Project 1 starts only after the final milestone of Project 2, the project manager must configure a cross-project predecessor linking the final milestone in Project 2 to Task 1 in Project 1. This establishes a dependency and aligns the timelines of the two projects​​.

In Adobe Workfront, to avoid sending unnecessary notifications when adjusting timelines, the Recalculate the project timeline option is used. This ensures that the timeline is updated appropriately based on the changes, but it prevents the system from sending notification alerts to the project team. Recalculation helps align task dependencies and timeline adjustments, preventing confusion among team members​​.

Workfront provides multiple ways for team members to track and locate their assigned work. The primary tools include the Workfront Home area, which centralizes all work items assigned to a user, and email notifications that can alert users to new assignments or updates. Additionally, users can view specific tasks in the Project tasks list. Workfront Home is a key component for workers as it consolidates all active assignments and updates in a single view​​.

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

To filter tasks that are incomplete and assigned to a specific user, the correct approach is to create a Task report, then filter by Task Status that is " Not Equal " to Complete. Additionally, the Assignment filter should include the user’s name to ensure only tasks assigned to the specified copywriter are shown​​.

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

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

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

The " Projected Date " in Workfront reflects the most likely completion date of a task based on the task ' s progress and any predecessors. Unlike the " Planned Date, " which is set manually, the Projected Date automatically updates as task progress changes, giving a real-time estimate of task completion​​.

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

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

In Adobe Workfront, the correct action is to set the task constraint to Fixed Dates . Adobe’s documentation explains that task constraints control when tasks can start or finish in a project plan. Depending on the constraint selected, a project manager may need to specify a planned start date, a planned completion date, or both dates. The Fixed Dates constraint is specifically used when a task must occur between exact dates, because Workfront requires both the Planned Start Date and Planned Completion Date when this constraint is selected. Adobe also states that when Fixed Dates is used, the task duration is calculated from the difference between those two planned dates. A predecessor only controls dependency order and does not guarantee September 10 through September 17. Setting the duration to one week defines only length, not the exact calendar dates. Therefore, to force the task to take place from September 10 through September 17, the correct answer is A. Set the Task Constraint to Fixed Dates .

In Adobe Workfront, and in general project management, the Critical Path refers to the sequence of tasks that directly impacts the project’s overall timeline. Tasks on the critical path are marked in red on a Gantt chart to indicate that any delay or change to these tasks will affect the entire project ' s completion date. These tasks are essential for maintaining the project schedule and ensuring timely delivery. Baselines are used for comparison against the current progress, and Milestones mark significant checkpoints but do not necessarily affect the project timeline if they are delayed​​.

Top of Form

Bottom of Form

In Adobe Workfront, the methodology that matches a traditional, sequential project approach is Waterfall . Adobe Workfront learning content describes traditional or waterfall methodology as a linear process where teams plan the final product and then move through the steps or phases required to deliver it. This is different from Scrum, where teams work from a backlog, plan iterations or sprints, and deliver work in smaller increments. It is also different from Kanban, which uses a board-based flow of work items through statuses rather than strict sequential project phases. Adobe Workfront documentation also distinguishes team types as Scrum Team , Kanban Team , and Waterfall Team , showing that Waterfall is recognized as a Workfront team/work management approach. Because the question describes each phase being completed before the next begins, that aligns directly with the Waterfall model’s structured, sequential planning style. Therefore, the correct answer is C. Waterfall .

=========

Milestones in Adobe Workfront allow project managers to mark significant phases in a project. There are two primary methods for associating milestone steps to tasks:

In-line editing a task list on a project : This method allows you to quickly assign milestones while editing the task list. It ' s a convenient option when working directly within a project ' s task list, ensuring you can associate tasks with milestone steps in a streamlined way without navigating away from the list view.

From the Milestone View in the Projects area : The Milestone View is specifically designed to help manage milestones. It allows you to view and organize milestones and their associated tasks in one place, making it easy to connect tasks to milestones without manually editing individual tasks.

These methods are integral for tracking progress and ensuring that tasks align with the significant steps of a project​​.

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 .

=========

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

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

For executive-level reporting, a program report grouped by department provides a holistic view of ongoing initiatives. This includes the health of programs, urgency, and alignment with business goals. This type of report is essential for leadership teams to assess overall performance and make informed decisions that align with the company’s strategic objectives​​.

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

The most comprehensive approach is to create two separate reports—one for tasks and one for issues —with filters set for " Pending Approval. " Grouping the results by project name ensures that the project manager can see all relevant tasks and issues organized per project. Adding these reports to a dashboard consolidates the information into a single view, providing easy access for tracking pending approvals​​.

In Adobe Workfront, the best report type for showing assignments given to everyone on a team is a Work Item report. Adobe’s Workfront terminology documentation defines a Work Item as either a task or an issue, and states that the Work Item report displays information for both tasks and issues. This is important because team assignments may include planned project tasks as well as issues or requests assigned to team members. A Task report would show task assignments only, while an Issue report would show issue/request assignments only. Neither one provides a combined view of all assigned work. Adobe also provides an example of a combined task and issue report, explaining that a Work Item report can show both tasks and issues accepted by users in one report. Therefore, when a manager wants a report on assignments everyone on the team has been given, the report type that covers all assigned work is B. Work Item .

=========

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 automatic project Condition is controlled by the project’s Condition Type when it is set to Progress Status . Adobe documentation explains that Project Condition is a visual indicator of how a project is progressing and is automatically calculated from the project’s Progress Status, which is based on task progress and project dates. The documentation also states that projects in certain statuses are always marked On Target , regardless of task dates or progress. These statuses include Idea , Requested , Approved , and Rejected . In Workfront terminology, the Progress Status On Time maps to the project Condition On Target . Among the answer choices, only Idea is listed by Adobe as a status that always defaults the automatic project Condition to On Target/On Time behavior. Planning and On Hold do not have this same default rule; On Hold projects can still show as At Risk or In Trouble. Therefore, the correct answer is A. Idea .