Oracle Cloud Infrastructure (OCI) is architected around geographically isolated regions. Each region is a separate geographic area that operates independently and is completely isolated from other regions. This intentional isolation is a core design principle for achieving high availability and fault tolerance. By deploying applications across multiple regions, an organization can design a disaster recovery strategy that protects against large-scale, region-wide events, thereby enhancing global resilience and ensuring service continuity.

A. OCI regions contain a finite number of availability domains (typically one or three), not an unlimited number. The concept of "infinite scalability" is an overstatement.

B. Regions are intentionally isolated, not interconnected to share resources for automatic compensation. Cross-region connectivity must be explicitly configured for disaster recovery, but they do not inherently share resources.

C. Availability domains are designed to be isolated from each other within a region, with independent power, cooling, and networking to prevent single points of failure. They do not share these critical resources.

1. Oracle Cloud Infrastructure Documentation

"Regions and Availability Domains": "An Oracle Cloud Infrastructure region is a localized geographic area... Regions are independent of other regions and can be separated by vast distances—across countries or even continents." This statement directly supports the concept of region isolation for fault tolerance (Answer D). The document also clarifies

"A region is composed of one or more availability domains

" refuting the "unlimited" claim in option A.

2. Oracle Cloud Infrastructure Documentation

"Resilience in Oracle Cloud Infrastructure": "Availability domains are isolated from each other

are fault tolerant

and are very unlikely to fail simultaneously... Because the availability domains do not share physical infrastructure

such as power or cooling

or the internal availability domain network

a failure that impacts one availability domain is unlikely to impact the availability of the others." This directly refutes the idea of shared resources for cost efficiency as stated in option C.