The correct option is Milestones provide a progress focused roadmap that tracks grouped issues and pull requests toward a goal. This aligns with the team’s plan to bundle roughly 18 issues and 4 pull requests into time bound targets for the next 45 days and to see how close each target is to completion.

Milestones in GitHub let you group issues and pull requests under a named goal with a due date. They show a progress bar and counts of open and closed items which gives the team an at a glance view of completion status. You can filter to see what remains or what is done and you can adjust scope as priorities shift, which makes milestones well suited for release planning over a fixed timeframe.

Milestones enforce consistent coding standards across the repository is incorrect because milestones track work and progress rather than enforce rules. Coding standards are typically enforced by linters and formatting tools along with workflows, branch protections, and code review policies.

Milestones run CI and CD workflows for builds and deployments is incorrect because builds and deployments are handled by automation tools such as GitHub Actions or other CI systems. Milestones only organize and display progress for issues and pull requests.

Milestones let multiple developers edit the same file in real time is incorrect because Git and GitHub coordinate changes through commits, branches, and merges rather than real time co editing. Real time editing is not a milestone feature.

Full AWS Practitioner Certification Question