Free ISTQB-CTFL: ISTQB-Foundation Level Exam Questions and Answers
144 verified practice questions for ISTQB-CTFL.
The first 10 questions on this page are free to read, answers included — no account and no card. A plan opens the rest of the bank, the full timed practice test and your weak-topic reporting.
Last updated: September 19, 2026
- Provider
- ISTQB
- Questions in our bank
- 1000+
- Free to read
- First 10, with answers
- Our test mode duration & pass mark
- 130 mins · 70%
- Verified answers
- Reviewed weekly
- Practice format
- Multiple choice
Recommended: Switch to Test Mode to start a practice test that simulates the real exam experience.
Question #1
Consider the following testing levels: 1) Component Testing 2) Integration Testing 3) System Testing 4) Acceptance Testing Which of the following statements is true?
Please select an optionIncorrectCorrect answer: D
All testing levels are applicable, independent of which software development life-cycle process (V-model, iterative, incremental) is used. Testing levels are defined based on the scope and objectives of testing, not on the software development model. Component testing, integration testing, system testing and acceptance testing are common testing levels that can be applied to any software development model, as long as they are planned and executed properly. The V-model is a software development model that emphasizes the relationship between each development phase and its corresponding testing phase. Iterative and incremental models are software development models that divide the development process into smaller cycles or iterations, where each iteration produces a working version of the software that can be tested and evaluated. Verified References: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus - Springer, page 18.
Was this answer correct?Question #2
Which of the following statements regarding inspection is NOT true?
Please select an optionIncorrectCorrect answer: B
An inspection is a type of review that follows a defined process with formal entry and exit criteria and roles and responsibilities for participants. An inspection can be performed by peers with different roles, such as moderator, author, reviewer and scribe. The following statement about inspection is not true: • B) The main purpose of an inspection is to find solutions to the problems. This statement is not true, as the main purpose of an inspection is to find defects or issues in a work product, not to find solutions to the problems. Finding solutions to the problems is a debugging or problem-solving activity that is usually performed by the author or developer after receiving the inspection report. The following statements about inspection are true: • A) An inspection may be led by a trained moderator who shall not be the author. This statement is true, as an inspection requires a moderator role who leads the inspection process and ensures that it follows the rules and standards. The moderator should be trained in inspection techniques and should not be the author of the work product under inspection, in order to avoid bias or conflict of interest. • C) An inspection can be performed by peers. This statement is true, as an inspection involves peer review, which means that the work product under inspection is evaluated by people who have similar roles or expertise as the author, but who are not directly involved in creating or modifying the work product. • D) An inspection shall follow a formal process based on rules and checklists with entry and exit criteria. This statement is true, as an inspection follows a formal process that consists of six main steps: planning, kick-off meeting, individual preparation, review meeting, rework and follow-up. Each step has defined rules and checklists to guide the participants and ensure consistency and quality. Each step also has entry and exit criteria to ensure that the prerequisites and objectives are met before moving to the next step. Verified References: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus - Springer, Chapter 3, page 28-29.
Was this answer correct?Question #3
Which of the following is a correct reason to apply test automation?
Please select an optionIncorrectCorrect answer: B
A correct reason to apply test automation is when there are a lot of repetitive testing tasks. Test automation is the use of software tools or scripts to perform or support testing activities, such as test case execution, test result comparison, test data generation, etc. Test automation can be beneficial when there are a lot of repetitive testing tasks that need to be performed frequently or consistently, such as regression testing, performance testing, load testing, etc. Test automation can help to save time and effort, increase reliability and accuracy, and improve coverage and efficiency of testing. The other options are not correct reasons to apply test automation. When a new test automation tool is launched is not a reason to apply test automation, but rather a factor for choosing a test automation tool. When it is easy to automate is not a reason to apply test automation, but rather a factor for evaluating the feasibility of test automation. When it is cheap to buy test automation tools is not a reason to apply test automation, but rather a factor for estimating the cost and benefit of test automation. Verified References: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus - Springer, page 10.
Was this answer correct?Question #4
For withdrawing money tram an Automated Teller Machine (ATM), the following conditions are required: - The bank card is valid - The PIN code is correct - Money is available in the user's account The following are some possible interactions between the user and the ATM: - The entered card is invalid The card is rejected - The PIN code is wrong The ATM asks for another PIN code - The requested amount is more than available in the user's account: The ATM asks for another amount - The requested amount is available in the user's account The ATM dispenses the money Which test design technique should be used to cover all possible combinations of the in put conditions?
Please select an optionIncorrectCorrect answer: B
A decision table is a technique that should be used to cover all possible combinations of input conditions for withdrawing money from an Automated Teller Machine (ATM). A decision table shows combinations of inputs and/or stimuli (causes) with their associated outputs and/or actions (effects). A decision table consists of four quadrants: conditions (inputs), actions (outputs), condition entries (values) and action entries (results). A decision table can be used to test components that have multiple inputs and outputs that depend on logical combinations of conditions. For example, for testing the ATM, we can identify three input conditions: the bank card is valid, the PIN code is correct, and money is available in the user’s account. We can also identify four output actions: the card is rejected, the ATM asks for another PIN code, the ATM asks for another amount, and the ATM dispenses the money. A decision table can show all possible combinations of these conditions and actions in a systematic way. Use case based testing is not a technique that can cover all possible combinations of input conditions for withdrawing money from an ATM. Use case based testing is a technique that verifies that a software product or system meets its specified requirements or user stories by executing realistic scenarios or workflows. Use case based testing can be used to test components that have complex or dynamic interactions with users or other systems. For example, for testing the ATM, we can identify several use cases, such as withdraw money, check balance, transfer money, etc. Each use case can have one or more scenarios that describe the steps and outcomes of the interaction. However, use case based testing may not cover all possible combinations of input conditions, as some scenarios may be omitted or overlooked. Boundary value analysis is not a technique that can cover all possible combinations of input conditions for withdrawing money from an ATM. Boundary value analysis is a technique that tests boundary values between partitions of equivalent data. Boundary values are values at the edge of an equivalence partition or at the smallest incremental distance on either side of an edge. Boundary value analysis can be used to test components that have input values that can be divided into partitions of equivalent data. For example, for testing the ATM, we can identify boundary values for the input amount, such as the minimum and maximum amount allowed by the system or the user’s account. However, boundary value analysis may not cover all possible combinations of input conditions, as some conditions may not have boundary values or may not be related to input values. Equivalence class partitioning is not a technique that can cover all possible combinations of input conditions for withdrawing money from an ATM. Equivalence class partitioning is a technique that divides the input data and output results of a software component into partitions of equivalent data. Each partition should contain data that is treated in the same way by the component. Equivalence class partitioning can be used to test components that have input values that can be divided into partitions of equivalent data. For example, for testing the ATM, we can identify equivalence partitions for the input amount, such as valid amount (within the range allowed by the system and the user’s account) and invalid amount (outside the range allowed by the system or the user’s account). However, equivalence class partitioning may not cover all possible combinations of input conditions, as some conditions may not be related to input values or may have more than two partitions. Verified References: [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus - Springer], Chapter 4, page 34-46.
Was this answer correct?Question #5
Which of the following statements about testing in the context of an agile (iterative- incremental) development model is correct?
Please select an optionIncorrectCorrect answer: C
In the context of agile (iterative-incremental) development models, testing is integrated into the development process and occurs continuously throughout the lifecycle of the project. Agile testing emphasizes adaptability and the need for feedback at various stages of development. Option C is correct because regression testing is indeed necessary whenever a new increment is added to the existing system. Agile development often involves frequent changes and additions to the codebase, which can potentially introduce new defects into previously tested code. Regression testing ensures that new changes have not adversely affected existing functionality. Options A, B, and D present misconceptions about agile testing: • A is incorrect because, in agile, all types of testing (unit, integration, system, acceptance) are important and occur throughout the iteration, not just unit and acceptance tests. • B is incorrect because agile methodologies advocate for continuous integration and testing, where development and testing activities overlap and support each other throughout an iteration. • D is incorrect because agile methodologies encourage a wide range of testing types, including both functional and non-functional, as well as exploratory testing, to ensure a comprehensive quality assessment.
Was this answer correct?Question #6
Which of the following would be LEAST appropriate as part of an incident report covering the observation of a failure during testing?
Please select an optionIncorrectCorrect answer: B
An incident report during testing should focus on factual observations of failures or defects in the system, including their impacts and how they deviate from expected results. Options A, C, and D describe specific issues that are directly related to the system's behavior or performance and are suitable for inclusion in an incident report. Option B, which describes the user interface as "complicated and confusing" and relates to the tester's personal difficulty in following the test script, is more subjective and relates to the tester's experience rather than an objective observation of a system failure. Therefore, option B is the least appropriate for an incident report.
Was this answer correct?Question #7
The four test levels used in ISTQB syllabus are: * 1. Component (unit) testing * 2. Integration testing * 3. System testing * 4. Acceptance testing An organization wants to do away with integration testing but otherwise follow V-model. Which of the following statements is correct?
Please select an optionIncorrectCorrect answer: A
The V-model is a software development life cycle model that defines four test levels that correspond to four development phases: component (unit) testing with component design, integration testing with architectural design, system testing with system requirements, and acceptance testing with user requirements. The V- model emphasizes the importance of verifying and validating each phase of development with a corresponding level of testing, and ensuring that the test objectives, test basis, and test artifacts are aligned and consistent across the test levels. Therefore, an organization that wants to follow the V-model cannot do away with integration testing, as it would break the symmetry and completeness of the V-model, and compromise the quality and reliability of the software or system under test. Integration testing is a test level that aims to test the interactions and interfaces between components or subsystems, and to detect any defects or inconsistencies that may arise from the integration of different parts of the software or system. Integration testing is essential for ensuring the functionality, performance, and compatibility of the software or system as a whole, and for identifying and resolving any integration issues early in the development process. Skipping integration testing would increase the risk of finding serious defects later in the test process, or worse, in the production environment, which would be more costly and difficult to fix, and could damage the reputation and credibility of the organization. Therefore, the correct answer is D. The other options are incorrect because: • A. It is not allowed as organizations can decide on the test levels to do depending on the context of the system under test. While it is true that the choice and scope of test levels may vary depending on the context of the system under test, such as the size, complexity, criticality, and risk level of the system, the organization cannot simply ignore or skip a test level that is defined and required by the chosen software development life cycle model. The organization must follow the principles and guidelines of the software development life cycle model, and ensure that the test levels are consistent and coherent with the development phases. If the organization wants to have more flexibility and adaptability in choosing the test levels, it should consider using a different software development life cycle model, such as an agile or iterative model, that allows for more dynamic and incremental testing approaches. • B. It is not allowed because integration testing is not an important test level and can be dispensed with. This statement is false and misleading, as integration testing is a very important test level that cannot be dispensed with. Integration testing is vital for testing the interactions and interfaces between components or subsystems, and for ensuring the functionality, performance, and compatibility of the software or system as a whole. Integration testing can reveal defects or inconsistencies that may not be detected by component (unit) testing alone, such as interface errors, data flow errors, integration logic errors, or performance degradation. Integration testing can also help to verify and validate the architectural design and the integration strategy of the software or system, and to ensure that the software or system meets the specified and expected quality attributes, such as reliability, usability, security, and maintainability. Integration testing can also provide feedback and confidence to the developers and stakeholders about the progress and quality of the software or system development. Therefore, integration testing is a crucial and indispensable test level that should not be skipped or omitted. • C. It is not allowed because integration testing is a very important test level and ignoring it means definite poor product quality. This statement is partially true, as integration testing is a very important test level that should not be ignored, and skipping it could result in poor product quality. However, this statement is too strong and absolute, as it implies that integration testing is the only factor that determines the product quality, and that ignoring it would guarantee a poor product quality. This is not necessarily the case, as there may be other factors that affect the product quality, such as the quality of the requirements, design, code, and other test levels, the effectiveness and efficiency of the test techniques and tools, the competence and experience of the developers and testers, the availability and adequacy of the resources and environment, the management and communication of the project, and the expectations and satisfaction of the customers and users. Therefore, while integration testing is a very important test level that should not be skipped, it is not the only test level that matters, and skipping it does not necessarily mean definite poor product quality, but rather a higher risk and likelihood of poor product quality. References = ISTQB Certified Tester Foundation Level Syllabus, Version 4.0, 2018, Section 2.3, pages 16-18; ISTQB Glossary of Testing Terms, Version 4.0, 2018, pages 38-39; ISTQB CTFL 4.0 - Sample Exam - Answers, Version 1.1, 2023, Question 104, page 36.
Was this answer correct?Question #8
Which of the following is the most important task of a typical test leader?
Please select an optionIncorrectCorrect answer: D
The most important task of a typical test leader is to coordinate the test strategy with project managers. The test strategy is a high-level document that defines the general approach and objectives of testing for a project or an organization. The test leader is responsible for defining, documenting, communicating, and implementing the test strategy in alignment with the project goals and constraints. The test leader also needs to coordinate with project managers and other stakeholders to ensure that the test strategy is feasible, effective, and efficient. The other options are not the most important tasks of a typical test leader. To automate tests is a task of a test automation engineer or a test automation specialist. To prepare and acquire test data is a task of a test analyst or a test engineer. To set up the test environment is a task of a test environment manager or a test environment specialist. Verified References: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus - Springer, page 13.
Was this answer correct?Question #9
Which of the following is a function of a dynamic analysis tool?
Please select an optionIncorrectCorrect answer: B
A dynamic analysis tool is a tool that performs analysis of a software product based on its behavior during execution. A dynamic analysis tool can monitor various aspects of a program’s run-time performance, such as memory usage, CPU load, response time, or resource leaks. A dynamic analysis tool can monitor the allocation, use and de- allocation of memory during run-time of a program, which can help detect defects such as memory leaks, buffer overflows, or memory corruption. A dynamic analysis tool cannot provide support for traceability of tests, test results and incidents to source documents, as this is a function of a test management tool. A dynamic analysis tool cannot execute programs step-by-step in order to reproduce failures and find corresponding defects, as this is a function of a debugging tool. A dynamic analysis tool cannot provide support for release of baselines consisting of configuration items, as this is a function of a configuration management tool. Verified References: [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus - Springer], Chapter 6, page 56-57.
Was this answer correct?Question #10
Given the following review types and review characteristics: * a. Pair review * b. Walkthrough * c. Technical review * d. Inspection * 1. Formal * 2. Informal * 3. Purposes include evaluating the quality of the work product under review and generating new ideas (e.g., brainstorming solutions) * 4. Purposes include Improving the software product and training the review participants Which of the following BEST matches the review type with the review characteristic?
Please select an optionIncorrectCorrect answer: D
Pair reviews are informal and typically involve two people reviewing the work product together, often in an informal setting. Walkthroughs are more formal and aim to educate stakeholders and evaluate the product, serving the dual purpose of improving the product and training participants. Technical reviews have a strong focus on improving the product's quality, often involving technical stakeholders. Inspections are the most formal review type and are aimed primarily at detecting defects.References:ISTQB Certified Tester Foundation Level Syllabus v4.0, Section 3.2.3 "Review Types".
Was this answer correct?
Continue with ISTQB-CTFL: ISTQB-Foundation Level Exam
Unlock the full question bank
You have read the first 10 questions. A subscription opens every question in ISTQB-CTFL: ISTQB-Foundation Level Exam, the full timed practice test, and your progress and weak-topic reporting.
Single exam
$19.99for 30 days
Full question bank and practice test for one exam, for 30 days.
Single exam
$49.99for 1 year
One exam for a full year. Nothing renews and nothing to cancel.
Full access
$39.99/mo
Every exam in the catalogue, month to month.
Full access
$199.99/yr
Every exam in the catalogue for a year.
Already subscribed? Sign in to pick up where you left off.
Other ISTQB certifications
- CTFL v4.0: Certified Tester Foundation Level (CTFL) v4.0 (opens in a new tab)
- CT-TAE: Certified Tester Test Automation Engineer (opens in a new tab)
- ISTQB - Agile Public (opens in a new tab)
- CTFL-AT: Certified Tester Foundation Level Agile Tester (opens in a new tab)
- ATTA: Advanced Technical Test Analyst (opens in a new tab)
- CTAL-TM: ISTQB - Certified Tester Advanced Level, Test Manager (opens in a new tab)
Reviews
★★★★★
This platform is a lifesaver. The practice questions and explanations are so detailed. It’s the best study tool I’ve ever used.
Hannah Smith
USA
★★★★★
I highly recommend Exam Practice. The feedback after each test helped me improve significantly, and I passed my exams easily.
Oscar Nyström
Sweden
★★★★★
Exam Practice is worth every penny. The mock exams are realistic, and the feedback helped me focus on key areas.
Amit Sharma
India
FAQ
Learn More: https://www.istqb.org/
- Q1: What are ISTQB Certification Exams?
- A: ISTQB (International Software Testing Qualifications Board) Certification Exams validate your expertise in software testing and quality assurance. These certifications demonstrate your proficiency in testing principles, techniques, and tools, ensuring you can effectively contribute to software quality within your organization.
- Q2: Why should I pursue ISTQB Certification?
- A: ISTQB Certification enhances your professional credibility, showcasing your skills and knowledge in software testing. This can lead to better job opportunities, higher salaries, and career advancement in software development, quality assurance, and IT management.
- Q3: What are the benefits of ISTQB Certification?
- A: Benefits include recognition as a certified software testing professional, improved job performance, access to exclusive resources, continuing education opportunities, and staying current with the latest software testing practices and industry standards.
- Q4: Who should take ISTQB Certification Exams?
- A: Software testers, quality assurance professionals, developers, project managers, and anyone involved in ensuring software quality should consider these certifications to validate their expertise and advance their careers.
- Q5: What types of ISTQB Certification Exams are available?
- A: ISTQB offers various certification paths, including:
- Q6: How do I prepare for ISTQB Certification Exams?
- A: Preparation can include official ISTQB training courses, study guides, practice exams, online tutorials, and hands-on experience in software testing and quality assurance practices.
- Q7: Where can I take ISTQB Certification Exams?
- A: ISTQB Certification Exams can be taken at authorized testing centers worldwide or online through remote proctoring, providing flexibility to fit your schedule and location.
- Q8: How do ISTQB Certifications impact my career?
- A: ISTQB Certifications significantly boost your career by demonstrating your expertise to employers, making you a more competitive candidate for advanced roles and promotions in software testing, quality assurance, and IT management.
- Q9: Are there any prerequisites for ISTQB Certification Exams?
- A: The Foundation Level (CTFL) has no prerequisites. However, Advanced and Expert Levels require candidates to have prior certification and relevant professional experience. Check the specific requirements for each certification path on the ISTQB website.
- Q10: How often do I need to recertify for ISTQB Certifications?
- A: ISTQB certifications currently do not have a mandatory recertification requirement, but staying updated with the latest software testing practices and continuing professional development is recommended to maintain your skills and relevance in the industry.