Knowledge check Compliance & Audit Trail
10 questions in pool · live exam draws 4
SPOCR03
Q1 multiple-choice · shift What changes when OCR moves from convenience to compliance?
Source: SPOCR03 §1.
Explanation: Compliance is additive discipline, not different technology. Same OCR engine + additional discipline on top.
Q2 multiple-choice · frameworks 21 CFR Part 11 applies to:
Source: SPOCR03 §2.
Explanation: 21 CFR Part 11 = FDA’s framework for electronic records + signatures in regulated pharma/medical contexts.
Q3 multiple-choice · chain-of-custody How many steps in the standard chain-of-custody for compliance OCR records?
Source: SPOCR03 §3.
Explanation: 7-step chain captures every transition from physical product to downstream record. Each transition leaves an audit log entry.
Q4 scenario · timezone Your customer operates studios in 3 time zones. Audit log timestamps should be:
Source: SPOCR03 §7.
Explanation: UTC eliminates time-zone ambiguity at audit. Local time in UI is convenience; UTC in the record is discipline.
Q5 multiple-choice · role-boundary OCR Specialist’s role in regulated industry engagements vs. customer’s RA professional?
Source: SPOCR03 §5.
Explanation: Healthy collaboration = role boundaries. Cross the boundary = expose customer + PhotoRobot to risk.
Q6 true-false · read-audit In compliance OCR pipelines, only write-events need audit logging; read-events can be untracked.
Source: SPOCR03 §7.
Explanation: Both reads + writes must be logged in compliance contexts. Auditor wants to know who saw what + when, not just what changed.
Q7 multiple-choice · validation Which is the OCR Specialist’s role in 21 CFR Part 11 validation?
Source: SPOCR03 §6.
Explanation: Technical contribution to validation; sign-off + defense is RA’s role.
Q8 scenario · revalidation-trigger Your validated pipeline’s OCR engine vendor releases a major update.
Source: SPOCR03 §6.
Explanation: Engine version change = revalidation trigger. Update + revalidate = healthy; update + skip = compliance citation risk.
Q9 multiple-choice · failure-modes Which is NOT a common compliance failure mode covered in SPOCR03?
Source: SPOCR03 §7.
Explanation: Common failures: log gaps, drift, unattributed changes, time-zone confusion, access without log, untested backups, re-shoot loops unaudited. Excessive training is not a failure mode.
Q10 multiple-choice · closing Best summary of SPOCR03’s discipline:
Source: SPOCR03 closing message.
Explanation: Compliance OCR is the same pipeline with discipline. Build for audit; collaborate with RA; manage drift; revalidate on change.
Ready to commit? You can review and change your answers before submitting. Once submitted, this attempt is final and we'll show you your score, correct answers, and explanations.
Submit final answers
