The correct options are Screen Scheme, Workflow Scheme, and Issue Type Scheme.

The Issue Type Scheme is created so the new project can have its own set or mapping of issue types that match the template. Creating a project from a template often produces a project specific Issue Type Scheme so that issue type changes do not affect other projects.

The Workflow Scheme maps workflows to issue types and templates commonly create a project level Workflow Scheme so the project can follow the template workflows independently from shared workflows.

The Screen Scheme defines which screens are used for create view and edit operations and templates typically generate a project specific Screen Scheme so the screens can be customized for the new project.

The Field Configuration Scheme is not listed as unique because Jira usually reuses a shared field configuration or associates an existing one instead of creating a new unique scheme by default.

The Notification Scheme is generally shared or applied from an existing scheme and is not automatically created as a unique scheme for each new project.

The Issue Security Scheme is only created uniquely when specific security configurations are requested and it is not a default unique scheme for a template created project.

The Permission Scheme is typically assigned from existing permission schemes and is not normally created as a project unique scheme by default.

Full AWS Practitioner Certification Question