OCI Multicloud Architect Professional flashcards
OCI Multicloud Architect Professional · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Oracle Interconnect for Azure
- A dedicated private link between a supported OCI region and Azure region, ordered from OCI and paired with an Azure ExpressRoute circuit, avoiding public internet traversal.
- Supported region pairing
- The interconnect only exists between specific OCI and Azure metros; not every OCI region has an Azure counterpart, so topology must follow the current published pair list.
- Multicloud versus hybrid
- Multicloud means two or more public clouds used together; hybrid means a private data center combined with at least one public cloud. The terms are not interchangeable.
- Interconnect bandwidth SKU
- The cross-cloud link is sold in fixed bandwidth options such as 1, 5, or 10 Gbps, and the selected SKU caps throughput for the virtual circuit.
- Egress on both sides
- Traffic over the interconnect is billed as egress from OCI and as ExpressRoute egress from Azure, so a cost model must count both directions.
- Virtual circuit versus ExpressRoute
- The OCI half of the interconnect is a virtual circuit on the DRG; the Azure half is an ExpressRoute circuit on a virtual network gateway. Both are required.
- Non-overlapping address spaces
- OCI VCN CIDRs and Azure VNet CIDRs must not overlap before any interconnect, peering, or route is configured, or routing becomes ambiguous.
- Dynamic routing gateway
- The OCI DRG attaches to VCNs and terminates the virtual circuit to Azure; it is the OCI anchor point for all cross-cloud routing.
- Azure ExpressRoute gateway
- The Azure side uses a virtual network gateway of type ExpressRoute attached to the VNet; its SKU determines throughput and supported features.
- BGP route propagation
- Over the interconnect, BGP advertises routes in both directions automatically; static routes require manual tables and do not fail over without extra automation.
- Hub-and-spoke on OCI
- A DRG with attached VCNs and DRG route tables steers spoke-to-spoke traffic; the Azure analogue is a hub VNet peered to spoke VNets.
- Cross-cloud DNS design
- OCI private DNS zones and Azure Private DNS zones are separate services; resolution across clouds needs conditional forwarders or a shared resolver.
- Security list versus NSG
- OCI security lists are stateless subnet-level filters; Azure NSGs are stateful and attach to subnets or NICs, so rule semantics differ between clouds.
- Transit routing hairpin
- Traffic from a third network to the other cloud must hairpin through the DRG and Azure gateway; both must explicitly permit transit routing.
- Asymmetric routing risk
- If forward and return paths differ across the interconnect, stateful firewalls may drop traffic; keep paths symmetric and verify before cutover.
- SAML federation to OCI
- Microsoft Entra ID acts as identity provider and OCI Identity Domain as relying party; group claims in the assertion map to OCI groups that policies reference.
- OCI policy syntax
- Policies read as allow group X to verb resource-type in compartment Y; there is no unified cross-cloud policy language with Azure RBAC.
- Instance principals
- OCI compute instances obtain short-lived tokens from the OCI metadata service; Azure managed identities do the same on Azure, and neither trusts the other cloud by default.
- OCI Vault versus Key Vault
- Encryption keys are cloud-scoped and regional; OCI Vault keys cannot encrypt Azure disks, so customer-managed key strategy must be implemented separately per cloud.
- Cross-cloud audit aggregation
- OCI Audit and Azure Activity Log are independent; both must be enabled and exported to a shared SIEM to see a unified cross-cloud activity trail.
- Private link trust model
- The interconnect is private but not implicitly trusted; security lists, NSGs, and host firewalls still apply on both sides of the connection.
- Secrets rotation across clouds
- Use OCI Vault and Azure Key Vault with a defined rotation and replication process, or a central secrets manager reachable from both, instead of manual copying.
- Autonomous Database replication
- Cross-cloud standby is achieved with Data Guard or GoldenGate; the standby needs interconnect connectivity and matching wallet and TNS configuration.
- Autonomous Database scaling
- Serverless Autonomous Database scales compute (ECPU or OCPU) and storage independently, and auto-scaling can be enabled per database.
- Base Database Service
- An OCI VM cluster offering with full OS access, RAC, and Data Guard support; chosen when specific database versions or host control are required.
- WebLogic Kubernetes Operator
- A portable way to run WebLogic Server on Kubernetes, including multicloud clusters, managing domains, servers, and lifecycle through Kubernetes custom resources.
- Fast-start failover observer
- An observer placed in a third location arbitrates Data Guard failover so neither cloud's failure can split brain the active-passive configuration.
- GoldenGate active-active
- Bidirectional replication between OCI and Azure Oracle databases enables reads in both regions with controlled write partitioning to avoid conflicts.
- DNS-based database failover
- A global name service or DNS failover record in front of the database tier lets applications reconnect to the surviving cloud without hard-coded endpoints.
- Synchronous transport latency
- Synchronous Data Guard transport across clouds is bounded by interconnect round-trip time; use it only where that latency still satisfies the recovery point objective.
- Oracle Interconnect ordering
- The interconnect is ordered from the OCI Console, which provisions both the OCI virtual circuit and the paired Azure ExpressRoute circuit in one workflow.
- DRG route tables
- DRG route tables on OCI control which attached VCNs and circuits can reach each other, enabling import and export filtering of cross-cloud routes.