CTFL-v4 Fundamentals of Testing Practice Question
A QA lead at a medical device software company is asked by an auditor to demonstrate that their process provides confidence the product meets regulatory requirements. The lead's team follows defined test design techniques, tracks coverage metrics, and reviews results against entry and exit criteria. A colleague argues that because testers never build the software, testing cannot contribute to quality. How should the lead explain testing's relationship to quality assurance in this regulated context?
⚠ Common exam trap
The trap here is assuming that finding and fixing defects is the same as assuring quality, which confuses quality control results with process-level quality assurance.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Testing is a form of quality control that measures product quality, while quality assurance is process-oriented and includes activities such as defining test processes and standards.
Testing is a quality control activity that evaluates work products, while quality assurance is concerned with the processes that produce them. In a regulated environment, defining test design techniques, coverage criteria, and entry/exit criteria are process-level quality assurance contributions, and executing tests against them produces quality control evidence. The lead should present both as complementary, since process definition and product measurement together give the auditor confidence.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Quality assurance is a subset of testing, since the only meaningful way to assure quality is to execute test cases and log defects until the defect count reaches zero.
Why it's wrong here
This inverts the relationship. Quality assurance encompasses broader process activities, of which testing is one contributor. Also, zero defects found does not equal assured quality, since tests can only show the presence of defects, never their absence. A medical device auditor would reject a claim that defect count alone demonstrates a compliant, capable development process.
- ✗
Testing is entirely separate from quality assurance, and testers should not be involved in reviewing requirements, designing processes, or defining standards because that would compromise their independence.
Why it's wrong here
Testing and quality assurance are related, and testers commonly participate in reviews of requirements and user stories, which is a recognized testing contribution to quality. Independence in reporting results does not forbid contributing to process improvement. This option overstates separation and would weaken the very process evidence the medical device auditor expects to see documented alongside test outcomes.
- ✗
Testing and quality assurance are the same activity, so demonstrating test results is sufficient evidence that the development process itself is compliant.
Why it's wrong here
This collapses two distinct concepts. Test results show the state of a specific work product at a point in time; they do not prove the development process meets a standard. An auditor reviewing a medical device manufacturer expects process documentation, defined procedures, and records of compliance, which test execution alone cannot supply. Treating the two as identical would leave the process evidence gap the auditor is probing.
- ✓
Testing is a form of quality control that measures product quality, while quality assurance is process-oriented and includes activities such as defining test processes and standards.
Why this is correct
Testing is a quality control activity that evaluates the work product against expectations, whereas quality assurance focuses on the process used to build it. In this medical device scenario, the lead's defined techniques, coverage metrics, and criteria are process-level QA elements, and the test execution results are QC evidence. The two are complementary, not mutually exclusive, so the colleague's premise misreads the distinction.
About these practice questions
Courseiva writes every CTFL-v4 question from scratch — 144 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official ISTQB exam blueprint
This CTFL-v4 practice question is part of Courseiva's free ISTQB certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CTFL-v4 exam.