The correct options are Administer sprints, Modify issues, View the project and Schedule issues into sprints.

Administer sprints is required because closing an active sprint and performing sprint level operations on the board requires the permission to manage or administer sprints for the project or board. Without this permission a project administrator cannot complete the sprint workflow even if they can edit issues.

Modify issues lets Riya update issue fields, set resolutions, or change statuses as needed to clear or prepare the remaining work before the sprint finishes. Being able to edit the issues that remain is a core requirement for finishing the sprint cleanly.

View the project is needed so Riya can access the project, open the sprint board, and see the issues that need action. You cannot administer sprints or modify issues in a project you cannot view.

Schedule issues into sprints allows Riya to move unresolved work into the backlog or into a future sprint when closing the current sprint. Scheduling is a distinct permission that controls placing issues into sprint containers and is necessary for resolving the three remaining issues without moving them across projects.

Transition issue workflow is incorrect because altering workflow configuration or the scheme is not required to close a sprint or to move issues into different sprint states. Closing a sprint usually requires scheduling and edit permissions rather than changing the workflow itself.

Allow moving issues between projects is incorrect because moving issues across projects is not a minimum requirement for finishing a sprint inside the same project. That permission grants a higher level capability that is not needed to resolve or reschedule the remaining issues for sprint closure.

Full AWS Practitioner Certification Question