nerdexam
Google

PROFESSIONAL-CLOUD-DATABASE-ENGINEER · Question #87

You are choosing a new database backend for an existing application. The current database is running PostgreSQL on an on-premises VM and is managed by a database administrator and operations team…

The correct answer is B. Migrate the existing database to Cloud SQL for PostgreSQL. When migrating a PostgreSQL workload with minimal cost and effort, Cloud SQL for PostgreSQL is the best fit because it uses the same engine and is fully managed, eliminating the need for a DBA team to manage infrastructure.

Migrating Databases to Google Cloud

Question

You are choosing a new database backend for an existing application. The current database is running PostgreSQL on an on-premises VM and is managed by a database administrator and operations team. The application data is relational and has light traffic. You want to minimize costs and the migration effort for this application. What should you do?

Options

  • AMigrate the existing database to Firestore.
  • BMigrate the existing database to Cloud SQL for PostgreSQL.
  • CMigrate the existing database to Cloud Spanner.
  • DMigrate the existing database to PostgreSQL running on Compute Engine.

How the community answered

(31 responses)
  • A
    10% (3)
  • B
    81% (25)
  • C
    6% (2)
  • D
    3% (1)

Why each option

When migrating a PostgreSQL workload with minimal cost and effort, Cloud SQL for PostgreSQL is the best fit because it uses the same engine and is fully managed, eliminating the need for a DBA team to manage infrastructure.

AMigrate the existing database to Firestore.

Firestore is a NoSQL document database, requiring significant data model changes for a relational PostgreSQL workload, increasing migration effort.

BMigrate the existing database to Cloud SQL for PostgreSQL.Correct

Cloud SQL for PostgreSQL is a fully managed service that uses the same PostgreSQL engine as the on-premises database, meaning no schema or query changes are required. It reduces operational burden by eliminating DBA infrastructure tasks, and is cost-effective for light-traffic relational workloads compared to alternatives like Cloud Spanner.

CMigrate the existing database to Cloud Spanner.

Cloud Spanner is a globally distributed relational database designed for massive scale and high availability, making it far more expensive and operationally complex than needed for a light-traffic workload.

DMigrate the existing database to PostgreSQL running on Compute Engine.

Running PostgreSQL on Compute Engine requires the same DBA and operations overhead as the on-premises VM, failing to reduce management burden or costs.

Concept tested: Selecting appropriate managed database service for PostgreSQL migration

Source: https://cloud.google.com/sql/docs/postgres/introduction

Topics

#Database Migration#Cloud SQL#PostgreSQL#Cost Optimization

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DATABASE-ENGINEER Practice