MENU
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?
Suggested Answer: C
Get Premium Professional Cloud Database Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
45 comments · newest first
LO
Louvenia
11 months ago
Bigtable seems like a weird pick for this. Not sure about that one.
DA
Dannette
11 months ago
Wait, can Cloud SQL really handle 99.999% uptime?
FL
Florinda
11 months ago
Firestore doesn't meet the ACID requirements, right?
DA
Dalene
11 months ago
I agree, Cloud Spanner is built for global transactions!
ST
Stefania
12 months ago
Cloud Spanner is the best choice for ACID and high availability.
AM
Amie
12 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.
CE
Cecily
1 year 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.
TO
Tonette
1 year 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.
TE
Tequila
1 year 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.
MA
Marica
1 year 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.
RI
Richelle
1 year 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.
CR
Craig
1 year 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.
KI
Kimbery
1 year 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.
AN
Annett
1 year 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.
NI
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.
RU
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.
SH
Shonda
1 year ago
Let's go with Cloud Spanner for our global transactional application.
EL
Elden
1 year ago
Cloud Spanner can handle the scale and ACID requirements, it's the way to go.
EL
Elfrieda
1 year ago
I agree, Cloud Spanner is the best option for this kind of application.
JU
Judy
1 year ago
Firestore is not suitable for this project, we need something more robust.
KE
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.
TO
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.
IS
Isabella
1 year ago
C) Use Cloud SQL.
SH
Shaniqua
1 year ago
B) Use Cloud Spanner.
RE
Reta
1 year ago
A) Use Firestore.
CY
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.
VE
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.
CH
Christoper
1 year ago
D) Use Bigtable.
WH
Whitney
1 year ago
C) Use Cloud SQL.
AL
Alica
1 year ago
B) Use Cloud Spanner.
VA
Val
1 year ago
A) Use Firestore.
RE
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.
AN
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.
KE
Keva
2 years ago
Bigtable? Really? That's like using a sledgehammer to crack a nut. This is a transactional app, not a big data use case.
GO
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.
OD
Odette
1 year ago
C) Use Cloud SQL.
MI
Minna
1 year ago
B) Use Cloud Spanner.
IZ
Izetta
1 year ago
A) Use Firestore.
CR
Cristy
2 years 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.
ME
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.
MA
Marcelle
1 year ago
I think Cloud Spanner would be the best choice. It's globally distributed and offers strong consistency.
CI
Ciara
2 years ago
I'm not sure about Cloud Spanner. Maybe we should consider Cloud SQL as well for this project.
PH
Phil
2 years ago
I agree with Janine. Cloud Spanner provides strong consistency and high availability.
ST
Stephen
2 years 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.
JA
Janine
2 years ago
I think we should use Cloud Spanner for this new application.