QPPV.COM KNOWLEDGE ASSESSMENT

Knowledge Assessment: Traceability Matrix in Computerised System Validation

Test your understanding of the concepts covered by Traceability Matrix in Computerised System Validation.

Question 1 of 10Pass mark: 80%

Question 1 of 10 A team proposes to include every email, meeting note and historical project record in the matrix. What is the most appropriate professional response?

Accept the proposal because greater complexity always increases assurance Reject all references other than test scripts Include the relationships necessary to demonstrate implementation, verification and maintenance, while avoiding unnecessary complexity Replace the matrix with an archive of all project communications

Question 2 of 10 Why should traceability continue during system retirement?

Retirement eliminates all regulatory obligations associated with the system Traceability helps demonstrate data retention, process continuity, preservation of evidence and fulfilment of ongoing obligations Retirement requires all historical validation evidence to be deleted Traceability is relevant only while the system is undergoing qualification

Question 3 of 10 What is the primary purpose of a Traceability Matrix in Computerised System Validation?

To provide a complete list of all validation documents To demonstrate that important requirements are implemented, verified and maintained throughout the lifecycle To replace the need for risk assessments and validation protocols To document only the final results of qualification testing

Question 4 of 10 Why is linking requirements to documented risks important in a risk-based validation programme?

It ensures every requirement receives identical testing It shows why the requirement matters and supports proportionate validation priorities It removes the need to assess residual risk after testing It limits traceability to patient safety risks only

Question 5 of 10 What does a mature Traceability Matrix enable an organisation to demonstrate about residual risk?

That all risks have been eliminated Which risks were addressed, which controls were validated, what deviations occurred and whether remaining risks are acceptable That risk assessment is required only before system implementation That residual risk can be inferred from the number of test cases

Question 6 of 10 Which characteristic best reflects an inspection-ready Traceability Matrix?

A large number of rows and document references regardless of relevance Completeness, accuracy, currency, internal consistency and linkage to objective evidence A matrix created immediately before an inspection from archived records A document containing only requirement IDs and validation report references

Question 7 of 10 Which pharmacovigilance function would generally warrant particularly careful traceability because failure could directly affect regulatory compliance and patient safety?

Office stationery ordering Expedited electronic regulatory reporting General employee social-event management Non-regulated internal communications

Question 8 of 10 Which statement best distinguishes a Traceability Matrix from a simple document index?

A matrix uses electronic software, whereas an index uses paper A matrix records logical relationships that explain why requirements exist and how they were implemented, verified and maintained A matrix contains only test execution results, whereas an index contains requirements A matrix is required to include every email and project record

Question 9 of 10 How does traceability support data integrity assurance?

By demonstrating that relevant data integrity controls were identified, specified, implemented, verified and maintained By proving that data can never be changed after entry By replacing access control and audit trail testing By focusing exclusively on data backup documentation

Question 10 of 10 A validation test fails for a requirement supporting regulatory reporting. Which set of traceability links best demonstrates controlled management of the finding?

Requirement → failed test → deviation → root cause and CAPA → retesting → residual risk assessment Failed test → deletion of the requirement → project closure Deviation → supplier release note only Requirement → successful unrelated test → approval without further investigation

QPPV.com

Knowledge Assessment: Traceability Matrix in Computerised System Validation

Cookie Settings