Limit available options for a radio button custom field per project and Make a custom field required on issue creation are correct.

The option to Limit available options for a radio button custom field per project is implemented by configuring a custom field context for the field. Custom field contexts allow you to scope which options are available on a per project or per issue type basis and that change only affects the field definition and its option set rather than screens or workflows.

The option to Make a custom field required on issue creation is done through the field configuration or field configuration scheme. Marking a field as required changes its validation and behavior when issues are created or edited and this is a field configuration level change rather than a screen layout change.

Assign differing default values for each issue type within a project for a radio button field is incorrect because setting different defaults per issue type usually requires creating separate contexts or adjusting screen defaults. That means you are not making a simple single field configuration change and you may also be changing contexts or screens to achieve the per issue type defaults.

Remove the priority field from all screens is incorrect because removing a field from screens modifies screen configurations and screen schemes. That action controls where a field appears and not the field configuration itself.

Full AWS Practitioner Certification Question