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 4 Question 78 Discussion

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

You are supporting a business-critical application in production deployed on Cloud Run. The application is reporting HTTP 500 errors that are affecting the usability of the application. You want to be alerted when the number of errors exceeds 15% of the requests within a specific time window. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Lashawn
3 months ago
I still think setting up an alerting policy directly in Cloud Monitoring is the simplest solution.
upvoted 0 times
...
Viva
3 months ago
That's true, automation would save time and ensure timely alerts.
upvoted 0 times
...
Man
3 months ago
I think using Cloud Function with Cloud Scheduler would provide a more automated approach.
upvoted 0 times
...
Cristen
3 months ago
But wouldn't it be more efficient to use Cloud Function with Cloud Composer to trigger the alert?
upvoted 0 times
...
Lashawn
4 months ago
I agree, setting up an alerting policy seems like the most direct way to get notified.
upvoted 0 times
...
Viva
4 months ago
I think the best option is to create an alerting policy in Cloud Monitoring.
upvoted 0 times
...
Janet
4 months ago
I think I would still prefer option C for simplicity, but I can see the benefits of automating with Cloud Function and Cloud Scheduler.
upvoted 0 times
...
Maricela
4 months ago
That's a good point. Maybe it's worth considering option D for a more automated approach.
upvoted 0 times
...
Milly
4 months ago
But wouldn't it be more proactive to use a Cloud Function with Cloud Scheduler to alert us daily?
upvoted 0 times
...
Karrie
4 months ago
I agree, setting up an alerting policy in Cloud Monitoring seems like the best choice to get notified quickly.
upvoted 0 times
...
Caprice
5 months ago
I think option C sounds like the easiest and most straightforward solution.
upvoted 0 times
...
Eliz
6 months ago
Haha, yeah, I hear you. Anything that can save us from writing and maintaining more code is a win in my book. Option C is definitely the easiest and most straightforward solution here.
upvoted 0 times
Keena
5 months ago
Creating an alerting policy in Cloud Monitoring is the way to go for this scenario.
upvoted 0 times
...
Tegan
5 months ago
Agreed, simplicity is key when dealing with production issues.
upvoted 0 times
...
Tammara
6 months ago
I prefer solutions that require minimal code and maintenance.
upvoted 0 times
...
Beula
6 months ago
It's simple and effective to get notified when errors exceed 15% of requests.
upvoted 0 times
...
Willie
6 months ago
Yeah, I agree. Setting up an alerting policy in Cloud Monitoring is convenient.
upvoted 0 times
...
Veronica
6 months ago
Option C is definitely the easiest and most straightforward solution here.
upvoted 0 times
...
...
Mel
6 months ago
Yeah, I was leaning towards option C as well. It's simple, out-of-the-box, and will get the job done without any extra overhead. Plus, I don't really want to be responsible for managing a Cloud Function or a Composer workflow, you know?
upvoted 0 times
...
Rosendo
6 months ago
I agree with Vesta. Option C seems like the way to go. It's built-in functionality in Google Cloud, so we don't need to worry about setting up any additional infrastructure like a Cloud Function or Cloud Composer.
upvoted 0 times
...
Vesta
6 months ago
Hmm, this is a pretty straightforward question. I think the best approach here is option C - creating an alerting policy in Cloud Monitoring. It's the most direct and efficient way to get alerted when the error rate exceeds the threshold.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77