MENU
Which statements ate true when the following policy is used? Select all that are correct.
Suggested Answer: D
Get Premium Google Cloud - Apigee Certified API Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
31 comments · newest first
SU
Sunshine
10 months ago
D sounds right, continueOnError means it keeps going, right?
VE
Veronika
10 months ago
C is interesting, but how can you spike with fewer requests?
GR
Gracia
10 months ago
I disagree with B, it shouldn't allow more than 5 overall.
BI
Billye
11 months ago
A is definitely true, 5 requests max!
AD
Adelina
11 months ago
Wait, really? I thought SpikeArrest would just block everything after 5!
EL
Elly
11 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.
CA
Cathrine
11 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.
SU
Susy
11 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.
GR
Gregoria
12 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.
CR
Crista
12 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.
CA
Catalina
1 year 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.
DE
Denna
1 year ago
Hmm, the continueOnError setting is throwing me off a bit. I'll need to review how that impacts the behavior.
DE
Denise
1 year ago
The spike arrest rate of 5 per second seems straightforward, but the other settings could make this more complex than it appears.
DI
Dick
1 year ago
This looks like a tricky question on spike arrest policies. I'll need to think through the details carefully.
AD
Adelle
1 year ago
I think all options are correct, but A and D are the most important ones to consider.
RO
Rosendo
1 year ago
I'm not sure about B and C, but A and D seem logical.
KA
Kara
1 year ago
I agree with Christoper, A and D make sense.
SU
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!
LO
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.
VA
Vannessa
1 year ago
C) It is possible to make fewer than 5 requests in a second and still cause a spike arrest
CH
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
NO
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
CH
Christoper
1 year ago
I think A and D are correct.
AU
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.
DA
Dalene
1 year ago
C) It is possible to make fewer than 5 requests in a second and still cause a spike arrest
WI
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
TA
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
NA
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.
BR
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.
PA
Pamella
1 year ago
C) It is possible to make fewer than 5 requests in a second and still cause a spike arrest
RE
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