Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional-Cloud-Developer Topic 14 Question 75 Discussion

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

You are a lead developer working on a new retail system that runs on Cloud Run and Firestore. A web UI requirement is for the user to be able to browse through alt products. A few months after go-live, you notice that Cloud Run instances are terminated with HTTP 500: Container instances are exceeding memory limits errors during busy times

This error coincides with spikes in the number of Firestore queries

You need to prevent Cloud Run from crashing and decrease the number of Firestore queries. You want to use a solution that optimizes system performance What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Ruth
10 days ago
Hmm, I don't know. I'm kind of partial to option C. Sure, it might not be the most sustainable solution, but it could buy us some time to figure out a better long-term strategy. And let's be real, sometimes you just gotta do what you gotta do to keep the system running, you know?
upvoted 0 times
...
Elmira
11 days ago
You know, I was thinking the same thing, Jannette. Using cursors and limits is probably the way to go. It's more efficient than relying on offsets, and it should help keep those Firestore queries under control.
upvoted 0 times
...
Jannette
12 days ago
I'm leaning towards option B. Modifying the query to use cursors and limits could help reduce the load on Firestore and prevent those memory issues on Cloud Run. Plus, it seems like a more elegant solution than just throwing more resources at the problem.
upvoted 0 times
...
Noemi
13 days ago
Ugh, this question is tricky. I'm not sure if I should go with option B or C. Increasing the memory limits on Cloud Run might help, but I'm worried that won't be a long-term solution if the Firestore queries are the real issue.
upvoted 0 times
...

Save Cancel