OCI Multicloud Architect Associate key terms

A deployment approach where an organization uses services from two or more public cloud providers, often combining them with on-premises systems, and manages them under shared governance rather than as isolated silos.

An environment that combines private or on-premises infrastructure with at least one public cloud, with orchestration and identity spanning the boundary so workloads can move between them.

A design principle in which applications avoid provider-specific dependencies so they can run on more than one cloud, typically achieved through containers, open standards, and abstraction layers.

The ability to move a workload, its configuration, and its data from one cloud to another with acceptable effort and downtime, usually supported by container images and infrastructure-as-code.

A condition where switching providers becomes costly because of proprietary APIs, data gravity, committed contracts, or deeply integrated managed services, reducing negotiating leverage and architectural flexibility.

The tendency of large datasets to attract applications and dependent services toward their location, because moving data across clouds is slower and more expensive than moving compute.

The charge a cloud provider applies when data leaves its network, which strongly influences multicloud topology by discouraging frequent cross-cloud data transfer.

A dedicated private network connection between OCI and another cloud provider such as Azure, AWS, or Google Cloud, offering predictable latency and bandwidth instead of routing traffic over the public internet.

OCI's dedicated private connectivity service that links an on-premises data center or another cloud to an OCI region through a connectivity partner or direct fiber, bypassing the public internet.

A virtual router in an OCI region that attaches to a VCN and terminates private connectivity such as FastConnect, site-to-site VPN, and cross-cloud links, and can route between multiple VCNs.

An OCI object that lets two VCNs in different regions or different tenancies connect through DRGs, enabling private cross-region and cross-organization traffic without internet exposure.

A private connection between two Virtual Cloud Networks that lets instances communicate using private IP addresses, subject to route table and security list configuration in each network.

A set of rules in an OCI VCN subnet that determines where outbound traffic is sent, including whether it goes to a gateway, a DRG, or a local service.

A subnet-level virtual firewall in OCI that permits or denies traffic by protocol, port, and source or destination CIDR, applied to all instances in the subnet.

An OCI virtual firewall applied to selected VNICs rather than whole subnets, allowing finer-grained rules for groups of instances such as application tiers.

A service that runs Oracle Exadata and Autonomous Database infrastructure inside Azure data centers, managed by Oracle, so workloads get low-latency access to Azure services while using Oracle database technology.

A service placing Oracle Exadata and base database services in Google Cloud regions, connected to OCI for management and billing, letting applications in Google Cloud reach Oracle databases with low latency.

Trust established between an external identity provider such as Microsoft Entra ID and OCI IAM, so users authenticate once and receive OCI access through mapped groups and policies.

The system that authenticates users and issues assertions about them, such as Microsoft Entra ID, Okta, or OCI IAM acting as an IdP for other services.

An XML-based federation standard used to exchange authentication assertions between an identity provider and a service provider, commonly used to federate enterprise directories with OCI.

The rule that translates groups from an external identity provider into OCI IAM groups, so that policies written against OCI groups apply automatically to federated users.

An OCI IAM statement written in human-readable syntax that grants a group permission to perform a set of verbs on a compartment or resource, forming the basis of authorization.

A logical container in OCI used to organize and isolate resources for access control, cost tracking, and quota management, and referenced as the scope in IAM policies.

The root container of an OCI account that holds all compartments, users, and resources, and serves as the top-level boundary for identity, billing, and governance.

An OCI identity mechanism that lets a compute instance call OCI APIs without storing user credentials, using dynamic group membership and policies to authorize the instance itself.

An OCI IAM group whose membership is defined by matching rules on resource attributes, such as compartment or tag, rather than by manually added users.

A short-lived identity that lets an OCI service, such as Functions or Data Flow, access other OCI resources on a user's behalf using policies rather than stored keys.

A managed Kubernetes service in OCI that runs containerized workloads across availability domains or virtual nodes, and can be paired with clusters in other clouds for portability.

An open-source container orchestration platform that schedules and scales containerized applications and provides a consistent deployment target across cloud providers.

Managing infrastructure through versioned definition files applied by tools such as Terraform, which makes environments reproducible and simplifies deploying the same design to multiple clouds.

A plugin that lets Terraform create and manage resources on a specific platform, such as OCI or Azure, so one configuration can target multiple clouds.

A feature that copies objects from an OCI bucket to a bucket in another region or another OCI tenancy, optionally to a different cloud, for disaster recovery or data locality.

A self-driving OCI database service that automates patching, tuning, and scaling, and can be deployed in other clouds through Oracle Database@Azure and Oracle Database@Google Cloud.

A preconfigured, governed baseline of compartments, identity, networking, and logging that an organization deploys before workloads, ensuring consistent controls across environments and clouds.

An OCI security posture service that detects risky configurations and activity against detector recipes and responds automatically, helping enforce consistent controls in multicloud estates.

An OCI service that records API activity in a tenancy, showing who did what and when, and is commonly exported to a central SIEM for cross-cloud monitoring.

The practice of collecting metrics, logs, and traces across clouds so teams can detect and diagnose problems in distributed applications, often through a shared monitoring platform.

A financial management discipline for cloud spending that combines cost visibility, budget alerts, tagging, and commitment planning across providers to control multicloud expenditure.

Applying key-value metadata to cloud resources so costs, ownership, and compliance can be tracked consistently, including across providers via a common tag taxonomy.