OCI 1Z0-997-25 Glossary: Key Terms
March 31, 2026
OCI 1Z0-997-25 glossary of enterprise architecture, multicloud design, resilience, governance, and cost terms.
Use this glossary to clean up high-confusion OCI architecture terms before you go back into mixed sets. On this exam, vocabulary mistakes usually hide a continuity, boundary, or control mistake.
High-value terms
| Term |
What it means here |
Why it matters on the exam |
| Blast radius |
the scope of systems or data affected when one design choice, misconfiguration, or failure goes wrong |
professional-level answers often win by shrinking this |
| Compartment strategy |
the organizational and access pattern used to separate OCI resources cleanly |
governance and least privilege often start here |
| Control plane |
the management and configuration layer used to create or administer resources |
many questions hinge on control-plane clarity versus workload traffic |
| Failure domain |
a boundary within which one failure can affect multiple components |
helps classify local redundancy vs broader recovery |
| Recovery objective |
the target for recovery speed and acceptable data loss |
RTO and RPO drive design complexity |
| Repeatability |
the ability to rebuild or change infrastructure reliably with the same result |
repeatability is a core operability signal |
| Resource Manager |
OCI service for Terraform-backed infrastructure automation |
anchors automation and repeatable-change questions |
| Resilience pattern |
the design approach used to absorb or recover from failure |
not every workload needs the same pattern |
| Service fit |
the degree to which a chosen OCI service matches the real workload need |
strong answers avoid oversized solutions |
| Traffic path |
the route requests or packets follow across tiers, gateways, or services |
network-path clarity is a recurring architect-level need |
Common confusion pairs
| Pair |
Clean separation |
| HA vs DR |
HA reduces local failure impact, DR handles larger outage and recovery scenarios |
| Compartment boundary vs network boundary |
compartments govern organization and access, network boundaries govern traffic movement |
| Control plane vs data plane |
the control plane manages resources, the data plane carries workload traffic or data operations |
| Capability vs fit |
a service may support a feature, but that does not make it the best architectural fit |
| Automation vs observability |
automation changes or rebuilds systems, observability helps teams understand system behavior and failure |
| Backup vs replication |
backup restores lost state, replication supports continuity or failover design |
| Region boundary vs failure-domain boundary |
region is a larger placement and residency boundary, failure domains are narrower resilience boundaries |
Fast recall anchors
| If you see… |
Think… |
| “how much can we lose?” |
recovery objective |
| “how far can one bad decision spread?” |
blast radius |
| “where should governance start?” |
compartment strategy |
| “can we rebuild this reliably?” |
repeatability and automation |
If three terms blur together
| Terms |
Short reset |
| HA, DR, backup |
HA keeps service running locally, DR handles larger outage, backup restores lost data or state |
| control plane, data plane, traffic path |
control plane manages resources, data plane carries work, traffic path explains how requests move |
| compartment, VCN, subnet |
compartment governs administrative scope, VCN is network boundary, subnet narrows placement and route context |
| repeatability, Resource Manager, rollback |
repeatability is the goal, Resource Manager is one automation control, rollback is the recovery move |
Route misses well
| If you missed because… |
Go next |
| you mixed up continuity or control terms |
FAQ |
| you need fast architecture tie-breaks |
Cheat Sheet |
| you need a paced rebuild of the weak lane |
Study Plan |
| you need the official Oracle or OCI source |
Resources |
Revised on Monday, June 15, 2026