ISTQB ISTQB-CTFL Practice Exams
Last updated on Oct 21,2026- Exam Code: ISTQB-CTFL
- Exam Name: ISTQB-Foundation Level Exam
- Certification Provider: ISTQB
- Latest update: Oct 21,2026
Question #79
A coach should refer a client to seek help from a non-coaching professional when the client
- A . needs support navigating a transitional period in their life
- B . requests guidance in determining which employees should lose their jobs
- C . wants help building better relationships
- D . seeks confidence and clarity during o career change
Correct Answer: B
B
Explanation:
The ICF Code of Ethics (Section 2.5) mandates referral to other professionals when client needs exceed coaching’s scope, which is limited to supporting personal and professional growth, not providing expert advice or managing organizational decisions (ICF Coaching Boundaries).
Let’s analyze:
B
Explanation:
The ICF Code of Ethics (Section 2.5) mandates referral to other professionals when client needs exceed coaching’s scope, which is limited to supporting personal and professional growth, not providing expert advice or managing organizational decisions (ICF Coaching Boundaries).
Let’s analyze:
Question #2
A document descnbes the test procedures that have been derived for the identified test sets Among other things, the order in which the test cases in the corresponding test set are to be executed according to the dependencies described by preconditions and postconditions is specified.
This document is a typical work product produced as part of:
- A . Test design.
- B . Test analysis
- C . Test Implementation.
- D . Test monitoring and control
Correct Answer: C
C
Explanation:
Test implementation involves finalizing the test procedures, including the order of execution of test cases based on their dependencies, preconditions, and postconditions. This phase ensures that all necessary test scripts, test data, and test environments are ready for execution. According to the ISTQB CTFL Syllabus v4.0, test implementation is the phase where detailed test procedures are derived and documented, making it a critical step before actual test execution.
C
Explanation:
Test implementation involves finalizing the test procedures, including the order of execution of test cases based on their dependencies, preconditions, and postconditions. This phase ensures that all necessary test scripts, test data, and test environments are ready for execution. According to the ISTQB CTFL Syllabus v4.0, test implementation is the phase where detailed test procedures are derived and documented, making it a critical step before actual test execution.
Question #3
Which of the following about typical information found within a test plan is FALSE?
- A . The need to temporarily have additional test personnel available for specific test phases and/or test activities
- B . The conditions that must be met in order for the test execution activities to be considered completed.
- C . The list of the product risks which have not been fully mitigated at the end of test execution.
- D . The conditions that must be met for part of all the planned activities to be suspended and resumed.
Correct Answer: C
C
Explanation:
A typical test plan includes various elements, such as resource requirements, test completion criteria, and suspension/resumption criteria. However, the list of product risks that have not been fully mitigated is generally not included in the test plan but rather in the risk management documentation.
The test plan focuses on planning and executing tests, including resource allocation and defining criteria for test suspension and resumption.
While risk management is crucial, unmitigated risks are typically documented in risk logs or separate risk management plans.
Reference: ISTQB CTFL Syllabus V4.0, Chapter 5.1.1, Test Planning.
C
Explanation:
A typical test plan includes various elements, such as resource requirements, test completion criteria, and suspension/resumption criteria. However, the list of product risks that have not been fully mitigated is generally not included in the test plan but rather in the risk management documentation.
The test plan focuses on planning and executing tests, including resource allocation and defining criteria for test suspension and resumption.
While risk management is crucial, unmitigated risks are typically documented in risk logs or separate risk management plans.
Reference: ISTQB CTFL Syllabus V4.0, Chapter 5.1.1, Test Planning.
Question #4
Which of the following statements best describes the way in which decision coverage is measured?
- A . Measured as the number of statements executed by the tests, divided by the total number of executable statements in the code.
- B . Measured as the number of lines of code executed by the tests, divided by the total number of lines of code in the test object.
- C . Measured as the number of decision outcomes executed by the tests, divided by the total number of decision outcomes in the test object.
- D . It is not possible to accurately measure decision coverage.
Correct Answer: C
C
Explanation:
Decision coverage, also known as branch coverage, is measured as the number of decision outcomes executed by the tests divided by the total number of decision outcomes in the test object. It ensures that every possible branch (true/false) decision in the code has been executed at least once.
Reference: ISTQB CTFL Syllabus V4.0, Section 4.3.2
C
Explanation:
Decision coverage, also known as branch coverage, is measured as the number of decision outcomes executed by the tests divided by the total number of decision outcomes in the test object. It ensures that every possible branch (true/false) decision in the code has been executed at least once.
Reference: ISTQB CTFL Syllabus V4.0, Section 4.3.2
Question #5
Which of the following statements about test reports are TRUE?
I. Test reports shall be approved by the test team.
II. Test reports shall give stakeholders information as basis for decisions.
Ill. Test reports shall summarize what happened through a period of testing.
IV. Test reports shall be approved by the development team, the test team and the customer
V. Test reports shall include information about remaining risks.
- A . II, III, V
- B . I, II, IV
- C . I, III, v
- D . II, III, IV
Correct Answer: A
A
Explanation:
Statements II, III and V are true about test reports. Test reports are documents that provide information on the results and status of testing activities for a given period or phase. Test reports should give stakeholders information as basis for decisions, such as whether to release the software product, whether to continue testing, whether to change the scope or priorities of testing, etc. Test reports should summarize what happened through a period of testing, such as what test cases were executed, what defects were found, what risks were identified, what issues were encountered, what achievements were made, etc. Test reports should include information about remaining risks, such as what defects are still open, what test cases are still pending, what functionalities are still untested, what uncertainties are still unresolved, etc. Statements I and IV are not true about test reports. Test reports do not need to be approved by the test team, the development team, or the customer, unless it is specified by the test policy or the test plan. Test reports only need to be reviewed and verified by the test leader or the test manager before being distributed to the intended recipients.
Verified Reference: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus – Springer, page 141.
A
Explanation:
Statements II, III and V are true about test reports. Test reports are documents that provide information on the results and status of testing activities for a given period or phase. Test reports should give stakeholders information as basis for decisions, such as whether to release the software product, whether to continue testing, whether to change the scope or priorities of testing, etc. Test reports should summarize what happened through a period of testing, such as what test cases were executed, what defects were found, what risks were identified, what issues were encountered, what achievements were made, etc. Test reports should include information about remaining risks, such as what defects are still open, what test cases are still pending, what functionalities are still untested, what uncertainties are still unresolved, etc. Statements I and IV are not true about test reports. Test reports do not need to be approved by the test team, the development team, or the customer, unless it is specified by the test policy or the test plan. Test reports only need to be reviewed and verified by the test leader or the test manager before being distributed to the intended recipients.
Verified Reference: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus – Springer, page 141.
Question #6
In maintenance testing, what is the relationship between impact analysis and regression testing?
- A . Impact analysis requires a regression testing for only the tests that have detected faults in previous SW release
- B . There is no relationship between impact analysis and regression testing.
- C . Impact analysis requires a regression testing for all program elements which were newly integrated (new functionalities).
- D . The impact analysis is used to evaluate the amount of regression testing to be performed.
Correct Answer: D
D
Explanation:
In maintenance testing, the relationship between impact analysis and regression testing is that the impact analysis is used to evaluate the amount of regression testing to be performed. Maintenance testing is a type of testing that is performed on an existing software product after it has been delivered or deployed, in order to ensure that it still meets its requirements and functions correctly after a change or a modification. Maintenance testing can be triggered by various reasons, such as corrective maintenance (fixing defects), adaptive maintenance (adapting to new environments), perfective maintenance (improving performance), preventive maintenance (avoiding future problems), etc. Impact analysis is a technique that is used to assess the extent and nature of changes introduced by maintenance activities on the software product or project. Impact analysis helps to identify which parts of the software product are affected by the changes, which parts need to be modified or updated accordingly, which parts need to be retested or verified for correctness or compatibility, etc. Regression testing is a type of testing that verifies that previously tested software still performs correctly after a change or a modification. Regression testing helps to detect any side effects or unintended consequences of maintenance activities on the software product’s functionality or quality. Regression testing can be performed at various levels and scopes depending on the impact analysis results. Therefore, in maintenance testing, impact analysis is used to evaluate the amount of regression testing to be performed.
Verified Reference: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus – Springer, page 20.
D
Explanation:
In maintenance testing, the relationship between impact analysis and regression testing is that the impact analysis is used to evaluate the amount of regression testing to be performed. Maintenance testing is a type of testing that is performed on an existing software product after it has been delivered or deployed, in order to ensure that it still meets its requirements and functions correctly after a change or a modification. Maintenance testing can be triggered by various reasons, such as corrective maintenance (fixing defects), adaptive maintenance (adapting to new environments), perfective maintenance (improving performance), preventive maintenance (avoiding future problems), etc. Impact analysis is a technique that is used to assess the extent and nature of changes introduced by maintenance activities on the software product or project. Impact analysis helps to identify which parts of the software product are affected by the changes, which parts need to be modified or updated accordingly, which parts need to be retested or verified for correctness or compatibility, etc. Regression testing is a type of testing that verifies that previously tested software still performs correctly after a change or a modification. Regression testing helps to detect any side effects or unintended consequences of maintenance activities on the software product’s functionality or quality. Regression testing can be performed at various levels and scopes depending on the impact analysis results. Therefore, in maintenance testing, impact analysis is used to evaluate the amount of regression testing to be performed.
Verified Reference: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus – Springer, page 20.
Question #6
In maintenance testing, what is the relationship between impact analysis and regression testing?
- A . Impact analysis requires a regression testing for only the tests that have detected faults in previous SW release
- B . There is no relationship between impact analysis and regression testing.
- C . Impact analysis requires a regression testing for all program elements which were newly integrated (new functionalities).
- D . The impact analysis is used to evaluate the amount of regression testing to be performed.
Correct Answer: D
D
Explanation:
In maintenance testing, the relationship between impact analysis and regression testing is that the impact analysis is used to evaluate the amount of regression testing to be performed. Maintenance testing is a type of testing that is performed on an existing software product after it has been delivered or deployed, in order to ensure that it still meets its requirements and functions correctly after a change or a modification. Maintenance testing can be triggered by various reasons, such as corrective maintenance (fixing defects), adaptive maintenance (adapting to new environments), perfective maintenance (improving performance), preventive maintenance (avoiding future problems), etc. Impact analysis is a technique that is used to assess the extent and nature of changes introduced by maintenance activities on the software product or project. Impact analysis helps to identify which parts of the software product are affected by the changes, which parts need to be modified or updated accordingly, which parts need to be retested or verified for correctness or compatibility, etc. Regression testing is a type of testing that verifies that previously tested software still performs correctly after a change or a modification. Regression testing helps to detect any side effects or unintended consequences of maintenance activities on the software product’s functionality or quality. Regression testing can be performed at various levels and scopes depending on the impact analysis results. Therefore, in maintenance testing, impact analysis is used to evaluate the amount of regression testing to be performed.
Verified Reference: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus – Springer, page 20.
D
Explanation:
In maintenance testing, the relationship between impact analysis and regression testing is that the impact analysis is used to evaluate the amount of regression testing to be performed. Maintenance testing is a type of testing that is performed on an existing software product after it has been delivered or deployed, in order to ensure that it still meets its requirements and functions correctly after a change or a modification. Maintenance testing can be triggered by various reasons, such as corrective maintenance (fixing defects), adaptive maintenance (adapting to new environments), perfective maintenance (improving performance), preventive maintenance (avoiding future problems), etc. Impact analysis is a technique that is used to assess the extent and nature of changes introduced by maintenance activities on the software product or project. Impact analysis helps to identify which parts of the software product are affected by the changes, which parts need to be modified or updated accordingly, which parts need to be retested or verified for correctness or compatibility, etc. Regression testing is a type of testing that verifies that previously tested software still performs correctly after a change or a modification. Regression testing helps to detect any side effects or unintended consequences of maintenance activities on the software product’s functionality or quality. Regression testing can be performed at various levels and scopes depending on the impact analysis results. Therefore, in maintenance testing, impact analysis is used to evaluate the amount of regression testing to be performed.
Verified Reference: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus – Springer, page 20.
Question #8
Which of the following is NOT an experience-based technique?
- A . Boundary value analysis.
- B . Error guessing
- C . Exploratory testing
- D . Fault attack
Correct Answer: A
A
Explanation:
Boundary value analysis is not an experience-based technique, but rather a specification-based technique (also known as black-box technique). Experience-based techniques are techniques that rely on the tester’s knowledge and intuition to derive and select test cases based on their experience with similar systems, technologies, domains, risks, etc. Some examples of experience-based techniques are error guessing, exploratory testing, fault attack, checklist-based testing, etc. Specification-based techniques are techniques that rely on the tester’s analysis and interpretation of the requirements or specifications of the system under test to derive and select test cases based on some criteria or rules. Some examples of specification-based techniques are equivalence partitioning, boundary value analysis, decision table testing, state transition testing, etc.
Verified Reference: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus – Springer, page 31.
A
Explanation:
Boundary value analysis is not an experience-based technique, but rather a specification-based technique (also known as black-box technique). Experience-based techniques are techniques that rely on the tester’s knowledge and intuition to derive and select test cases based on their experience with similar systems, technologies, domains, risks, etc. Some examples of experience-based techniques are error guessing, exploratory testing, fault attack, checklist-based testing, etc. Specification-based techniques are techniques that rely on the tester’s analysis and interpretation of the requirements or specifications of the system under test to derive and select test cases based on some criteria or rules. Some examples of specification-based techniques are equivalence partitioning, boundary value analysis, decision table testing, state transition testing, etc.
Verified Reference: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus – Springer, page 31.
Question #9
Which of the following statements about the testing quadrants is TRUE?
- A . The higher the number of the testing quadrant, the more important the tests associated with this quadrant are
- B . Automated acceptance tests produced during BDD and ATDD are classified in quadrant 02.
- C . Exploratory tests are classified in quadrant Q3, and they are usually included in a continuous integration process.
- D . Automated unit tests produced during TDD are classified in quadrant Q4 as they are technology facing.
Correct Answer: B
B
Explanation:
The correct statement is
B. According to the ISTQB CTFL syllabus, the testing quadrants help to categorize tests based on their purpose and whether they are technology-facing or business-facing, and whether they support the team or critique the product. Quadrant Q2 includes tests that are business-facing and support the team, such as automated acceptance tests produced during Behavior-Driven Development (BDD) and Acceptance Test-Driven Development (ATDD).
Quadrant Q3 includes business-facing tests that critique the product, such as exploratory testing, usability testing, and user acceptance testing. These tests are typically manual and focus on evaluating the product from a user perspective, rather than being part of a continuous integration process.
Quadrant Q4 includes technology-facing tests that critique the product, such as performance tests, security tests, and other non-functional tests, which can be automated but are not related to unit tests produced during TDD.
B
Explanation:
The correct statement is
B. According to the ISTQB CTFL syllabus, the testing quadrants help to categorize tests based on their purpose and whether they are technology-facing or business-facing, and whether they support the team or critique the product. Quadrant Q2 includes tests that are business-facing and support the team, such as automated acceptance tests produced during Behavior-Driven Development (BDD) and Acceptance Test-Driven Development (ATDD).
Quadrant Q3 includes business-facing tests that critique the product, such as exploratory testing, usability testing, and user acceptance testing. These tests are typically manual and focus on evaluating the product from a user perspective, rather than being part of a continuous integration process.
Quadrant Q4 includes technology-facing tests that critique the product, such as performance tests, security tests, and other non-functional tests, which can be automated but are not related to unit tests produced during TDD.
Question #10
Which of the following is a correct reason to apply test automation?
- A . When a new test automation tool is launched
- B . When there are a lot of repetitive testing tasks
- C . When it is easy to automate
- D . When it is cheap to buy test automation tools
Correct Answer: B
B
Explanation:
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 Reference: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus – Springer, page 10.
B
Explanation:
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 Reference: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus – Springer, page 10.