The subtask will count as a change to sprint scope yet it will not be represented on the burndown chart.

Adding a subtask to an issue that is already in an active sprint increases the sprint scope because there is now an additional work item assigned to that sprint. The burndown chart in a board that burns down estimates when work is completed only reflects estimate changes when work is finished, so creating a new subtask does not immediately change the burndown until the subtask s estimate is completed or consumed.

The subtask will not change the sprint scope and it will be shown on the burndown chart is incorrect because adding a new subtask does change sprint scope. The statement also wrongly assumes the burndown will immediately reflect the new work item when the board is configured to burn down completed estimates.

The subtask will not alter the sprint scope and it will not appear on the burndown chart is incorrect because it denies the scope change that occurs when a new work item is added to an active sprint. The part about not appearing on the burndown is only half true for this board configuration.

The subtask will update the sprint scope and it will appear on the burndown if the board uses remaining estimate or time tracking fields is incorrect in this scenario because the board is configured to burn down estimates when work is completed. That configuration does not show the new subtask on the burndown until the estimate is completed or the completed-estimate metric is affected.

Full AWS Practitioner Certification Question