A wastewater SCADA modernization project needs an Events rule to deliver matching OCI resource changes somewhere useful. Which set lists the documented Events action destinations?

For the wastewater SCADA modernization Events rule, documented action destinations are Oracle Functions, Notifications topics, and Streaming streams. A Function action runs serverless work on the matched CloudEvent; a Notifications topic informs human or system subscribers; a Streaming action lands the match on a bus so multiple consumers can read and replay it. Those three destinations cover automate, inform, and fan-out patterns after a rule matches. Listing OCI Queue, email-as-a-service, and arbitrary public webhooks as first-class Events actions invents destinations Events does not expose directly—email typically rides Notifications subscriptions, and Queue is a separate producer/consumer inbox, not an Events action type. Connector Hub tasks, API Gateway deployments, and Vault secrets are useful OCI building blocks but are not the documented Events action targets for delivering matched resource-state events. Object Storage buckets, Autonomous Database, and “Service Connector only” similarly misstate the action catalog; writing results to buckets or databases is something a Function (or connector pipeline) does after delivery, not an Events action itself. Exam caveat: naming a destination that does not exist yet fails delivery—the rule picker references pre-created Functions, topics, or streams and does not fabricate them when you enable the rule. Operational check: before going live, ensure each action OCID resolves in the correct compartment and that the Events service principal (or dynamic group policies) can invoke the Function, publish to the topic, or put records on the stream.