The correct options are The field must be reusable across many projects and Users must be limited to choosing a single value from the field.

The field must be reusable across many projects points to a custom field because custom fields can be defined globally and then applied across many projects and contexts. Components are project scoped so they are not suitable when the attribute must be shared and managed across multiple projects.

Users must be limited to choosing a single value from the field describes a single-select custom field option which enforces a one‑choice selection. Custom fields can be created as single choice fields so users can pick only one value while keeping that same field available in many projects.

Selecting a value will automatically assign the issue to a specific user is incorrect because automatic assignment is a behavior provided by components through a component lead or default assignee and by automation rules, not an inherent reason to prefer a custom field.

Project administrators will configure and manage the field within each project is incorrect because custom fields are created and configured at the global administration level and then associated to projects through contexts and screens, while components are what project administrators manage per project.

Full AWS Practitioner Certification Question