OCI 1Z0-1042-25 Glossary: Key Terms

Use this glossary to clean up high-confusion OCI integration terms, then route misses back to the right support page.

High-value terms

• API Gateway: The OCI edge layer for publishing and protecting APIs.
• Backoff: The delay strategy between retries so failures do not cause immediate retry storms.
• Connector pattern: A reusable path that moves or transforms data between services with a defined source and destination.
• Idempotency: The property that allows safe retry without duplicate side effects.
• Notification topic: The publish point used to fan out messages to subscribed endpoints.
• Queue: A buffered async work pattern where consumers process messages independently of producers.
• Retry policy: The rule set that defines whether and how failed delivery is attempted again.
• Service Connector Hub: The OCI service that routes data between OCI services without hand-built glue code.
• Streaming: The OCI managed event-stream service for ordered event ingestion and processing.
• Workflow orchestration: The step-by-step coordination of tasks, conditions, and failure paths across services.

Common confusion pairs

• API Gateway vs load balancer: An API gateway manages API exposure and policies. A load balancer distributes traffic but is not the same control layer.
• Queue vs streaming: Queues are work-delivery oriented. Streaming is event-log oriented.
• Retry vs idempotency: Retry decides whether you try again. Idempotency decides whether retry is safe.
• Event trigger vs scheduled trigger: Event triggers react to changes. Scheduled triggers run by time.
• Secret storage vs config value: Secrets need controlled storage and rotation. Normal config does not carry the same risk profile.

Where to review next

• Weekly sequence and weak-spot planning: Study Plan
• API, event, and retry traps: Cheat Sheet
• Last-week questions: FAQ
• Canonical Oracle and OCI references: Resources