The correct answer is: URLs that contain the previous project key will redirect to the new project key.

When a project key is changed Jira updates the issue keys and creates redirects from the old issue URLs to the new keys. This means bookmarks and external links that reference the previous key will resolve to the issues under the new key and users will not generally lose access to those linked issues.

Users must edit their saved filters to use the new project key is incorrect because saved filters and JQL queries are resolved by Jira using internal identifiers and the URL redirects preserve access. Most filters do not require manual rewriting after a key change.

Some dashboards and reports will display errors is incorrect in general because gadgets and reports that reference issues or filters will normally continue to work due to the redirects and the underlying issue identifiers. Only very unusual custom integrations that rely on hard coded assumptions might need attention.

A new project can be created using the previous project key is incorrect because the previous key remains associated with the project history and the redirect behavior. You cannot simply reuse the old key without first addressing the existing project and redirect mapping.

You must manually update Confluence Jira issue macros to reference the new key is incorrect because Confluence macros that link to Jira issues will follow the same redirects and will continue to display the linked issues. Manual updates are not normally required for standard issue macros.

Full AWS Practitioner Certification Question