The correct answer is Cumulative flow diagram.

The Cumulative flow diagram shows the amount of work in each workflow state as stacked bands over time and it makes it easy to see how work accumulates and flows between states. The width of each band indicates work in progress for that state and the trend of the bands lets you calculate throughput and estimate cycle time. The diagram also provides both numeric counts and a qualitative visual that highlights historical and current bottlenecks when bands widen or constrict.

The Cumulative flow diagram therefore meets all parts of the requirement because it shows per state WIP, supports throughput and cycle time analysis, and reveals where and when bottlenecks occurred.

Velocity chart is focused on how much work the team completes per sprint and it is useful for capacity forecasting. It does not show work split by workflow state across time so it will not reveal state level bottlenecks in the same way.

Version burndown tracks remaining work for a version or release over time and it helps monitor scope and progress. It does not present work by workflow state or provide the stacked time based view needed to spot where work is queuing.

Control chart displays cycle time distribution and trends for individual issues and it can help with calculating average cycle time and detecting variability. It does not however show how much work is in each workflow state as a stacked timeline so it will not by itself reveal state level bottlenecks visually.

Sprint health report gives a quick summary of sprint progress and high level health indicators and it is useful for status checks. It does not provide the detailed, time based breakdown of WIP by workflow state that is required to analyze historical and current bottlenecks.

Full AWS Practitioner Certification Question