Domain 1: Introduction to Multicloud (10%)

Domain 1 of the 1Z0-1151-25 OCI Multicloud Architect Professional exam covers multicloud concepts, business benefits, use cases, and Oracle's multicloud architecture framework. This domain represents approximately 5 questions on the 50-question exam. Despite its small weight, this domain establishes the vocabulary and conceptual foundation that the other four domains build on.

1. Multicloud Definitions: Multicloud vs. Hybrid Cloud

Understanding the distinction between multicloud and hybrid cloud is foundational. The exam will test whether you can correctly classify a given scenario.

Sources: Cloudflare: Multicloud vs. Hybrid Cloud, VMware: Hybrid Cloud vs. Multi-Cloud

Exam trap: A hybrid cloud that also uses a second public cloud provider is both hybrid and multicloud. These are not mutually exclusive categories. A deployment that uses on-premises infrastructure plus OCI plus Azure is hybrid (because of the on-premises component) and multicloud (because of OCI + Azure).

Oracle's definition: Oracle defines multicloud as the coordinated use of cloud services from two or more public cloud vendors. Organizations use multicloud architectures to distribute computing resources, minimize downtime and data loss risk, and access unique capabilities across providers. (Oracle Multicloud Architecture Framework)

2. Business Benefits of Multicloud

The exam tests whether you understand why organizations adopt multicloud, not just what multicloud is. Each benefit has a specific business rationale.

Avoiding Vendor Lock-in

Single-cloud dependence creates pricing leverage for the provider and migration risk for the customer. Multicloud distributes workloads so no single vendor controls the entire stack. Oracle specifically positions its Database@ services so customers can choose where Oracle Database runs rather than being locked to OCI. (Oracle Multicloud Database)

Best-of-Breed Service Selection

No single cloud provider leads in every service category. Multicloud allows organizations to pick the strongest offering for each workload: Oracle for databases, Azure for enterprise integrations (Active Directory, Office 365), Google Cloud for analytics and AI (BigQuery, Vertex AI), AWS for compute breadth. The Oracle Multicloud Architecture Framework formalizes this as the Cloud Core pillar: selecting the most appropriate service from each CSP.

Cost Optimization

Multicloud enables competitive pricing negotiation and workload placement on the lowest-cost provider for each service type. Oracle claims applications cost approximately 30% less on OCI compared to alternatives. (Oracle Multicloud Solutions) Universal Credits provide flexible cost management across multicloud deployments.

Risk Management and Resilience

Distributing workloads across providers reduces the blast radius of a single provider's outage. If Azure experiences a regional failure, OCI-hosted databases remain available. This is distinct from multi-region redundancy within a single cloud because it eliminates single-provider systemic risk (e.g., a provider-wide IAM outage).

Regulatory Compliance and Data Residency

Different jurisdictions have different data residency requirements. With 70+ global cloud regions across OCI and partner clouds, multicloud provides geographic flexibility to place data where regulations require it. (Oracle Multicloud Solutions) The Database@Azure parent/child site architecture is specifically designed to keep parent and child sites in the same country for data sovereignty compliance. (Oracle Database@Azure Architecture)

Geographic Reach

OCI alone has fewer regions than Azure or AWS. By partnering with Azure, Google Cloud, and AWS, Oracle extends the geographic footprint where Oracle Database services are available without building its own data centers in every location.

3. Common Multicloud Use Cases

The Oracle Multicloud Architecture Framework identifies five multicloud architectural patterns. The exam expects you to match workload requirements to the correct pattern.

Application and Database Split-Stack

The most common multicloud pattern. The application tier runs on one cloud (e.g., Azure or Google Cloud) while the Oracle Database runs on OCI. This pattern leverages Oracle's database strengths without forcing the application team to use OCI for compute, networking, or middleware.

Example: A .NET application on Azure communicating with Oracle Autonomous Database on OCI via the Oracle Interconnect for Azure. (Oracle Multicloud Database)

Analytics and Database Split-Stack

Data resides in Oracle Database on OCI while analytics processing runs on a partner cloud's specialized services: Google BigQuery, Azure Synapse Analytics, or AWS analytics. Zero-ETL integration allows analytics without traditional extract-transform-load pipelines. (Oracle Multicloud Database)

SaaS/ERP Data Analytics and Integration

Oracle SaaS applications (Fusion ERP, HCM) integrate with custom applications running on other clouds. Data from Oracle Retail Cloud is replicated to SQL Server for near-real-time integration with custom Azure applications. OCI GoldenGate enables real-time data replication. (Oracle Multicloud Solutions)

