OCI 1Z0-1151-25 glossary of hybrid connectivity, governance, networking, and workload placement terms.
On this page
Use this glossary to clean up high-confusion OCI multicloud terms before you go back into mixed question sets. On this exam, vocabulary errors usually hide a boundary error.
High-value terms
Term
What it means here
Why it matters on the exam
Boundary service
a control or service that marks where one trust or platform boundary hands off to another
multicloud questions often hinge on the handoff, not the component list
Cross-cloud trust
the identity relationship that lets users or workloads operate across provider boundaries
weak answers blur authentication and authorization
Data locality
where data is stored, processed, or replicated
locality drives sovereignty, latency, and egress trade-offs
Egress path
the path traffic or data takes when leaving an environment
path choice affects exposure, cost, and performance
FastConnect
OCI private connectivity model for dedicated connections
it is a common tie-break against VPN or broader public patterns
Landing zone
the prepared OCI foundation for identity, network, security, and governance
landing-zone thinking keeps control placement deliberate
Placement strategy
where each workload, control, or dataset should live
many misses come from placing everything in one cloud by default
Shared responsibility boundary
the line between provider duties and customer duties, and between one platform team and another
recovery and monitoring ownership depend on this
Sovereignty constraint
a rule that limits where data or services may reside or be operated from
sovereignty is a hard boundary, not just a preference
Trust boundary
the scope inside which identities, permissions, or security assumptions are valid
every multicloud design should make trust boundaries explicit
Common confusion pairs
Pair
Clean separation
Interoperability vs consolidation
Interoperability coordinates across clouds. Consolidation reduces platform count.
Identity boundary vs network boundary
Identity decides who can act. Network decides where traffic can move.
Private connectivity vs public integration path
Private connectivity narrows exposure. Public paths may be simpler but usually widen edge risk.
Data locality vs latency concern
Locality is mainly a governance and placement issue. Latency is mainly a performance issue.
Shared responsibility vs full control
Shared responsibility divides duties across providers and teams. Full-control thinking usually ignores managed layers.
Replication vs recovery
Replication moves or copies data. Recovery proves service can resume inside target objectives.
Federation vs copied credentials
Federation centralizes trust. Credential copying spreads secrets and weakens control.
Segmentation vs connectivity
Connectivity creates a path. Segmentation constrains that path.
Fast recall anchors
If you see…
Think…
“Who should authenticate whom?”
trust boundary
“How should environments connect privately?”
egress and connectivity boundary
“Where should the data live?”
locality, sovereignty, and replication trade-off
“Who owns failover and evidence?”
shared responsibility and operations boundary
If three terms blur together
Terms
Short reset
federation, authorization, audit
federation gets identities in, authorization scopes what they can do, audit proves what happened
FastConnect, VPN, public path
FastConnect is dedicated private connectivity, VPN is private over the internet, public path is the broadest exposure
data locality, sovereignty, egress
locality is placement, sovereignty is the hard legal or policy limit, egress is the cost and path effect of moving data
backup, replication, failover
backup protects recoverability, replication maintains copies, failover is the operational switch during disruption