The correct option is Maintain because it allows release coordinators to triage issues, apply labels and milestones, and guide pull request workflows while withholding admin and destructive capabilities such as deleting the repository or administering security and team access.

This role is designed for people who manage a repository day to day. It enables full issue and pull request management including labeling, milestone management, and merging or coordinating merges. It also allows non sensitive repository management like releases and some settings while preventing actions reserved for administrators such as changing visibility, deleting or transferring the repository, or managing teams and security settings.

The Triage role focuses on managing issues and pull requests without write access and it cannot merge pull requests or perform broader repository management, so it does not meet the coordination and workflow needs described.

The Write role grants push access and permits merging pull requests, yet it does not include the wider non sensitive repository management capabilities that coordinators typically need, and it is not the role GitHub recommends for repository managers who must avoid admin powers.

The Read role is view only and cannot triage, label, milestone, or guide pull requests, so it clearly does not satisfy the requirements.

Full AWS Practitioner Certification Question