Why NoSQL on GCP matters - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why choose NoSQL databases on GCP?

Which of the following is the main reason to use NoSQL databases on Google Cloud Platform instead of traditional SQL databases?

A NoSQL databases on GCP do not support horizontal scaling.

B NoSQL databases on GCP always guarantee ACID transactions across multiple tables.

C NoSQL databases on GCP provide flexible schemas that adapt easily to changing data structures.

D NoSQL databases on GCP require less storage space than SQL databases for the same data.

💡 Hint

Think about how data changes over time and how databases handle that.

NoSQL databases on GCP are designed to handle flexible, evolving data structures by allowing schema changes without downtime. This is unlike traditional SQL databases that require fixed schemas.

❓ Architecture

intermediate

Best GCP NoSQL service for global low-latency access

You want to build a globally distributed application with low-latency data access and automatic scaling. Which GCP NoSQL service fits best?

A Cloud Firestore in Native mode

B Cloud Bigtable

C Cloud SQL

D Cloud Spanner

💡 Hint

Consider which service is designed for mobile and web apps with global reach.

Cloud Firestore in Native mode is a NoSQL document database designed for global distribution with low latency and automatic scaling, ideal for mobile and web apps.

❓ service_behavior

advanced

How Cloud Bigtable handles scaling

What happens when you add nodes to a Cloud Bigtable cluster?

A Data is duplicated on all nodes without redistribution.

B The cluster automatically redistributes data to balance load across nodes.

C The cluster stops accepting writes during scaling.

D You must manually move data to new nodes after adding them.

💡 Hint

Think about how a big table keeps performance smooth as it grows.

Cloud Bigtable automatically redistributes data when nodes are added to balance the load and maintain performance without downtime.

❓ security

advanced

Securing NoSQL data on GCP

Which GCP feature helps protect NoSQL data by controlling who can read or write documents in Cloud Firestore?

A Cloud IAM roles and policies

B Cloud CDN caching

C Cloud Storage lifecycle rules

D Cloud Functions triggers

💡 Hint

Think about how you control user permissions in GCP.

Cloud IAM roles and policies let you control access to Cloud Firestore data by defining who can read or write documents.

✅ Best Practice

expert

Designing for high availability with Cloud Firestore

You want your Cloud Firestore database to remain available even if a whole GCP region goes down. What is the best practice to achieve this?

A Use Cloud Bigtable instead of Firestore for multi-region availability.

B Use Firestore in Datastore mode with single-region configuration.

C Manually replicate data between two Firestore instances in different regions.

D Use Firestore in Native mode with multi-region configuration.

💡 Hint

Consider built-in multi-region support for automatic failover.

Firestore in Native mode with multi-region configuration automatically replicates data across multiple regions to provide high availability and resilience to regional failures.