You currently have transactional data stored on-premises in a PostgreSQL database. To modernize your data environment, you want to run transactional workloads and support analytics needs with a…

Question

Options

• AMigrate and modernize your database with Cloud Spanner.
• BMigrate your workloads to AlloyDB for PostgreSQL.
• CMigrate to BigQuery to optimize analytics.
• DMigrate your PostgreSQL database to Cloud SQL for PostgreSQL.

• A
  18% (5)
• B
  71% (20)
• C
  4% (1)
• D
  7% (2)

Explanation

AlloyDB for PostgreSQL is the right fit because it is fully PostgreSQL-compatible (no database management system change required) and is purpose-built for hybrid transactional and analytical workloads (HTAP) - its built-in columnar engine accelerates analytics queries without requiring a separate analytics database, satisfying both requirements at once with minimal complexity.

Why the distractors fail:

• A (Cloud Spanner) changes the database engine - Spanner is a globally distributed, proprietary system, not PostgreSQL, violating the "no DBMS change" constraint and adding significant cost and complexity.
• C (BigQuery) is a serverless data warehouse optimized for analytics only; it cannot handle transactional (OLTP) workloads, which is half the requirement.
• D (Cloud SQL for PostgreSQL) stays on PostgreSQL and is cheaper, but it is designed primarily for transactional workloads - it lacks the integrated analytics acceleration that AlloyDB provides, so you'd still need a separate analytics solution.

Memory tip: Think of AlloyDB as "Cloud SQL's high-performance sibling" - both are PostgreSQL-compatible, but AlloyDB adds a columnar engine for analytics, making it the answer whenever a question combines PostgreSQL compatibility + transactional + analytics in one service.

No community discussion yet for this question.