Cisco 200-901 Exam - Topic 4 Question 67 Discussion

Actual exam question for Cisco's 200-901 exam

Question #: 67
Topic #: 4

A developer must test the performance and reliability of an application. After functional and load tests are run, the application crashes due to traffic spikes from users. Which type of API constraint must be implemented to maintain reliability?

Arate limiting

Bpagination

Cpayload limits

Dfiltering

Show Suggested Answer

Suggested Answer: A

by Jolene at Dec 22, 2023, 07:28 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Sharika

9 months ago

Filtering won't solve the crash issue; it’s all about managing requests!

upvoted 0 times

...

Solange

9 months ago

Wait, are we sure rate limiting is the only solution? Seems too simple.

upvoted 0 times

...

Felton

10 months ago

Payload limits could help too, but rate limiting is key here.

upvoted 0 times

...

Ligia

10 months ago

I think pagination is more about data retrieval, not reliability.

upvoted 0 times

...

Johnson

10 months ago

Definitely rate limiting! It's essential for handling traffic spikes.

upvoted 0 times

...

Tayna

10 months ago

Filtering seems off-topic for this scenario; it’s more about refining data rather than managing user load.

upvoted 0 times

...

Keva

11 months ago

I feel like payload limits could also be relevant, but they don't directly address the issue of too many users at once.

upvoted 0 times

...

Mel

11 months ago

I'm not entirely sure, but I think pagination is more about managing data retrieval rather than handling traffic spikes.

upvoted 0 times

...

Page

11 months ago

I remember we discussed rate limiting in class as a way to control the number of requests a user can make. That seems like the right choice here.

upvoted 0 times

...

Cecil

11 months ago

Definitely go with rate limiting. That's the key API constraint to implement when you need to maintain reliability and prevent crashes during high traffic periods.

upvoted 0 times

...

Gail

11 months ago

Based on the question, I think rate limiting is the best answer. It allows you to set a limit on the number of requests per second/minute, which can help prevent the system from being overwhelmed during traffic spikes.

upvoted 0 times

...

Rory

11 months ago

I'm a bit confused on the difference between rate limiting and payload limits. Can those both help with reliability in this case?

upvoted 0 times

...

Laurel

11 months ago

Rate limiting seems like the obvious choice here. If the app is crashing due to traffic spikes, we need a way to control the incoming requests and prevent overloading the system.

upvoted 0 times

...

Kenia

11 months ago

Hmm, this seems like a tricky one. I'll need to think carefully about the different API constraints and how they relate to maintaining reliability.

upvoted 0 times

...

Krystina

11 months ago

Okay, I've got a strategy for this. I'll start by eliminating the options I'm sure aren't correct, like Jenkins and Travis CI, since they aren't directly related to GitOps. Then I'll focus on the remaining choices and try to determine which one is built on the GitOps toolkit.

upvoted 0 times

...

Berry

11 months ago

Okay, I think I have a good handle on the problem now. The key is to identify the right cloud design patterns to address the billing and provisioning challenges.

upvoted 0 times

...

Wendell

11 months ago

This looks like a straightforward architecture question. I'll start by identifying the three-tier structure they're asking about.

upvoted 0 times

...

Tammi

2 years ago

Filtering? Really? That's like using a water gun to put out a forest fire. Rate limiting is clearly the way to go here. Gotta keep those traffic spikes under control.

upvoted 0 times

...

Yun

2 years ago

Ah, come on, you guys are overthinking this. Payload limits are the way to go. Keep those payloads nice and small, and you won't have any issues with the application crashing.

upvoted 0 times

...

Lilli

2 years ago

I dunno, man. Pagination could be a good option too. Helps control the load on the system, right? Maybe a combination of rate limiting and pagination would be the way to go.

upvoted 0 times

Larue

2 years ago

We should consider both options to ensure the application runs smoothly.

upvoted 0 times

...

Anastacia

2 years ago

Yeah, that sounds like a solid plan for maintaining reliability.

upvoted 0 times

...

Sherly

2 years ago

Maybe a combination of rate limiting and pagination is the key.

upvoted 0 times

...

Cherelle

2 years ago

Yes, rate limiting could definitely help manage traffic spikes.

upvoted 0 times

...

Iola

2 years ago

I agree, but don't you think rate limiting would help too?

upvoted 0 times

...

Simona

2 years ago

Pagination could be a good option for controlling load.

upvoted 0 times

...

Nickolas

2 years ago

Whoa, this is a tough one! I'm definitely leaning towards rate limiting as the solution here. Seems like the best way to maintain reliability when you're dealing with traffic spikes.

upvoted 0 times

...