This configuration correctly separates the work effort from the time span. The Task Constraint of "Must Start On" locks the start date to September 23. Planned Hours represents the total amount of work or effort required, which is 10 hours. Duration defines the total working timeframe from the task's start to its completion, which is 2 weeks. This allows the 10 hours of work to be distributed across the 2-week period as needed, fulfilling all requirements of the scenario.

A. This option incorrectly assigns the time span (2 weeks) to "Planned Time" and the work effort (10 hours) to "Duration," which reverses their intended meanings in Adobe Workfront.

C. This option uses incorrect terminology. "Issue Duration" is a field specific to Issues, not Tasks. While a "Start Date" can be set, a "Must Start On" constraint is the correct mechanism to enforce it.

1. Adobe Workfront Documentation

"Overview of Task Constraints": This document explains that the "Must Start On" (MSO) constraint forces a task to begin on the specified date. This directly supports the use of this constraint for the September 23 start requirement. (See section: "Must Start On").

2. Adobe Workfront Documentation

"Overview of Planned Hours": This source defines Planned Hours as "the amount of time you estimate it will take to complete a work item." This confirms that the 10 hours of work effort should be entered in the Planned Hours field. (See section: "How Workfront uses Planned Hours").

3. Adobe Workfront Documentation

"Duration and Duration Type overview": This article clarifies the distinction between Duration and Planned Hours. It states

"Duration is the amount of time (in business days) that it will take for a work item to be completed

from the start date to the completion date." This validates setting the Duration to 2 weeks to represent the total time span. (See section: "Understanding the difference between Duration and Planned Hours").