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 Cloud - Apigee Certified API Engineer Exam - Topic 10 Question 5 Discussion

Which statements ate true when the following policy is used? Select all that are correct.5ps
D) The continueOnError setting means that normal flow processing will resume even if the traffic exceeds the spike arrest rate
A) The rate of 5 per second indicates that 5 requests can be made at any time during a second: but the 6th and later requests dunng the same second would be rejected
B) Spike arrest is calculated separately on each message processor, so you could end up with significantly more than 5 calls in a second
C) It is possible to make fewer than 5 requests in a second and still cause a spike arrest

Google Cloud - Apigee Certified API Engineer Exam - Topic 10 Question 5 Discussion

Actual exam question for Google's Google Cloud - Apigee Certified API Engineer exam
Question #: 5
Topic #: 10
[All Google Cloud - Apigee Certified API Engineer Questions]

Which statements ate true when the following policy is used? Select all that are correct.

5ps

Show Suggested Answer Hide Answer
Suggested Answer: D

by Theodora at May 04, 2025, 04:25 PM

Limited Time Offer

25%

Off

Get Premium Google Cloud - Apigee Certified API Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Sunshine
7 months ago
D sounds right, continueOnError means it keeps going, right?
upvoted 0 times
...
Veronika
7 months ago
C is interesting, but how can you spike with fewer requests?
upvoted 0 times
...
Gracia
7 months ago
I disagree with B, it shouldn't allow more than 5 overall.
upvoted 0 times
...
Billye
7 months ago
A is definitely true, 5 requests max!
upvoted 0 times
...
Adelina
7 months ago
Wait, really? I thought SpikeArrest would just block everything after 5!
upvoted 0 times
...
Elly
8 months ago
Option D seems off to me. I thought the continueOnError setting would actually stop processing if the limit is exceeded, not let it continue.
upvoted 0 times
...
Cathrine
8 months ago
I feel like option C could be true too. If there are fewer than 5 requests, maybe there's still a way to trigger the spike arrest? I need to double-check that.
upvoted 0 times
...
Susy
8 months ago
I'm not so sure about option B. I remember something about how SpikeArrest works, but I thought it applied globally, not separately on each processor.
upvoted 0 times
...
Gregoria
8 months ago
I think option A is correct because it mentions that only 5 requests are allowed per second, and the 6th would be rejected. That sounds right.
upvoted 0 times
...
Crista
9 months ago
The wording on some of these options is a bit confusing. I'll need to re-read them a few times to make sure I understand the nuances.
upvoted 0 times
...
Catalina
9 months ago
Okay, I think I have a handle on this. Let me walk through the different options and see which ones make sense given the policy details.
upvoted 0 times
...
Denna
9 months ago
Hmm, the continueOnError setting is throwing me off a bit. I'll need to review how that impacts the behavior.
upvoted 0 times
...
Denise
9 months ago
The spike arrest rate of 5 per second seems straightforward, but the other settings could make this more complex than it appears.
upvoted 0 times
...
Dick
9 months ago
This looks like a tricky question on spike arrest policies. I'll need to think through the details carefully.
upvoted 0 times
...
Adelle
1 year ago
I think all options are correct, but A and D are the most important ones to consider.
upvoted 0 times
...
Rosendo
1 year ago
I'm not sure about B and C, but A and D seem logical.
upvoted 0 times
...
Kara
1 year ago
I agree with Christoper, A and D make sense.
upvoted 0 times
...
Sunny
1 year ago
Haha, good thing I don't work in a call center, or I'd be constantly getting spike arrests! 5 calls per second? That's like lightning fast!
upvoted 0 times
...
Lorrine
1 year ago
D is just wrong. The 'continueOnError' setting means the message will continue processing even if the spike arrest is triggered. That's the opposite of what it's saying.
upvoted 0 times
Vannessa
1 year ago
C) It is possible to make fewer than 5 requests in a second and still cause a spike arrest
upvoted 0 times
...
Chu
1 year ago
B) Spike arrest is calculated separately on each message processor, so you could end up with significantly more than 5 calls in a second
upvoted 0 times
...
Nohemi
1 year ago
A) The rate of 5 per second indicates that 5 requests can be made at any time during a second: but the 6th and later requests during the same second would be rejected
upvoted 0 times
...
...
Christoper
1 year ago
I think A and D are correct.
upvoted 0 times
...
Audra
1 year ago
B is definitely true. If you have multiple message processors, the spike arrest would be calculated separately on each one, so you could easily exceed the 5 per second limit.
upvoted 0 times
Dalene
1 year ago
C) It is possible to make fewer than 5 requests in a second and still cause a spike arrest
upvoted 0 times
...
Willetta
1 year ago
B) Spike arrest is calculated separately on each message processor, so you could end up with significantly more than 5 calls in a second
upvoted 0 times
...
Tasia
1 year ago
A) The rate of 5 per second indicates that 5 requests can be made at any time during a second: but the 6th and later requests during the same second would be rejected
upvoted 0 times
...
...
Nan
1 year ago
A and C seem correct. The policy clearly states the rate is 5 per second, so anything above that would be rejected.
upvoted 0 times
Brigette
1 year ago
User: A and C seem correct. The policy clearly states the rate is 5 per second, so anything above that would be rejected.
upvoted 0 times
...
Pamella
1 year ago
C) It is possible to make fewer than 5 requests in a second and still cause a spike arrest
upvoted 0 times
...
Refugia
1 year ago
A) The rate of 5 per second indicates that 5 requests can be made at any time during a second: but the 6th and later requests during the same second would be rejected
upvoted 0 times
...
...

Save Cancel