FIDO Quality Control & Process Improvement 3 — Questions and Answers
Question 1: A quality engineer creates a traceability matrix linking FIDO specification requirements to test cases. What is the primary benefit of this artifact?
- Ensuring every specification requirement has test coverage and no requirement is untested (Correct answer)
- Automatically generating test scripts from the specification
- Reducing the number of test cases needed for certification
- Mapping FIDO metadata entries to hardware SKUs
Correct answer: Ensuring every specification requirement has test coverage and no requirement is untested
A requirements traceability matrix (RTM) guarantees bidirectional coverage: every requirement maps to tests, and every test maps back to a requirement.
Question 2: Which statistical process control (SPC) tool would best help a FIDO hardware team monitor whether biometric sensor accuracy is drifting over production batches?
- Control chart (X-bar and R chart) (Correct answer)
- Pareto chart
- Fishbone diagram
- SIPOC diagram
Correct answer: Control chart (X-bar and R chart)
Control charts track a process metric over time with control limits, making drift and out-of-control conditions immediately visible across production batches.
Question 3: A FIDO authenticator manufacturer implements FMEA (Failure Mode and Effects Analysis) before releasing a new product. What does the Risk Priority Number (RPN) represent?
- Severity × Occurrence × Detectability, used to rank failure modes by risk (Correct answer)
- The number of test cases required for each failure mode
- The percentage of units expected to fail in the field
- The FIDO certification score assigned during conformance testing
Correct answer: Severity × Occurrence × Detectability, used to rank failure modes by risk
RPN = Severity × Occurrence × Detectability; higher RPNs indicate failure modes requiring the most urgent corrective action.
Question 4: In a FIDO conformance test run, a test suite reports 'WARN' for an optional feature and 'FAIL' for a mandatory requirement. Which finding must be resolved before certification?
- Only the FAIL, because mandatory requirements are non-negotiable for certification (Correct answer)
- Both FAIL and WARN, because all findings block certification
- Only the WARN, because optional features carry more risk
- Neither, because conformance tests are advisory only
Correct answer: Only the FAIL, because mandatory requirements are non-negotiable for certification
FIDO conformance testing requires all mandatory requirements to pass; optional features generating WARNs do not block certification.
Question 5: A Kanban board is used to manage a FIDO authenticator bug backlog. A column labeled 'WIP Limit: 3' is full. What should the team do when a new critical defect is discovered?
- Finish or escalate an existing WIP item before pulling the new defect into that column (Correct answer)
- Immediately add the critical defect regardless of the WIP limit
- Move all WIP items to 'Done' without resolving them
- Increase the WIP limit to 4 to accommodate the new item
Correct answer: Finish or escalate an existing WIP item before pulling the new defect into that column
Kanban WIP limits exist to prevent multitasking overload; the correct action is to clear or escalate existing work before adding new items, even critical ones.
Question 6: A FIDO relying party conducts user acceptance testing (UAT) for a new WebAuthn registration flow. UAT passes but post-launch error rates spike. What quality process failure likely occurred?
- UAT did not adequately represent the diversity of real user devices and browsers (Correct answer)
- The attestation format was changed after UAT
- The server's CBOR decoder was not included in the UAT scope
- The FIDO metadata service was offline during UAT
Correct answer: UAT did not adequately represent the diversity of real user devices and browsers
UAT environment mismatches—particularly limited device/browser coverage—are the most common cause of defects surfacing only in production.
Question 7: Which lean quality principle best describes removing the manual step of having a developer sign off attestation format checks that automated FIDO conformance tooling can already verify?
- Eliminate waste (muda) by automating redundant manual steps (Correct answer)
- Implement poka-yoke to prevent defects at source
- Apply Just-In-Time delivery to reduce inventory
- Use value stream mapping to identify bottlenecks
Correct answer: Eliminate waste (muda) by automating redundant manual steps
Lean identifies unnecessary manual review of items already checked by automation as 'muda' (waste), and eliminating it improves throughput without reducing quality.
A quality engineer creates a traceability matrix linking FIDO specification requirements to test cases.
What is the primary benefit of this artifact?