Exam Professional Data Engineer topic 1 question 188 discussion

A. Use Cloud Spanner to configure a single region instance initially, and then configure multi-region Cloud Spanner instances after securing funding. When you create a Cloud Spanner instance, you must configure it as either regional (that is, all the resources are contained within a single Google Cloud region) or multi-region (that is, the resources span more than one region). You can change the instance configuration to multi-regional (or global) at anytime.

Although A is good, but concerning about the cost. Then D will be much more suitable

I go to D. Cloud SQL is usually used for web application (CRM) (https://cloud.google.com/blog/topics/developers-practitioners/your-google-cloud-database-options-explained?hl=en)

Although A is good, but concerning about the cost. Then D will be much more suitable

Although A is good, but concerning about the cost. Then D will be much more suitable

I think is D The best for Web app is Cloud SQL, and Spanner is the best for data more than 30GB

A - This option allows for optimization for cost initially with a single region Cloud Spanner instance, and then optimization for global presence and performance after funding with multi-region instances. Cloud Spanner supports native JDBC drivers and is horizontally scalable, providing very high performance. A single region instance minimizes costs initially. After funding, multi-region instances can provide lower latency and high availability globally. Cloud SQL does not scale as well and has higher costs for multiple high availability regions. Bigtable does not support JDBC drivers natively. Therefore, Spanner is the best choice here for optimizing both for cost initially and then performance and availability globally post-funding.

Spanner has some limitations with JDBC. Maybe the quetion wants to help us tp choose Cloud SQL

Answer D: Cost effective transactional database Cloud SQL. Spanner is good case for data more than 30 GB

B and C has no sense because of the driver. D looks like a good option, but HA it's not to improve performance or global presence: The purpose of an HA configuration is to reduce downtime when a zone or instance becomes unavailable. This might happen during a zonal outage, or when an instance runs out of memory. With HA, your data continues to be available to client applications. So the best option is A.

https://cloud.google.com/spanner/docs/jdbc-drivers Ans A https://cloud.google.com/spanner/docs/instance-configurations#tradeoffs_regional_versus_multi-region_configurations The last part of the question makes it easy

Yes Spanner is expensive , but the question expresslty states that "after securing funding you want to have a global presence" the word globally is repeatedly stated there. Answer is A.

Spanner is expensive, they haven't mentioned the size of db... optimize for cost then option is Cloud SQL which cost effective and highly available in case of multi region.

A is the best option. It is globally scalable and it also meets the cost goal as it says that initially it will be configurated as single region wich is cheaper than multi region.

Spanner is expensive can't be A Would choose D

Spanner still support JDBC https://cloud.google.com/spanner/docs/jdbc-drivers