Free AD0-E911 Practice Test

In Adobe Workfront, the Condition is an automatically calculated, reportable variable that indicates the health of a project. Its value (e.g., On Target, At Risk, In Trouble) is determined by comparing the project's Planned Completion Date against its Projected Completion Date. The Projected Completion Date is itself influenced by the progress and estimated dates of tasks within the project. This direct relationship between planned and projected dates makes 'Condition' the correct answer for the variable that reflects the project's timeline health.

A. Status: This is a manually updated field by the project manager to indicate the current state of work (e.g., Current, On Hold, Complete), not an automatic calculation based on date variances.
C. Progress Status: This indicates how a project is progressing against its timeline based on task completion (e.g., On Time, Late, Ahead), not the variance between overall planned and projected completion dates.

1. Adobe Experience League Documentation - "Overview of Project Condition and Condition Type": This document explicitly states

"The Condition of a project indicates whether the project is on track to complete on time. Workfront calculates it by comparing the Planned Completion Date of the project with the Projected Completion Date of the project." (Section: "How Workfront calculates Project Condition").

2. Adobe Experience League Documentation - "Glossary of Adobe Workfront terminology":

Condition: "An indicator of the progress of a work item

in relation to the planned completion date. The condition is calculated by comparing the projected completion date of the work item with the planned completion date."

Status: "The attribute of a project

task

or issue that indicates its current state in the workflow (for example

New

In Progress

or Complete)." This confirms it reflects the workflow state

not a date calculation.

3. Adobe Experience League Documentation - "Overview of Project Progress Status": This document defines Progress Status as an indicator of whether the project is on time

late

or ahead. It clarifies

"Workfront calculates the Progress Status of a project by comparing the percent complete of the project with the percentage of the total duration that has passed." This is a different calculation than the one described in the question.

The Estimated Date in Adobe Workfront represents a realistic projection of when a task will finish based purely on real-time progress, percent complete, and the status of predecessor tasks. Unlike other date metrics, the Estimated Date is explicitly designed to bypass hard scheduling limitations. Workfront’s internal analysis calculates this date entirely independently of any applied Task Constraints (such as "Must Finish On") or user-entered Commit Dates, providing project managers with an unfiltered, data-driven view of the task's true expected completion timeline

B. Projected Date: This date type is directly influenced by task constraints. If a strict constraint is applied, the Projected Date defaults to that constraint instead of ignoring it.

C. Planned Date: This date reflects the scheduled baseline dictated by initial project planning and constraints. It does not dynamically calculate completion likelihood based on real-time task progress.

Adobe Workfront Official Documentation, Overview of Projected and Estimated Dates, section "Understand when the Estimated Dates update on tasks". (Specifies that Estimated Dates reflect analysis regardless of Task Constraints). Adobe Workfront Official Documentation, Overview of the Task Planned Completion Date, section "Manually set the Planned Completion Date of a task". (Details how Planned Dates are tied to manual input and constraints, not dynamic progress).

The Burndown Chart is a graphical representation of work remaining versus time, which is a hallmark artifact for tracking progress within a time-boxed Scrum iteration (or Sprint). Within Adobe Workfront's agile tools, the Burndown Chart is a specific feature of the iteration view, designed to help Scrum teams visualize their progress toward completing the work committed in the Sprint Backlog. It provides immediate insight into whether the team is on track to meet the sprint goal.

A. Backlog of stories and issues: A backlog is a core component of many agile methodologies, including Kanban, not just Scrum. Therefore, it is not unique to a Scrum iteration.
B. Workload Balancer for assigning users to tasks: The Workload Balancer is a general resource management tool within Adobe Workfront used for capacity planning across all types of projects, not exclusively for Scrum iterations.

1. Adobe Workfront Documentation, "Burndown chart overview": This document explicitly defines the tool's purpose: "The burndown chart is a graphical representation of the work remaining in an iteration versus the time. You can use the burndown chart to determine whether your team is on track to complete the work of the iteration in the time allotted." This directly links the Burndown Chart to the Scrum iteration concept.

2. Adobe Workfront Documentation, "Create a backlog": This source clarifies that backlogs are not exclusive to Scrum. It states, "You can manage the backlog of a Kanban or a Scrum team on an agile board." This confirms that backlogs are used in at least two different agile methodologies within Workfront.

3. Adobe Workfront Documentation, "Workload Balancer overview": This page describes the Workload Balancer as a tool for "viewing the capacity of your resources and seeing how much of their time is allocated to work." Its application is for resource management in general, not a feature unique to the Scrum process.

In Adobe Workfront, a matrix report is designed to display aggregated or summarized data, not individual row-level details. For a column to appear in the matrix view, it must be configured with a summarization function (e.g., Sum, Count, Average, Min, Max). If a column is added to the report's view but is not set to be summarized, Workfront will not display it in the final matrix output. The project manager's issue stems from failing to apply this necessary aggregation to the column.

B. Update the grouping using text mode: Text mode is an advanced method for editing report elements. The core requirement is to summarize the column, which can be done through the standard user interface without needing text mode.
C. Update the conditional formatting of the column: Conditional formatting alters the visual appearance of data (like color or style) based on specific criteria. It does not control the visibility or inclusion of a column in a matrix report.

1. Adobe Experience League Documentation - Create a matrix report:

Section: "Understand how columns work in a matrix report"

Content: "In a matrix report

any column that you want to display information must be aggregated. If a column is not aggregated

it does not display in the matrix view

although it is still a column in the report. For example

if you want to display the Planned Hours on a project

you must summarize the column by selecting Sum as the aggregator for this column." This directly confirms that summarization is required for a column to be visible.

When a task is assigned to a team in Adobe Workfront, it becomes an unassigned work item available to all team members. These items appear in the "Team Requests" area, typically accessible from the Home page. A team member who wishes to volunteer for and take ownership of the task navigates to this section and clicks the "Work on it" button. This action assigns the task directly to that user and moves it from the team's queue to their personal work list.

A. Team Settings > Select Assign to: "Team Settings" is used for configuring team properties and membership, not for managing incoming work requests.
B. Team Settings > Work on it: The "Team Settings" area is incorrect for this action. This area is for administrative configuration of the team.
D. Team Requests > Select Assign to: The "Select Assign to" option is typically used by a manager to manually assign the request to a specific team member, not for a member to self-assign or volunteer.

1. Adobe Workfront Documentation

"Manage team requests": This document states

"When a user assigns a work item to a team

it displays in the Team Requests list for all members of the team. Any member of the team can then assign the work item to themselves." It further clarifies the action: "Click Work On It next to the task name. The task is automatically assigned to you."

Source: Adobe Experience League

Workfront Documentation. Navigate to the "Manage team requests" article.

2. Adobe Workfront Documentation

"Accept and complete work": This guide explains the function of the "Work On It" button. "When you are ready to start working on a work item

you can click the Work On It button. This indicates to other users that you have started working on the item... Clicking Work On It also assigns the item to you if it was previously unassigned."

Source: Adobe Experience League

Workfront Documentation. See the section "Accept work by clicking 'Work On It'".

3. Adobe Workfront Documentation

"Assign work to a team": This article details the process from the assigner's perspective and the outcome for the team. "After a work item is assigned to a team

any member of the team can accept the work item and start working on it... They can find it in the Team Requests section in the Home area."

Source: Adobe Experience League

Workfront Documentation. Review the article "Assign work to a team".

Adobe Workfront enables project managers to efficiently assign multiple tasks from different projects simultaneously. This is achieved by creating a task report that consolidates tasks from various projects into a single list view. From this report, the manager can select multiple tasks and use the bulk assignment feature to assign them to a specific user, team, or job role in one action. This method eliminates the need to navigate into each individual project plan, directly addressing the manager's requirement for cross-project assignments.

A. Assign work using the Resource Planner. The Resource Planner is a tool for high-level capacity planning and forecasting resource availability and allocation, not for making direct assignments to specific tasks.
B. Assign work by drag-and-drop. Drag-and-drop is a user interface mechanism typically available within specific contexts like a single project's task list or the Workload Balancer, not the primary method for bulk assigning tasks across multiple projects from a report.

1. Adobe Experience League, Workfront Documentation. "Assign work in bulk." In the overview section, it states, "You can assign multiple tasks, issues, or projects to users from a list. This is useful when you want to assign all items in a list to the same resources." This confirms that using a list (report) is the method for bulk assignment across projects.

2. Adobe Experience League, Workfront Documentation. "Assign tasks." Under the section "Assign multiple tasks from a list," the documentation details the process: "Go to a list of tasks...Select multiple tasks, then click the More icon...and then click Assign." This procedure works on any task list, including reports that span multiple projects.

3. Adobe Experience League, Workfront Documentation. "Resource Planner overview." This document describes the tool's purpose: "Using the Resource Planner, you can view the allocation of your resources and the availability of your job roles...The Resource Planner helps you manage your resource allocation." This clearly distinguishes its function from direct task assignment.

A user granted 'Contribute' permissions on a project can add work items such as tasks, issues, and documents. This permission level is designed for team members who need to actively participate in the project's execution by adding and updating work, but without having the ability to alter the project's core structure or settings. The fact that the user has the same system-wide access level as the project owner simply ensures they are not limited by their system role; the governing factor for their actions on this specific project is the 'Contribute' permission they were granted.

A. Add a custom form: This action requires 'Manage' permissions on the project, as it involves modifying the project's attributes and data structure, which is beyond the scope of a contributor.
B. Attach a template to the project: Attaching a template to an existing project is a significant structural change. This capability is reserved for users with 'Manage' permissions on the project.

1. Adobe Workfront Documentation

"Share a project in Adobe Workfront": This document explicitly outlines the actions available for each permission level. In the section "Functionality available for each permission level

" the table shows that users with 'Contribute' permissions can "Add tasks to the project." Conversely

editing project details

which includes adding a custom form

requires 'Manage' permissions.

Reference: Adobe Experience League. (n.d.). Share a project in Adobe Workfront. Retrieved from the Adobe Workfront documentation portal. Specifically

review the permissions table under the main sharing section.

2. Adobe Workfront Documentation

"Create and manage tasks": This guide details the prerequisites for task creation. It states that to add a task to a project

a user needs at least 'Contribute' permissions to the project.

Reference: Adobe Experience League. (n.d.). Create and manage tasks. Retrieved from the Adobe Workfront documentation portal. See the "Access requirements" section.

3. Adobe Workfront Documentation

"Add a custom form to an object": This article specifies the access requirements for attaching custom forms. It confirms that a user must have 'Manage' permissions on the project to add a custom form to it.

Reference: Adobe Experience League. (n.d.). Add a custom form to an object. Retrieved from the Adobe Workfront documentation portal. See the "Access requirements" section.

The most effective and scalable best practice is to incorporate the approval process directly into the project template used by the marketing team. When a new project is created from this template, it will automatically inherit the pre-configured approval process. This ensures consistency, eliminates the need for manual setup on each project, and prevents the risk of human error where an approval might be forgotten. Triggering the approval when the project status changes to "Complete" correctly places the review step just before the project is formally closed.

A. A global approval process would apply to all projects in the system, not just those for the marketing team, making it too broad and potentially disruptive to other departments.
B. Creating a single-use approval process manually for each new project is inefficient, prone to error, and not a sustainable best practice for a recurring, standardized requirement.

1. Adobe Experience League - Create and modify project templates: "Templates are reusable frameworks that allow you to quickly create new projects... You can attach a template to a project... This includes... Approval processes." This source confirms that adding an approval process to a template is a standard function for ensuring process consistency on new projects. (See section: "Overview of project templates").

2. Adobe Experience League - Add an approval process to a template: "When you add an approval process to a template, any project created from that template automatically includes the approval process." This directly supports the chosen answer (C) as the intended method for automatically applying a standard approval to a set of future projects. (See section: "Add an approval process to a project template").

3. Adobe Experience League - Approval process overview: This document distinguishes between system-wide (global) approvals and those attached to specific objects like templates. It clarifies that global approvals are for processes that must apply to all items of a certain type in the system, which is not the requirement here, thus invalidating option A. (See section: "Associate a new or existing approval process with work").

This solution effectively addresses both stakeholder requirements. A program-specific dashboard provides continuous, real-time access to current metrics, satisfying the first need. Setting up a weekly automated report delivery directly fulfills the request for a regular recap. This combination of a "pull" mechanism (the dashboard) for on-demand data and a "push" mechanism (the automated report) for periodic summaries is the most efficient and comprehensive way to keep executives informed within Adobe Workfront.

B: This option requires manual intervention weekly, which is inefficient, less reliable, and more prone to human error than an automated process. C: A calendar reminder does not deliver a report or a recap; it only prompts stakeholders to view the dashboard, failing to meet the requirement for a pushed weekly summary.

1. Dashboards Overview

Adobe Experience League: "A dashboard is a collection of reports that gives you a comprehensive view of project information in real time." This supports the use of a dashboard for providing access to current metrics. (Source: Adobe Workfront Documentation

"Dashboards overview

" Section: "Get started with dashboards").

2. Schedule a report delivery

Adobe Experience League: "You can schedule a report to be delivered to yourself and to other users automatically on a recurring basis... For example

you can schedule a report to be sent every Monday morning that shows all of the late tasks on a project." This directly supports the capability to set up a weekly automated report to be sent as a recap. (Source: Adobe Workfront Documentation

"Schedule a report delivery

" Section: "Schedule a report for delivery").

In Adobe Workfront reporting, wildcard variables are used to create dynamic filters. To filter for a date that is one month in the future, the correct syntax is TODAY + 1m. The TODAY variable represents the current date, and the + 1m modifier adds exactly one calendar month to it. This combination accurately targets the desired date range for the filter.

A. TODAY + 1bm: This is incorrect because 1bm represents one "business month," which calculates based on working days, not a standard calendar month as implied by the question.
C. CURRENTDATE + 4w: This is incorrect because 4w represents four weeks (28 days). This is an imprecise approximation for a calendar month, which can have 28, 29, 30, or 31 days.

1. Adobe Experience League - Wildcard filter variables: This official documentation outlines the available wildcards for filtering in Adobe Workfront. It specifies that $$TODAY (or TODAY) represents the current date and that the m modifier is used to denote months. The b prefix is used for business time units (bm)

and w is used for weeks.

Section: "Date-Based Wildcards" and the table of "Wildcard Syntax". This section confirms +1m adds one month to the specified date variable.