1Z0-1111-26 Exam Dumps and Practice Questions

In distributed tracing within OCI APM:

Root span (C): The first span in a trace, representing the entry point of a user request (e.g., an HTTP request from a browser). It has no parent span and initiates the chain of subsequent spans across services.

Why not A or B?

Ajax call (A): A type of request, not a span term.

Trace ID (B): A unique identifier for the entire trace, not a span.

The root span is foundational to tracing a request's journey.

To investigate user activity and REST API calls over the last six hours, the OCI Audit service is the appropriate tool.

Audit (E): This service automatically records all API operations (including REST API calls) performed on OCI resources. It provides detailed logs with user details, timestamps, and actions, ideal for security and compliance investigations. You can filter audit logs by time range (e.g., last six hours) and user attributes.

Why not A, B, C, or D?

Notifications (A): Sends alerts but doesn't store or analyze API call details.

Service Connectors (B): Moves data between services, not for auditing.

Management Agent (C): Collects metrics/logs from resources, not API audit data.

Logging (D): Handles application and system logs, not API activity tracking.

Audit logs are retained for 90 days by default, making this a perfect fit.

OCI Audit records API operations and related activity across supported OCI services. The Audit configuration supports a retention period of up to 365 days. The setting is defined at the tenancy or root-compartment level and applies across all regions and compartments in that tenancy. It cannot be configured independently for individual compartments. Audit records are also not retained indefinitely by the Audit service. If an organization needs to preserve them for longer than 365 days, it should archive the records externally, commonly by routing Audit logs to Object Storage through OCI Logging and Service Connector Hub. Therefore, the correct statements are that Audit logs have a maximum retention of 365 days and that retention is controlled through a tenancy-level setting. Oracle documentation

OCI Notifications implements a publish-subscribe messaging model. A topic is a communication channel to which producers publish messages. Each topic can have one or more subscriptions, and every subscription identifies an endpoint that receives messages published to that topic. Supported endpoint types include email, SMS, HTTPS custom URLs, OCI Functions, and supported messaging integrations. Topics do not define the message format and are not used to create network-security policies. Similarly, subscriptions are not groups of resources monitored by OCI Monitoring. Monitoring alarms, Events rules, service connectors, applications, or users can publish messages to a topic, after which Notifications delivers those messages to the topic's subscriptions. Therefore, subscriptions represent receiving endpoints, while topics provide the shared communication channel through which messages are distributed. Oracle documentation

Apdex measures perceived user satisfaction with the response times of applications and services. OCI Application Performance Monitoring compares observed request durations with configured Apdex thresholds and classifies the resulting experience as satisfied, tolerating, or frustrated. These classifications contribute to a decimal score between 0 and 1, where a higher value indicates that a greater proportion of requests delivered an acceptable experience. Apdex thresholds are configured at the APM Domain level and may be applied to spans matching specified patterns. The measurement is not a CPU-utilization percentage, a storage-capacity value, or a simple transaction count. Although those measurements may help diagnose application performance, they do not directly represent user satisfaction. Therefore, user satisfaction based on application response-time thresholds is the correct description. Oracle documentation