OCI 1Z0-1084-25 resources for official links, blueprint checks, study tools, and source review.
Use these resources to reach the right Oracle source fast. Do not treat them as a generic OCI bookmark list. Start from the weak lane you keep missing, then open the narrowest official doc that resolves it.
| If your miss sounds like… | Open this first | Why |
|---|---|---|
| “I need the right auth path for code.” | SDK and CLI configuration | auth setup and signing behavior anchor many developer questions |
| “I need to understand runtime workload identity.” | Calling services from an application | this is the main identity boundary source for workload auth |
| “I need secure synchronous API entry.” | API Gateway | API Gateway is the ingress and policy lane |
| “I need short-lived serverless execution behavior.” | Functions | Functions is the main execution-unit source |
| “I need trigger routing and event-driven flow.” | Events | Events anchors reactive trigger questions |
| “I need lightweight fan-out delivery.” | Notifications | Notifications fits alerting and simple publish-subscribe delivery |
| “I need durable ordered async processing.” | Streaming | Streaming is the durable event-flow lane |
| Need | Start local | Then confirm with |
|---|---|---|
| fast auth, API, and retry tie-breaks | Cheat Sheet | the narrow OCI doc for that identity or service lane |
| term cleanup | Glossary | the product doc for the confused pair |
| pacing and weak-lane rebuild | Study Plan | exam page for current code and scope |
| last-week question cleanup | FAQ | exam page or canonical OCI doc |
Use this order:
1Z0-1084-25If a summary sounds more certain than the Oracle source, downgrade it.
| Do not… | Because… |
|---|---|
| read every OCI developer page end to end | this exam rewards service-boundary judgment more than total product saturation |
| treat every async service as interchangeable | Events, Notifications, and Streaming answer different delivery problems |
| memorize service names without identity thinking | auth path and compartment scope still decide whether the design is safe |
| stop at “the request works” without replay thinking | retry and idempotency still matter |