I85PREP
⌘ K
OCI Developer Professional study materials
OCI Developer Professional study resources

OCI Developer Professional: Oracle Cloud Infrastructure Developer

OCI Developer Professional · Work through your exam, one topic at a time.

All guide sections

Oracle Cloud Infrastructure Developer

This domain tests how you build, deploy, secure, and operate applications on OCI, not how well you memorize console screens. Expect serverless functions, API Gateway, containers and OKE, DevOps pipelines, Streaming, and IAM resource principals.

Core rules and concepts

  • OCI Functions packages code as a Docker image stored in OCIR. Invoke it through API Gateway, OCI Events, or an SDK; use application configuration for environment values and resource principals for OCI API calls.
  • API Gateway routes match a path and HTTP method to a backend: a function, an HTTP endpoint, or an OCI service. Authentication can be JWT, OAuth2, or a custom authorizer function; request and response policies transform payloads.
  • OKE runs Kubernetes with node pools; OCIR is the private registry. Use image pull secrets and VCN-native pod networking so pods get VCN IPs.
  • DevOps service separates build pipelines (Managed Build, Deliver Artifacts, Trigger Deployment stages) from deployment pipelines (rolling, blue-green, canary). Triggers connect source repos.
  • Streaming is Kafka-compatible: partitions preserve order, consumer groups share partitions, and retention is time- or size-based.

Worked example

A function must read an Object Storage bucket and publish to a stream, then be exposed at POST /ingest. Create a dynamic group matching the function in its compartment. Grant it read buckets in compartment prod and use stream-push in compartment prod. Deploy the function with a resource principal, then add an API Gateway route /ingest (POST) whose backend is that function. The reasoning: the dynamic group makes the function a principal; the policy supplies least-privilege verbs; the route provides the public entry point without embedding credentials.

Traps that cost marks

  • Putting user credentials in function code instead of using resource principals.
  • Forgetting that the function image must exist in OCIR and the function's execution role must pull it.
  • Creating an API Gateway route but no authentication or authorizer, then wondering why calls fail.
  • Mixing build and deployment pipeline stages; artifact delivery belongs in the build pipeline.