The correct answers are Users can revert any bulk edit they perform and Bulk edit can set the resolution field directly for multiple issues.

The statement Users can revert any bulk edit they perform is not true because bulk change operations do not provide a single undo button. Changes made by a bulk edit are committed and you must run additional bulk operations, use automation or restore from backups to reverse them. The issue history and audit log record the changes but they do not automatically revert the edits.

The statement Bulk edit can set the resolution field directly for multiple issues is not true because the Resolution field is normally set by workflow transitions rather than by the plain Edit bulk action. To set resolution for many issues you typically perform a bulk Transition that sets the resolution or use automation, scripting, or apps that explicitly allow changing resolution in bulk.

The Transition Issues project permission is required to change an issue status is not a valid choice because that statement is actually correct. Project participants need the Transition Issues permission to perform transitions and change an issue status.

You can change an issue type using either the Edit Issues action or the Move Issues action is not a valid choice because that statement is correct in practice. You can edit the Issue Type field when it is available on the edit screen and you can also use Move Issues to change type when moving between projects or when scheme restrictions apply.

The Edit Issues bulk operation can modify custom field values is not a valid choice because that statement is correct. The Edit Issues bulk operation can update custom fields that are present on the edit screen and are applicable to the selected issue types.

Full AWS Practitioner Certification Question