Google Professional Cloud Database Engineer Exam - Topic 9 Question 41 Discussion

Actual exam question for Google's Professional Cloud Database Engineer exam

Question #: 41
Topic #: 9

[All Professional Cloud Database Engineer Questions]

Your company is developing a new global transactional application that must be ACID-compliant and have 99.999% availability. You are responsible for selecting the appropriate Google Cloud database to serve as a datastore for this new application. What should you do?

AUse Firestore.

BUse Cloud Spanner.

CUse Cloud SQL.

DUse Bigtable.

Show Suggested Answer

Suggested Answer: C

https://cloud.google.com/sql/docs/sqlserver/configure-ssl-instance#server-certs

by Tran at Sep 12, 2024, 02:28 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Database Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Louvenia

9 months ago

Bigtable seems like a weird pick for this. Not sure about that one.

upvoted 0 times

...

Dannette

9 months ago

Wait, can Cloud SQL really handle 99.999% uptime?

upvoted 0 times

...

Florinda

10 months ago

Firestore doesn't meet the ACID requirements, right?

upvoted 0 times

...

Dalene

10 months ago

I agree, Cloud Spanner is built for global transactions!

upvoted 0 times

...

Stefania

10 months ago

Cloud Spanner is the best choice for ACID and high availability.

upvoted 0 times

...

Amie

10 months ago

Bigtable seems like it’s more for analytics and not really for transactional workloads, so I don’t think that’s the right option here.

upvoted 0 times

...

Cecily

11 months ago

Cloud SQL could work, but I feel like it might struggle with the scale and availability needed for a global app. I’m leaning towards Cloud Spanner.

upvoted 0 times

...

Tonette

11 months ago

I remember practicing a question similar to this, and I think Firestore is more for NoSQL use cases, so it might not fit the ACID requirement.

upvoted 0 times

...

Tequila

11 months ago

I think Cloud Spanner might be the right choice since it’s designed for global transactions and ACID compliance, but I’m not entirely sure about the 99.999% availability part.

upvoted 0 times

...

Marica

11 months ago

Okay, I think I've got this. Based on the ACID compliance and high availability needs, Cloud Spanner seems like the obvious choice here. I'll mark that as my answer.

upvoted 0 times

...

Richelle

11 months ago

Hmm, I'm not sure about this one. There are a few different Google Cloud database options, and I'll need to research the capabilities of each to determine which one best fits the requirements.

upvoted 0 times

...

Craig

11 months ago

This seems like a straightforward question about selecting the right Google Cloud database for a transactional application. I'll need to carefully consider the requirements of ACID compliance and 99.999% availability.

upvoted 0 times

...

Kimbery

11 months ago

I'm a bit confused by the different database options. I'll need to review the details of each one to understand their features and capabilities before I can confidently select the best option for this application.

upvoted 0 times

...

Annett

11 months ago

Okay, I've got this. The first consideration is the types of roll-up summaries available, and the second is the limit on object references. I'll make sure to clearly explain my reasoning.

upvoted 0 times

...

Nieves

1 year ago

Cloud Spanner is the clear winner here. It's the only option that can handle the ACID compliance and high availability needed for a global transactional app. The others are just not up to the task.

upvoted 0 times

...

Rutha

1 year ago

Hah, Firestore? This isn't a mobile app, it's a global transactional beast! Cloud Spanner is the only choice here that can handle the scale and ACID requirements.

upvoted 0 times

Shonda

1 year ago

Let's go with Cloud Spanner for our global transactional application.

upvoted 0 times

...

Elden

1 year ago

Cloud Spanner can handle the scale and ACID requirements, it's the way to go.

upvoted 0 times

...

Elfrieda

1 year ago

I agree, Cloud Spanner is the best option for this kind of application.

upvoted 0 times

...

Judy

1 year ago

Firestore is not suitable for this project, we need something more robust.

upvoted 0 times

...

Kerrie

1 year ago

Bigtable? Really? That's like using a sledgehammer to crack a nut. This is a transactional app, not a big data use case.

upvoted 0 times

...

Tommy

1 year ago

I'd go with Cloud SQL. It's a relational database, which is perfect for a transactional app, and it has high availability. Plus, it's a familiar option.

upvoted 0 times

Isabella

1 year ago

C) Use Cloud SQL.

upvoted 0 times

...

Shaniqua

1 year ago

B) Use Cloud Spanner.

upvoted 0 times

...

Reta

1 year ago

A) Use Firestore.

upvoted 0 times

...

Cyril

1 year ago

Cloud Spanner is the way to go! It's ACID-compliant and has the availability we need. Firestore is great, but it's not the best fit for a transactional app.

upvoted 0 times

Veda

1 year ago

Cloud Spanner is the way to go! It's ACID-compliant and has the availability we need. Firestore is great, but it's not the best fit for a transactional app.

upvoted 0 times

...

Christoper

1 year ago

D) Use Bigtable.

upvoted 0 times

...

Whitney

1 year ago

C) Use Cloud SQL.

upvoted 0 times

...

Alica

1 year ago

B) Use Cloud Spanner.

upvoted 0 times

...

Val

1 year ago

A) Use Firestore.

upvoted 0 times

...

Rebbecca

1 year ago

Cloud Spanner is the clear winner here. It's the only option that can handle the ACID compliance and high availability needed for a global transactional app. The others are just not up to the task.

upvoted 0 times

...

Andra

1 year ago

Hah, Firestore? This isn't a mobile app, it's a global transactional beast! Cloud Spanner is the only choice here that can handle the scale and ACID requirements.

upvoted 0 times

...

Keva

1 year ago

Bigtable? Really? That's like using a sledgehammer to crack a nut. This is a transactional app, not a big data use case.

upvoted 0 times

Golda

1 year ago

Bigtable? Really? That's like using a sledgehammer to crack a nut. This is a transactional app, not a big data use case.

upvoted 0 times

...

Odette

1 year ago

C) Use Cloud SQL.

upvoted 0 times

...

Minna

1 year ago

B) Use Cloud Spanner.

upvoted 0 times

...

Izetta

1 year ago

A) Use Firestore.

upvoted 0 times

...

Cristy

1 year ago

I'd go with Cloud SQL. It's a relational database, which is perfect for a transactional app, and it has high availability. Plus, it's a familiar option.

upvoted 0 times

Meghann

1 year ago

I agree, Cloud Spanner sounds like the right fit for our needs. It can handle the high availability and ACID compliance we require.

upvoted 0 times

...

Marcelle

1 year ago

I think Cloud Spanner would be the best choice. It's globally distributed and offers strong consistency.

upvoted 0 times

...

Ciara

1 year ago

I'm not sure about Cloud Spanner. Maybe we should consider Cloud SQL as well for this project.

upvoted 0 times

...

Phil

1 year ago

I agree with Janine. Cloud Spanner provides strong consistency and high availability.

upvoted 0 times

...

Stephen

1 year ago

Cloud Spanner is the way to go! It's ACID-compliant and has the availability we need. Firestore is great, but it's not the best fit for a transactional app.

upvoted 0 times

...

Janine

1 year ago

I think we should use Cloud Spanner for this new application.

upvoted 0 times

...