OCI Multicloud Architect Professional key terms

A dedicated, private, low-latency network link between an OCI region and an Azure region, ordered through Oracle and provisioned in paired locations. It carries traffic outside the public internet and is billed per port plus data egress.

Oracle Cloud Infrastructure's dedicated private connectivity service that links an on-premises or partner network to a VCN without traversing the internet. In multicloud designs it terminates the Oracle side of an interconnect or partner circuit.

Microsoft Azure's private connectivity service that connects Azure virtual networks to on-premises or partner networks through a connectivity provider. On the Oracle Interconnect it is the Azure-side circuit that pairs with an OCI FastConnect circuit.

Two redundant physical ports, one in each of two diverse edge devices, that Oracle provisions for a multicloud interconnect. Both ports must be ordered together so a single device failure does not drop the cross-cloud link.

A logical Layer 2 or Layer 3 connection carried over a FastConnect or ExpressRoute physical circuit. Multiple virtual circuits can share one port pair, letting a single interconnect serve several VCNs or virtual networks.

The Azure resource representing a private connection through a connectivity provider, defined by peering type, bandwidth, and service key. Peering must be configured before traffic can flow to an Azure virtual network.

The Azure-side gateway subnet resource that terminates ExpressRoute or VPN traffic for a virtual network. It is the Azure counterpart to an OCI dynamic routing gateway in a cross-cloud routing design.

An OCI virtual router attached to a VCN that provides a path for private traffic to FastConnect, site-to-site VPN, or another VCN. It learns and advertises routes so subnets can reach remote networks.

An OCI resource that links two VCNs across regions through dynamic routing gateways, enabling private cross-region traffic. It is commonly used to extend a multicloud architecture across OCI regions.

An OCI resource that connects two VCNs in the same region without leaving the Oracle network. It is cheaper and simpler than a remote peering connection but cannot span regions.

Oracle's virtual cloud network, a software-defined network scoped to a region and composed of subnets, route tables, gateways, and security rules. It is the OCI building block that connects to Azure through the interconnect.

A contiguous CIDR range inside a VCN that can be public or private and is tied to a route table and security lists. Instances and database endpoints are placed in subnets that determine their reachability.

A set of rules in a VCN that maps destination CIDR blocks to a target gateway such as a dynamic routing gateway or NAT gateway. Correct route tables are essential for traffic to reach Azure subnets.

A VCN-level set of ingress and egress firewall rules applied to all resources in a subnet. Rules are stateful, and both the source and destination security lists must permit traffic.

An OCI or Azure resource that applies allow rules to a selected group of compute instances or network interfaces rather than a whole subnet. It enables finer-grained, workload-level control than subnet-wide rules.

A specially named subnet in an Azure virtual network that hosts the virtual network gateway. It must not contain other resources, and its address range must be large enough for the gateway SKU.

An addressing rule requiring that every connected network use distinct IP ranges so routes are unambiguous. Overlapping ranges across OCI and Azure break cross-cloud routing and are hard to fix after deployment.

A network design where a central hub VCN or virtual network holds shared connectivity and inspection services, and spoke networks connect through it. It centralizes cross-cloud routing and security controls.

Forwarding traffic between attached networks through a central gateway or appliance instead of direct peer links. In OCI it may require enabling transit routing on a dynamic routing gateway and adding route rules.

A third-party firewall, router, or inspection VM deployed in a VCN or virtual network. It is often placed in a hub to inspect traffic crossing between OCI and Azure.

A private IP address inside a virtual network that exposes a managed service without public exposure. Azure Private Link and OCI private endpoints are used to reach databases and object storage privately across clouds.

A DNS zone resolvable only from linked virtual networks, used to map service names to private IP addresses. Cross-cloud designs need resolver forwarding so OCI names resolve in Azure and vice versa.

Configuring resolvers in one cloud to forward queries for the other cloud's zones to that cloud's DNS servers. Without it, private hostnames fail to resolve across the interconnect.

An OCI gateway that lets a VCN reach Oracle services such as Object Storage without using the internet or a NAT gateway. It keeps service traffic on the Oracle network.

An OCI container for users, groups, and identity policies that can have its own authentication settings and federation. It isolates identities for different workloads or tenants within one tenancy.

An OCI statement granting a group or dynamic group access to resources, written as allow statements with a verb, resource type, and compartment. Policies are scoped by compartment and evaluated by rule.

A logical container inside an OCI tenancy used to organize resources and scope access policies. Policies written at a compartment apply to resources beneath it in the hierarchy.

The root account that owns all OCI resources for an organization, containing compartments, identity domains, and the root compartment. Cross-cloud designs often span multiple tenancies for isolation.

An OCI group whose membership is defined by matching rules on instance or resource attributes rather than manual assignment. It enables workloads to obtain instance principals without stored credentials.

An OCI authentication mechanism that lets a compute instance call Oracle APIs using its identity and a dynamic group membership. It removes the need to embed user credentials in code.

An OCI identity used by serverless and managed services such as Functions to call other Oracle services. Access is granted through policies that reference the resource type.

Trusting an external identity provider, such as Microsoft Entra ID, to authenticate users who then receive OCI access. It avoids duplicate credentials and centralizes joiner-mover-leaver processes.

A signed XML statement from an identity provider that asserts a user's identity and attributes after authentication. OCI consumes it during federated single sign-on to establish the user session.

An automated protocol for pushing user and group records from an identity provider into a target system. It keeps OCI identity domains synchronized with Entra ID without manual account creation.

A security approach that grants least-privilege access between workloads and verifies every flow rather than trusting a network perimeter. In multicloud it means explicit rules between OCI and Azure subnets.

Oracle's self-driving managed database that automates patching, tuning, scaling, and backups. It can run in a dedicated or shared infrastructure and is often the primary database in multicloud application designs.

The managed standby feature of Autonomous Database that maintains a synchronized copy in another region or cloud for disaster recovery. It supports switchover and failover with minimal data loss.

Switching application traffic to a standby database or region after a primary failure. Success depends on DNS changes, connection string updates, and tested recovery time objectives.

A named connection from one Oracle database to another that lets SQL statements query remote tables. Cross-cloud links must traverse the interconnect or a private endpoint rather than the public internet.

A service that runs Oracle Exadata and Oracle Database infrastructure inside Azure data centers, managed by Oracle. It lets Azure applications use Oracle databases with low latency and Azure-native networking.

Oracle's engineered database platform combining database servers and storage servers with smart offload. It underpins high-performance Oracle Database deployments and the Database@Azure offering.

A managed OCI offering for running Oracle Database on virtual machines or bare metal with Oracle-managed patching and backups. It suits workloads needing full database control without self-managed hosts.

Oracle's Java application server for deploying enterprise Java applications. In multicloud designs it can run on OCI compute or Kubernetes and connect to databases over private links.

A controller that manages WebLogic domains as Kubernetes resources, automating server startup, scaling, and lifecycle. It is the standard way to run WebLogic on OCI Kubernetes Engine.

Oracle's managed Kubernetes service for running containerized workloads on OCI. It hosts WebLogic domains and microservices that call databases over private endpoints.

A design that provides at least two independent network paths between OCI and Azure so one failure does not sever connectivity. It typically uses diverse port pairs, devices, and availability domains.