Horizontal Workload Distribution

Workloads are distributed across multiple clouds for parallel processing or resource scaling. Kubernetes and VM workloads span OCI, Azure, and AWS simultaneously. This pattern is used for compute-intensive tasks where a single provider cannot meet capacity requirements.

Production and Development Split Deployment

Production runs on one cloud while development and testing run on another. This allows teams to use their preferred tools in development (e.g., Google Cloud for AI/ML experimentation) while maintaining production on a different provider (e.g., OCI for database performance).

Exam trap: Know the difference between split-stack (different tiers on different clouds) and single-stack (everything on one cloud). A single-stack deployment is not multicloud even if the organization uses multiple clouds for different applications.

4. Oracle Multicloud Architecture Framework

The Oracle Multicloud Architecture Framework defines four design pillars. This is a key testable topic. You need to know each pillar, what it covers, and how they relate.

Pillar 1: Cloud Core

The foundational services layer. Cloud Core is about selecting the right service from the right provider for each component of the solution.

Components:

• Network — Virtual networks, subnets, load balancers
• Compute — VMs, containers, serverless
• Storage — Block, object, file storage
• Security and Compliance — Service-level security controls
• Performance and Cost Optimization — Right-sizing, reserved capacity
• Reliability and Resilience — Availability zones, fault domains
• Operational Efficiency — Managed services vs. self-managed

Key principle: Choosing an inappropriate service leads to poor design and higher costs. Selecting the most suitable database service for performance and cost optimization in OCI while hosting the application stack with another CSP delivers the true value of a multicloud solution. (Oracle Multicloud Architecture Framework)

Pillar 2: Cloud Network Access

The connectivity layer that links users, data centers, and cloud services to the Cloud Core.

Components:

• VPN access — Site-to-site and client VPN connections
• Internet access — Public-facing services and APIs
• Dedicated connections — Private, high-bandwidth links to core services

Connected infrastructure types:

• Data center and branch offices
• SD-WAN and MPLS networks
• IoT devices and 5G endpoints
• Cloud direct connection edge points (FastConnect, ExpressRoute, Cloud Interconnect)

Source: Oracle Multicloud Architecture Framework Pillars Diagram

Pillar 3: Cloud Operations

The management and monitoring layer that integrates operating models across multiple CSPs.

Components:

• Orchestration and Automation — Infrastructure as Code (Terraform, OCI Resource Manager, ARM templates)
• Visibility and Manageability — Centralized monitoring, logging, alerting across clouds

Cloud Operations increases operational efficiency by providing unified management beyond vendor boundaries. Without this pillar, teams manage each cloud independently, creating operational silos and inconsistent practices.

Pillar 4: Cloud Security and Governance

The cross-cutting pillar that spans all other pillars. In the framework diagram, Cloud Security and Governance appears on the right side, covering the full vertical stack.

Components:

• Data Control — Encryption at rest and in transit, key management
• Secure Access — Network segmentation, firewall rules, private endpoints
• Compliance — Regulatory alignment, audit logging, policy enforcement
• Identity Federation — Cross-cloud SSO, unified IAM across OCI and partner clouds

Exam trap: Cloud Security is not just another pillar alongside the other three. It spans all pillars. On the framework diagram it is positioned vertically across Cloud Network Access, Cloud Core, and Cloud Operations. Questions may test whether you understand this cross-cutting relationship.

5. Oracle's Multicloud Service Model

Oracle's multicloud approach has evolved through two generations. Understanding this evolution is essential for the exam.

Generation 1: Interconnects (2019+)

The original approach uses dedicated private network connections between OCI and partner clouds.

How it works: The interconnect pairs an OCI FastConnect virtual circuit with a partner ExpressRoute or Cloud Interconnect circuit. Traffic passes over a private network using private IP addresses. BGP dynamic routing handles path selection across two redundant sessions. Each interconnect circuit comes with a redundant circuit on a different physical router in the same point-of-presence (POP) for high availability. (Microsoft Learn: Azure OCI Networking, Oracle Interconnect for Azure)

Limitation: Even with sub-2ms latency, the database and application are in separate data centers. For latency-sensitive workloads (OLTP, real-time analytics, AI inference), this is still too much.

Generation 2: Database@ Services (2022+)

The current approach physically colocates OCI hardware inside partner cloud data centers, reducing cross-cloud latency from milliseconds to microseconds.

How Database@ works — Parent/Child site model:

