MENU
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?
Suggested Answer: C
Get Premium ITIL-4-Specialist-Create-Deliver-and-Support Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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.
29 comments · newest first
IE
Iesha
10 months ago
Wait, emergency changes (D)? That sounds chaotic! How would that even work?
LI
Lizbeth
10 months ago
Not sure about C, though. Isn't safe-to-fail just a way to excuse failures?
GO
Golda
10 months ago
Increasing the size of changes (B) seems risky. More complexity = more problems!
ER
Erinn
11 months ago
Totally agree with C! We need a structured approach.
CA
Carmelina
11 months ago
I think option C is the best choice! Safe-to-fail testing sounds smart.
LY
Lynette
11 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.
LA
Lai
11 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.
SU
Sunny
11 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?
RO
Robt
12 months ago
I remember we discussed the importance of having a structured change model, so option C sounds familiar to me.
MI
Miesha
12 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.
OR
Orville
12 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.
BR
Brunilda
1 year 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.
DE
Desmond
1 year 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.
LO
Long
1 year ago
I see your point, Rebbecca. But I think option D could also be effective in quickly identifying errors.
MI
Mitsue
1 year ago
Emergency changes? What is this, a fire drill? Let's stick to a proper change model, folks.
HA
Hannah
1 year ago
Emergency changes are risky, we need a structured approach
JO
Joanne
1 year ago
C) Create a change model for development changes that includes the use of safe-to-fail testing
WI
Wilda
1 year ago
A) Create a standard change model for development changes and initiate as a service request
RE
Rebbecca
1 year ago
I disagree, I believe option C is better because safe-to-fail testing can help identify issues early.
SH
Shawna
1 year ago
Option B? Increase the size of changes? That's like trying to put a band-aid on a bullet wound.
AL
Alex
1 year ago
I agree with Micaela. Safe-to-fail testing is the way to go. Gotta love those fail-safes!
LA
Lai
1 year ago
User 3: I agree with Lai, safe-to-fail testing sounds like the way to go.
LO
Lonna
1 year ago
User 2: I disagree, I believe option C with safe-to-fail testing is the best approach.
CE
Celeste
1 year ago
User 1: I think we should go with option A.
MA
Marta
1 year ago
I think option A is the best approach.
MI
Micaela
1 year ago
Option C is the best approach. Safe-to-fail testing is crucial for reducing failures in complex systems.
KA
Karina
1 year 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.
GL
Glendora
1 year ago
User 2: I agree, having a change model that includes safe-to-fail testing is key for success.
JA
James
1 year ago
User 1: Option C is definitely the way to go. Safe-to-fail testing can really help prevent failures.