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 retail organization is migrating its regional e-commerce order processing system to Google Cloud. The system has the following data management requirements:
Which Google Cloud service should the organization choose?
Firestore is a fully managed, serverless NoSQL document database designed for mobile, web, and server application development. Instead of storing data in traditional relational tables with uniform rows and columns, Firestore organizes data into documents (which contain key-value pairs and nested objects) grouped into collections.
JOIN operations across normalized tables.The organization were building a mobile or web application (such as a live chat app, gaming leaderboards, or a collaborative workspace) that required a flexible NoSQL document schema, real-time client synchronization, offline support, and automatic scaling.
When choosing between Cloud SQL and Firestore, the decision primarily hinges on schema requirements and query patterns. Structured data requiring relational integrity and SQL joins belongs in Cloud SQL, whereas semi-structured, hierarchical data accessed by client apps belongs in Firestore.
BigQuery is Google Cloud's fully managed, serverless enterprise data warehouse. Rather than serving as an operational database for day-to-day application transactions, BigQuery is designed for online analytical processing (OLAP)—enabling organizations to run fast SQL analytics, business intelligence reporting, and machine learning over terabytes to petabytes of data.
The organization wanted to consolidate historical order data from multiple operational systems into a centralized data warehouse to run large-scale business intelligence queries, analyze multi-year sales trends, or train predictive machine learning models.
A foundational concept in cloud data management is differentiating between databases and data warehouses. Operational databases (like Cloud SQL) power live applications through fast, row-level transactions (OLTP), whereas data warehouses (like BigQuery) aggregate historical data from those databases to power analytical decision-making (OLAP).
Cloud Spanner is a fully managed, mission-critical relational database service engineered for global scale. It uniquely combines the benefits of traditional relational database structure—such as strict schemas, SQL queries, and strong ACID transactions—with the horizontal scalability typically found only in NoSQL databases.
The organization needed a globally distributed relational database capable of scaling horizontally to millions of transactions per second across multiple continents with 99.999% availability and strong global consistency, without being tied to a MySQL or SQL Server engine.
Both Cloud SQL and Cloud Spanner are relational databases on Google Cloud that use predefined schemas and support SQL (including DQL, DDL, and DML statements). However, Cloud SQL is the right choice for regional workloads requiring standard open-source or commercial engines (MySQL, PostgreSQL, SQL Server), whereas Cloud Spanner is reserved for global, horizontally scalable relational workloads.
Cloud SQL is a fully managed relational database service on Google Cloud that supports industry-standard database engines, including MySQL, PostgreSQL, and SQL Server. Its primary purpose is to handle structured, operational data while automating time-consuming database administration tasks such as software patching, backups, replication, and capacity management.
INSERT, UPDATE, and DELETE statements. It provides direct compatibility with MySQL and SQL Server, enabling seamless migration of existing regional applications.Unlike data warehouses (such as BigQuery) that are built for large-scale analytics, or NoSQL databases (such as Firestore) that use flexible document schemas, Cloud SQL is purpose-built for regional, structured OLTP workloads requiring standard MySQL or SQL Server compatibility.
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