Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional Cloud Developer Topic 8 Question 90 Discussion

Actual exam question for Google's Professional Cloud Developer exam
Question #: 90
Topic #: 8
[All Professional Cloud Developer Questions]

For this question refer to the HipLocal case study.

HipLocal wants to reduce the latency of their services for users in global locations. They have created read replicas of their database in locations where their users reside and configured their service to read traffic using those replicas. How should they further reduce latency for all database interactions with the least amount of effort?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Terina
1 months ago
I'm all about that Kubernetes life, but for this scenario, I think Cloud Spanner is the way to go. Managed databases are the future, my friends. Now, if only they had a 'Ludicrous Speed' option...
upvoted 0 times
Aleisha
5 days ago
I agree, Cloud Spanner seems like the best option for reducing latency.
upvoted 0 times
...
Jamal
9 days ago
C) Migrate the database to Firestore in Datastore mode and use it to serve all global user traffic.
upvoted 0 times
...
Oretha
11 days ago
B) Migrate the database to Cloud Spanner and use it to serve all global user traffic.
upvoted 0 times
...
Louann
13 days ago
A) Migrate the database to Bigtable and use it to serve all global user traffic.
upvoted 0 times
...
...
Regenia
1 months ago
Cloud Spanner all the way! I heard it's like the Ferrari of databases - fast, reliable, and perfect for global businesses. Although, I'd love to see a 'Turbo' mode that could really boost those latency numbers.
upvoted 0 times
...
Cruz
2 months ago
Hmm, I'm leaning towards the Cloud Spanner option too. It's designed for global-scale applications, so it should be a great fit for HipLocal's needs. Plus, it's a managed service, which means less overhead for them.
upvoted 0 times
Magnolia
10 days ago
Hmm, I'm leaning towards the Cloud Spanner option too. It's designed for global-scale applications, so it should be a great fit for HipLocal's needs. Plus, it's a managed service, which means less overhead for them.
upvoted 0 times
...
Thurman
11 days ago
B) Migrate the database to Cloud Spanner and use it to serve all global user traffic.
upvoted 0 times
...
Felicidad
24 days ago
A) Migrate the database to Bigtable and use it to serve all global user traffic.
upvoted 0 times
...
...
Kina
2 months ago
I'm not sure about Bigtable or Firestore for this use case. They're more for non-relational data, right? I think the Kubernetes Engine option could work, but it might be overkill for just improving database latency.
upvoted 0 times
Glory
13 days ago
I think the Kubernetes Engine option could work, but it might be overkill for just improving database latency.
upvoted 0 times
...
Jeffrey
18 days ago
D) Migrate the services to Google Kubernetes Engine and use a load balancer service to better scale the application.
upvoted 0 times
...
Jolanda
1 months ago
I'm not sure about Bigtable or Firestore for this use case. They're more for non-relational data, right?
upvoted 0 times
...
King
1 months ago
C) Migrate the database to Firestore in Datastore mode and use it to serve all global user traffic.
upvoted 0 times
...
Shenika
1 months ago
B) Migrate the database to Cloud Spanner and use it to serve all global user traffic.
upvoted 0 times
...
Eve
1 months ago
A) Migrate the database to Bigtable and use it to serve all global user traffic.
upvoted 0 times
...
...
Paris
2 months ago
Cloud Spanner seems like the best choice here. It's a fully managed relational database service with built-in global replication and low latency. Definitely worth considering.
upvoted 0 times
...
Charlene
2 months ago
I see both points, but I think option C might be a good compromise as Firestore in Datastore mode can also handle global traffic effectively.
upvoted 0 times
...
Estrella
2 months ago
I disagree, I believe option D is the way to go as using Google Kubernetes Engine can help with scaling the application efficiently.
upvoted 0 times
...
Cary
2 months ago
I think option B is the best choice because Cloud Spanner is designed for global scalability.
upvoted 0 times
...

Save Cancel