Google Professional Cloud Developer Exam - 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?

AMigrate the database to Bigtable and use it to serve all global user traffic.

BMigrate the database to Cloud Spanner and use it to serve all global user traffic.

CMigrate the database to Firestore in Datastore mode and use it to serve all global user traffic.

DMigrate the services to Google Kubernetes Engine and use a load balancer service to better scale the application.

Show Suggested Answer

Suggested Answer: C

by Annita at Aug 28, 2024, 03:34 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Tyisha

6 months ago

Totally agree, scaling is key for performance!

upvoted 0 times

...

Mabel

6 months ago

Wait, can Kubernetes really help with latency?

upvoted 0 times

...

Gianna

6 months ago

Firestore might not handle heavy traffic as well.

upvoted 0 times

...

Galen

7 months ago

I think Cloud Spanner is the best option here.

upvoted 0 times

...

Tayna

7 months ago

Bigtable is great for large datasets!

upvoted 0 times

...

Isadora

7 months ago

I practiced a similar question where using Kubernetes helped with scaling, but I wonder if that would actually reduce latency as much as the database migrations would.

upvoted 0 times

...

Nieves

7 months ago

I feel like Firestore in Datastore mode might be a simpler solution, but I can't recall if it really offers the performance boost we need for global users.

upvoted 0 times

...

Tijuana

7 months ago

I think migrating to Bigtable could be a good option since it’s designed for scalability, but I’m not completely confident about the read/write consistency.

upvoted 0 times

...

Coral

8 months ago

I remember we discussed how Cloud Spanner can handle global transactions with low latency, but I'm not sure if it's the best fit for this case.

upvoted 0 times

...

Clay

8 months ago

I'm leaning towards option D - moving to GKE and using a load balancer. That could help scale the application and improve overall performance, without the need for a full database migration. Seems like the least amount of effort to achieve the goal.

upvoted 0 times

...

Gabriele

8 months ago

Okay, let's think this through. The key is to reduce latency for all database interactions, not just reads. Migrating to a fully managed service like Bigtable or Cloud Spanner could help with that, but it might be a lot of effort. I'd want to explore other options first.

upvoted 0 times

...

Azzie

8 months ago

Hmm, I'm a bit confused. The question mentions they already have read replicas set up, so I'm not sure if migrating the entire database is the best solution. Maybe there's a way to optimize the existing setup further?

upvoted 0 times

...

Nydia

8 months ago

This question seems straightforward - we just need to find the option that reduces latency with the least effort. I think migrating to a fully managed database service like Cloud Spanner or Firestore could be a good approach.

upvoted 0 times

...

Becky

8 months ago

I feel like I've seen a question about calling Freestyle Jobs in a Pipeline before, and I think it is possible.

upvoted 0 times

...

Jame

8 months ago

I'm not totally confident, but I'm leaning towards D - universal. That seems like the rule type that would cover both intra- and inter-zone traffic.

upvoted 0 times

...

Terina

1 year 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

Jeff

11 months ago

True, managed databases like Cloud Spanner can definitely improve performance.

upvoted 0 times

...

Artie

11 months ago

I think Cloud Spanner is more suitable for serving global user traffic efficiently.

upvoted 0 times

...

Delbert

11 months ago

But what about Bigtable? Wouldn't that also help with reducing latency?

upvoted 0 times

...

Aleisha

11 months ago

I agree, Cloud Spanner seems like the best option for reducing latency.

upvoted 0 times

...

Jamal

12 months ago

C) Migrate the database to Firestore in Datastore mode and use it to serve all global user traffic.

upvoted 0 times

...

Oretha

12 months ago

B) Migrate the database to Cloud Spanner and use it to serve all global user traffic.

upvoted 0 times

...

Louann

12 months ago

A) Migrate the database to Bigtable and use it to serve all global user traffic.

upvoted 0 times

...

Regenia

1 year 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

1 year 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

12 months ago

upvoted 0 times

...

Thurman

12 months ago

B) Migrate the database to Cloud Spanner and use it to serve all global user traffic.

upvoted 0 times

...

Felicidad

1 year ago

A) Migrate the database to Bigtable and use it to serve all global user traffic.

upvoted 0 times

...

Kina

1 year 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

12 months ago

I think the Kubernetes Engine option could work, but it might be overkill for just improving database latency.

upvoted 0 times

...

Jeffrey

12 months 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 year 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 year ago

C) Migrate the database to Firestore in Datastore mode and use it to serve all global user traffic.

upvoted 0 times

...

Shenika

1 year ago

B) Migrate the database to Cloud Spanner and use it to serve all global user traffic.

upvoted 0 times

...

Eve

1 year ago

A) Migrate the database to Bigtable and use it to serve all global user traffic.

upvoted 0 times

...

Paris

1 year 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

1 year 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

1 year 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

1 year ago

I think option B is the best choice because Cloud Spanner is designed for global scalability.

upvoted 0 times

...