1Z0-1111-26 Sample Questions & Answers

Monitor cloud environments with metrics and alarms · Explain the key concepts of Monitoring Service

• A

  absent()

• B

  count()

• C

  rate()

• D

  increment()

Monitor cloud environments with metrics and alarms · Configure Alarm Definitions using best practices

• A

  The alarm evaluates only the first trigger rule unless the && operator joins both rules in a single MQL string, and Trigger delay minutes adjusts the PostMetricData ingestion frequency.

• B

  The alarm is evaluated once every minute (1,440 times per day) at a fixed 1m resolution regardless of the 5m query interval, and it transitions from OK to FIRING only after a trigger rule condition continuously holds true for its configured Trigger delay minutes (pendingDuration).

• C

  The alarm evaluates at a resolution equal to Trigger delay minutes (every 3 minutes for CRITICAL and every 5 minutes for WARNING) and requires the oci monitoring alarm-state reset CLI command to return to OK.

• D

  The alarm is evaluated once every 5 minutes (288 times per day) to match the 5m query interval, and it transitions immediately to FIRING on the first breached evaluation before waiting pendingDuration minutes to send the notification.

Monitor cloud environments with metrics and alarms · Configure Alarm Definitions using best practices

• A

  Choosing whether to group notifications across all tracked metric streams or split notifications per metric stream

• B

  Routing alarm status changes directly to an OCI Queue channel as a native alarm destination

• C

  Writing firing alarm payloads directly to an OCI Object Storage bucket without configuring a destination topic or stream

• D

  Attaching an inline Python remediation script that executes inside the Monitoring service whenever the alarm transitions to FIRING

• E

  Selecting either an OCI Notifications topic or an OCI Streaming stream as the destination for alarm messages

Monitor cloud environments with metrics and alarms · Configure Alarm Definitions using best practices

• A

  False

• B

  True

Respond to cloud resource changes in real-time · Determine Event Structure, Event Types and Rules

• A

  The eventID field is a unique UUID (not an OCID), cloudEventsVersion is set to 0.1, and the mandatory extensions element in OCI's CloudEvents implementation holds the originating compartment OCID (or tenancy OCID if emitted from the root compartment).

• B

  The data object forms the outer envelope containing cloudEventsVersion: "2.0", while the inner envelope object contains the resource payload.

• C

  The eventID field contains a globally unique OCID formatted as ocid1.event.oc1.., and extensions is an optional field that is omitted unless free-form tags are attached.

• D

  The source field stores the originating compartment OCID, eventTime is formatted in Unix epoch milliseconds, and eventType follows the syntax oci. . . .

Respond to cloud resource changes in real-time · Determine Event Structure, Event Types and Rules

• A

  Create separate Events rules for event types, attributes, and tags, and chain them sequentially because a single Events rule can only evaluate one condition type.

• B

  Write a Monitoring Query Language (MQL) predicate inside the Events rule condition block using curly-bracket dimension filters {tag.costCenter = "prod"}.

• C

  Define rule conditions that match on Event Type (formatted as com.oraclecloud. . ), and combine them with Attribute filters and Filter Tag conditions so only events satisfying all specified condition types trigger the rule actions.

• D

  Attach a Logging Analytics ingest-time lookup and parser to the Events rule so that non-matching com.oraclecloud. . events are dropped prior to evaluation.