The correct answer is: A workflow status property is configured to restrict attachments.

A workflow status property can prevent certain operations while an issue remains in a particular status. If the Obsolete status has a property that disables or blocks attachments then users will be able to add files on other issues but not when an issue is in Obsolete. That behaviour fits Priya's scenario because the restriction applies only while the issue is in that status.

A workflow transition property is configured is incorrect because transition properties apply during the transition itself and not to actions performed while the issue is in a status. A transition property would not cause attachments to be blocked when an issue is sitting in Obsolete.

The project permission scheme does not grant the Attach Files permission is incorrect because a missing attach permission would block attachments across the project for the affected users. The problem described only occurs for issues in a single status so a project permission issue is unlikely.

The attachment field is absent from the issue screen is incorrect because hiding a field on the screen would affect visibility for all issues on that screen and would not selectively block attachments only when an issue is in the Obsolete status. Attachments can also be added by other means such as drag and drop or the API.

A workflow condition prevents the action is incorrect because workflow conditions control who can execute transitions and when transitions are available. Conditions do not prevent users from performing actions like adding attachments while the issue remains in a given status.

Full AWS Practitioner Certification Question