Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco 350-201 Exam - Topic 12 Question 77 Discussion

A security incident affected an organization's critical business services, and the customer-side web API became unresponsive and crashed. An investigation revealed a spike of API call requests and a high number of inactive sessions during the incident. Which two recommendations should the engineers make to prevent similar incidents in the future? (Choose two.)
B) Determine API rate-limiting requirements. and D) Automate server-side error reporting for customers.
A) Configure shorter timeout periods.
C) Implement API key maintenance.
E) Decrease simultaneous API responses.

Cisco 350-201 Exam - Topic 12 Question 77 Discussion

Actual exam question for Cisco's 350-201 exam
Question #: 77
Topic #: 12
[All 350-201 Questions]

A security incident affected an organization's critical business services, and the customer-side web API became unresponsive and crashed. An investigation revealed a spike of API call requests and a high number of inactive sessions during the incident. Which two recommendations should the engineers make to prevent similar incidents in the future? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: B, D

Contribute your Thoughts:

0/2000 characters
Kati
8 months ago
I’m surprised they didn’t mention session management!
upvoted 0 times
...
Ruthann
9 months ago
Wait, why not just increase server capacity instead?
upvoted 0 times
...
Marylou
9 months ago
Shorter timeout periods make sense too!
upvoted 0 times
...
Yolande
9 months ago
Automating error reporting sounds like a good idea, but is it really enough?
upvoted 0 times
...
Bong
9 months ago
Definitely need to determine API rate-limiting requirements.
upvoted 0 times
...
Micaela
9 months ago
I'm a little confused by the options. Decreasing simultaneous API responses and automating error reporting don't seem directly relevant to the problem described. I'll need to carefully analyze each choice to determine the best two recommendations.
upvoted 0 times
...
Noemi
10 months ago
I feel pretty confident about this one. Configuring shorter timeouts and implementing API rate-limiting seem like the two most effective recommendations to prevent similar incidents in the future.
upvoted 0 times
...
Tran
10 months ago
Okay, let's see. Based on the details provided, it sounds like the issue was caused by a spike in API calls and inactive sessions. So I'd recommend looking at rate-limiting and session management as potential solutions.
upvoted 0 times
...
Felicitas
10 months ago
Hmm, I'm a bit unsure about this one. There are a few options presented, and I'm not sure which two would be the best recommendations. I'll need to think it through carefully.
upvoted 0 times
...
Nell
10 months ago
This seems like a straightforward question about preventing API-related incidents. I think the key is to identify the root causes and implement appropriate mitigation strategies.
upvoted 0 times
...
Willetta
11 months ago
Decreasing simultaneous API responses sounds familiar, but I wonder if it would really solve the issue of unresponsive APIs during high traffic.
upvoted 0 times
...
Donte
11 months ago
I’m a bit confused about the options, but I feel like implementing API key maintenance might not directly address the spike in requests.
upvoted 0 times
...
Brittni
11 months ago
I remember practicing a question about rate limiting, and it seems like determining API rate-limiting requirements would definitely be a solid recommendation.
upvoted 0 times
...
Glory
11 months ago
I think configuring shorter timeout periods could help, but I'm not entirely sure if that's the best option.
upvoted 0 times
...
Veronica
11 months ago
Okay, I've got it! The import and data extract activities are the two that can be automated based on the information provided. Sending the notification to the email specialist is a manual task.
upvoted 0 times
...
Jacquelyne
11 months ago
I'm feeling confident about this one. Consumption assets are things that are used up or depleted through use, unlike capital assets that are used for production. So the answer has to be D, food and drink.
upvoted 0 times
...
Jospeh
11 months ago
I think Peter Calthorpe is associated with the Congress for New Urbanism, but I'm not completely sure.
upvoted 0 times
...
Thurman
2 years ago
Haha, 'Automate server-side error reporting for customers'? That's a good one. As if customers really want to know all the nitty-gritty details when the API goes down. Let's stick to the practical solutions, folks.
upvoted 0 times
...
Celia
2 years ago
I'm not so sure about A. Shorter timeouts might just create more headaches with users constantly getting logged out. I think B and C are the way to go - implement rate-limiting and maintain those API keys to keep things secure.
upvoted 0 times
...
Marti
2 years ago
I agree, Desire. A and B seem like the obvious choices here. Shorter timeouts could help clear out inactive sessions, and rate-limiting the API calls would prevent that spike in requests.
upvoted 0 times
Marion
2 years ago
B) Determine API rate-limiting requirements.
upvoted 0 times
...
Clare
2 years ago
A) Configure shorter timeout periods.
upvoted 0 times
...
...
Desire
2 years ago
Hmm, this is a tricky one. I think the key is to focus on reducing the load on the API during peak times and maintaining better session management. What do you guys think?
upvoted 0 times
...

Save Cancel