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

OCI Multicloud Architect Professional: Multicloud Database and Application Architectures (Autonomous Database, Database Service, WebLogic)

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

All guide sections

Multicloud Database and Application Architectures (Autonomous Database, Database Service, WebLogic)

Multicloud Database and Application Architectures (Autonomous Database, Database Service, WebLogic)

This domain tests placing Oracle data services and WebLogic application tiers across OCI and Azure without breaking latency, security, or recovery. Know the managed options and the connectivity they require.

Core rules

  • Oracle Database Service for Microsoft Azure (ODSA) offers Autonomous Database and Exadata Database Service in OCI to Azure customers, with private connectivity through Oracle Interconnect for Microsoft Azure. It is a managed database service, not a generic network link.
  • Autonomous Database provides private endpoints, TLS/wallet-based connections, auto scaling, and Autonomous Data Guard for a standby. Use connection pooling and size the interconnect for peak database traffic.
  • Oracle Base Database Service and Exadata Database Service give more control (for example, VM DB systems, RAC, Data Guard). Choose them when you need specific features, versions, or topology control.
  • WebLogic domains contain an admin server, managed servers, clusters, JDBC data sources, and JMS. On OCI, use WebLogic for OCI or the WebLogic Kubernetes Operator; keep the WebLogic tier close to its database and design session replication and JDBC pooling for cross-cloud latency.
  • Prefer private IPs and private DNS names end to end; do not expose a database publicly to make a multicloud app work.

Worked example

Azure Kubernetes Service runs a Java app; Autonomous Database is in OCI. Create an ADB private endpoint in the OCI VCN, route Azure app subnet 10.1.1.0/24 to the DRG and the OCI CIDR to the Azure VNet gateway, allow TCP 1521 in NSG/security list, and configure the JDBC URL with TCPS and the wallet. Use a bounded connection pool. Reasoning: the database stays private; the app uses the interconnect; pooling avoids connection storms over higher-latency links.

Traps

Using ADB's public endpoint, omitting the wallet/TLS, designing chatty SQL across clouds, assuming the interconnect guarantees low latency for every region pair, and splitting WebLogic clusters across clouds without a latency and session-replication plan.