nerdexam
Google

PROFESSIONAL-CLOUD-DATABASE-ENGINEER · Question #161

You are the DBA working at a large bank in Europe. Your business-critical banking application runs on Oracle 12.2 in your on-premises data center. You decided to modernize your on- premises Oracle…

The correct answer is C. AlloyDB Omni deployed as a Kubernetes-based cluster on-premises satisfies every stated requirement. Kubernetes is open-source, ensuring portability. Running on-premises keeps data within the European regulatory jurisdiction for data residency…

Designing and Implementing Database Solutions

Question

You are the DBA working at a large bank in Europe. Your business-critical banking application runs on Oracle 12.2 in your on-premises data center. You decided to modernize your on- premises Oracle database by migrating to AlloyDB. You must meet the following requirements:

  • Remain on-premises and maintain open-source portability.
  • Meet regulatory requirements for data residency.
  • Support both OLTP and OLAP workloads.
  • Maintain high availability (HA) mode and automatic failover.

What should you do-

Options

  • ADeploy AlloyDB Omni in a standalone VM on-premises, and set up disaster recovery (DR) in
  • BMigrate to AlloyDB for PostgreSQL by using Database Migration Service.
  • CDeploy Kubernetes-based AlloyDB Omni database cluster on-premises. Enable HA by using the
  • DDeploy AlloyDB Omni as a docker-based container in your on-premises VM, enable HA for it, and

Explanation

The correct answer is C. AlloyDB Omni deployed as a Kubernetes-based cluster on-premises satisfies every stated requirement. Kubernetes is open-source, ensuring portability. Running on-premises keeps data within the European regulatory jurisdiction for data residency compliance. AlloyDB Omni inherently supports both OLTP and OLAP workloads. Critically, the Kubernetes-based AlloyDB Omni operator provides native HA and automatic failover by managing leader election and pod rescheduling. Option A (standalone VM) lacks native HA/automatic failover. Option B (AlloyDB for PostgreSQL via DMS) moves data to Google Cloud, violating the on-premises data residency requirement. Option D (Docker-based Omni) lacks the orchestration layer needed for reliable automatic failover.

Topics

#AlloyDB Omni#On-premises Databases#High Availability#Kubernetes

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DATABASE-ENGINEER Practice