mediumMultiple ChoiceObjective-mapped
200-901 Practice Question: A developer has created a Webex Teams bot that…
A developer has created a Webex Teams bot that listens for messages in a specific room and responds with information from an external database. The bot uses the Webex API's 'messages.create' method to post replies. During testing, the bot sometimes fails to respond, but no errors are logged. The developer checks the Webex Developer Portal and sees that the bot's rate limit is set to 10 requests per second. The bot's average load is 5 requests per second, but occasionally spikes to 15 requests per second for a few seconds. The developer wants to ensure the bot functions reliably without exceeding rate limits. Which approach should the developer implement?
⚠ Common exam trap
Cisco often tests the misconception that simply catching HTTP 429 errors and retrying immediately is sufficient, when in fact exponential backoff is required to avoid compounding the rate limit violation.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Implement a request queue that limits outgoing requests to 10 per second and uses exponential backoff on failure.
Implementing a request queue that limits outgoing requests to 10 per second and uses exponential backoff on failure ensures the bot respects the Webex API rate limit of 10 requests per second. The queue smooths out spikes (e.g., 15 req/s) by buffering excess requests, while exponential backoff handles any HTTP 429 responses gracefully by retrying after increasing delays, preventing further rate limit violations. This approach directly addresses the bot's intermittent failure without relying on external support or sacrificing functionality.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Implement a request queue that limits outgoing requests to 10 per second and uses exponential backoff on failure.
Why this is correct
This ensures steady request rate and handles errors gracefully.
- ✗
Request a higher rate limit from the Webex API support team.
Why it's wrong here
This is external and not guaranteed; programmatic handling is required.
- ✗
Catch HTTP 429 (Too Many Requests) errors and immediately retry the request.
Why it's wrong here
Immediate retry may continue to hit the rate limit; exponential backoff is needed.
- ✗
Reduce the bot's overall request rate to 5 per second to stay well within the limit.
Why it's wrong here
This reduces responsiveness and may still have spikes that exceed the limit.
Go deeper
Related to this question
About these practice questions
One of 989 original 200-901 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 200-901 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-901 exam.