Getting Started With Oci practice questions

OCI Public Cloud Region

Why wrong: Public cloud regions are multi-tenant facilities managed by Oracle, not located within the customer's data center.

OCI Dedicated Region

Why wrong: While Dedicated Region also runs on-premises, Cloud@Customer is the standard scalable option for bringing a subset of OCI services to a local data center when the full region footprint is not required.

OCI Multi-Cloud

Why wrong: Multi-cloud refers to using OCI in conjunction with other hyperscalers like Microsoft Azure, not an on-premises deployment model.

The database cluster automatically fails over its primary role to an instance in a different Availability Domain.

Why wrong: Fault domains exist within the same Availability Domain, so failover happens locally among the remaining FDs unless a multi-AD architecture was explicitly configured.

The entire Availability Domain is taken offline to synchronize the maintenance state across all Fault Domains.

Why wrong: Maintenance is applied on a per-fault-domain basis to prevent taking down the entire Availability Domain.

Instances in Fault Domain 1 are automatically migrated to Fault Domain 2, causing a brief network partition.

Why wrong: OCI does not automatically migrate running instances between fault domains during maintenance.

Deploy both instances in the same Availability Domain but assign them to different Fault Domains.

Why wrong: Fault domains protect against hardware failures and maintenance within a single availability domain, not a complete availability domain outage.

Deploy both instances in separate OCI Regions using an explicit cross-region pairing gateway.

Why wrong: While cross-region deployment offers disaster recovery, the immediate requirement for high availability against an AD outage is satisfied by using multiple ADs within the same region.

Deploy both instances in the same Availability Domain and configure autonomous cross-AD scaling.

Why wrong: OCI does not have an autonomous cross-AD scaling feature that mitigates a complete AD outage for a single subnet without multi-AD design.

Dynamic Routing Gateways

Why wrong: Dynamic Routing Gateways are used to connect VCNs to on-premises networks or other VCNs, not for instance fault distribution.

Cross-Region Replication

Why wrong: Cross-region replication is a storage feature, not a compute distribution method for single-AD resiliency.

Secondary Regions

Why wrong: Secondary regions are used for disaster recovery across geographic distances, not for localized single-AD hardware isolation.

Compartments

Why wrong: Compartments are logical access-control boundaries used to organize resources, not geographic constructs.

Availability Domains

Why wrong: Availability domains are isolated data centers within the same region, not across different countries or major European hubs.

Fault Domains

Why wrong: Fault domains are groupings of hardware within a single availability domain.

Deploy instances across three Fault Domains in a single Availability Domain with automated compute health checks.

Why wrong: A single AD deployment does not protect against a regional disaster event affecting the entire geographic area.

Backup daily block volumes to Object Storage and restore them in a secondary region upon disaster declaration.

Why wrong: This backup and restore approach results in a high RPO (hours) and high RTO (hours), failing to meet the requirement.

Deploy an active-passive architecture across two OCI regions using asynchronous database replication and manual DNS failover.

Why wrong: Asynchronous replication introduces a measurable RPO, and manual DNS failover increases the RTO beyond seconds.

Fault domains provide automatic geographic failover across different countries.

Why wrong: Geographic failover is handled at the region level, not via fault domains.

Fault domains automatically replicate virtual machine memory across different availability domains.

Why wrong: Fault domains operate within a single availability domain, and VM memory is not synchronously replicated across ADs by default.

Each Fault Domain has its own dedicated external internet gateway to route traffic around broken switches.

Why wrong: Internet gateways are regional or VCN-level resources, not isolated per fault domain.

A software-defined network boundary that connects local data centers to the OCI backbone.

Why wrong: This describes a Dynamic Routing Gateway or FastConnect, not an availability domain.

A logical grouping of users and compartments for billing purposes.

Why wrong: Compartments and tenancy IAM policies handle user and billing organization, not availability domains.

A hardware rack dedicated entirely to a single enterprise customer on-premises.

Why wrong: This describes OCI Dedicated Region or Exadata Cloud@Customer, not an availability domain.

Oracle Autonomous Database on Dedicated Exadata Infrastructure in the Public Cloud

Why wrong: This is hosted in Oracle's public cloud data centers, not on-premises as requested.

OCI Exadata Cloud@Customer

Why wrong: Exadata Cloud@Customer provides Oracle Database and specific infrastructure services on-premises, but not the complete portfolio of all OCI public cloud services.

OCI Compute Cloud@Customer

Why wrong: Compute Cloud@Customer provides rack-scale cloud infrastructure for running virtualized workloads on-premises, but lacks the full scope of all OCI public cloud services found in a Dedicated Region.

Local Peering Gateway (LPG)

Why wrong: An LPG is used to peer VCNs within the same region.

