Before enabling an Events rule that should invoke a Function and also notify a topic, what must already be true about those destinations?
Select an answer to reveal the explanation.
Short Explanation
Create the Function, topic, or stream—and the IAM that lets Events deliver—before you point a rule at them. The picker will not invent the destination. A disabled action stages safely; a missing OCID fails.
Full Explanation
Before enabling an Events rule that should invoke a Function and also notify a topic, those destinations must already exist. The rule’s action picker references an existing Oracle Function, Notifications topic, or Streaming stream by OCID; it does not create them when you save or enable the rule. IAM that allows Events to deliver to each destination must also be in place, or matches will fail at delivery time even when filters are perfect. Claiming Events will auto-create a Function and topic from the rule name when you enable the rule invents provisioning behavior the service does not have. Saying only the stream may be pre-created while Functions and topics spawn lazily on first match is equally unsupported—all three action types require pre-existing resources. Treating destinations as optional placeholders whose OCIDs Events fabricates at delivery time would break reliable automation and is not how actions are configured. Exam caveat: a rule can be created with actions staged or disabled while destinations are still being built, but enabling delivery against a deleted or wrong-compartment OCID fails silently from the emitter’s perspective—uploads still succeed while automation does not. Operational check: create the Function and topic first, attach policies, select both as actions on the rule, emit a test event, and verify Function invocation metrics and a Notifications delivery before relying on production traffic.