Select Two (Multi-Select) Questions

OCI Queue / OCI Streaming (via service endpoints)

Correct. Notifications can publish messages to streaming or queue endpoints.

HTTPS Custom Webhooks

Correct. HTTPS endpoints allow integration with webhooks, Slack, PagerDuty, etc.

Email

Correct. Notifications can send alerts via email.

Automated backups managed by OCI to Oracle-managed Object Storage

OCI provides automated daily/weekly backups to Object Storage.

On-demand manual backups triggered via the OCI Console, CLI, or API to Object Storage

Users can take on-demand full backups whenever needed.

Using Oracle Recovery Manager (RMAN) directly against the database

RMAN is the underlying engine for Oracle database backups and can be executed manually.

Geolocation steering (routing traffic based on the geographic location of the client)

Geolocation steering routes users to the closest regional endpoint for performance and DR resilience.

Failover steering (routing traffic to primary, failing over to secondary on health check failure)

Failover steering explicitly directs traffic to a primary endpoint and switches to secondary if health checks fail.

Load Balancer steering (distributing traffic across multiple endpoints with weighted distribution)

Load balancer steering distributes traffic across multiple endpoints based on weights.

Users manage and control the worker node pools (compute shapes, scaling, OS patches).

Correct. Worker nodes run in the customer tenancy and are managed by the user.

Oracle manages and patches the Kubernetes control plane (master nodes) at no additional charge.

Correct. Control plane management is fully managed by Oracle and free of charge.

Distribute OKE worker node pools across multiple Fault Domains or Availability Domains.

Spreading worker nodes across Fault Domains or Availability Domains ensures that hardware failures do not take down all replicas of a microservice.

Configure Kubernetes Pod Disruption Budgets (PDBs) to control minimum available pods during maintenance or scaling events.

PDBs ensure that cluster updates or node drains do not terminate too many pod replicas simultaneously, maintaining application availability.

OCI Load Balancers and Network Load Balancers

Load balancers are supported by FSDR to reroute traffic during failover.

Oracle Database systems (Base Database and Exadata Database Service)

Database systems are fully integrated into FSDR workflows for role transitions.

OCI Compute instances (including boot and block volumes)

Compute instances and their attached storage are core resources managed by FSDR.

OCI Notifications can publish messages to email, PagerDuty, or HTTPS endpoints triggered by service alarms or events.

OCI Notifications supports multiple subscription endpoints including email, SMS, OCI Functions, and HTTPS webhooks.

OCI Events can capture custom application events emitted via the OCI SDK by publishing custom metrics/events.

Applications can emit custom events to the OCI Events service using the OCI SDK for custom event-driven workflows.

An OCI Events rule can directly trigger an OCI Function as an action target.

OCI Events natively supports OCI Functions as an action target for processing emitted cloud events.

Deploying application tiers across two OCI regions with DNS Traffic Management health checks for automated failover

DNS traffic steering routes users to the secondary region if the primary region fails health checks.

Replicating critical block volumes and object storage data to the secondary region

Cross-region replication ensures application binaries and data are available in the DR region.

Configuring Oracle Data Guard between the primary database and a standby database in a secondary region

Cross-region Data Guard ensures database recoverability in another region.

Automate failover orchestration using tools like OCI Full Stack Disaster Recovery.

Automation reduces human error and speeds up recovery execution.

Conduct regular disaster recovery drills using non-disruptive testing features like Snapshot Standby.

Regular drills validate RTO/RPO assumptions and team readiness.

Ensure adequate compute and database capacity is provisioned or reserved in the target DR region.

Capacity constraints in the DR region can prevent successful failover.

Level of automation configured for failover (e.g., Fast-Start Failover vs. manual scripts)

Manual interventions increase RTO, whereas automated tools like FSFO reduce it significantly.

Network bandwidth and latency between the primary and DR regions

Network performance directly impacts redo transport lag and replication speed.

Business criticality and acceptable data loss window during unexpected outages

Business requirements dictate the target RPO and RTO thresholds.

Leveraging Transportable Tablespaces (TTS) combined with RMAN cross-platform conversion

Correct. TTS is ideal for bulk transport of large data volumes.

Utilizing Oracle Zero Downtime Migration (ZDM) physical migration workflows

Correct. ZDM automates complex physical migrations efficiently.

Configuring Oracle Data Guard or GoldenGate for ongoing delta synchronization prior to cutover

Correct. Data Guard/GoldenGate synchronize delta changes to ensure minimal downtime cutover.

Oracle SQL Developer migration workbench / Data Loading features.

SQL Developer supports data loading and schema migration to Autonomous Database.

Oracle Zero Downtime Migration (ZDM) service.

ZDM supports automated migrations to Autonomous Database.

Oracle Data Pump (import/export).

Data Pump is a primary migration mechanism for moving schemas into Autonomous Database.

Redundant FastConnect virtual circuits terminating on separate DRG ports or diverse provider locations.

Redundant FastConnect circuits eliminate single points of failure in hybrid connectivity.

Redundant IPSec VPN tunnels configured on the Dynamic Routing Gateway.

Multiple IPSec VPN tunnels provide automatic failover for on-premises connectivity.

Executing pre-checks in the target DR region to validate resource readiness and configurations

Pre-checks validate that all required infrastructure and permissions are in place before executing a failover.

Verifying database role transition and redo application status on the standby database

Ensuring the database is promoted and in sync is critical for application data integrity.

Orchestrating traffic rerouting via DNS or Load Balancers to point clients to the DR region

Rerouting traffic ensures incoming client requests reach the active DR environment.

Object versioning support to protect against accidental deletion or overwriting.

Versioning preserves previous states of objects for recovery.

Data is automatically replicated across multiple fault domains and availability domains.

Redundancy across fault/availability domains ensures high durability.

Oracle Database Enterprise Edition (EE)

Correct. EE is a supported base database edition.

Oracle Database Standard Edition 2 (SE2)

Correct. SE2 is a supported base database edition.

Multi-node database clustering across distinct Fault Domains or Availability Domains

RAC nodes are distributed across fault domains to survive individual node or hardware failures.

Application Continuity or Transparent Application Failover (TAF) for seamless session recovery

Application Continuity replays transient failures so application sessions survive node outages.

Redundant Exadata Storage Servers (Storage Cells) providing clustered grid storage

Exadata storage cells use mirroring and grid disk redundancy to survive storage hardware failures.

OCI Object Storage Archive tier (for long-term retention policies)

Correct. Archive storage is supported for long-term backup retention.

OCI Object Storage (Standard tier buckets)

Correct. OCI Object Storage is the default and primary native backup destination.

Consolidate multiple non-CDB databases into a single Multitenant Container Database (CDB) with multiple PDBs.

Consolidation reduces overhead and maximizes resource sharing across workloads.

Configure Exadata Smart Flash Cache policies appropriately for OLTP versus DSS workloads.

Tuning flash cache attributes optimizes I/O performance based on workload characteristics.

Dynamically scale OCPU counts on the Exadata infrastructure based on peak and off-peak workload schedules.

Exadata Dedicated infrastructure allows scaling compute OCPUs to match workload demands.

Exadata Storage Server Resource Management (IORM) for fine-grained I/O prioritization

Correct. IORM manages and prioritizes storage I/O across databases sharing Exadata cells.

Exadata Smart Flash Cache and Persistent Memory (PMEM) integration for ultra-low latency I/O

Correct. Exadata hardware incorporates Smart Flash Cache and PMEM for high-speed caching.

Exadata Smart Scan offloading database query processing to storage servers

Correct. Smart Scan offloads SQL processing queries directly to Exadata storage cells.