Dynamic Routing Gateway (DRG)

Why wrong: A DRG is used to connect VCNs to on-premises networks or other VCNs across regions, not ADs.

OCI FastConnect

Why wrong: FastConnect connects on-premises networks to OCI, not internal availability domains.

Regions and availability domains are completely independent and interchangeable concepts.

Why wrong: They have a strict hierarchical relationship where regions contain availability domains.

Each availability domain represents a separate public cloud region in a different country.

Why wrong: Availability domains are grouped inside a single region.

An availability domain spans across multiple global regions to provide high availability.

Why wrong: Availability domains are strictly contained within a single region and do not span across regions.

The instance is placed in a default scratchpad fault domain and must be manually moved later.

Why wrong: There is no scratchpad fault domain; instances are placed directly into a functional FD.

OCI places the instance in Fault Domain 1 by default every time.

Why wrong: OCI uses a distribution algorithm rather than always selecting Fault Domain 1.

The instance fails to launch until a Fault Domain is explicitly provided in the API request.

Why wrong: Specifying a fault domain is optional; OCI handles placement automatically if omitted.

Deploy the nodes in the same Fault Domain and configure OCI Compute Auto-Scaling.

Why wrong: Auto-scaling does not prevent hardware failure in a single fault domain.

Deploy the nodes across three different OCI regions using asynchronous database links.

Why wrong: While cross-region deployment is valid for DR, single-AD fault isolation is handled via fault domains.

Deploy all three nodes in the same Fault Domain to maximize internal rack-level network performance.

Why wrong: Deploying all nodes in a single fault domain creates a single point of failure for rack power or switch issues.

OCI Hybrid Cloud via VPN Connect.

Why wrong: VPN Connect securely connects on-premises networks to public cloud regions over the internet.

OCI FastConnect with a dedicated private circuit.

Why wrong: FastConnect provides private network connectivity to the public cloud, but does not provide an isolated cloud data center on-premises.

OCI Public Cloud with a dedicated Virtual Cloud Network (VCN).

Why wrong: A VCN in the public cloud shares multi-tenant underlying infrastructure and internet-connected control planes.

All inter-region traffic must traverse the public internet via encrypted IPsec VPN tunnels.

Why wrong: OCI utilizes its private global network backbone for inter-region traffic rather than forcing data over the public internet.

OCI regions are isolated from each other; cross-region data transfer requires third-party WAN optimizers.

Why wrong: Regions are connected via Oracle's robust internal backbone without needing third-party optimizers.

Inter-region communication is restricted to metadata only; user data cannot be moved between regions.

Why wrong: Users can freely transfer data, back up volumes, and replicate databases across regions.

To isolate network traffic between different virtual cloud networks (VCNs).

Why wrong: VCNs and security lists manage network traffic isolation.

To segregate billing and cost-management data across different departments.

Why wrong: Compartments and tags handle billing and cost tracking.

To define geographic boundaries for global data residency compliance.

Why wrong: Regions and countries define data residency boundaries, not fault domains.

A security boundary used to manage user permissions and access control.

Why wrong: IAM compartments and policies handle security and permissions.

A virtual machine image template used to launch compute instances.

Why wrong: This describes an OCI custom image or OS image.

A physical server rack installed in a customer's private office.

Why wrong: This describes an on-premises cloud rack, not a region.

To increase the processing speed of CPU instructions.

Why wrong: Hardware placement does not alter CPU clock speeds.

To reduce data transfer costs between cloud regions.

Why wrong: Intra-region traffic between ADs and FDs does not incur regional data egress charges.

To satisfy legal requirements for cross-border data transfer.

Why wrong: Cross-border compliance is governed by regions, not AD/FD distribution.

An outage in one OCI region automatically triggers a failover to the nearest secondary region.

Why wrong: Failover must be configured and managed by the customer using traffic management and replication strategies; it is not automatic.

All OCI regions must contain exactly three Availability Domains.

Why wrong: Many OCI regions contain a single Availability Domain with multiple fault domains.

OCI regions share common control planes to synchronize global configurations in real-time.

Why wrong: Regions are designed with high independence and autonomy to prevent cascading failures.

Dedicated Region is managed entirely by the customer, whereas Cloud@Customer is managed by Oracle administrators remotely.

Why wrong: Both are fully managed by Oracle as cloud services delivered on-premises.

Cloud@Customer requires internet access to function, whereas Dedicated Region operates entirely without power redundancy.

Why wrong: Both models maintain high standards of power redundancy and secure connectivity.

Dedicated Region is hosted by Oracle in a public facility, whereas Cloud@Customer is hosted in a partner data center.

Why wrong: Both are deployed physically inside the customer's designated data center facility.