Cisco Exam 350-901 Topic 5 Question 68 Discussion

Actual exam question for Cisco's 350-901 exam

Question #: 68
Topic #: 5

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 Willow at Mar 15, 2024, 01:05 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Clarinda

6 months ago

I think not enforcing any rate limiting could lead to high usage and impact application performance.

upvoted 0 times

...

Terrilyn

6 months ago

That might be true, but having it on the server side adds an extra layer of protection.

upvoted 0 times

...

Allene

6 months ago

But wouldn't enforcing rate limiting on the client side only be enough to reduce response latency?

upvoted 0 times

...

Clarinda

7 months ago

I agree, it helps to control the flow of API calls and protect the application.

upvoted 0 times

...

Terrilyn

7 months ago

I think implementing rate limiting on both client and server sides is the best practice.

upvoted 0 times

...

Ty

7 months ago

I believe option B is the most secure approach, covering both client and server sides.

upvoted 0 times

...

Rachael

7 months ago

But wouldn't implementing rate limiting on both client and server sides be more effective in controlling API calls?

upvoted 0 times

...

Dean

7 months ago

I agree with Tammara, server-side rate limiting can prevent excessive use and reduce latency.

upvoted 0 times

...

Tammara

7 months ago

I think implementing rate limiting on the server side would be the best option.

upvoted 0 times

...

Teddy

8 months ago

I'm with Beckie on this one. B is the way to go. Gotta protect that application from getting hammered, but also keep those response times snappy. Can't have one without the other, you know?

upvoted 0 times

...

Tequila

8 months ago

Haha, C is just begging for some serious performance issues, don't you think? I mean, who in their right mind would choose to not enforce any rate limiting at all? That's just asking for trouble.

upvoted 0 times

...

Claribel

8 months ago

You know, I was initially thinking D - server-side rate limiting only. But then I realized that could lead to a lot of wasted client-side resources if the requests are getting throttled. B makes a lot more sense to me.

upvoted 0 times

...

Beckie

8 months ago

Hmm, this is a tricky one. I'm definitely leaning towards B - implementing rate limiting on both the client and server sides. That way, we can protect the application from excessive use and also ensure low response latency.

upvoted 0 times