Oracle Cloud Infrastructure Observability Professional Free Sample Questions

Define the pillars of Observability · Summarize on OCI Observability and Management Services

1. A

   OCI Connector Hub serves as the primary time-series database for metrics and traces, whereas OCI Notifications performs machine-learning log clustering.

2. B

   Monitoring watches system state against predefined conditions, whereas observability combines metrics (OCI Monitoring), logs (OCI Logging and Logging Analytics), and distributed traces (OCI Application Performance Monitoring) to debug unknown failure modes and optimize performance.

3. C

   OCI Stack Monitoring replaces Application Performance Monitoring by capturing Real User Monitoring browser spans without deploying agents on underlying hosts.

4. D

   Observability relies exclusively on CloudEvents messages in OCI Events to trace microservice requests, while OCI Monitoring stores unstructured application logs for long-term archival.

Define the pillars of Observability · Summarize on OCI Observability and Management Services

1. A

   Use OCI Events rules with an OCI Functions action for real-time bucket state changes; OCI Logging with OCI Connector Hub to route service logs to Object Storage and OCI Logging Analytics; and OCI Stack Monitoring with Management Agents to monitor the WebLogic and database stack.

2. B

   Use OCI Monitoring absence alarms to detect bucket deletions, OCI Events to stream VCN Flow Logs into Metrics Explorer, and OCI Application Performance Monitoring browser agents to discover WebLogic and Oracle Database topologies.

3. C

   Use OCI Connector Hub as an event generator for bucket state changes, OCI Application Performance Monitoring to archive VCN Flow Logs into Object Storage, and the Unified Monitoring Agent to map WebLogic application topologies in Metrics Explorer.

4. D

   Use OCI Audit with a saved search to invoke OCI Functions directly, OCI Stack Monitoring to transfer VCN Flow Logs to Object Storage, and OCI Logging Search to perform NLP semantic clustering on database health metrics.

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

1. A

   Each aggregated data point is assigned a unique metric OCID at the end of the 5-minute window; for alarm queries the resolution automatically scales to match the pendingDuration value.

2. B

   Each aggregated data point timestamp marks the end of the 5-minute window (for example, 02:05 represents raw points from 02:00:n to 02:05:00); for metric queries the resolution defaults to the 5m interval, whereas for alarm queries the only valid resolution is 1m.

3. C

   Each aggregated data point timestamp marks the start of the 5-minute window (for example, 02:00:00 covers 02:00:00 to 02:05:00); the resolution defaults to 1m for metric queries and 5m for alarm queries.

4. D

   Each aggregated data point timestamp marks the midpoint of the 5-minute window; both metric queries and alarm queries enforce a fixed 60m resolution unless overridden in the dimension filter.

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

1. A

   absent()

2. B

   count()

3. C

   rate()

4. D

   increment()

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

1. 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.

2. 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).

3. 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.

4. 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

1. A

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

2. B

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

3. C

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

4. D

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

5. E

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