A known error has been created after diagnosis of a problem was complete but before a workaround has been found. Is this a valid approach?
1) No, the known error should be created before the problem is logged
2) No, a known error record is created when the original incident is raised
3) No, a known error record should be created with the next release of the service
4) Yes for information purposes, a known error record can be created at any time it is prudent to do so
Answers
Answer:4
Explanation:
Yes for information purposes, a known error record can be created at any time it is prudent to do so
Answer:
The correct answer to the given question is:
4) Yes for information purposes, a known error record can be created at any time it is prudent to do so
Explanation:
The problem management process uses reactive as well as proactive approaches:
Reactive problem management is activated if problems are identified that require analysis and implementation of a longer-term solution. For example, incident management may select an incident or a set of related incidents whose root cause cannot be resolved during incident management, to prevent similar incidents from reoccurring. to act.
Proactive problem management is an ongoing activity that identifies problems to prevent problems from occurring. For example, incident management will analyze incident records, activity logs, etc. to find patterns and trends that may indicate the presence of fundamental errors.
Once the problem has been identified and diagnosed, it becomes a "known error". Where possible, Issue Management will provide an alternative - a temporary solution that can be used to resolve related issues while a permanent solution to the problem is being developed.
Once the final resolution has been implemented, the issue profile will be officially closed. This will ensure that the crash log contains the complete historical description and that all related records are up to date.
#SPJ2