The correct choices are Site administrators will add and remove group members, The same users will be active contributors across several projects, You need to assign permissions that apply across the entire Jira site, and Members must be able to perform bulk changes across many issues.

Groups are managed centrally in site administration so they are the right choice when site administrators will add and remove group members. Central management keeps membership consistent and reduces duplicate work across projects.

Using a group makes sense when the same users are active contributors across several projects because you can grant access once and reuse that group in multiple project permission schemes and configurations.

When you need to assign permissions that apply across the entire Jira site a group is appropriate because global permissions and product access are granted at the site level and are typically assigned to groups rather than individual project roles.

Bulk change is controlled by a global permission that affects many issues so granting that capability to a group makes it easier to allow members to perform bulk changes across many issues without managing membership in each project.

A project administrator will be in charge of changing the group membership is incorrect because project administrators cannot manage site groups. If project admins must control membership it is better to use project roles or project level membership options.

Team members require the "Work On Issues" permission to be assigned via a global group is incorrect because the Work On Issues permission is a project permission and it can be assigned via project roles or groups within a permission scheme. It does not have to be assigned only through a global group and using project roles often gives better per project flexibility.

Full AWS Practitioner Certification Question