Questions for the AD0-E908 were updated on : Dec 01 ,2025
What is one of the primary benefits to setting up an automated proofing workflow instead of a basic
workflow?
B
Explanation:
One of the primary benefits of setting up an automated proofing workflow in Workfront, as opposed
to a basic workflow, is the ability to create a series of review stages with dependencies between
stages. This feature enhances the review process by:
Organizing Reviews: Multiple stages can be defined, ensuring that each stage is completed before the
next begins, which helps maintain a structured and sequential review process.
Dependencies: Dependencies between stages ensure that proofs move through the review process in
an orderly manner, with specific actions required at each stage.
Automation and Efficiency: Automating this process reduces the manual intervention needed,
speeding up the overall proofing process and ensuring consistency across reviews.
This approach is highlighted in various user guides and advanced workflow setup training sessions for
Workfront, emphasizing its efficiency and effectiveness in managing complex review processes.
Which Workfront objects can date effective billing rates be used with?
B
Explanation:
Date-effective billing rates in Workfront are applicable to the following objects:
Companies: Allows setting specific billing rates for different companies.
Users: Enables individual billing rates based on the user.
Job Roles: Provides the ability to define billing rates based on job roles, ensuring accurate billing for
various roles within the organization.
These settings ensure that billing rates can be adjusted and applied accurately across various entities
within Workfront, allowing for flexible and precise financial management. This information is
confirmed in Workfront's advanced training documentation and usage guidelines for billing rates.
A project manager wants to track specific types of issues on a project along with additional custom
fields for each type. What is one way to accomplish this requirement?
C
Explanation:
Identify the Requirement: The project manager wants to track specific types of issues with additional
custom fields for each type within a project.
Understanding Queues and Custom Forms in Workfront: Workfront allows the creation of queues to
manage different types of requests or issues. Queue topics can be used to categorize these issues,
and custom forms can be applied to capture additional information specific to each issue type.
Steps to Create a Queue with Custom Forms:
Navigate to the Project: Go to the project where you want to track specific issues.
Create a Queue: In the project settings, create a queue.
Define Queue Topics: Set up queue topics to represent the different types of issues (e.g., Bug
Reports, Change Requests, etc.).
Assign Custom Forms: Create custom forms with the necessary fields for each issue type and assign
them to the corresponding queue topics.
Implementation:
Setup Custom Fields: Ensure the custom fields on the forms are configured correctly to capture all
required information.
Test the Queue: Test the queue by creating sample issues to ensure that the custom forms are
working as expected for each issue type.
Reference: Documentation on creating queues, queue topics, and assigning custom forms can be
found in the Workfront Help section.
A project team has configured a Kanban board with columns for backlog, in progress, on hold, and
completed statuses. The project manager wishes to automatically archive cards that have been
closed for longer than two weeks.
What should the project manager change in order to make this happen?
A
Explanation:
Identify the Requirement: The project manager wishes to automatically archive cards that have been
closed for longer than two weeks on a Kanban board.
Understanding Card Falloff in Workfront: Workfront allows for the configuration of automatic
archiving (card falloff) based on the time a card has been in a specific column. This is useful for
maintaining a clean and organized Kanban board.
Steps to Configure Card Falloff:
Navigate to the Board: Go to the Kanban board where the columns for backlog, in progress, on hold,
and completed statuses are set up.
Access Configuration: Click on "Configure" to access the board settings.
Select Cards: In the configuration settings, go to the "Cards" section.
Enable Card Falloff: Enable the option for card falloff and set it specifically for the "Closed" column.
Set the falloff duration to two weeks.
Implementation:
Apply Settings: Save the configuration changes to ensure that cards in the Closed column will
automatically archive after two weeks.
Monitor: Regularly check to ensure that the card falloff is functioning as expected and that closed
cards are being archived after the specified time.
Reference: The setup for card falloff and archiving can be found in the Workfront Documentation
related to board configurations and managing Kanban boards.
An admin-level user has created a group status for tasks in projects. The admin notices in testing that
the custom task status is only available in some of the projects with assigned Marketing team
members.
Why is the group status missing in some projects?
C
Explanation:
Identify the Requirement: The admin notices that the custom task status is only available in some
projects with assigned Marketing team members.
Understanding Group Statuses: Group statuses in Workfront are linked to specific groups and are only
available in projects that are associated with those groups.
Review Project Details:
Check Project Association: Ensure that the projects where the status is missing are correctly
associated with the Marketing group.
Update Project Details: If necessary, update the project details to associate them with the Marketing
group. This will ensure that the custom group statuses are available.
Implementation:
Verify Group Settings: Confirm that the custom statuses are correctly set up for the Marketing group
in the group settings.
Communicate with Users: Inform project managers and team members about the association
requirements for using custom group statuses.
Reference: Documentation on group statuses and project associations in Workfront can be found in
the Workfront Help Center and administrative training materials.
A customer wants to use custom statuses to move a project's tasks through different process stages.
Not every user in the system needs to use these custom statuses.
What must an admin-level user do to support this customer requirement?
B
Explanation:
Identify the Requirement: The customer wants to use custom statuses for project tasks, but not all
users need to use these statuses.
Creating Custom Statuses:
Navigate to Setup: Go to the Setup area in Workfront.
Custom Statuses: Within the Setup area, select "Statuses".
Create New Status: Add new custom statuses that are relevant to the project's workflow stages.
Associating Custom Statuses with Groups:
Select Group: Identify the group associated with the projects that need these custom statuses.
Assign Statuses to Group: In the Group settings, assign the newly created custom statuses. This
ensures that only users within this group will have access to and can use these statuses.
Implementation and Training:
Communicate with Users: Inform the relevant users about the new custom statuses and how they
will be used within their projects.
Provide Training: Offer training to ensure users understand how and when to use the custom statuses
appropriately.
Reference: Detailed instructions on creating and managing custom statuses can be found in the
Workfront Documentation and training sessions.
What are two differences between an issue and a task? (Choose two.)
C, A
Explanation:
Identify the Requirement: The differences between tasks and issues need to be clarified.
Understanding Tasks and Issues in Workfront:
Tasks: Represent planned work and are created within projects. They have specific start and end
dates, assigned resources, and dependencies.
Issues: Represent unplanned work that arises and needs to be addressed. Issues can be created
within projects or as standalone items and often require immediate attention.
Key Differences:
Creation:
Tasks: Can only be created within the context of a project. They are part of the project’s planned
workflow and structure.
Issues: Can be created within projects or attached to tasks. They provide a way to log unplanned
work or problems that need resolution.
Nature of Work:
Tasks: Represent planned, scheduled work that follows the project timeline and milestones.
Issues: Represent unplanned, often urgent work that needs to be addressed outside of the planned
workflow.
Reference: Documentation on managing tasks and issues in Workfront can be found in the Workfront
Help Center and training materials provided during onboarding and ongoing education.
A Workfront Admin has a request to set up an Automated Workflow Template. How can they ensure
the design team can view the new templates?
C
Explanation:
Identify the Requirement: The admin needs to set up an Automated Workflow Template and ensure
that the design team can view the new templates.
Understanding Sharing Mechanisms in Workfront: Workfront allows administrators to share
templates, projects, and reports with specific users or groups to ensure visibility and collaboration.
Creating the Automated Workflow Template:
Navigate to Templates: In Workfront, go to the Templates section.
Create New Template: Select the option to create a new workflow template.
Define Workflow: Set up the workflow steps, including tasks, approvals, and dependencies, as
required for the design team's processes.
Save the Template: Ensure the workflow template is saved correctly in the system.
Sharing the Workflow Template:
Select the Template: Go to the created workflow template in the Templates section.
Share with Design Team: Use the sharing options to specifically share the template with the Design
Team group. This ensures that only the design team has access to the new workflow template.
Set Permissions: Define the level of access the design team will have, such as view, edit, or manage
permissions.
Communication and Training:
Notify the Design Team: Inform the design team about the new workflow template and how they can
access and use it.
Provide Training: Offer training sessions or materials to help the design team understand how to use
the new automated workflow template effectively.
Reference: The process for sharing templates in Workfront is detailed in the Workfront
Documentation and training materials available through Adobe Workfront Help.
A client requires that employees account for any "breaks" during their day in order to report on
utilization. How would a System Administrator configure this requirement?
B
Explanation:
Identify the Requirement: The client needs to track "breaks" during the employees' workday to
report on utilization. This requires a way for employees to log their break times accurately.
Understand Workfront's Time Tracking Capabilities: Workfront allows the creation of different hour
types which can be assigned to timesheets. This flexibility helps in categorizing time entries for
various activities, such as work, meetings, training, and breaks.
Creating a "Break" General Hour Type:
Navigate to Setup: As a system administrator, go to the Setup area in Workfront.
Access Hour Types: Under the "Timesheets & Hours" section, select "Hour Types".
Add New Hour Type: Click on the option to add a new hour type.
Define Hour Type: Name the new hour type as "Break". You can provide a description for clarity. This
will help users understand that this category is specifically for logging break times.
Save the Hour Type: Ensure to save the new hour type so that it becomes available for timesheet
entries.
Assigning the "Break" Hour Type to User's Timesheet Profile:
Navigate to User's Profile: Go to the user's profile settings.
Edit Timesheet Profile: Within the profile, locate the section for timesheet settings.
Add Hour Type: Include the newly created "Break" hour type to the list of available hour types that
users can select when logging their hours.
Save Changes: Ensure that all changes are saved so users can start using the "Break" hour type in
their timesheets.
Implementation and Training:
Communicate with Users: Inform users about the new "Break" hour type and provide instructions on
how to log their break times in their timesheets.
Monitor Utilization: Track the usage of the new hour type to ensure that it is being utilized correctly
and effectively for reporting purposes.
Reference: Documentation for setting up and managing hour types in Workfront can be found in the
Adobe Workfront Help section or specific training materials provided by Workfront administrators.
How can a project manager ensure that progress on the board is also tracked in a project?
C
Explanation:
To ensure that progress on the board is also tracked in a project, a project manager can use
connected cards. Connected cards link tasks or issues on an agile board directly to tasks or issues
within a project, ensuring that updates made on the board are reflected in the project and vice versa.
Enable Agile in the Project:
Navigate to the project settings.
Ensure that the project is set up for agile tracking by enabling the relevant agile settings.
Create Connected Cards:
Within the agile board, create connected cards by linking tasks or issues directly to the corresponding
tasks or issues in the project.
This can typically be done by selecting the task or issue on the board and choosing the option to
connect it to a project task or issue.
Update and Track Progress:
As team members update the connected cards on the agile board, the progress will automatically be
tracked in the linked project tasks or issues.
This ensures that both the board and the project reflect the same status and progress.
Reference:
The use of connected cards for ensuring synchronization between board progress and project
tracking is covered in the agile and project management training materials provided by Workfront
(webinaradminessentialsuxinterfacedesignmar1520231678820264387).
Which two objects can an issue be converted to? (Choose two.)
A, C
Explanation:
Converting an issue to a task:
Issues can be converted into tasks within a project. This allows for better tracking and management
of the work required to resolve the issue.
Reference: "Issue Management and Conversion" in Workfront documentation.
Converting an issue to a project:
Issues can also be converted into standalone projects. This is useful when an issue requires a series
of tasks and resources that warrant its own project structure.
Reference: "Issue to Project Conversion" in Workfront documentation.
An administrator has assigned custom project status names to the Finance group. The administrator
creates a sub-group under the Finance group, called "AP\
Which project status names will apply to the AP sub-group?
B
Explanation:
Inherited status names:
Sub-groups inherit the project status names from their parent group unless explicitly overridden.
Therefore, the AP sub-group under the Finance group will use the same custom project status names
assigned to the Finance group.
Reference: "Group and Sub-group Configuration" in Workfront documentation.
A designer notices that no tasks associated with a specific project appear on their timesheet. The
project owner verified that the designer is assigned to several tasks and that the tasks occur during
the week of the current timesheet
Which setting can cause this experience?
B
Explanation:
Project status and timesheets:
For tasks to appear on a timesheet, the project status must be set to "Current." If the project status is
anything other than Current (e.g., Planning, Complete, or On Hold), tasks from that project will not
automatically populate the timesheet.
Reference: "Timesheet Settings and Configuration" in Workfront documentation.
What does the Cost Performance Index (CPI) of a project in Workfront track?
A
Explanation:
The CPI measures the cost efficiency of budgeted resources on a project. It is calculated by dividing
the earned value (EV) by the actual cost (AC). A CPI value greater than 1 indicates that the project is
under budget.
Reference: "Project Performance Metrics" in Workfront documentation.
An admin-level user recommends assigning the role Reviewer & Approver to someone who needs to
review a proof. What are two reasons why the admin-level user would make this recommendation9
(Choose two.)
This allows the Reviewer to indicate they have completed their review, even if there is no feedback.
AC
Explanation:
The Reviewer & Approver role allows the user to provide a final decision on the proof, which includes
options like Approve, Changes Needed, or Not Relevant. This role is ideal for those who need to
summarize their overall feedback and make a conclusive decision.
Reference: "Reviewer & Approver Role" section in Workfront Proof documentation.
Notification upon approval:
By assigning the Reviewer & Approver role, the user is notified when an approval decision is made on
the proof. This ensures that they are kept in the loop and can follow up as necessary.
Reference: "Proof Notifications and Alerts" section in Workfront Proof documentation.