Create a single automation that listens for multiple issue events including "Issue Updated" "Issue Assigned" and "Issue Transitioned" applies a JQL condition priority = Critical and sends a Slack notification is the correct choice.

The single automation that listens for multiple issue events is efficient because Jira Automation supports combining multiple issue events in one rule and you can use a JQL condition such as priority = Critical to ensure only critical issues trigger the action. An event driven rule sends notifications immediately when an assignment, transition or update occurs and the Slack action delivers the alert to the team without the delay or overhead of separate rules.

Configure three separate automation rules where one uses the "Issue Assigned" trigger the next uses the "Issue Transitioned" trigger and the third uses the "Issue Updated" trigger with a JQL condition priority = Critical and a Slack message action is not ideal because it creates extra maintenance work and it increases the risk of duplicate notifications when more than one event happens in quick succession.

Implement a single scheduled automation that runs every five minutes queries for recently changed issues with priority = Critical and posts a message to Slack is incorrect because scheduled polling introduces delays and can miss the immediacy of event driven notifications and it can also complicate de-duplication when the same issue changes multiple times between runs.

Create two automation rules where the first uses the "Issue Assigned" trigger and the second uses the "Issue Updated" trigger and both check priority = Critical before sending a Slack message is incomplete because it omits the "Issue Transitioned" event and so it would not notify on state changes that are important for releases.

Full AWS Practitioner Certification Question