Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
You are designing the data layer for a global retail and financial ledger application expected to grow beyond 150 TB across multiple continents. Your application has the following requirements:
Which Google Cloud database service should you choose?
Cloud SQL is a fully managed relational database service for MySQL, PostgreSQL, and SQL Server. It handles administrative tasks such as backups, patching, and high-availability failover while running database software on managed Compute Engine virtual machines.
Your relational workload was under 64 TB, operated primarily within a single region, and did not require global horizontal write scaling or synchronous multi-region replication.
Developers often choose Cloud SQL for lifting and shifting existing MySQL, PostgreSQL, or SQL Server applications, whereas globally distributed workloads exceeding 64 TB require a horizontally scalable database architecture.
Cloud Spanner is a fully managed, globally distributed relational and multi-model database service. It combines the strict ACID transactional consistency and SQL semantics of a traditional relational database with the horizontal scalability and high availability of a distributed NoSQL system.
GoogleSQL as well as a PostgreSQL interface) for normalized relational schemas, cross-table joins, and table interleaving. It also provides native JSON and BYTES data types so you can store semi-structured data alongside structured tables without creating a separate database.Unlike Cloud SQL (limited to under 64 TB and vertical write scaling), Firestore (a schemaless document database not built for normalized SQL joins), or Bigtable (lacking multi-row ACID transactions), Cloud Spanner is the only service that delivers global horizontal write scalability, petabyte capacity, strict multi-region ACID consistency, and relational plus semi-structured JSON support together.
Bigtable is a fully managed, NoSQL wide-column database service engineered for massive analytical and operational workloads. It excels at storing terabytes to petabytes of sparse, key-value or time-series data with consistently low latency and high throughput.
Your workload involved petabyte-scale time-series, IoT, or analytical event ingestion that required ultra-low latency key-value lookups and did not need ACID transactions or relational SQL joins.
When evaluating petabyte-scale databases on Google Cloud, Bigtable targets high-throughput non-relational wide-column workloads without multi-row ACID guarantees, whereas Cloud Spanner provides petabyte-scale horizontal scalability with full relational semantics and ACID compliance.
Firestore is a fully managed, serverless NoSQL document database designed for mobile, web, and server applications. It stores data in documents organized into collections and offers single-digit millisecond read latency alongside automatic scaling.
Your application primarily stored schemaless or semi-structured documents, needed real-time client synchronization or offline caching for web and mobile apps, and did not depend on normalized relational tables with SQL joins.
A common misconception is that NoSQL databases cannot support ACID transactions. While Firestore does provide strong consistency and ACID transactions, its document-centric data model makes it less suitable than a relational engine for complex normalized ledger schemas.
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 Validated