OCI 1Z0-931-25 Glossary: Key Terms
March 31, 2026
OCI 1Z0-931-25 glossary of tuning, automation, AI features, and operational terms.
Use this glossary to clean up high-confusion Autonomous Database language fast. This exam gets easier when you keep provisioning boundary, security, performance, and recovery in separate mental buckets.
High-value terms
| Term |
What to remember |
| audit trail |
the record of actions and access events used for security and compliance review |
| Autonomous Database |
Oracle’s managed database service with automated operational features |
| dedicated infrastructure |
deployment model with stronger isolation and dedicated-capacity boundaries |
| elastic scaling |
the ability to increase or decrease capacity to match demand |
| observability |
the signals used to understand health, performance, and operations over time |
| provisioning model |
the service option and configuration path chosen at setup time |
| recovery point |
the recoverable state the service can return to after failure |
| serverless deployment |
model where more infrastructure management is abstracted from the user |
| service boundary |
the limit of what the managed service handles versus what the user still owns |
| workload type |
the usage pattern the service or configuration must support |
Common confusion pairs
| Pair |
Keep this distinction clear |
| serverless vs dedicated |
stronger abstraction and elasticity versus stronger dedicated-environment boundary |
| auditability vs observability |
evidence of actions and access versus system-behavior visibility |
| scaling vs tuning |
changing capacity versus improving how capacity is used |
| backup vs recovery plan |
an asset versus the operational path that uses that asset |
| managed feature vs user responsibility |
Oracle automates many tasks, but the user still owns design, access, and operations choices |
| private access vs strong password |
reduced exposure versus credential strength |
Fast recall anchors
| If you see… |
Think… |
| “who still owns this?” |
service boundary |
| “record of who changed what” |
audit trail |
| “system is slow” |
check workload shape before scaling |
| “can we recover?” |
backup plus tested restore plus runbook |
| “should this be public?” |
private path first |
If three terms blur together
| Blurry group |
Reset with this rule |
| backup, restore, continuity |
stored recovery asset, actual recovery action, and service continuity are different |
| managed, secure, operable |
automation does not remove exposure, access, or monitoring duties |
| scaling, tuning, troubleshooting |
more capacity, better efficiency, and root-cause diagnosis are different moves |
| serverless, dedicated, service boundary |
deployment model and ownership boundary must be read together |
Route next
| Need |
Go here next |
| weekly pacing and weak-lane repair |
Study Plan |
| security, recovery, and operations tie-breaks |
Cheat Sheet |
| last-week decision cleanup |
FAQ |
| official Oracle sources |
Resources |
Revised on Monday, June 15, 2026