The correct options are Only Jira administrators can create new issue types across the instance and The default issue type for a scheme can be set to None.

In Jira the set of issue types is a system wide configuration and Only Jira administrators can create new issue types across the instance. Project administrators can manage which existing issue types are associated with a project but they cannot create new global issue types.

An issue type scheme can be left without a default and The default issue type for a scheme can be set to None. This lets projects require that users pick an issue type at creation or rely on other project specific behaviors instead of forcing a particular default.

Project administrators can add new issue types for company managed projects is incorrect because creating new issue types is performed at the instance level by Jira administrators. Project administrators can only associate or reorder existing issue types for their projects.

Issue types are always ordered with Epic first then standard types then sub task types is incorrect because ordering is determined by the issue type scheme and project configuration and it is not a fixed global rule. Sub task types are managed separately and display order can vary by scheme and UI context.

Full AWS Practitioner Certification Question