New Year Sale ! 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 PL
Mob_nav_barsMENU

Cisco Exam 350-901 Topic 6 Question 81 Discussion

Actual exam question for Cisco's 350-901 exam
Question #: 81
Topic #: 6
[All 350-901 Questions]

A developer is designing a modem, distributed microservice enterprise application. The application will be integrating with other systems and focus on a large deployment, so control of API calls is necessary. What is the best practice to reduce application response latency and protect the application from excessive use?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Helene at Sep 13, 2024, 08:15 AM

Limited Time Offer

25%

Off

Get Premium 350-901 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Ira
2 months ago
Option B all the way. Gotta love that dual-layer of defense against excessive API usage. Keeps the app running smoothly.
upvoted 0 times
...
Audria
2 months ago
Haha, option C is like saying 'Let's just let the users hammer our API until it crashes!' Not a smart move.
upvoted 0 times
Ivette
26 days ago
D: Option D seems like the best practice to ensure the application is protected and responsive.
upvoted 0 times
...
Fidelia
1 months ago
C: Yeah, option A is not enough to control excessive use and reduce latency.
upvoted 0 times
...
Venita
1 months ago
B: I agree, we need to implement rate limiting on both the client and server sides to protect the application.
upvoted 0 times
...
Cornell
2 months ago
A: Definitely not option C, that's just asking for trouble.
upvoted 0 times
...
...
Galen
2 months ago
I think option C is the worst choice here. No rate limiting at all? That's just asking for trouble!
upvoted 0 times
Annmarie
1 months ago
I think option D is a good compromise. Implementing rate limiting on the server side can still help protect the application without adding too much complexity.
upvoted 0 times
...
Annmarie
1 months ago
I think option B would be the best choice. Implementing rate limiting on both the client and server sides provides a more robust defense against excessive use.
upvoted 0 times
...
Annmarie
2 months ago
I agree, option C is definitely not the way to go. It leaves the application vulnerable to abuse.
upvoted 0 times
...
...
Pansy
2 months ago
Definitely option D. Implementing rate limiting on the server side is the most reliable way to control API calls and protect the application.
upvoted 0 times
Kerry
2 months ago
Implementing rate limiting on the server side is definitely the best practice for reducing latency and preventing excessive use.
upvoted 0 times
...
Jennie
2 months ago
I agree, server-side rate limiting provides better control and protection for the application.
upvoted 0 times
...
Benton
2 months ago
Option D is the way to go. Server-side rate limiting is key for controlling API calls.
upvoted 0 times
...
...
Leonard
2 months ago
I agree with Julio, having rate limiting on both sides provides a more robust protection against excessive use.
upvoted 0 times
...
Julio
3 months ago
I disagree, I believe implementing rate limiting on both client and server sides is more effective.
upvoted 0 times
...
Tammara
3 months ago
I think implementing rate limiting on the client side is the best practice.
upvoted 0 times
...
Roslyn
3 months ago
Option B is the way to go! Rate limiting on both client and server sides is the best way to protect the application and reduce latency.
upvoted 0 times
Arthur
2 months ago
D: Rate limiting on the server side is important for controlling API calls.
upvoted 0 times
...
Graham
2 months ago
C: It definitely helps protect the application and reduce latency.
upvoted 0 times
...
Dean
2 months ago
B: I agree, implementing rate limiting on both client and server sides is crucial.
upvoted 0 times
...
Portia
2 months ago
A: I think option B is the best choice.
upvoted 0 times
...
Ahmed
2 months ago
Implementing rate limiting on both sides will definitely help in managing the traffic and ensuring the application runs smoothly.
upvoted 0 times
...
Derick
3 months ago
I agree, it's important to have control over API calls to prevent excessive use and maintain application performance.
upvoted 0 times
...
Elenor
3 months ago
Option B is the way to go! Rate limiting on both client and server sides is the best way to protect the application and reduce latency.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77