Cisco Exam 350-901 Topic 13 Question 75 Discussion

Actual exam question for Cisco's 350-901 exam

Question #: 75
Topic #: 13

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?

AImplement rate limiting on the client side.

BImplement rate limiting on the client and server sides.

CDo not enforce any rate Imiting

DImplement rate limiting on the server side.

Show Suggested Answer

Suggested Answer: B

by Nenita at Jun 23, 2024, 08:39 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Ludivina

4 months ago

Ah, the age-old question of rate limiting. Option B is the way to go, my friends. Gotta protect that server and those clients from each other. Wouldn't want the whole system to go down in a blaze of glory, now would we?

upvoted 0 times

...

Franklyn

4 months ago

I'm gonna have to go with Option B. Gotta keep those API calls in check on both ends, you know? Can't have the server getting overwhelmed and the client just going wild. Balance is key, people!

upvoted 0 times

...

Selma

4 months ago

Option C? Are you kidding me? No rate limiting? That's like leaving the front door wide open and expecting no one to walk in. Definitely gotta go with Option B for this one.

upvoted 0 times

...

Fabiola

5 months ago

Option B is the way to do it. Gotta protect that API from being overloaded, am I right? Can't have the whole system crashing down because someone went a little trigger-happy with the requests.

upvoted 0 times

Madalyn

4 months ago

Yolando: Absolutely, we need to ensure the application can handle the load and maintain performance.

upvoted 0 times

...

Janna

4 months ago

It's important to control the flow of requests to prevent excessive use and reduce latency.

upvoted 0 times

...

Yolando

4 months ago

I agree, implementing rate limiting on both client and server sides is crucial for protecting the API.

upvoted 0 times

...

Jesusa

4 months ago

Option B is definitely the way to go. Can't risk the system getting overloaded.

upvoted 0 times

...

Paris

5 months ago

I think Option D is the best choice. Server-side rate limiting is the way to go - let the backend handle that heavy lifting. Keep those clients on a tight leash!

upvoted 0 times

Viva

3 months ago

I believe enforcing rate limiting on the server side is the most efficient solution.

upvoted 0 times

...

Izetta

3 months ago

I think implementing rate limiting on both the client and server sides would provide the best protection.

upvoted 0 times

...

Valentine

3 months ago

I agree, server-side rate limiting is definitely the way to go.

upvoted 0 times

...

Carli

3 months ago

Implementing rate limiting on the server side is the best practice for controlling API calls.

upvoted 0 times

...

Linn

4 months ago

I agree, server-side rate limiting is more secure and efficient.

upvoted 0 times

...

Hayley

4 months ago

Option D is definitely the way to go. Let the server handle the rate limiting.

upvoted 0 times

...

Delsie

5 months ago

I think not enforcing any rate limiting can lead to potential issues with application performance and security.

upvoted 0 times

...

Lucy

5 months ago

Option B is the way to go. Implementing rate limiting on both client and server sides ensures a robust and scalable solution. Gotta keep those API calls in check, you know?

upvoted 0 times