The correct options are It provides clear visual cues about the purpose of the pull request and It classifies the type of change being proposed.

Labels add immediately recognizable visual markers on pull requests, which makes intent and status easy to scan in lists and timelines. This speeds triage and helps teams and stakeholders quickly understand context without opening every pull request.

Using a consistent label taxonomy lets the team categorize changes as bug fixes, enhancements, documentation updates, refactors, or breaking changes. This improves filtering and reporting and it supports queries for release notes and project planning.

The option It automatically assigns reviewers to the pull request is incorrect because labels do not assign reviewers on their own. Reviewers can be requested manually or by repository rules and integrations, but a label alone does not trigger reviewer assignment.

The option It automatically triggers a Cloud Build pipeline for the pull request is incorrect because adding a label does not start Cloud Build. Cloud Build triggers are configured in Google Cloud and listen for specific repository events, and labels by themselves do not invoke those triggers.

Full AWS Practitioner Certification Question