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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

PeopleCert ITIL 4 Specialist Create Deliver and Support Exam - Topic 8 Question 6 Discussion

Actual exam question for PeopleCert's ITIL 4 Specialist Create Deliver and Support exam
Question #: 6
Topic #: 8
[All ITIL 4 Specialist Create Deliver and Support Questions]

A popular social media app is part of a complex network of systems. Most changes to the service are successful, except for those made by a development team that has many failed changes.

Which is the BEST approach to reduce the number of failures?

Show Suggested Answer Hide Answer
Suggested Answer: C

Creating a change model that includes safe-to-fail testing allows development changes to be tested in controlled conditions, reducing the risk of failure and improving change success rates.


by Salome at Apr 29, 2025, 09:25 PM

Limited Time Offer

25%

Off

Get Premium ITIL 4 Specialist Create Deliver and Support Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Iesha
4 months ago
Wait, emergency changes (D)? That sounds chaotic! How would that even work?
upvoted 0 times
...
Lizbeth
4 months ago
Not sure about C, though. Isn't safe-to-fail just a way to excuse failures?
upvoted 0 times
...
Golda
4 months ago
Increasing the size of changes (B) seems risky. More complexity = more problems!
upvoted 0 times
...
Erinn
4 months ago
Totally agree with C! We need a structured approach.
upvoted 0 times
...
Carmelina
5 months ago
I think option C is the best choice! Safe-to-fail testing sounds smart.
upvoted 0 times
...
Lynette
5 months ago
Option D feels like a quick fix, but I wonder if it really addresses the root cause of the failures. It might just lead to more chaos in the long run.
upvoted 0 times
...
Lai
5 months ago
I think we practiced a question similar to this where creating a standard change model helped reduce errors. So, option A might be a good choice too.
upvoted 0 times
...
Sunny
5 months ago
I'm not entirely sure, but increasing the size of changes like in option B seems risky. Bigger changes might just lead to bigger failures, right?
upvoted 0 times
...
Robt
6 months ago
I remember we discussed the importance of having a structured change model, so option C sounds familiar to me.
upvoted 0 times
...
Miesha
6 months ago
I feel pretty confident about this one. The key is to establish a proper change management process, with a standard model and safe-to-fail testing. That way, the development team can catch issues early and reduce the number of failures.
upvoted 0 times
...
Orville
6 months ago
Ah, this is a tricky one. I can see the appeal of the emergency change approach, but I'm not sure that's the best long-term solution. I think the safe-to-fail testing option is the most comprehensive and sustainable approach.
upvoted 0 times
...
Brunilda
6 months ago
Hmm, I'm a bit unsure about this one. Increasing the size of changes to make them easier to handle seems counterintuitive to me. I'm leaning towards the option that involves a standard change model and service requests.
upvoted 0 times
...
Desmond
6 months ago
This seems like a straightforward question about change management. I think the best approach is to create a change model that includes safe-to-fail testing, so the development team can identify and address issues before deploying changes.
upvoted 0 times
...
Long
11 months ago
I see your point, Rebbecca. But I think option D could also be effective in quickly identifying errors.
upvoted 0 times
...
Mitsue
11 months ago
Emergency changes? What is this, a fire drill? Let's stick to a proper change model, folks.
upvoted 0 times
Hannah
10 months ago
Emergency changes are risky, we need a structured approach
upvoted 0 times
...
Joanne
10 months ago
C) Create a change model for development changes that includes the use of safe-to-fail testing
upvoted 0 times
...
Wilda
10 months ago
A) Create a standard change model for development changes and initiate as a service request
upvoted 0 times
...
...
Rebbecca
11 months ago
I disagree, I believe option C is better because safe-to-fail testing can help identify issues early.
upvoted 0 times
...
Shawna
11 months ago
Option B? Increase the size of changes? That's like trying to put a band-aid on a bullet wound.
upvoted 0 times
...
Alex
11 months ago
I agree with Micaela. Safe-to-fail testing is the way to go. Gotta love those fail-safes!
upvoted 0 times
Lai
10 months ago
User 3: I agree with Lai, safe-to-fail testing sounds like the way to go.
upvoted 0 times
...
Lonna
11 months ago
User 2: I disagree, I believe option C with safe-to-fail testing is the best approach.
upvoted 0 times
...
Celeste
11 months ago
User 1: I think we should go with option A.
upvoted 0 times
...
...
Marta
11 months ago
I think option A is the best approach.
upvoted 0 times
...
Micaela
11 months ago
Option C is the best approach. Safe-to-fail testing is crucial for reducing failures in complex systems.
upvoted 0 times
Karina
11 months ago
User 3: It's important to have a process in place to catch errors before they cause major issues. Option C sounds like the best approach.
upvoted 0 times
...
Glendora
11 months ago
User 2: I agree, having a change model that includes safe-to-fail testing is key for success.
upvoted 0 times
...
James
11 months ago
User 1: Option C is definitely the way to go. Safe-to-fail testing can really help prevent failures.
upvoted 0 times
...
...

Save Cancel