Exam Associate Cloud Engineer topic 1 question 188 discussion

Read the question : The application is used exclusively by employees in a single physical location.

B -> minimal code changes

Clue is PostgresSQL

B. Cloud SQL Reason: • Cloud SQL supports PostgreSQL, allowing you to deploy your application with minimal code changes since the first version is already implemented in PostgreSQL. • It provides ACID guarantees, strong consistency, and fast queries, which are crucial for transactional workloads like order management. • Cloud SQL is a fully managed relational database service, making it ideal for use cases with structured data and multi-table transactional updates.

Its a matter of cost efficiency. While Spanner is also an option it is an absolute waste for this situation. You would be a prodigal to use it just for this. The company I work for uses it only for the most important things and it costs them 1/4 million a month. So, yeah, very very expensive option

B

Read the question : The application is used exclusively by employees in a single physical location.

Cloud spanner does everyhting cloud SQL already does. + It offers globality which we don't need and horizontal scaling that is mentionned nowhere

C. Select Cloud Spanner. Cloud Spanner offers strong consistency, fast queries, and importantly, ACID guarantees for updates in multi-table transactions. Cloud Spanner is well suited for large transactional databases that require horizontal scaling and offers relational database semantics. Even if the first version was PostgreSQL, Cloud Spanner is the best choice for this kind of application with strict requirements for ACID transactions. Cloud SQL is also a relational database service, and while some database engines offer ACID transactions, it is not designed like Cloud Spanner for the strict requirements of multi-table transactional updates. Reference link: Google Cloud - Cloud Spanner: https://cloud.google.com/spanner Reference link: Google Cloud - ACID Transactions in Cloud Spanner: https://cloud.google.com/spanner/docs/transactions

the best choice for this application is Cloud SQL for PostgreSQL. It offers the required strong consistency, fast queries, and ACID guarantees for multi-table transactional updates. It is also a good choice for applications that are implemented in PostgreSQL and that you want to deploy to the cloud with minimal code changes.

B. instead of C. because it's use in a single physical location and is compatible with PostgreSQL.

B makes sense.

Its B because of single location, usually cloud sql is for non global or/and HA sql ddbb, spanner is for global sql ddbb

key: single physical location

The answer is B. One of the major advantages of Spanner is that the data is replicated over the Globe, since this data will only be accessed at one location Cloud SQL will be sufficient.

Not only Cloud Spanner has the ACID guarantees. SQL and others can be.......now I go to B (I have changed my vote)

C is the right answer Only Cloud Spanner has the ACID guarantees and String consistency as mentioned in the question, for those who are saying B because of minimal changes with PostgreSQL check all the feature of CloudSpanner with below link https://cloud.google.com/spanner#all-features https://cloud.google.com/spanner/docs/postgresql-interface