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 Exam 300-910 Topic 11 Question 71 Discussion

Actual exam question for Cisco's 300-910 exam
Question #: 71
Topic #: 11
[All 300-910 Questions]

What is a principle of chaos engineering?

Show Suggested Answer Hide Answer
Suggested Answer: B

Comments

Meghan
7 hours ago
Absolutely. B is the textbook chaos engineering principle. Though I have to say, 'common user access on system monitoring infrastructure' is a new one to me. Is that some kind of next-level chaos engineering I'm not aware of?
upvoted 0 times
...
Eden
8 hours ago
You know it, my friend! I think option B is the way to go. Chaos engineering is all about purposefully injecting failures into your system to see how it responds. That way, you can identify and fix any weak points before they become a problem.
upvoted 0 times
...
Joni
1 days ago
Haha, yeah, C is a nice thought but a bit too idealistic. Chaos engineering is all about embracing the fact that mistakes and disruptions are inevitable, and figuring out how to deal with them.
upvoted 0 times
...
Aja
1 days ago
Whoa, this question is a real brain-teaser! I'm not too familiar with chaos engineering, but I'm guessing it's all about proactively testing your system's resilience, yeah?
upvoted 0 times
...
Jenifer
2 days ago
Yeah, B is the clear winner here. Though I do like the idea of 'prevent mistakes that cause infrastructure service disruption' - that's kind of the end goal of chaos engineering, isn't it?
upvoted 0 times
...
Edmond
4 days ago
I agree, B is the way to go. Chaos engineering is about being proactive and stress-testing your systems, not just reacting to issues. The whole point is to find weaknesses before they become real problems.
upvoted 0 times
...
Erick
6 days ago
This is a pretty straightforward chaos engineering question. I think the correct answer is B - proactive testing based on system responsiveness. Chaos engineering is all about deliberately introducing failures and disruptions to see how your system reacts, not just waiting for something to go wrong.
upvoted 0 times
...

Save Cancel