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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

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

by Deandrea at Jan 26, 2024, 06:23 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Mila
4 months ago
Wait, are we really hitting memory limits? That's unexpected!
upvoted 0 times
...
Bettye
4 months ago
I disagree, using integer offsets can lead to performance issues.
upvoted 0 times
...
Maybelle
4 months ago
A custom index could help optimize queries too!
upvoted 0 times
...
Lourdes
4 months ago
Isn't increasing memory limits just a band-aid solution?
upvoted 0 times
...
Lelia
4 months ago
I think modifying the query with cursors is the way to go.
upvoted 0 times
...
Krissy
5 months ago
I practiced a similar question where using limits on queries helped reduce load, so I’m leaning towards modifying the query with cursors.
upvoted 0 times
...
Sharika
5 months ago
I feel like creating a custom index could improve query performance, but I’m not entirely sure how that interacts with memory issues.
upvoted 0 times
...
Twana
5 months ago
I think increasing the memory limits for Cloud Run could help, but it might just be a temporary fix. We should really focus on optimizing the queries.
upvoted 0 times
...
Tasia
5 months ago
I remember we discussed optimizing Firestore queries in class, but I'm not sure if using cursors or offsets is better for performance.
upvoted 0 times
...
Dominic
5 months ago
Modifying the query to use integer offsets instead of cursors is an interesting idea, but I'm not sure if that will have the same performance benefits. I'll need to weigh the pros and cons of each approach.
upvoted 0 times
...
Gracia
5 months ago
Creating a custom index over the products could help speed up the queries, but I'm not sure if that alone will be enough to prevent the Cloud Run instances from crashing. I'll need to consider a more comprehensive solution.
upvoted 0 times
...
Sunshine
5 months ago
Cursors with limits sounds like a good way to optimize the Firestore queries and reduce the load on the system. I'll make sure to research that approach in more detail.
upvoted 0 times
...
Vallie
5 months ago
Hmm, the memory limits issue on Cloud Run is definitely the key problem to address here. I'm leaning towards modifying the Cloud Run configuration to increase the memory limits.
upvoted 0 times
...
Noe
5 months ago
This seems like a tricky one. I'll need to think through the different options carefully to figure out the best approach.
upvoted 0 times
...
Dulce
6 months ago
Okay, I remember learning that IPv4 addresses are made up of 4 octets, each 8 bits long. So the total length must be 32 bits. I'll select A.
upvoted 0 times
...
Verda
6 months ago
Okay, I think I've got it. The key is in the "type of database use" column - it says "application data access only", so the database can't be used for certain other purposes.
upvoted 0 times
...
Ruth
2 years 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
2 years 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
Wilda
2 years ago
Agreed, let's go ahead and implement the solution and keep an eye on the system's performance.
upvoted 0 times
...
Ezekiel
2 years ago
Let's make the changes and monitor the performance to see if it helps with the memory limits issue.
upvoted 0 times
...
Mary
2 years ago
Definitely, optimizing the queries will benefit the overall system in the long run.
upvoted 0 times
...
Micheal
2 years ago
I'm on board with that plan, it seems like the most efficient way to handle the situation.
upvoted 0 times
...
Krystal
2 years ago
Sounds good to me, let's implement that solution to prevent Cloud Run from crashing during busy times.
upvoted 0 times
...
Theodora
2 years ago
I agree, it will help optimize the system performance and reduce the number of Firestore queries.
upvoted 0 times
...
Lottie
2 years ago
I think we should go with option B and modify the query with cursors and limits.
upvoted 0 times
...
...
Jannette
2 years 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
2 years 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