In Adobe Workfront, the Critical Path feature in the Gantt chart helps a project manager understand which tasks can affect the project timeline when delays occur. Adobe documentation explains that Workfront automatically identifies a sequence of tasks that have the potential to impact the project's timeline and flags those tasks as Critical Path tasks. It also states that any delay in a task on the Critical Path directly impacts the project's projected completion date because there is no float on the critical path. In the Gantt chart, Critical Path tasks are visually marked, making it easier for the project manager to see which delayed work can affect successor or downstream tasks and the overall schedule. Actual Dates show when work actually started or completed, and % Complete shows progress on a task, but neither is specifically designed to show schedule impact across dependent tasks. Therefore, the correct answer is C. Critical Path.

When a user updates the Commit Date to a date later than the original planned date in Adobe Workfront, the Planned Completion Date of the task is automatically updated to reflect the new commit date. This feature ensures that the timeline is adjusted based on the most current commitment by the task assignee, which can then impact downstream tasks and the overall project schedule.
This change streamlines project planning and helps keep task dependencies aligned with realistic completion expectations.

In Adobe Workfront, the correct action is to set the task constraint to Fixed Dates. Adobe's documentation explains that task constraints control when tasks can start or finish in a project plan. Depending on the constraint selected, a project manager may need to specify a planned start date, a planned completion date, or both dates. The Fixed Dates constraint is specifically used when a task must occur between exact dates, because Workfront requires both the Planned Start Date and Planned Completion Date when this constraint is selected. Adobe also states that when Fixed Dates is used, the task duration is calculated from the difference between those two planned dates. A predecessor only controls dependency order and does not guarantee September 10 through September 17. Setting the duration to one week defines only length, not the exact calendar dates. Therefore, to force the task to take place from September 10 through September 17, the correct answer is A. Set the Task Constraint to Fixed Dates.

In Adobe Workfront, risks associated with a project should be logged as part of the project business case. The "Risk" section within the business case allows stakeholders to document any potential threats to the project timeline, scope, or resources. Identifying this risk as a "schedule" risk helps communicate the potential delay to the project stakeholders and allows it to be tracked and mitigated effectively.

In Adobe Workfront, Scrum supports this hybrid approach because teams can keep structured project planning in Workfront while managing selected tasks as agile stories within iterations, commonly called sprints. Adobe documentation explains that Scrum teams use a backlog and then plan an iteration by selecting tasks or issues from that backlog. Adobe also notes that many organizations use the words sprint and iteration interchangeably, and that iteration planning occurs after the backlog has been groomed and prioritized. This allows planned project tasks to remain part of a Workfront project while the team manages execution through sprint-based agile practices. Waterfall is structured and sequential, but it does not provide sprint-based task management. Kanban provides flexible visual flow through a board, but it is not centered on fixed sprint or iteration planning. Therefore, the Workfront methodology that combines structured planning with sprint flexibility is A. Scrum.