Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A global enterprise runs a monolithic on-premises database that handles both customer transactions (OLTP) and large-scale analytical reporting. Due to rapid growth, the company faces capacity limits and high costs from pre-provisioning hardware. They want to refactor their database architecture into cloud-native Google Cloud services to meet the following requirements:
Which database modernization strategy should the organization implement?
Refactoring a monolithic database that handles mixed workloads involves decoupling Online Transaction Processing (OLTP) from Online Analytical Processing (OLAP) and moving each workload to a purpose-built, cloud-native service. Spanner is a fully managed, globally distributed relational database that provides strong consistency, high availability, and SQL support for transactional operations. BigQuery is a fully managed, serverless, massively parallel processing (MPP) enterprise data warehouse designed specifically for large-scale data analytics.
Traditional on-premises systems often force organizations to run mixed workloads on rigid, pre-provisioned hardware, resulting in resource contention and expensive over-provisioning. By modernizing into a cloud-native architecture that pairs Spanner for global transactions with BigQuery for serverless analytics, the organization achieves unmatched global scale, eliminates infrastructure management, and optimizes long-term total cost of ownership.
Cloud SQL is a fully managed relational database service for MySQL, PostgreSQL, and SQL Server that automates routine administrative tasks such as backups, patching, and replication. Database sharding is a horizontal scaling technique where a single logical database is manually partitioned into multiple smaller database instances (shards) based on specific criteria, such as customer ID or geographic region, to distribute read and write loads.
Migrating to Cloud SQL would be the right choice if the organization wanted to replatform a regional relational database (such as self-hosted MySQL or PostgreSQL) to a managed service without needing global multi-region write scalability or petabyte-scale serverless data warehousing.
When an application outgrows the vertical scaling limits of a regional relational database like Cloud SQL, Google Cloud recommends refactoring to Spanner for automated, globally distributed horizontal scaling rather than building complex manual sharding logic into the application layer.
Memorystore for Redis is a fully managed, in-memory datastore service designed to provide sub-millisecond data access and high throughput by caching frequently accessed data in RAM. Firestore is a flexible, scalable NoSQL document database built for mobile, web, and server development that offers high availability and effortless horizontal scaling, often prioritizing availability and flexible schemas over traditional relational constraints.
This combination would be appropriate if the organization were building a cloud-native mobile or web application that required a flexible NoSQL document store (Firestore) paired with an in-memory caching layer (Memorystore for Redis) to accelerate read performance for heavily accessed keys.
In modern cloud architectures, Memorystore for Redis is deployed alongside primary databases (such as Cloud SQL, Spanner, or Firestore) to absorb repetitive read traffic and lower latency, while BigQuery is used as the dedicated platform for long-term analytical storage and reporting.
BigQuery is Google Cloud's serverless, petabyte-scale enterprise data warehouse designed to ingest, store, and analyze massive datasets using standard SQL. Consolidating workloads into BigQuery means moving data tables into its columnar storage engine (Capacitor) and executing queries through its distributed execution engine (Dremel). While BigQuery excels at aggregating and scanning vast amounts of historical and analytical data, it is fundamentally an Online Analytical Processing (OLAP) platform rather than an operational database.
This approach would be appropriate if the organization only needed to migrate legacy data warehouse, business intelligence, and historical reporting workloads from an on-premises system, with no requirement to run real-time operational transactions.
A common misconception during cloud database modernization is assuming that a SQL-compatible serverless data warehouse can replace a relational transactional database. In a modern cloud-native architecture, BigQuery complements operational databases like Spanner or Cloud SQL by serving as the downstream analytical engine rather than replacing the transactional book of record.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated