Question 1

A Workfront developer is tasked with building a new custom form to collect project requests. The
form will display different sets of options based on different selections, which requires the use of
display logic and skip logic in the form.
What are two considerations the developer should take into account when building the conditional
logic in the form? (Choose two.)

Accepted Answer

C, D

Explanation: When building a custom form with conditional logic, a developer must understand the default behavior of fields and the limitations of the logic types. By default, all custom fields added to a form are visible unless a specific display logic rule is created to hide them. This is a foundational principle for the developer to consider when deciding which fields need rules. Additionally, it is a critical technical limitation that skip logic cannot be applied to non-input elements like widgets or section breaks; it can only target fields. This directly impacts how the developer must structure the form to achieve the desired conditional navigation.

Question 2

Which two actions are necessary for a request queue to be visible in the system? (Choose two.)

Accepted Answer

A, D

Explanation: For a request queue to be visible and accessible to users in the Adobe Workfront system, two primary conditions must be met. First, the underlying project must be explicitly configured to function as a queue by selecting the "Publish as Help Request Queue" option in the Queue Details. Second, the project itself must be active. In Workfront, an active project is one with a status that equates to "Current." If the project's status is, for example, "Planning" or "Complete," the associated request queue will not be visible for new submissions.

Question 3

A client's organizational structure has employees moving on and off projects and switching their
Workfront responsibilities often. Why would the system administrator recommend sharing objects
with Groups rather than individual users?

Accepted Answer

C

Explanation: Using groups for sharing is a best practice for managing permissions at scale, especially in dynamic environments. When an employee's role or project assignment changes, a system administrator only needs to add or remove them from the relevant group. This single action automatically updates the user's access to all objects shared with that group. This method is significantly more efficient and less error-prone than manually adjusting permissions for an individual user on every single project, task, report, and other relevant objects.

Question 4

A project manager is using information in the Portfolio Optimizer to analyze which projects to prioritize. Where is this information coming from?

Accepted Answer

C

Explanation: The Adobe Workfront Portfolio Optimizer is a tool designed to help organizations prioritize projects to maximize value against a set budget. It achieves this by analyzing various data points associated with each project. The primary source for this data is the project's Business Case. The Business Case is the central object in Workfront that contains all the necessary inputs for portfolio analysis, including financial information (e.g., Cost, Net Present Value, ROI) and strategic alignment metrics (e.g., the Alignment Score). The optimizer pulls this comprehensive set of data directly from the Business Case to build its prioritization models.

Question 5

A marketing team has identified a new workflow for a digital deliverable process. What are the three main benefits of utilizing a project template for their new Workflow? (Choose three.)

Accepted Answer

A, C, E

Explanation: Project templates in Adobe Workfront are designed to standardize and accelerate project creation. Their primary benefits include establishing a consistent, repeatable process (A) by pre-defining tasks, durations, and dependencies. They enhance efficiency (E) by eliminating the need to build each new project from scratch, saving significant time and effort. Templates also allow for pre-configuring sharing and access permissions (C), ensuring that the correct stakeholders are automatically granted the appropriate level of access from the project's inception, which improves security and collaboration.

Question 6

How can a project manager ensure that progress on the board is also tracked in a project?

Accepted Answer

C

Explanation: Connected cards are the specific feature within Adobe Workfront designed to link a card on a board to an existing project object, such as a task or an issue. When a team member updates the status of a connected card on the board (e.g., moving it to a "Done" column), the progress is automatically synchronized with the corresponding task in the project plan. This mechanism provides the project manager with accurate, real-time visibility into the progress of project-related work being managed by an agile team on a board, ensuring alignment between the board and the project.

Question 7

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?

Accepted Answer

B

Explanation: In Adobe Workfront, the automatic population of tasks and issues onto a user's timesheet is directly governed by the status of the parent project. For tasks to appear, the project's status must be configured in the system settings to "equate with" the Current status. If a project is in a status like "Planning" or "On Hold" that does not equate to Current, its tasks will not be added to timesheets automatically, regardless of user assignments or task dates. This ensures that time is only tracked against active, approved work.

Question 8

Dashboards are a quick way to access information in reports, calendars, and from external pages. Which constraints apply to the creation of dashboards?

Accepted Answer

C

