Adobe AD0-E911 - Adobe Workfront Project Manager Certified Professional

In Workfront, a " Portfolio " is a parent object that can contain multiple programs and projects. Each Portfolio can have a hierarchy of child objects such as programs, which further break down into projects. A project, while it contains tasks and issues, is considered a child within the larger hierarchy of a portfolio. Issues, on the other hand, are typically linked to tasks or projects but are not used as parent objects. This hierarchy enables Workfront users to organize and manage their work across various levels​​​.

In Workfront, when a task owner is unavailable due to time off, they can update the Commit Date to reflect when they are available to work on the task. This prevents delays and ensures the task is completed within a revised timeline. The Commit Date feature is designed to accommodate personal schedules and ensure tasks are accurately tracked without putting the task " At Risk " unnecessarily​​.

In Workfront, when adjusting user access, it’s important to ensure that Program Manager A only has the necessary level of access to their own program. To rectify the over-access issue, the portfolio manager must share the relevant program with Program Manager A with the correct Manage access and remove their broader Manage access to the portfolio. This restricts their control to only their specific program​​.

In Workfront, creating a program-specific dashboard allows for the presentation of real-time data to stakeholders. Additionally, automated reports can be set to send out weekly, meeting the requirement for a consistent recap. This automation reduces the manual effort of downloading and sending reports each week​​.

In Workfront, Teams are operational entities that can be assigned to tasks, while Groups are organizational entities that are not assignable to tasks. Additionally, work requests can be routed to both Groups and Teams, depending on how the organization is structured and how the routing is set up​​.

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

In Workfront, creating a custom status specifically for " Backlog " allows the team to differentiate between work that is pending capacity and work that is actively being planned. This prevents confusion and allows for better project tracking, ensuring that tasks move smoothly from backlog to the planning phase when appropriate​​.

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