Users can translate project components, Users can translate the locked custom field, and Users are unable to translate the Resolution field are correct.

Users can translate project components is correct because components are project scoped and their names and descriptions can be localized within a company managed project when the localization features are used.

Users can translate the locked custom field is correct because custom field option labels and values can be localized even when the field configuration is locked, provided the localization or translation workflow for custom field options is available to the project administrators or translators.

Users are unable to translate the Resolution field is correct because Resolution is a system field with globally managed values and it is not provided as a translatable, project scoped field in company managed project localization workflows.

Users can translate issue types is incorrect because issue types are global scheme entities and they are not translated on a per project basis in company managed projects.

Users can translate priorities is incorrect because priorities are shared global entities and priority names are not localized per company managed project through the normal translation UI.

Users can translate statuses is incorrect because statuses are part of workflow definitions and they are managed globally or by workflow scheme rather than being translatable per project in company managed projects.

Full AWS Practitioner Certification Question