Cloud Digital Leader Google Cloud Products and Services Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Cloud SQL

  Why this is correct

  Cloud SQL is a fully managed relational database service that supports PostgreSQL, providing automated backups, point-in-time recovery, and high availability with synchronous replication across zones. It offers native PostgreSQL compatibility, so applications can migrate without any changes to their SQL or data access layer. With managed maintenance, scaling, and built-in security features like IAM integration and encryption at rest, Cloud SQL is the pragmatic default choice for most PostgreSQL migrations to Google Cloud.

• ✗

  Memorystore

  Why it's wrong here

  Memorystore is a fully managed in-memory cache service that offers the Redis and Memcached protocols, engineered for low latency and high throughput as a cache or message broker. It does not provide a relational data model, SQL engine, or ACID transactions, and its primary storage is ephemeral unless persistence is explicitly enabled, which still does not make it PostgreSQL-compatible. Therefore, it cannot be used as the target for migrating an on-premises PostgreSQL database; it could only serve as a cache in front of a real database.

• ✓

  AlloyDB

  Why this is correct

  AlloyDB is a fully managed, PostgreSQL-compatible database service built on Google Cloud's infrastructure, offering significantly higher performance than standard PostgreSQL through a columnar accelerator and adaptive caching. It provides automated backups, continuous availability, and cross-region replication, making it ideal for enterprise workloads that demand both high transaction throughput and fast analytical queries on the same data. AlloyDB also supports the PostgreSQL wire protocol, so migrating from an on-premises database requires minimal effort, though it may offer more features and scalability than the organization actually needs.

• ✗

  Filestore

  Why it's wrong here

  Filestore is a managed network file storage service that provides NFS mounts for compute instances, commonly used for shared filesystems in media processing, on-premises workload lift-and-shift, or content repositories. It is a file storage service, not a database, and offers no SQL engine, query processing, connection pooling, or transactional semantics, so it cannot serve as a replacement for a relational database. Choosing Filestore for a PostgreSQL migration would be a fundamental mismatch, as it supports neither the PostgreSQL wire protocol nor any relational data operations.

• ✗

  Cloud Bigtable

  Why it's wrong here

  Cloud Bigtable is a NoSQL, wide-column database designed for low-latency analytical and operational workloads, not a relational SQL engine. It fails the requirement for full PostgreSQL compatibility because it does not support SQL joins, transactions, or PostgreSQL-specific data types. The option is tempting because Bigtable offers high availability and automated backups, but those features serve time-series or IoT use cases, not a relational database migration requiring ACID compliance and PostgreSQL syntax.

Go deeper

Related to this question