Practice Free AD0-E911 Exam Online Questions
A user wants to know if a task is pending approval.
Which task field would the user review?
- A . Status
- B . Critical Path
- C . Priority
A
Explanation:
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.
Which initial project setting would a project owner use to identify and report on key tasks on a project?
- A . Milestone Path
- B . Schedule
- C . Resource Leveling Mode
A
Explanation:
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.
A marketing team wants to manage their projects using a traditional, sequential approach where each phase must be completed before the next begins.
Which project management methodology in Workfront supports this approach?
- A . Scrum
- B . Kanban
- C . Waterfall
C
Explanation:
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.
Task 2 has a 5-day duration, is tied to Task 1 with a predecessor, and is expected to begin once Task 1 is completed. Due to a resource availability conflict, Task 1 was rescheduled to start 1 week later. Once Task 1 was rescheduled, the planned start date on Task 2 did not dynamically shift by 5 days as expected but instead remained the same planned start date that existed before the change to Task 1.
What may have caused the planned start date of Task 2 to remain the same?
- A . The primary assignee had already submitted a Commit Date for the previous planned start date on Task 2, even though the project owner did not accept this Commit Date, the project plan made this date a Must Start On Constraint on Task 2.
- B . The project owner has at some point made a manual change to the planned start date of Task 2, which has in turn changed the Task Constraint of Task 2 to Must Start On.
- C . The primary assignee had scheduled time off during the new planned start date that Task 2 should have shifted toward. Due to this time off scheduled the date remained the same.
- D . The project owner has at some point made a manual change to the Task Constraint of Task 2 to As Soon As Possible, which has forced the date of Task 2 to be static.
B
Explanation:
In this scenario, the fact that Task 2’s start date did not shift automatically despite its dependency on Task 1 suggests that a manual override was applied, resulting in a Task Constraint of "Must Start On." This type of constraint locks a task to a specific date, preventing it from dynamically adjusting based on changes to its predecessor. The other options either do not explain why the start date remained static or involve user-specific scheduling conflicts, which would not affect the system-driven date adjustment.
What is unique to a Scrum iteration?
- A . Backlog of stories and issues
- B . Workload Balancer for assigning users to tasks
- C . Burndown Chart
C
Explanation:
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.
Which project Condition is set when the Progress Status of the project is Behind or At Risk?
- A . Late
- B . At Risk
- C . In Trouble
B
Explanation:
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.
The executive team at Company A has asked the Workfront System Administrator how they can get visibility into the health, importance, and strategic alignment of active projects across the organization so that they can quickly make data-driven business decisions.
Which report grants the executive team this visibility?
- A . A project report showing active projects grouped by portfolio showing project condition, project priority, and custom data aligning the project initiative to business goals.
- B . A portfolio report showing all projects grouped by team showing project condition, the alignment score, and custom data aligning the project initiative to business goals.
- C . A program report showing active projects grouped by department showing program health, project urgency, and custom data aligning the project initiative to business goals.
C
Explanation:
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.
A project manager has set up and launched a new project for an annual marketing campaign.
Where can the project team locate their work requests?
- A . Email, Workfront Home, Project tasks list
- B . Email, Automatic Reminders, Workfront Home
- C . Event Notifications, Approval processes, Email
A
Explanation:
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.
A project manager compares the original schedule for a task to another set of dates that moved later after predecessors slipped and the assignee changed a completion commitment.
What do these later, system-calculated dates represent?
- A . They are Planned Dates that show the originally scheduled task dates.
- B . They are Projected Dates that show the current forecast for task start and finish.
- C . They are Milestone Path Dates that show when milestone tasks are expected to occur.
B
Explanation:
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.
Which project elements can be used to measure a project’s adherence to its original schedule?
- A . Number of tasks, actual completion dates, and project status
- B . Project baselines, planned completion dates, and actual completion dates
- C . Workload balancer data, planned completion dates, and expenses
B
Explanation:
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.
