Question 220
While resolving an implementation issue on a predictive initiative, a safety-critical project has a high-severity defect but the weekly report hides it inside an appendix. Which evidence would best substantiate that the intended outcome is actually achieved?
Explanation
Correct Answer
Check issue records and escalation receipts against severity thresholds. The evidence tests whether the intended behavior or acceptance occurred instead of relying on unsupported assurances. In this case, communication frequency must respond to impact, not only the calendar. The stated constraint is: A safety-critical project has a high-severity defect but the weekly report hides it inside an appendix. The chosen assurance is the most direct response under these conditions.
Incorrect Answers
Reconcile report assertions with signed tests and compliance evidence locations. This response addresses another situation in the same task area: A compliance reviewer receives polished milestone reports but cannot identify which evidence links to an approval claim. There, reporting transparency requires traceability from a claim to supporting evidence. For the current situation—A safety-critical project has a high-severity defect but the weekly report hides it inside an appendix—this option would leave the specific need unresolved: communication frequency must respond to impact, not only the calendar.
Review escalated cases against the published contact and response protocol. This response addresses another situation in the same task area: A vendor integration is delayed because engineering, legal, and procurement use different escalation channels. There, complex stakeholder communication needs clear routing and handoff accountability. For the current situation—A safety-critical project has a high-severity defect but the weekly report hides it inside an appendix—this option would leave the specific need unresolved: communication frequency must respond to impact, not only the calendar.
Audit decision-log timestamps and team acknowledgments against change approvals. This response addresses another situation in the same task area: A remote hybrid team learns about critical scope decisions only through private messages to its manager. There, reliable communications require a discoverable shared record, not personal inbox dependence. For the current situation—A safety-critical project has a high-severity defect but the weekly report hides it inside an appendix—this option would leave the specific need unresolved: communication frequency must respond to impact, not only the calendar.