The correct option is Screen Scheme.

Screens control which fields are shown on create edit and view operations and a Screen Scheme maps those operations to the specific screens used by the project. If Priya can set the Due Date on the create screen but cannot see it on the edit screen then the edit operation is using a different screen. Changing the project's Screen Scheme so that the edit operation uses a screen that contains the Due Date field will make the field appear when editing.

Field Configuration is about field behaviors such as whether a field is required hidden or has custom help text and it does not assign fields to the create edit or view operations. Because Priya can set the Due Date when creating issues the field is not hidden so Field Configuration is not the correct setting to change.

Issue Security Scheme controls visibility of entire issues by security level and it does not determine which fields display on an edit screen. That scheme affects who can see an issue not which fields are on a screen.

Project Permissions govern who can perform actions such as creating editing or transitioning issues and they do not control the layout of fields on screens. Since Priya already can create issues changing Project Permissions would not make the Due Date appear on the edit operation.

Full AWS Practitioner Certification Question