ISTQB ISTQB-CTFL Online Practice Questions and Exam Preparation

ISTQB ISTQB-CTFL Online Questions & Answers

• Question 111:

  Which of the statements on confirmation testing and regression testing is correct?

  A. Regression tests are performed to confirm that defects have been corrected and no longer lead to errors
  B. Confirmation tests are performed to confirm that changes have no undesired effects
  C. Regression tests are performed to confirm that errors have been corrected and no longer lead to failures
  D. Confirmation tests are performed to confirm that defects have been corrected and no longer lead to failures
  D. Confirmation tests are performed to confirm that defects have been corrected and no longer lead to failures

  ---

  Explanation

• Question 112:

  An application is subjected to a constant load for an extended period of time as part of a performance test While running this test, the response time of the application steadily slows down, which results in a requirement not being met This slowdown is caused by a memory leak where the application code does not properly release some of the dynamically allocated memory when it is no longer needed. Which of the following statements is TRUE?

  A. The slowdown is a failure while the memory leak is a defect
  B. The slowdown is a defect while the memory leak is an error.
  C. The slowdown is an error; the memory leak is a defect.
  D. The slowdown is a defect; the memory leak is a failure.
  A. The slowdown is a failure while the memory leak is a defect

  ---

  Explanation

  In software testing terminology, a failure is an observable deviation of the software from its expected behavior. A defect (or bug) is the cause of the failure in the software's code. In this case, the observed slowdown is the failure, while the underlying memory leak in the application code is the defect causing this failure. This distinction is clearly outlined in the ISTQB CTFL Syllabus v4.0, which differentiates between failures (observable issues) and defects (underlying issues in the code).

• Question 113:

  Which of the following would be the LEAST likely to be used as the basis for a test exit criteria?

  A. Test schedules
  B. Cost of testing performed so far
  C. Confidence of testers in tested code
  D. Number of unfixed defects
  A. Test schedules

  ---

  Explanation

  Test exit criteria are the conditions or requirements that must be met before testing can be concluded. Test exit criteria are usually defined in the test plan and agreed by the stakeholders. Test exit criteria can be based on various factors, such as test coverage, defect status, quality level, risk level, etc. Test schedules would be the least likely to be used as the basis for test exit criteria, because test schedules are not directly related to the quality or performance of the software product, but rather to the time or resources allocated for testing. Test schedules can be used as the basis for test entry criteria, which are the conditions or requirements that must be met before testing can start. The other options are more likely to be used as the basis for test exit criteria. Cost of testing performed so far can be used as a basis for test exit criteria, because it can indicate the return on investment or the cost-benefit ratio of testing. Confidence of testers in tested code can be used as a basis for test exit criteria, because it can reflect the level of satisfaction or assurance of the testers about the quality or reliability of the software product. Number of unfixed defects can be used as a basis for test exit criteria, because it can indicate the level of risk or impact of the remaining defects on the software product. Verified

  References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 13.

• Question 114:

  Which of the following software development models BEST exemplifies a model that does NOT support the principle of early testing?

  A. The iterative development model
  B. The V-model
  C. The Waterfall model
  D. The incremental development model
  C. The Waterfall model

  ---

  Explanation

  The Waterfall model exemplifies a software development model that does not support the principle of early testing. In the Waterfall model, each phase must be completed before the next begins, which delays testing until after the completion

  of the earlier phases like requirements gathering and design. This can often result in finding defects later in the development cycle, making them more expensive and time-consuming to fix (ISTQB not-for-profit association) (ISTQB not-forprofit association).

  References:

  ISTQB Certified Tester Foundation Level Syllabus v4.0: https://istqb-main-web-prod.s3.amazonaws.com /media/documents/ISTQB_CTFL_Syllabus-v4.0.pdf ISTQB News Release on CTFL v4.0: https://www.istqb.org/news/posts/istqbreleases-certified-tester-foundation-level-v40-ctfl/

• Question 115:

  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
  B. When there are a lot of repetitive testing tasks

  ---

  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

  References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 10.

• Question 116:

  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.
  D. The impact analysis is used to evaluate the amount of regression testing to be performed.

  ---

  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

  References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 20.

• Question 117:

  Which of the following BEST describes exploratory testing?

  A. Exploratory testing is a suitable test technique which may replace both black-box and white-box test techniques
  B. Exploratory testing is a valid and useful black-box test technique since it focuses on test cases related to the architecture and design of a system
  C. Exploratory testing requires both solid specifications and much project time available for test execution
  D. Exploratory testing may be used within defined time periods, during which the tester may follow a test charter as a guide
  D. Exploratory testing may be used within defined time periods, during which the tester may follow a test charter as a guide

  ---

  Explanation

  Exploratory testing involves simultaneous test design and execution and is guided by a test charter, which outlines what needs to be tested, how it should be tested, and what to look for. This technique is typically conducted within predefined

  time periods, known as time-boxing, which allows testers to explore a system, understand its functionalities, and identify potential issues without detailed documentation or prior test case planning. The key aspects of exploratory testing

  include flexibility, adaptability, and the ability to respond to system behavior during testing.

  References:

  ISTQB Certified Tester Foundation Level Syllabus v4.0, Section 4.4.2.

• Question 118:

  What does configuration management enable for testing?

  A. It enables the scheduling of test resources.
  B. It enables the derivation of test cases and test data.
  C. It enables the creation of test progress reports.
  D. It enables the versioning of the test elements.
  D. It enables the versioning of the test elements.

  ---

  Explanation

• Question 119:

  Which of the following statements best describes an advantage of the whole team approach?

  A. It allows the team to deliver software faster by skipping testing and documentation activities.
  B. It enables the team to share responsibility for quality and collaborate with stakeholders throughout the project.
  C. It enables a better division of labor as the team shares a common workspace in one physical location.
  D. It fosters competition and individualism among team members to achieve higher performance.
  B. It enables the team to share responsibility for quality and collaborate with stakeholders throughout the project.

  ---

  Explanation

• Question 120:

  Which of the following statements is assigned correctly as a project or product risk?

  A. The software does not perform its intended functions according to the specification: this is a project risk.
  B. The gradual expansion of the project scope result in significant rework: this is a product risk.
  C. The system architecture does not adequately support some of the non-functional requirements: this is a product risk.
  D. User experience feedback does not meet product expectations: this is a project risk.
  C. The system architecture does not adequately support some of the non-functional requirements: this is a product risk.

  ---

  Explanation