OCI 1Z0-1109-25 glossary of pipelines, deployments, observability, and release automation terms.
On this page
Use this glossary to clean up high-confusion OCI DevOps terms before you go back into mixed sets. On this exam, terminology mistakes usually hide a delivery-stage or recovery mistake.
High-value terms
Term
What it means here
Why it matters on the exam
Artifact
a build output or packaged unit that moves through a pipeline
strong answers keep artifacts immutable and traceable
Build stage
the automation step where code is compiled, assembled, or packaged
build is not the same as release into a target
Deployment stage
the pipeline step where a validated artifact is promoted into an environment
deployment is where blast radius starts to matter
Drift
the gap between intended infrastructure state and the state that actually exists
drift turns IaC assumptions into operational risk
Pipeline
a staged automation flow that moves changes through validation and release
the whole exam is organized around pipeline-stage judgment
Resource Manager
OCI service for Terraform-backed infrastructure deployment and control
it anchors IaC questions on this exam
Rollback
the recovery action that returns a change or environment to a known-good state
rollback readiness is a strong-answer signal
Runbook
the documented operational procedure for handling common tasks or incidents
response quality is part of DevOps maturity
Telemetry loop
the flow of logs and metrics back into delivery or operations decisions
observability helps judge release health
Validation gate
the checkpoint changes must pass before moving to the next stage
gates reduce blast radius and force evidence
Common confusion pairs
Pair
Clean separation
Build vs deploy
build creates the release unit, deploy places it into a target environment
Pipeline stage vs target environment
the stage is the control step, the environment is where the change lands
IaC tool vs DevOps service
the tool defines or applies infrastructure, the DevOps service coordinates the broader delivery loop
Rollback vs redeploy
rollback returns to a prior known-good state, redeploy repeats a deployment path and may not solve the issue
Monitoring vs logging
monitoring tracks numeric health and conditions, logging captures detailed event records
Validation gate vs approval step
a validation gate checks evidence, an approval step is a human or policy handoff
Drift vs failed apply
drift is long-lived state mismatch, a failed apply is a specific execution failure
Fast recall anchors
If you see…
Think…
packaged release unit
artifact
repeatable infrastructure change
Resource Manager and IaC lifecycle
“can we return safely?”
rollback
“how do we know the release is good?”
telemetry loop and validation gate
If three terms blur together
Terms
Short reset
build, artifact, deploy
build creates the artifact, the artifact is the release unit, deploy moves it into the target
plan, apply, drift
plan previews intended change, apply executes it, drift is later mismatch from that intent
rollback, redeploy, verify
rollback restores known-good state, redeploy repeats a path, verify decides whether the change is healthy