Exam Professional Data Engineer topic 1 question 159 discussion

Correct: A It asks for scaling up which can be done in cloud sql, horizontal scaling is not possible in cloud sql Automatic storage increase If you enable this setting, Cloud SQL checks your available storage every 30 seconds. If the available storage falls below a threshold size, Cloud SQL automatically adds additional storage capacity. If the available storage repeatedly falls below the threshold size, Cloud SQL continues to add storage until it reaches the maximum of 30 TB.

Should be C.

Correct: C - Cloud Spanner hint is automatically scale, CloudSQL dont scale

Cloud SQL Cloud SQL can store up to 30 TB of data. It offers limited scalability as per the lesser load. You can easily work with MySQL code in Cloud SQL. Cloud SQL is a cost-effective service. Cloud Spanner: Cloud Spanner is used to store more than 30 TB of data. It provides better scalability and SLOs. Cloud Spanner is an expensive service. It provides strong transactional consistency. It is built on Google Cloud’s dedicated network that ensures low latency, security, and reliability.

C. Cloud Spanner and an explanation of the other options: Why Cloud Spanner is the best fit: Fully managed service: Cloud Spanner is fully managed by Google, simplifying database administration. Automatic scaling It handles scaling seamlessly, both horizontally and vertically. Transactional consistency: Cloud Spanner is known for its strong transactional consistency, including globally distributed transactions. Scalable up to 6 TB (and beyond): It easily accommodates your 6 TB requirement and can scale much larger if needed. SQL Support: Cloud Spanner offers a familiar SQL interface.

Although the type of automatic scaling isn't specified, Cloud SQL does not allow for outright dynamic capacity auto scaling, so I believe the answer would be C

C. Cloud Spanner Here's why: Fully Managed: Cloud Spanner is a fully managed database service provided by Google Cloud. Automatic Scaling: It automatically scales horizontally to handle increased workloads and data volumes. Transactional Consistency: Cloud Spanner provides strong transactional consistency with support for ACID transactions. Scalability: It can easily scale up to and beyond 6 TB while maintaining performance and consistency. SQL Queries: Cloud Spanner supports SQL queries, making it compatible with existing SQL-based analytics and applications.

I would go to C.

All the arguments below can essentially be boiled down to two questions. 1) is Cloud SQL fully managed? (yes), 2) Does it autoscale? It depends, is the answer. The question is horrifyingly worded, as it comes down to an ambiguity coinflip. I'm going with C, it feels like it's a better fit.

Did not refer to global, thus not spanner. A is correct

Transactional consistency: spanner provides strong consistency across rows, regions, and continents.

Answer : A Cloud SQL and Cloud Spanner are the options for the questions. But here as per requirement they don't need horizontal scaling, they want manager SQL instance and it should support 6 TB of storage. Cloud SQL can support up to 64 TB of storage https://cloud.google.com/sql/docs/quotas#:~:text=Cloud%20SQL%20storage%20limits,core%3A%20Up%20to%203%20TB.

Not horizontal scaling is required, cloud SQL will work for 10 TB

i will go with A, since the question doesnt specifically say it should be scaling horizontally

"Able to scale up to 6 TB" -seems to be the key it looks like autoscaling is related to storage - possible in case of Cloud SQL

Spanner is consistent and fully-managed https://cloud.google.com/spanner/docs/transactions?hl=en

A seems to be correct because of the scaling factor of 6 TB because cloud sql easily supports up to 40 TB and obviously there is a limitation of GLOBALLY MULTI REGIONAL which is nothing to do with question. Hence A seems more closer.