In OCI APM, span context (e.g., Trace ID, Span ID) is propagated across services to track requests.

In HTTP header (B): Span context is embedded in HTTP headers (e.g., X-B3-TraceId) during transfer

between services. This allows APM to correlate spans across distributed systems for a single user

request.

Why not A, C, or D?

Service boundaries (A): This is a conceptual term, not a location for data.

HTTP call (C): Too vague—“HTTP call” isn’t a specific storage location.

Browser and microservices (D): Context originates here but is transferred via headers, not stored

locally during transit.

This follows the OpenTracing standard used by OCI APM.

Reference: APM Traces and Spans

Logging Analytics is a core O&M service:

Monitor, aggregate, index, and analyze log data (A): Collects logs from OCI and external sources,

indexes them for search, and provides analytics (e.g., clustering) to monitor and troubleshoot

systems.

Why not B or C?

B: Log centralization occurs, but “subscription model” isn’t a feature.

C: Resource creation is an Events Service use case, not Logging Analytics.

This is its primary observability role.

Reference: Logging Analytics Overview

In OCI Stack Monitoring, once Management Agents are deployed and resources (e.g., databases,

applications) are discovered, the immediate next step is the collection of metric data.

Metric data is immediately collected (A): Management Agents are lightweight processes that

continuously collect performance and health metrics from discovered resources (e.g., CPU usage,

memory utilization) and send them to OCI services like Monitoring or Stack Monitoring. This data

becomes available for visualization and analysis right after discovery.

Why not B, C, or D?

Alarm rules (B): Alarms are configured separately in the OCI Monitoring service and only trigger after

metric data is collected and thresholds are breached—not an immediate post-discovery action.

Resource discovery (C): Discovery happens before this stage, as the question assumes resources are

already discovered. Agents don’t rediscover resources post-setup.

Notifications (D): Notifications require separate configuration (e.g., via the Notifications service) and

are not an automatic outcome of agent setup and discovery.

This aligns with Stack Monitoring’s purpose of providing real-time visibility into resource

performance.

Reference: Stack Monitoring Overview, Management Agent

Management Agents require group membership and policies to interact with OCI services:

AgentUsersGrp (A): A predefined dynamic group for all Management Agents in a tenancy. With an

attached policy granting upload permissions (e.g., allow dynamic-group AgentUsersGrp to use

discovery-service-family in tenancy), agents can send data to the discovery service for resource

detection.

Why not B, C, or D?

B and C: Specific to Stack Monitoring roles, not general agent uploads.

D: A generic name, not a predefined OCI group.

AgentUsersGrp is the standard for this purpose.

Reference: Management Agent Policies

The Observability Lakehouse in Operations Insights is a data repository for operational analytics:

Enables custom analytics (B): Supports trending (e.g., usage patterns), forecasting (e.g., resource

needs), capacity planning, and workload profiling using advanced analytical tools, enhancing

resource optimization.

Allows Oracle Enterprise Manager’s data (D): Integrates operational data from Enterprise Manager

(e.g., database metrics) for use cases like performance analysis and anomaly detection.

Why not A or C?

Statistical analysis of AI data (A): Too vague; Lakehouse focuses on operational data, not AI-specific

stats.

Identifies future resource usage (C): Partial benefit of B, but not a standalone feature.

These capabilities improve operational decision-making.

Reference: Operations Insights Observability Lakehouse

OCI Application Performance Monitoring (APM) provides tools to monitor application performance:

Distributed Tracing (A): Tracks requests across microservices, showing latency and dependencies via

traces and spans.

Real User Monitoring (C): Captures real user interactions with web applications (e.g., page load

times) using a Browser Agent.

Why not B or D?

Capacity Planning (B): Available in Operations Insights, not APM.

Java Management (D): Not a feature of APM; Java Agent is a tool, not a feature.

These features align with APM’s focus on performance and user experience.

Reference: APM Overview

A Log Source in Logging Analytics defines how logs are collected and processed:

Which Parsers to use (A): Specifies the parsers (e.g., Syslog, JSON) that extract fields from logs,

enabling structured analysis.

Where to find Logs (C): Defines the log location (e.g., file path /var/log/messages, database

connection string), directing the collection process.

Why not B or D?

Where to store Log data (B): Storage is managed by Logging Analytics, not defined in the Source.

Which Management Agents to use (D): Agents are associated with Entities, not specified in the

Source.

These elements configure log ingestion effectively.

Reference: Logging Analytics Log Sources

Operations Insights provides:

Capacity Planning (A): Forecasts resource needs based on historical trends and scenarios.

Exadata Insights (D): Analyzes Exadata system performance and capacity.

Why not B or C?

Database Fleet Monitoring (B): A goal, not a named capability; covered under broader features.

Entity Topology Viewing (C): More aligned with Stack Monitoring, not Operations Insights.

These capabilities optimize resource management.

Reference: Operations Insights Overview

SQL Warehouse in Operations Insights categorizes SQL performance:

Degraded (A): SQL statements with declining performance over time (e.g., increased latency),

indicating potential issues.

Plan changes (C): SQL statements with altered execution plans, impacting performance or resource

use.

Why not B or D?

Climbing (B): Not a standard category; possibly a misnomer.

Efficient (D): Positive performance isn’t a focus category.

These help identify and resolve SQL issues.

Reference: SQL Warehouse Categories

For repeated notifications in OCI Monitoring:

Repeat notification was not enabled while creating the Alarm (B): The “Repeat Notification” option

must be enabled in the alarm definition, specifying an interval (e.g., every 5 minutes). If disabled,

only one notification is sent when the alarm fires, explaining the subscriber’s issue.

Why not A, C, or D?

A: False; OCI supports repeat notifications if configured.

C: Trigger condition is mandatory for any alarm; this isn’t the issue.

D: Notification frequency isn’t tied to metric streams, only the repeat setting.

Repeat Notification ensures ongoing alerts.

Reference: Creating Alarms