The correct options are To group related issues and pull requests under one release target and To see how much work remains toward a specific goal or release.

Milestones let maintainers associate issues and pull requests with a single named goal such as a version or release. This creates a central place to plan scope and track the set of related work which improves visibility and coordination across the team.

Milestones also provide a clear view of progress with counts and a progress bar for open and closed items. This makes it easy to assess remaining work toward the goal and to adjust priorities so the target can be met.

To automate repository workflows is incorrect because automation is handled by GitHub Actions while milestones are used for grouping and tracking work.

To manage and audit third party dependencies is incorrect because dependency management and auditing are provided by the dependency graph and Dependabot rather than milestones.

To declare that the repository is currently stable is incorrect because stability is communicated through releases, tags, or documentation while milestones are for organizing and tracking progress.

Full AWS Practitioner Certification Question