OCI 1Z0-1093-25 glossary of AI-enabled database services, performance, governance, and data access terms.
On this page
Use this glossary to clean up high-confusion cloud database-service language fast. This exam gets easier when you keep service fit, management boundary, resilience, and day-2 operations in separate buckets.
High-value terms
Term
What to remember
Base Database
Oracle managed database tier with a defined management boundary and more direct-control characteristics than a stronger autonomous path
dedicated service model
deployment path with stronger isolation or dedicated-environment characteristics
Exadata service
higher-end Oracle database service lane focused on performance and scale
HA
high availability aimed at reducing service interruption from failure
management boundary
the line between what the service automates and what the team still owns
migration path
the method used to move an existing workload into the target service
provisioning model
the service and deployment approach selected for a workload
recovery plan
the path for restoring data and service after failure
service fit
how well a database service matches workload and operations needs
workload profile
the practical usage pattern the target service must support
Common confusion pairs
Pair
Keep this distinction clear
service feature vs service fit
a feature may exist without making the service the best workload match
backup vs HA
recover later versus stay available through a smaller failure
HA vs DR
local continuity versus larger-environment recovery
managed service vs managed outcome
Oracle automates some work, but the team still owns design and operations choices
migration tool vs migration strategy
tool choice executes the move; strategy decides cutover, rollback, and risk
performance claim vs operability
stronger raw capability is not automatically better if the service is harder to secure, recover, or run
Fast recall anchors
If you see…
Think…
“lowest operations burden”
stronger managed or autonomous lane
“more direct control”
base or DB-system-style boundary
“restore after corruption or deletion”
backup and restore
“stay up through failure”
HA
“recover after bigger-site loss”
DR
If three terms blur together
Blurry group
Reset with this rule
backup, HA, DR
recover later, stay available locally, and recover after a larger outage are different goals
service fit, performance, management burden
the best answer balances all three instead of maximizing one
migration, cutover, rollback
tool execution, switchover timing, and recovery path are separate decisions
managed, secure, and auditable
automation does not remove the need for access control and evidence