Field Configuration of the project "PeopleCare" is correct.

The most likely cause is that the Issue Security field has been hidden or its visibility altered in the project field configuration so the security level is not being set on new issues. When the Issue Security field is hidden by the field configuration the create screen cannot apply the intended security selection and issues may therefore be created without the confidential level and become visible to all users.

Field configurations control whether a field is visible or hidden for a project and this can override what appears on screens. If the Issue Security field is hidden at the field configuration level then the issue security scheme cannot enforce the intended restriction for new issues even though the scheme and permissions are configured correctly.

Issue Type Screen Scheme of the project "PeopleCare" is incorrect because screen schemes only associate screens with issue types and do not by themselves hide a field that has been turned off in the field configuration. A missing field on a screen could be caused by the screen, but the symptom described is more consistent with the field being hidden by configuration.

Issue Security Scheme of the project "PeopleCare" is incorrect because the security scheme and its levels are already defined and mapped. The scheme would not allow everyone to see issues if the security level was actually being applied to new issues as intended.

Global permissions is incorrect because global permissions control broad actions like logging in or creating projects and they do not directly make every newly created issue visible regardless of issue security levels.

Permission Scheme of the project "PeopleCare" is incorrect because the permission scheme shown grants Browse Projects to any logged in user which is expected for the project, but issue visibility is governed by issue security levels and field visibility rather than the project permission scheme.

Full AWS Practitioner Certification Question