The correct options are Project dashboard, Issue security level, and Saved filter subscription.

Project dashboard can be controlled at the project level by assigning project roles so that specific roles can have view or edit access to a dashboard that pertains to that project.

Issue security level uses project roles to determine who can see particular issues because security levels reference roles or users to limit visibility within the project.

Saved filter subscription can target project roles so that members of a role receive scheduled filter results for the project and stay informed without individual configuration.

Application access is not correct because application access is a global user entitlement and it is managed at the site level rather than being assigned per project role.

Group membership is not correct because groups are a separate identity construct and you assign users to groups rather than assigning groups as a configuration item to a project role.

Global permission is not correct because global permissions apply across the whole instance and are granted at the global level rather than being bound to project roles.

Full AWS Practitioner Certification Question