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

Actual exam question for Google's Apigee-API-Engineer exam
Question #: 5
Topic #: 10
[All Apigee-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

Contribute your Thoughts:

Adelle
1 months ago
I think all options are correct, but A and D are the most important ones to consider.
upvoted 0 times
...
Rosendo
1 months ago
I'm not sure about B and C, but A and D seem logical.
upvoted 0 times
...
Kara
1 months ago
I agree with Christoper, A and D make sense.
upvoted 0 times
...
Sunny
2 months 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
2 months 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
18 days ago
C) It is possible to make fewer than 5 requests in a second and still cause a spike arrest
upvoted 0 times
...
Chu
20 days 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
23 days 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
2 months ago
I think A and D are correct.
upvoted 0 times
...
Audra
2 months 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 months 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 months 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
2 months 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
3 months 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
2 months 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
2 months ago
C) It is possible to make fewer than 5 requests in a second and still cause a spike arrest
upvoted 0 times
...
Refugia
2 months 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