The correct options are Counts comparing proposed pull requests and merged pull requests for the selected period, Lists of issues that were opened and closed during the chosen timeframe, The number of commits to the default branch and the contributors who made them in that period, and A concise overview that summarizes recent repository activity in the selected window.

The Pulse page includes clear pull request activity metrics for the chosen window. You can quickly see how many pull requests were opened compared to how many were merged so you can gauge review and merge throughput.

It also reports issue activity for that timeframe. You can review which issues were opened and which were closed so you can understand triage and resolution pace.

Pulse highlights commit activity on the default branch for the selected window and shows who contributed those commits. This helps you identify the volume of changes and the people involved.

All of this is presented in a high level summary so you get a quick snapshot of recent repository activity without drilling into multiple pages.

Total number of repository forks is not part of Pulse. Fork counts appear on the repository header and in network insights rather than on the Pulse activity summary.

A list of unresolved review conversations across pull requests is not shown on Pulse. Unresolved conversations are managed within individual pull requests or code review views and are not summarized on the Pulse page.

Full AWS Practitioner Certification Question