Cisco 350-901 Exam - Topic 7 Question 54 Discussion

Actual exam question for Cisco's 350-901 exam

Question #: 54
Topic #: 7

Refer to the exhibit.

This snippet of a script has recently started exiting abnormally with an exception stating ''Unexpected HTTP Response code: 429''.

Which solution handles rate limiting by the remote API?

AOption A

BOption B

COption C

DOption D

Show Suggested Answer

Suggested Answer: B

by Dierdre at Apr 26, 2023, 05:52 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Peggie

10 months ago

Not sure about that, I’ve had issues with Option A before.

upvoted 0 times

...

Sharee

10 months ago

Totally agree with Option B, it’s the most reliable.

upvoted 0 times

...

Ressie

10 months ago

Wait, is that a 429 error? I thought it was just a timeout!

upvoted 0 times

...

Jacqueline

11 months ago

I think Option C might actually handle it better.

upvoted 0 times

...

Avery

11 months ago

Option B is definitely the way to go for rate limiting.

upvoted 0 times

...

Pearline

11 months ago

I vaguely remember that we should also consider implementing a delay between requests. I hope one of the options covers that, but I can't quite picture them right now.

upvoted 0 times

...

Edward

11 months ago

I feel like option B might be the answer since it mentions exponential backoff, which we talked about as a way to handle rate limits. But I’m a bit uncertain.

upvoted 0 times

...

Lavonda

11 months ago

I practiced a similar question about handling API responses. I think implementing a retry mechanism could be the right approach, but I can't recall if that's in one of the options.

upvoted 0 times

...

Daniel

11 months ago

I remember we discussed HTTP status codes in class, and 429 means too many requests. I think it relates to rate limiting, but I'm not sure which option specifically addresses that.

upvoted 0 times

...

Ashlyn

11 months ago

I think the key here is understanding how the email address is updated in the system. If it's not updated in All Subscribers, then option B is likely the correct answer.

upvoted 0 times

...

Magda

11 months ago

Okay, let's see here. The key things I need to remember are the compression, deduplication, and quota settings. I think I can piece this together.

upvoted 0 times

...

Tish

11 months ago

I think the dependent variable is always supposed to be a measure of behavior, but I'm not totally sure if it fits with this specific statement.

upvoted 0 times

...

Virgilio

1 year ago

Option B all the way. Retry with a specific delay is the API's way of saying 'Chill out, dude. I need a breather.'

upvoted 0 times

Chau

1 year ago

I've had success with Option D in the past. It's worth considering as well.

upvoted 0 times

...

Leah

1 year ago

I think Option C might also work, it could help manage the rate limiting more efficiently.

upvoted 0 times

...

Veronika

1 year ago

I agree, Option B is the way to go. It gives the API some time to recover.

upvoted 0 times

...

Rupert

1 year ago

I'm not sure what 'backoff' means, but Option B seems the most straightforward solution. This 'unexpected HTTP 429' error is really starting to bug me!

upvoted 0 times

Leonida

1 year ago

User1: Yeah, that HTTP 429 error can be really annoying.

upvoted 0 times

...

Keneth

1 year ago

User2: I agree, Option B seems like the most straightforward solution.

upvoted 0 times

...

Loren

1 year ago

User1: Option B is the way to go for handling rate limiting.

upvoted 0 times

...

Colene

1 year ago

Option C with the 'backoff' strategy seems like a good approach too. Gradually increasing the delay between retries is a sensible way to deal with rate limiting.

upvoted 0 times

...

Joseph

1 year ago

The 'retry_after' parameter in Option B looks like the best way to handle the rate limiting issue. It allows the script to gracefully wait and try again after the specified time.

upvoted 0 times