The correct options are Iteration Burndown Chart, Burnup Chart, Velocity Report, and Iteration Summary Report.

These four reports are tied to sprint or iteration data and so they appear only on a Scrum board in an organization-managed project. Scrum boards define sprints and track completed work and the reports need that sprint context to produce meaningful metrics.

The Iteration Burndown Chart shows remaining work within a sprint and depends on sprint start and end dates and on sprint scope. Because it measures work remaining per iteration it is only available where sprints are defined, which is the Scrum board in an organization-managed project.

The Burnup Chart visualizes scope changes and work completed across a sprint or release and it requires sprint or version boundaries to show progress versus scope. That dependence on iteration or release context is why the Burnup Chart is available only on the Scrum board.

The Velocity Report summarizes the amount of work completed per sprint over recent iterations and it uses completed sprint data to calculate averages. That sprint focus makes the Velocity Report a Scrum board only report in organization-managed projects.

The Iteration Summary Report gives an overview of what was completed, moved, or carried over during a sprint and it explicitly reports on one sprint at a time. For that reason the Iteration Summary Report is available only on the Scrum board.

Control Chart is incorrect because it focuses on cycle time and throughput metrics and it is not limited to Scrum boards. The control chart can be used with other board types where cycle time data is relevant.

Cumulative Flow Diagram is incorrect because it shows work in each workflow state over time and it is commonly available across board types. It is not exclusive to Scrum boards and therefore it is not one of the reports that appear only on the Scrum board in an organization-managed project.

Full AWS Practitioner Certification Question