Question 740
A network team equates a known hardware defect with every user report that mentions it. Which long-term measure is most useful in this situation?
Explanation
Correct Answer
The continuing control addresses the recurring risk that related incidents may have a common cause, but not every incident is itself a documented known error.
Incorrect Answers
This safeguard maintains a different technical control: This is a practical follow-up for the risk that delegation without clear boundaries can create inconsistent decisions. The recurring risk here is governed by: The continuing control addresses the recurring risk that related incidents may have a common cause, but not every incident is itself a documented known error. The relevant review is “Use knowledge and problem records with clear classification”.
“Include cross-boundary flow measures in improvement reviews” is a sensible check for: The safeguard sustains value by monitoring the concern that a service cannot be optimized solely within one team's boundaries. It is not the prevention measure for the current dependency: The continuing control addresses the recurring risk that related incidents may have a common cause, but not every incident is itself a documented known error. The closer guardrail is “Use knowledge and problem records with clear classification”.
The alternate safeguard protects a separate dependency: A release is the version or set of components being made available; testing provides evidence of correctness. For this failure the continuing exposure is: The continuing control addresses the recurring risk that related incidents may have a common cause, but not every incident is itself a documented known error. Maintain “Use knowledge and problem records with clear classification” instead.