What are the two items required to create a rule for the Oracle Cloud Infrastructure (OCI) Events Service? (Choose two.)

To create a rule in the OCI Events Service, you need to define what triggers the rule and what

happens when it’s triggered. The two required components are:

Actions (B): These specify the tasks to perform when an event matches the rule (e.g., invoking a

function, sending a notification, or streaming to a service). Without an action, the rule has no effect.

Rule Conditions (C): These define the criteria for matching events (e.g., event type like

com.oraclecloud.computeapi.launchinstance.end or resource attributes). Conditions filter which

events trigger the rule.

Why not A, D, or E?

Management Agent Cloud Service (A): This is unrelated to Events Service rules; it’s for monitoring

resources.

Install Key (D): This is used for agent installation, not event rules.

Service Connector (E): While it can work with Events Service, it’s a separate service and not a

required component of an event rule itself.

These two elements form the core of an OCI Events Service rule, enabling event-driven automation.

Reference: OCI Events Service Rules