Browse Projects, Edit Issues, and Schedule Issues are correct.

Browse Projects is required so Maya can open and view the project board and the active sprint. Without the ability to browse the project she cannot access the sprint to perform any closing actions.

Edit Issues lets her change issue fields and make the updates needed when resolving or reassigning issues before the sprint is closed. Editing is needed to adjust fields such as the Sprint field or other details for the remaining tickets.

Schedule Issues allows changing an issue's backlog placement and its sprint assignment so she can move unresolved work out of the active sprint or schedule it for the next sprint. This permission is therefore necessary to handle unresolved issues when completing the sprint.

Manage Sprints is not correct because the minimum actions to complete the sprint are covered by browsing, editing, and scheduling permissions rather than relying on a separate manage sprints flag for this scenario.

Move Issues is not correct because moving issues between projects is not required to complete the active sprint. Changing sprint assignment within the same project is handled by the schedule and edit permissions.

Transition Issues is not correct because changing workflow status is not a minimum requirement to close the sprint. Closing a sprint focuses on sprint assignment and backlog placement rather than on performing workflow transitions.

Full AWS Practitioner Certification Question