Explanation: A dashboard in Adobe Workfront acts as a container for reports, calendars, and other elements. The dashboard's permissions do not override the permissions of the individual components it displays. For a user to view the data within a report on a dashboard, they must have been granted viewing rights to that specific report. If the underlying report is not shared with the user, the dashboard panel will appear empty or show an error, making the dashboard ineffective for that user. This makes sharing a critical constraint for dashboard functionality.

Question 9

What license types in Workfront allow a user to create, edit, and delete reports?

Accepted Answer

C

Explanation: According to the Adobe Workfront licensing model, the ability to create, edit, and delete reports is a high-level function reserved for users with specific license types. The Plan license, designed for portfolio and program managers, and the Standard license (the current designation for the Work license), designed for project managers, both provide these capabilities. These licenses grant users the necessary permissions to build and manage reports for tracking projects, resources, and portfolios, assuming their assigned access level also permits it. The other license types mentioned are designed for users with more limited roles who do not require report-building functionality.

Question 10

Which reporting element has an option of conditional formatting?

Accepted Answer

B

Explanation: Conditional formatting is a feature used to visually highlight data within a report based on specified rules or conditions. In the context of Adobe Analytics, this functionality is applied to data visualizations, specifically within Freeform Tables in Analysis Workspace. A Freeform Table is a type of data "View" that presents metrics and dimensions. By applying conditional formatting to this view, analysts can automatically color-code cells or apply icons to emphasize performance, identify outliers, or track progress against goals, making the data easier to interpret at a glance.

Question 11

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?

Accepted Answer

C

Explanation: In Adobe Workfront, newly created objects, including Automated Workflow templates, are not shared with all users by default. To make a template visible and usable by a specific set of users, such as the "design team," a Workfront Administrator must explicitly grant them access. The most direct and precise method is to use the sharing settings for the template and share it directly with the "Design Team" entity. This ensures that only the intended team members can view and apply the template, adhering to the principle of least privilege.

Question 12

A manager needs to create a Request queue that tracks requests for Creative assets and Website
changes, and assigns the requests to different teams for follow-up.
Which steps must be completed to meet this need?

Accepted Answer

B

Explanation: To meet the manager's requirement, distinct pathways for "Creative assets" and "Website changes" are needed. This is achieved by creating two Queue Topics, one for each request type. To automatically assign these requests to different teams, two Routing Rules must be configured. Each Routing Rule is then linked to its corresponding Queue Topic. This ensures that when a user selects a specific topic on the request form, the associated rule is triggered, directing the request to the correct team's project or queue for fulfillment.

Question 13

A marketing team has created a new project template for a Print Deliverable workflow. They need to
ensure that new projects that use the new template are shared with marketing team only upon
project creation.
How would they meet these requirements?

Accepted Answer

C

Explanation: To ensure new projects automatically inherit specific sharing permissions, those permissions must be configured on the source template. By adding the marketing team to the sharing settings of the project template, any project subsequently created from that template will automatically grant the specified access level to the marketing team upon its creation. This automates the sharing process and ensures consistent access control for all projects within that workflow, directly meeting the requirement.

Question 14

Which component may be added to Canvas Dashboards, but not legacy Dashboards?

Accepted Answer

B

Explanation: Canvas Dashboards, built within Analysis Workspace, support a wide array of components, including non-data "widgets" like Text, Shapes, and Images. These widgets allow for the creation of highly customized, infographic-style reports with rich context, titles, and annotations. Legacy Dashboards, in contrast, were restricted to a rigid grid of data-driven "reportlets" and did not have the functionality to add these freeform, contextual elements. This flexibility is a key differentiator of the modern canvas environment.

Question 15

A project manager needs to share a Custom Form that was created to support their portfolio. What should the project manager understand about this requirement?

Accepted Answer

B

Explanation: According to Adobe Workfront's functionality, the creator (or anyone with 'Manage' access) of a Custom Form has granular control over its visibility and usage. They can share the form with specific entities within the system, including individual users, job roles, groups, teams, and even entire companies. For each entity, permissions can be set to either 'View,' which allows the form to be attached to objects, or 'Manage,' which grants the ability to view, edit the form's structure, and share it with others. This system allows for precise access control, ensuring that forms are only available to the intended audience for specific purposes.

Free Adobe AD0-E908 Actual Exam Questions