When should a workaround be created?
When should a workaround be created?
A workaround is created when a problem cannot be resolved quickly. Workarounds serve as temporary solutions to reduce or eliminate the impact of an incident or problem until a permanent resolution is found. They are typically documented during problem management to help manage future incidents with similar issues, and this can be done at any stage without waiting for complete analysis.
Correct answer is C : When a problem cannot be resolved quickly, it is often useful to find and document a workaround for future incidents, based on an understanding of the problem https://www.bmc.com/blogs/itil-problem-management/
A is correct. Incident can not be resolved pernament >> solved by workarround >> many INC like that cause a Problem. So that mean Workarround was created before Problem is logged
Correct is A: A workaround is a solution that reduces or eliminates the impact of an incident or problem for which a full resolution is not yet available. Some workarounds reduce the likelihood of incidents. ▪ Workarounds are documented in problem records ▪ Workarounds can be done at any stage, it doesn’t need to wait for analysis to be complete ▪ If a workaround has been documented early in problem control, then this should be reviewed and improved after problem analysis is complete
For me still C is right.
If you are able to resolve a problem you don't have to create a workaround so A is wrong. Thus when you cannot fix the problem permanenty but you have a solution to remedate a problem you can create a workaround.
definition: "The purpose of problem management is to reduce the likelihood and impact of incidents by identifying actual and potential causes of incidents, and managing workarounds and known errors."
So A? because "This can be done at any stage,it doesn't need to wait for analysis to be complete"
If the issue has a solution, it can not be called as a problem.
you can`t logg workaround when incident is created. If workaround is found incident is closed. So C it is
This is a tricky one. Generally, I would go for A, but the part “once the incident is logged” suggests that this is not the correct answer, as not all Incidents need workarounds. C is correct.
Answer is C: 5.2.8 ) WHEN A PROBLEM CANNOT BE RESOLVED QUICKLY, it is often useful to find and document a workaround for future incidents, based on an understanding of the problem. Workarounds are documented in problem records. This can be done at any stage; it doesn’t need to wait for analysis to be complete. If a workaround has been documented early in problem control, then this should be reviewed and improved after problem analysis has been completed.
Chapter 5: ITIL management practices, page 131 describes this. Answer C is correct.
For those who chose A - if you would do this, you service would be full of workarounds :D You have to at least try to solve a problem first, don't give up to workarounds instantly..
I would go for C after reading the question again with more care.
C. When a problem cannot be resolved quickly is correct answer.
CORRECT ANSWER C/ When a problem cannot be resolved quickly, it is often useful to find and document a workaround for future incidents,
Must be C, if the incident has a resolution, no work-around is needed (this for option A). If the workaround already exists, it is probably a problem where the root-cause has not been fixed for. You only create work-arounds for problems/incidents you cannot fix right away and therefore are to complex.
C is correct.
A is correct. Incident can not be resolved pernament >> solved by workarround >> many INC like that cause a Problem. So that mean Workarround was created before Problem is logged.
Its A, incident vs problem. Problem is deeper than an incident, where as incidents create a problem. Workarounds can be introduced immediately.
It seems both A And C, vaild for this question But, C is very close one compare to A Workaround is a temporary solution,it will be used when problem is not have a solution immediately and at the same time, mitigate the existing business impact and need to restore the service with minimal impact or recovery fully.
Workarounds can be done at any stage. If it's been documented early in problem control, it should be reviewed and improved after problem analysis.
C because this answer is not against the statement that workaround can be create at any stages. It only says when the problem can't be solved quickly.