The "Reviewer & Approver" role is recommended when a user needs to do more than just provide feedback. This role uniquely grants the ability to make a formal decision on the proof (e.g., Approved, Changes Required, Not Relevant). This decision acts as a definitive summary of their overall feedback (B) and serves as a formal mechanism to indicate that their review is complete, even if no specific comments or markups were added (A). A standard "Reviewer" can only add comments and cannot make these binding decisions.

C. This is incorrect because the standard "Reviewer" role also allows for making comments and markups; this capability is not exclusive to the "Reviewer & Approver" role.

D. Notifications are configured within the proof's workflow settings and are not a primary function or reason for assigning a specific user role like "Reviewer & Approver."

1. Adobe Workfront Documentation, "Proof roles overview." This document explicitly outlines the capabilities of each role. It states that both "Reviewer" and "Reviewer & Approver" can "Make comments and markups," invalidating option C. It also specifies that only roles with "Approver" permissions can "Make a decision on the proof," which directly supports options A and B as the key differentiator.

2. Adobe Workfront Documentation, "Make a decision on a proof in the proofing viewer." This guide details the decision-making process for approvers. It states, "As an approver on a proof, you must make a decision on the proof to indicate whether it's ready for the next step in its lifecycle." This confirms that making a decision is the formal method for an approver to complete their review and summarize their findings, supporting the reasoning for answers A and B.

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.

A. Through ad hoc cards: Ad hoc cards are used for unplanned work or tasks that are not associated with a formal project, so they do not track progress against a project.

B. Through enabling agile tracking: "Agile tracking" is a broad methodology or practice, not a specific tool feature that connects a board card to a project task for progress updates.

1. Adobe Experience League Documentation, "Use connected cards on a board." This document explicitly states, "You can connect cards to existing Workfront objects, such as tasks or issues. This allows you to manage the work on the card and have the progress automatically update on the connected object." (See the "Overview of connected cards" section).

2. Adobe Experience League Documentation, "Create ad hoc cards on a board." This source clarifies the purpose of ad hoc cards: "You can create ad hoc cards on a board to represent work that is not tied to a Workfront object." This confirms they are not for tracking progress within a project. (See the introductory paragraph).

3. Adobe Experience League Documentation, "Boards overview." This document provides context on the different types of cards: "Cards on a board can be ad hoc cards (standalone cards that are not connected to other Workfront objects) or they can be connected to tasks and issues on projects." (See the "Cards" section).

In Adobe Workfront, the "Card Falloff" feature is specifically designed to automatically remove cards from a board after they have resided in a designated column for a specified period. To implement this, the project manager must access the board's configuration settings. The correct path is to navigate to the board's Configure menu, select the Cards section, and then enable the Card Falloff option. Within this setting, they can specify the "Closed" column and set the time period to 14 days (two weeks) for automatic archival.

B. Select the Closed column > select Edit and set Archive Limit to two weeks

Editing a column directly typically allows for changing its name, Work-In-Progress (WIP) limit, or policies, not for setting time-based archival rules.

C. Select the three ellipses next to the board name > select Archive and set for two weeks.

This action would pertain to archiving the entire board, not for setting up an automated rule to archive individual cards from a specific column.

1. Adobe Workfront Documentation - Configure cards on a board:

"You can configure cards to automatically fall off a board after a specified number of days. When a card falls off a board, it is removed from the board but the associated task or issue is not deleted."

The procedure is detailed as: "Click the More menu ... then click Configure. ... In the left panel, click Cards. ... In the Card Falloff section, select the checkbox to enable card falloff. ... Select a column from the drop-down menu. ... Specify the number of days..."

Source: Adobe Experience League, "Configure cards on a board," Workfront Documentation. (Specific section: "Enable card falloff").

To ensure users can both use a template and access the projects created from it, two distinct sharing configurations on the template are required. Template Sharing controls which users can view and select the template to create a new project. Project Sharing defines the access permissions that are automatically inherited by any new project created from that template, granting the specified users access to the resulting project instance. Both must be configured to fulfill the complete requirement.

C. Template Group: This is not a specific configuration item in Adobe Workfront. While you can share a template with a group, "Template Group" is not the name of the setting itself.

D. Team Sharing: This is a method of sharing, not a fundamental configuration item. You can share with a team, but the core settings are "Template Sharing" and "Project Sharing."

1. Adobe Workfront Documentation - Share a project template:

Section: "Access to the template and to the projects created from it": "When you share a template, you can also grant users access to the projects that are created using the template. You grant access to the template and to the projects created with it separately."

Section: "Share a template": This section details the steps for configuring "Template Sharing" which "gives them access to use it to create projects."

Section: "Configure sharing for the projects created with the template": This section explains how to use the "Project Sharing" tab to "grant users access to the projects that are created using the template." This directly supports the distinction between the two required settings.

(Source: Adobe Experience League, "Share a project template", Workfront Documentation. Document ID: 000013988)

In Adobe Workfront, billing rates are used to calculate project revenue and are foundational for financial management. The system allows for the creation of date-effective billing rates, which means different rates can be applied for the same object over different time periods. According to official documentation, these billing rates can be specifically created for and associated with three types of objects: Companies, Users, and Job Roles. This allows for granular control over billing, accommodating rate changes over time for specific clients (Companies), individuals (Users), or functional positions (Job Roles).

A. Job roles. Users. Groups: Workfront does not support the direct association of billing rates with Groups. Groups are primarily used for managing user access and permissions, not for financial rate structures.

C. Users. Teams. Job Roles: Billing rates cannot be directly applied to Teams in Workfront. Teams are organizational units for work assignment and collaboration, not for defining financial rates.

1. Adobe Experience League, Workfront Documentation. In the article "Create and manage billing rates," the introduction explicitly lists the objects for which billing rates can be created.

Reference: "You can create billing rates for the following items in Workfront: Companies, Job Roles, Users."

Source: Adobe Experience League, Create and manage billing rates, Section: "Create and manage billing rates".

2. Adobe Experience League, Workfront Documentation. The same document details how to create date-effective rates, which is a property of the billing rate record that is then associated with the supported objects.

Reference: The section "Create date-effective billing rates" explains the concept of having multiple rates for different time periods, a feature applicable to the billing rates associated with the objects listed above (Companies, Users, Job Roles).

Source: Adobe Experience League, Create and manage billing rates, Section: "Create date-effective billing rates".