The core requirement is to reduce a task's duration by adding more resources while keeping the total amount of work (40 hours) constant. The Effort Driven Duration Type is specifically designed for this scenario. When a task is set to Effort Driven, the total Planned Hours (effort) are treated as a fixed value. As more resources (users) are assigned to the task, Adobe Workfront automatically recalculates and shortens the task's duration by distributing the fixed effort among the assignees. This allows the 40 hours of work to be completed in less time by four people.

B. Change the Task Duration Type to Calculated Work: This is incorrect because the Calculated Work type recalculates the total work based on the duration and the number of resources. It would increase the planned hours, not shorten the duration.

C. Change the Task Constraint to Fixed Dates: This only forces the task to start and end on specific dates. It does not change the underlying calculation of how work is distributed among resources to meet that deadline.

D. Change the Task Constraint to As Soon As Possible: This is a scheduling constraint that places the task as early as possible based on dependencies. It does not influence the relationship between duration, work, and resource allocation.

1. Adobe Experience League

Workfront Documentation. "Overview of Task Duration and Duration Type." In the section "The Effort Driven Duration Type

" it states: "When you select the Effort Driven Duration Type

Workfront recalculates the duration of the task when you assign more resources to it. The Planned Hours on the task are distributed equally among the new resources and the duration is shortened." This directly supports the correct answer.

2. Adobe Experience League

Workfront Documentation. "Overview of Task Duration and Duration Type." The section "The Calculated Work Duration Type" explains: "When you select the Calculated Work Duration Type

Workfront recalculates the Planned Hours (Work) for the task using the following formula: Planned Hours = Task Duration number of resources assigned percent allocation of resources." This confirms why option B is incorrect for this scenario.

3. Adobe Experience League

Workfront Documentation. "Task Constraint overview." This document details the function of various task constraints

including "Fixed Dates" and "As Soon As Possible

" clarifying that their purpose is to define scheduling boundaries

not to manage the work-duration-resource calculation

which makes options C and D incorrect.