I85PREP
⌘ K
OCI Multicloud Architect Professional study materials
OCI Multicloud Architect Professional study resources

OCI Multicloud Architect Professional: Multicloud Fundamentals and Oracle Interconnect for Microsoft Azure

OCI Multicloud Architect Professional · Work through your exam, one topic at a time.

All guide sections

Multicloud Fundamentals and Oracle Interconnect for Microsoft Azure

Multicloud Fundamentals and Oracle Interconnect for Microsoft Azure

This domain tests whether you can design a private OCI–Azure connection and explain what the interconnect does-and does not-provide. The exam expects fluency with paired regions, FastConnect/ExpressRoute concepts, DRG attachment, route tables, and the difference between network plumbing and managed database services.

Core rules

  • Oracle Interconnect for Microsoft Azure is a private, pre-provisioned connection in supported OCI/Azure paired regions. On OCI it is consumed as a FastConnect-style virtual circuit; on Azure it is consumed as an ExpressRoute circuit. Traffic stays off the public internet.
  • The interconnect is not a router. You must attach a DRG to the OCI VCN, add a VCN route table rule pointing the Azure CIDR to the DRG, configure the DRG route table for the interconnect attachment, and configure the Azure VNet gateway and effective routes. Security lists and NSGs must also allow the database port.
  • Address plans must not overlap. The interconnect is regional and does not automatically provide global transit between every OCI and Azure region.
  • Oracle Database Service for Microsoft Azure (ODSA) is a managed database offering that uses this connectivity; the interconnect itself supplies no database, DNS, or identity service.

Worked example

An Azure app subnet 10.1.1.0/24 must reach an Autonomous Database private endpoint at 10.0.2.10 in an OCI VCN 10.0.0.0/16. Provision the interconnect in a supported pair, attach the DRG to the VCN, add VCN route 10.1.0.0/16 → DRG, add a DRG route for 10.1.0.0/16 → interconnect attachment, add an Azure route for 10.0.0.0/16 → VNet gateway, allow TCP 1521 in the NSG and OCI security list. Reasoning: forwarding requires both route planes and both firewalls to agree.

Traps

Overlapping CIDRs, a route in only one direction, forgetting the DRG route table, assuming the interconnect auto-creates DNS or identity federation, and confusing ODSA with the interconnect itself.