1. Child site (in partner data center): Oracle Exadata hardware deployed in isolated, secure areas of the partner's data center within an availability zone. All hardware is operated and managed exclusively by OCI personnel. (Oracle Database@Azure Architecture)
2. Parent site (in OCI regional data center): Contains the Oracle Database@ control plane. Located in the same geographic area as the child site (e.g., Azure East US/Virginia pairs with OCI US East/Ashburn).
3. The child site is considered an extension of the OCI parent site, maintaining the same security, management, resiliency, and performance profile.

Key architectural distinction: The Database@ model is not the same as running Oracle Database on partner cloud VMs. Oracle owns, operates, and manages all the hardware. The partner cloud provides the data center facility, network, physical security, and hardware monitoring. Customers get OCI-native database services with the same features, scalability, and pricing as running directly on OCI. (Oracle Multicloud Database)

Source: Oracle Multicloud Database

6. Oracle's Multicloud Partners

Oracle Database@Azure

• GA: December 2023 (initial), expanded to 28+ Azure regions by early 2026
• Available services: Autonomous Database, Exadata Database Service, HeatWave, Base Database Service, Zero Data Loss Autonomous Recovery Service
• Billing: Managed through Azure Marketplace; unified Azure bill
• Identity: Azure AD federation with OCI IAM; Azure users can access OCI Console with Azure credentials
• Provisioning: Through Azure portal and APIs natively

Sources: Oracle Database@Azure Architecture, Oracle Multicloud Database

Oracle Database@Google Cloud

• GA: September 2024
• Available services: Autonomous Database, Exadata Database Service, Exadata on Exascale, Base Database Service, Zero Data Loss Autonomous Recovery Service
• Billing: Managed by Google Cloud; consolidated bill for Google Cloud usage and OCI database services
• Identity: Google Cloud IAM integration for Exadata and Autonomous Database resources
• Provisioning: Through Google Cloud Console, gcloud CLI, Terraform, or Oracle Database@Google Cloud API
• Unique: Customer-managed encryption keys (CMEK) support; zero data transfer fees on Cross-Cloud Interconnect

Sources: Google Cloud: Oracle Database@Google Cloud Overview, Oracle Multicloud Database

Oracle Database@AWS

• Announced: September 2024 at Oracle CloudWorld
• Status at exam launch: Preview (GA expected mid-2025)
• Available services: Autonomous Database, Exadata Database Service
• Key integrations: Amazon EC2, Amazon Bedrock (GenAI), AWS analytics services (zero-ETL), Amazon S3
• Billing: Through AWS Marketplace with unified billing

Source: Oracle Multicloud Database

Exam note: The 1Z0-1151-25 exam focuses on Azure and Google Cloud partnerships. Database@AWS was in preview when exam objectives were finalized. Domain 1 may reference AWS at a conceptual level, but deep AWS-specific questions are unlikely.

Key Concepts for Exam Preparation

Terms to Know

Likely Exam Traps

1. Multicloud is not hybrid cloud — but they can overlap. A deployment using on-premises + OCI + Azure is both.
2. Database@ is not the same as interconnects — Database@ colocates hardware; interconnects are network links between separate data centers.
3. Oracle manages the hardware in Database@ — not the partner cloud. The partner provides the facility, not the database infrastructure.
4. Cloud Security and Governance spans all pillars — it is not a standalone layer at the same level as Cloud Core.
5. The parent site is always in the same country as the child site — this is a data sovereignty design decision, not a coincidence.
6. Single-stack is not multicloud — running everything on one cloud (even if you also use other clouds for other projects) does not make that deployment multicloud.

References

1. Oracle Multicloud Architecture Framework — Four pillars, design considerations, use cases
2. Oracle Multicloud Architecture Framework Pillars Diagram — Pillar components and relationships
3. Oracle Multicloud Solutions — Overview of all multicloud offerings
4. Oracle Multicloud Database Strategy (AWS, Google Cloud, Azure) — Three-partnership comparison, Database@ model
5. Oracle Database@Azure Architecture — Parent/child site model, HA, security
6. Oracle Database@Google Cloud Overview (Google Cloud Docs) — Services, networking, IAM, billing
7. Oracle Interconnect for Azure — FastConnect + ExpressRoute details
8. Microsoft Learn: Azure-OCI Networking — Interconnect technical setup
9. Oracle CloudWorld 2024 Multicloud Expansion Announcement — Database@AWS announcement, regional expansion
10. 1Z0-1151-25 Exam Page — Official exam objectives and format