OCI 1Z0-1109-25 FAQ for exam format, topics, prep strategy, practice, and common candidate traps.
This exam is about delivery-loop judgment. Strong answers usually decide which stage owns the problem, which control should stop bad changes earlier, and which signals should verify a release before it spreads.
| Question | Short answer |
|---|---|
| What is the most important skill? | Choosing safe defaults: release gates, rollback plans, least privilege, and observability. |
| Do I need Terraform experience? | You do not need expert Terraform depth, but you must understand IaC lifecycle and state boundaries. |
| What does the exam punish most? | Treating DevOps as only CI/CD while ignoring infrastructure safety and post-deploy feedback. |
| What hands-on work matters most? | A small believable delivery loop from source to build, deploy, verify, and rollback. |
| What should I trust if notes disagree? | The current Oracle exam page and OCI documentation. |
Choosing safe defaults is the main skill. This exam rewards candidates who understand that a pipeline without verification, rollback, least privilege, and operational feedback is incomplete.
Questions get easier when you classify them first:
| Lane | What it is really testing |
|---|---|
| source and build | how changes become trustworthy artifacts |
| deploy and release | how artifacts reach targets safely |
| IaC and infrastructure | how environments are defined, reviewed, and changed safely |
| observability | how you know the change is healthy |
| recovery | how you stop blast radius and return to known-good state |
You do not need to be a Terraform specialist, but you do need practical IaC instincts:
| IaC concern | Why it matters here |
|---|---|
| plan and review discipline | prevents unsafe blind applies |
| state boundary awareness | avoids cross-environment mistakes |
| module or scope separation | keeps change units smaller and clearer |
| drift thinking | infrastructure truth can differ from intended state |
It punishes shallow DevOps thinking.
Common traps:
| Trap | Better reading |
|---|---|
| “The pipeline passed, so production is safe.” | release success still needs verification and rollback readiness |
| “IaC is separate from DevOps.” | infrastructure delivery is part of the delivery loop |
| “Observability is an afterthought.” | metrics, logs, and alarms help judge release quality |
| “Automation removes the need for recovery planning.” | automation without recovery is incomplete |
You do not need a giant platform build. You need one believable release loop.
Route the miss by delivery stage.
| If your misses sound like… | Weak lane | Fix next |
|---|---|---|
| “I chose the wrong release strategy.” | deployment and release | review canary, blue-green, rolling, and blast-radius trade-offs |
| “I ignored state or environment separation.” | IaC | review plan, review, apply, state, and scope boundaries |
| “I shipped the change but never proved it worked.” | observability | review logs, metrics, alarms, dashboards, and verification gates |
| “I automated the path but had no recovery move.” | rollback and operations | review recovery triggers and known-good restore logic |
Use this order:
1Z0-1109-25If a summary sounds more certain than the Oracle source, downgrade it.
Do less broad reading and more delivery-stage classification.
| Keep doing | Stop doing |
|---|---|
| rereading confusion tables like build vs deploy and rollback vs redeploy | opening unrelated new CI/CD tools |
| reviewing the cheat sheet and glossary | treating DevOps as only pipeline YAML |
| checking official docs for disputed boundaries | building a large new IaC lab late |
| practicing source → build → deploy → verify → rollback order | trusting unsupported community summaries over Oracle docs |