1Z0-1084-25 Cheatsheet — OCI Developer Professional (Auth, APIs, Functions, Events)

Last-mile 1Z0-1084-25 review: OCI auth patterns (API keys, instance/resource principals), API/SDK/CLI usage, Functions and event-driven design, and operational safety rules.

On this page

Use this for last‑mile review. Pair it with the Syllabus.

1) Auth pickers (high-yield)

You’re building…	Prefer	Why
Local dev tooling	User API signing key	simple dev workflow
Code running on OCI compute	Instance principal	avoids storing keys
Code running inside OCI service	Resource principal	least key management

Exam cue: if the prompt says “avoid long-lived credentials”, pick instance/resource principals.

2) OCI CLI: a few commands worth recognizing

1# list compartments in a tenancy
2oci iam compartment list --compartment-id <tenancy-ocid>
3
4# list buckets in a compartment/namespace
5oci os bucket list --compartment-id <compartment-ocid> --namespace <ns>

3) Event-driven mental model (services and boundaries)

    flowchart LR
	  API["API Gateway"] --> FN["Functions"]
	  FN --> OBJ["Object Storage"]
	  OBJ --> EVT["Events"]
	  EVT --> NOTIF["Notifications"]
	  NOTIF --> SUB["Subscribers (email/webhook/...)"]

Rule: events should be idempotent; assume retries and “at least once” delivery.

4) SDK usage: what questions are usually testing

Correct compartment scoping (resources live in a compartment).
Correct auth choice (user API key vs instance/resource principal).
Basic operational safety: retries, logging, and error handling.

5) Functions + API Gateway (exam-friendly reminders)

Put secrets in Vault, not environment variables checked into source control.
Log correlation IDs and basic metrics for troubleshooting.
Design handlers to be safe on retries (idempotency).

Syllabus

Practice

Browse Exams — Mock Exams & Practice Tests