MENU
Which API policy can be applied to limit the number of requests an individual client can make to an API?
Suggested Answer: A
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
In Flow Builder, Run and Debug modes have distinct functionalities:
Run Mode:
Executes the flow as it is, allowing you to see the end-to-end execution based on the latest saved version.
Typically used to verify that the flow works as expected under normal conditions.
Debug Mode:
Provides detailed information for each step of the flow, including input and output data, and any errors encountered.
Useful for troubleshooting and identifying issues within the flow, allowing developers to understand how the flow executes and where problems may arise.
Debug mode is specifically designed to aid in diagnosing and fixing issues by providing a granular view of the flow's execution.
34 comments · newest first
MA
Madonna
11 months ago
I disagree, Rate limiting is the standard approach.
MA
Mammie
11 months ago
Wait, can OAuth 2.0 really limit requests? Seems odd.
RO
Roselle
12 months ago
Definitely Client ID Enforcement for tracking individual users.
AR
Arlene
12 months ago
I think Spike Control is more effective for sudden bursts.
AN
Antonette
1 year ago
Rate limiting - SLA-Based is the way to go!
SA
Samuel
1 year ago
I’m leaning towards C, but I vaguely recall that Spike Control also has something to do with managing request loads.
GA
Garry
1 year ago
I feel like Client ID Enforcement might be about authentication rather than limiting requests, but I could be wrong.
TH
Theola
1 year ago
I remember practicing a similar question, and I think rate limiting is definitely related to controlling request numbers.
TE
Teri
1 year ago
I think it's either B or C, but I'm not entirely sure which one specifically limits requests per client.
WA
Wai
1 year ago
OAuth 2.0 access token enforcement could also be a valid option, since that would allow you to control access and limit requests at the token level. But Spike Control does seem like the most direct approach for this scenario.
SH
Shaquana
1 year ago
Definitely Spike Control. That's the policy that allows you to set limits on the number of requests a client can make within a certain time frame, right? Seems like the most straightforward solution here.
NI
Nicholle
1 year ago
Hmm, I'm not sure about this one. I'll have to think it through carefully. Maybe Client ID Enforcement or Rate limiting - SLA-Based could also work?
OR
Ora
1 year ago
I think the answer is Spike Control, since that policy is specifically designed to limit the number of requests a client can make to an API.
RE
Rex
1 year ago
Okay, let me think this through. The key seems to be that the principle is about ensuring privacy doesn't come at the expense of functionality. I'm leaning towards option D, but I'll double-check the wording to be sure.
EL
Elouise
1 year ago
I hope the exam doesn't have any trick questions like 'How many chickens can fit in an API?' That would really ruffle my feathers!
LE
Levi
2 years ago
I'm going to go with C) Rate limiting - SLA-Based. It just sounds like the most straightforward way to cap the number of requests from a client.
EL
Elinore
1 year ago
I'm not sure, but A) Client ID Enforcement might also be a valid option for limiting requests.
ZA
Zana
1 year ago
I think D) OAuth 2.0 access token enforcement could also be a good choice to limit requests.
MI
Mitsue
1 year ago
I agree, C) Rate limiting - SLA-Based seems like the best option to control the number of requests.
ER
Erick
2 years ago
B) Spike Control could also be a valid answer, as it helps regulate the incoming traffic to an API and prevent spikes in usage.
MA
Ma
1 year ago
C) Rate limiting - SLA-Based
VI
Victor
1 year ago
B) Spike Control
GE
Georgeanna
1 year ago
A) Client ID Enforcement
BU
Bulah
2 years ago
D) OAuth 2.0 access token enforcement sounds like a good option too, but I'm not sure if it's specifically for limiting the number of requests.
GR
Graham
2 years ago
C) Rate limiting - SLA-Based is another option to restrict the number of requests a client can make.
JO
Johnetta
2 years ago
A) Client ID Enforcement can be used to limit the number of requests an individual client can make to an API.
FR
Frankie
2 years ago
I think the correct answer is C) Rate limiting - SLA-Based. This policy allows you to set limits on the number of requests a client can make to an API.
FR
Francoise
1 year ago
Rate limiting is a common practice in API management.
KI
Kina
1 year ago
It's important to control the number of requests to prevent overload.
JA
Janae
1 year ago
Yes, that policy allows you to set limits on the number of requests a client can make.
TA
Taryn
2 years ago
I believe the correct answer is C) Rate limiting - SLA-Based.
IS
Isabella
2 years ago
I'm not sure, but I think OAuth 2.0 access token enforcement could also be a valid option.
DO
Dong
2 years ago
I agree with Selene. Rate limiting is commonly used to control the number of requests.
SE
Selene
2 years ago
I think the answer is C) Rate limiting - SLA-Based.