The correct answer is Add the aud-grp group to the Reviewers project role in the project "SHIFT".

Adding Add the aud-grp group to the Reviewers project role in the project "SHIFT" gives the aud-grp the Browse Projects permission for that specific project. The Auditors project role already grants Create issues and Edit issues in the shared permission scheme. Once aud-grp has Browse Projects for the SHIFT project they will be able to edit issues there because they will have both the browse and edit permissions within that project.

Add the Auditors project role to the Browse Projects permission is incorrect because changing which role holds Browse Projects in the shared permission scheme would affect every project that uses that scheme. The requirement is to enable editing only for aud-grp in the SHIFT project without changing permissions for other projects.

Add the rev-grp group to the Auditors project role in the project "SHIFT" is incorrect because rev-grp is a different group and adding it to Auditors does not grant aud-grp any additional rights. The problem is that aud-grp lacks the Reviewers role membership in SHIFT.

Set aud-grp as a default member of the Reviewers project role in system configuration is incorrect because making aud-grp a default member applies that membership across all projects. The question asks for a change scoped only to the SHIFT project so a project level role assignment is the right approach.

Full AWS Practitioner Certification Question