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

Salesforce Certified MuleSoft Hyperautomation Developer (Mule-Dev-202) Exam - Topic 8 Question 19 Discussion

Posted by Brittani on Dec 08, 2024 at 01:10 PM

AnyAirlines releases a new REST API that exposes access to an RPA process. The RPA process can only handle a limited number of interactions per second before the API begins returning errors.

Which policy should AnyAirlines apply to prevent the API from being overloaded?

Suggested Answer: C

To prevent an API from being overloaded, the Spike Control policy is suitable. It helps manage sudden bursts of traffic by limiting the rate at which requests are processed. Here's how it works:

Preventing Overloads:

Spike Control smooths out bursts of incoming requests by enforcing a rate limit over a short period, protecting the backend systems from being overwhelmed by excessive traffic.

Configuration:

Apply the Spike Control policy to the API to define the maximum number of requests allowed within a specific timeframe.

This ensures that the API can handle a limited number of interactions per second, preventing errors due to overload.

Implementation:

In Anypoint Platform, configure the Spike Control policy to the desired thresholds, ensuring the RPA process can handle the load effectively without errors.


Anypoint Platform Spike Control Documentation

Get Premium Salesforce Certified MuleSoft Hyperautomation Developer (Mule-Dev-202) Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
33 comments · newest first
MI
Miss 11 months ago
Definitely not JSON threat protection, that's irrelevant here.
DA
Darrin 11 months ago
Surprised they didn't mention caching options!
KE
Keneth 12 months ago
Client ID Enforcement seems unnecessary for this.
JO
Jolanda 12 months ago
I think Spike Control could work too.
BE
Ben 1 year ago
Rate Limiting - SLA is the way to go!
LA
Lavera 1 year ago
I feel like we had a similar question about API management, and rate limiting was definitely the answer there too.
JA
Jackie 1 year ago
Client ID enforcement sounds familiar, but I don't think it directly addresses the issue of overloading the API.
DE
Delfina 1 year ago
I'm not entirely sure, but I think spike control might be relevant since it deals with sudden bursts of traffic.
DY
Dyan 1 year ago
I remember we discussed rate limiting in class, and it seems like the best option here to manage the number of interactions.
MO
Moira 1 year ago
I'm a bit confused by the different choices. JSON threat protection and Client ID Enforcement don't seem directly relevant to the problem. I'm leaning towards Spike Control, but I'll double-check the details.
IR
Irene 1 year ago
Okay, let's see. The key is to find a policy that can handle the limited number of interactions per second. I think Rate Limiting - SLA is the best option here.
JA
Jarvis 1 year ago
Hmm, I'm not sure about this one. I'll have to think it through carefully. Maybe Spike Control could work, but I'm not totally confident.
JO
Joaquin 1 year ago
This seems like a straightforward API protection question. I'd go with Rate Limiting - SLA to prevent the API from being overloaded.
TE
Teresita 2 years ago
I'm feeling spicy - C. Spike Control! Gotta keep those API requests from getting too hot to handle.
LA
Lachelle 2 years ago
B. Rate Limiting - SLA is the way to go. Don't want the flight attendants to start handing out free in-flight entertainment, if you catch my drift.
AL
Alfreda 2 years ago
↳ replying to Lachelle
Zena: True, but Rate Limiting is more specific to this scenario.
DO
Dottie 2 years ago
↳ replying to Lachelle
User 3: C) Spike Control could also help prevent overload.
ZE
Zena 2 years ago
↳ replying to Lachelle
User 2: Agreed, we need to control the number of interactions per second.
ED
Edda 2 years ago
↳ replying to Lachelle
User 1: B) Rate Limiting - SLA
FI
Fidelia 2 years ago
D. Client ID Enforcement, of course. Gotta keep those API keys on lock-down, you know what I'm saying?
LO
Louis 2 years ago
C. Spike Control all the way! Ain't nobody got time for those pesky API errors.
KA
Karol 2 years ago
↳ replying to Louis
C) Spike Control
SH
Sharan 2 years ago
↳ replying to Louis
B) Rate Limiting - SLA
TE
Tennie 2 years ago
↳ replying to Louis
A) JSON threat protection
JE
Jesusita 2 years ago
Client ID Enforcement could also be useful to track and limit the number of interactions from each client.
PA
Paris 2 years ago
I believe Spike Control could also be a good option to prevent sudden spikes in interactions.
RO
Robt 2 years ago
I agree with Cecilia, Rate Limiting - SLA would help prevent the API from being overloaded.
DO
Dottie 2 years ago
Hmm, I'd go with B. Rate Limiting - SLA to prevent that API from getting overloaded. Gotta keep those flights running smoothly, right?
BL
Blair 2 years ago
↳ replying to Dottie
Let's go with Rate Limiting - SLA then. It's the best option for this situation.
WH
Whitney 2 years ago
↳ replying to Dottie
Definitely, we don't want any errors causing disruptions.
DA
Darci 2 years ago
↳ replying to Dottie
Agreed, we need to make sure the API can handle the traffic.
SU
Susana 2 years ago
↳ replying to Dottie
I think B is the way to go. Rate Limiting - SLA will help prevent overload.
CE
Cecilia 2 years ago
I think the best policy would be Rate Limiting - SLA.
0/2000 characters

Save Cancel