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

In Adobe Workfront, when a project ' s progress status is marked as Behind or At Risk , the project condition is set to At Risk . This indicates that the project may not meet its deadline or performance metrics, signaling to the project team and stakeholders that corrective action may be necessary. The " In Trouble " status is reserved for more severe cases, and " Late " is generally used for tasks or projects that have passed their planned completion dates without being finished.

The At Risk status allows proactive intervention to address potential issues before they escalate into bigger problems​​.

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 .

=========

Adobe Workfront, information about the Group and Portfolio assigned to a project is stored in the " Project Details " section. This section contains the overall information regarding a project, such as the Portfolio it belongs to and the Group responsible for it. The " Queue Details " section pertains to request queues, while " Metrics " generally involves the measurement and tracking of key performance indicators but not specific data like Group and Portfolio.

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

To measure a project’s adherence to its original schedule, the most critical elements are Project Baselines , Planned Completion Dates , and Actual Completion Dates . The baseline captures the original planned schedule, while the planned and actual completion dates provide the data to compare the project ' s progress against the initial schedule. This comparison helps project managers identify any deviations from the original plan and assess the project ' s performance​​.

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.

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

=========

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 initial project setting used to identify and report on key tasks is the Milestone Path . Adobe documentation explains that milestones can be associated with tasks to indicate important steps in the life of a project, and that the collection of predefined milestones is called a milestone path. Workfront also states that milestone paths allow key tasks in a project to be associated with predefined milestones, giving managers and stakeholders a high-level view of project progress. In practice, the project owner applies a milestone path to the project first, then associates individual key tasks with milestones from that path. This supports milestone reporting and milestone views across projects. Schedule controls working and non-working time for date calculations, while Resource Leveling Mode relates to resolving resource allocation conflicts. Neither setting is designed to mark key tasks for milestone reporting. Therefore, the correct answer is A. Milestone Path .

=========

In Adobe Workfront, custom billing rates for a specific project are handled through project-level billing rate overrides in the project finance area. Adobe documentation explains that billing rates calculate revenue for projects and tasks, and that role billing rates can be overridden for a project or company. For project-specific custom rates, Adobe’s project finance documentation states that a project manager can specify a different billing rate for a job role on a specific project, and Workfront then uses the project-level rate instead of the system-level rate to calculate revenue. The documented steps are to go to the project, open the Billing Rates or Rates > Billing area, and add a new billing rate override for the relevant job role. Project Details > Billing Information is not the documented location for updating custom project billing rate overrides, and Project Settings > Access Levels relates to permissions rather than financial rates. Therefore, the correct answer is C. Project Finances > Override Project-Level Billing Rates .

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

In Workfront, the " Request Submission Process " is used when a formal submission is required for review before the project proceeds to the planning phase. This process ensures that all necessary documentation, such as the business case, is completed and submitted to the sponsor for approval, streamlining the review process​​.

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, team members can be subscribed to a request so that they receive updates whenever changes or comments are made. This ensures they stay informed of any progress or issues. Adding a request to favorites only bookmarks it for easy access, but does not trigger automatic notifications. Making multiple primary contacts is not an efficient way to handle notifications​​.

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 .

=========

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 Workfront, users with " Contribute " access are typically able to modify and interact with content but are not allowed to perform higher-level administrative tasks like attaching templates or adding tasks. Adding a custom form is within the scope of what a user with Contribute access can do, as it involves adding data input fields to an existing project​​.

In Adobe Workfront proofing, the user should choose a Basic workflow when the proof recipients need to be added manually based on information from the request, such as the project requester and additional approvers listed in request details. Adobe’s documentation for creating an advanced proof with a Basic workflow states that the user selects Basic in the Workflow type section, then specifies the users to add and chooses each person’s proof role. This fits the scenario because the reviewers and approvers are determined by the request information rather than by a preconfigured staged workflow. By contrast, Adobe explains that an Automated Workflow is best when the review process is complex or when proofs are regularly sent to the same people, because it moves the proof from stage to stage and notifies participants when it is their turn. “Manual” is not the documented proof workflow type for this setup. Therefore, the correct workflow is B. Basic .

=========

Groups in Adobe Workfront serve as organizational entities that can be associated with specific Companies or Projects to manage workflows or permissions more effectively. Additionally, each Group can have a Group Administrator assigned, who is responsible for managing the group ' s settings, permissions, and workflows. These roles and associations help in structuring how work and permissions are allocated across different teams or departments​​.

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

The Projected Date in Adobe Workfront is dynamically calculated based on the progress of the task, any task constraints, and its dependencies. This date provides a more accurate reflection of when a task is likely to be completed, considering the current progress and any updates to predecessor tasks. On the other hand, the Planned Date refers to the originally scheduled completion date, and the Estimated Date is not manually entered but inferred from system calculations​​.

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

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 .