ISTQB ISTQB-CTFL Online Practice Questions and Exam Preparation

ISTQB ISTQB-CTFL Online Questions & Answers

• Question 341:

  Which statement about exploratory testing is TRUE?

  A. It cannot be used in regulated domains.
  B. It combines learning, test design, and execution simultaneously.
  C. It replaces all scripted testing.
  D. It is limited to usability testing.
  B. It combines learning, test design, and execution simultaneously.

  ---

  Explanation

  Exploratory testing integrates learning and execution in real time.

• Question 342:

  A software module to be used in a mission critical application incorporates an algorithm for secure transmission of data.

  Which review type is most appropriate to ensure high quality and technical correctness of the algorithm?

  A. Walkthrough
  B. Informal Review
  C. Technical Review
  D. Management Review
  C. Technical Review

  ---

  Explanation

  A technical review is a type of formal review that involves a team of technical experts who evaluate a software product against a set of predefined quality criteria. A technical review is suitable for ensuring high quality and technical correctness of complex or critical software components, such as algorithms, architectures or designs. A technical review is not a walkthrough, which is an informal review led by the author of the work product. A technical review is not an informal review, which is a review that does not follow a defined process and has no formal entry or exit criteria. A technical review is not a management review, which is a type of formal review that focuses on business aspects and project progress. Verified

  References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, Chapter 3, page 29- 30.

• Question 343:

  Which of the following is correct with regards to debugging?

  A. Debugging identifies the cause of a failure
  B. Debugging is often performed by test engineers
  C. Debugging is considered part of the testing activities
  D. Debugging is intended to find as many defects as possible in the code
  A. Debugging identifies the cause of a failure

  ---

  Explanation

  Debugging is the process of finding, analyzing and removing the causes of failures in software. Debugging is not considered part of testing, but rather a development activity that can involve testing. Debugging is not intended to find as many defects as possible, but rather to fix the specific failure that was observed. Debugging is usually performed by developers, not by test engineers. Verified

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

• Question 344:

  Exploratory testing is an experience-based test technique

  A. Where a developer and a tester work together on the same workstation while the developer actively writes code, the tester explores the code to find defects.
  B. That can be organised into sessions guided by test charters outlining test objectives that will guide the testers' exploration
  C. Where a team of testers explores all possible test techniques in order to determine the most suitable combination of these techniques to apply for a test project.
  D. That aims at finding defects by designing tests that exercise all possible combinations of input values and preconditions
  B. That can be organised into sessions guided by test charters outlining test objectives that will guide the testers' exploration

  ---

  Explanation

  Exploratory testing is an experience-based test technique where testers actively engage with the software, learning about its behavior while simultaneously designing and executing tests. According to the ISTQB CTFL syllabus, exploratory testing can be structured into sessions guided by test charters, which outline the test objectives and provide direction for the testers' exploration. This method is particularly useful in situations where test documentation is limited or where rapid feedback is needed. Thus, option B correctly describes how exploratory testing can be organized.

• Question 345:

  For a given set of test-cases, which of the following is a benefit of running these tests with a test automation tool?

  A. Test coverage is increased
  B. The total cost of the test project always decreases
  C. The time spent on repetitive tasks is reduced
  D. The number of found bugs is reduced
  C. The time spent on repetitive tasks is reduced

  ---

  Explanation

• Question 346:

  Which ONE of the following statements does NOT describe how testing contributes to higher quality?

  A. Properly designed tests that pass reduce the level of risk in a system.
  B. The testing of software demonstrates the absence of defects.
  C. Software testing identifies defects, which can be used to improve development activities.
  D. Performing a review of the requirement specifications before implementing the system can enhance quality.
  B. The testing of software demonstrates the absence of defects.

  ---

  Explanation

  The testing of software does not demonstrate the absence of defects, but rather the presence of defects or the conformance of the software to the specified requirements1. Testing can never prove that the software is defect-free, as it is impossible to test all possible scenarios, inputs, outputs, and behaviors of the software2. Testing can only provide a level of confidence in the quality of the software, based on the coverage, effectiveness, and efficiency of the testing activities.

  The other options are correct because:

  A. Properly designed tests that pass reduce the level of risk in a system, as they verify that the system meets the expected quality attributes and satisfies the needs and expectations of the users and clients4. Risk is the potential for loss or harm due to the occurrence of an undesirable event5. Testing can help to identify, analyze, prioritize, and mitigate the risks associated with the software product and project.

  C. Software testing identifies defects, which can be used to improve development activities, as they provide feedback on the quality of the software and the effectiveness of the development processes7. Defects are flaws or errors in the software that cause it to deviate from the expected or required results or behavior. Testing can help to detect, report, track, and resolve the defects, and prevent them from recurring in the future.

  D. Performing a review of the requirement specifications before implementing the system can enhance quality, as it can ensure that the requirements are clear, complete, consistent, testable, and aligned with the needs and expectations of the users and clients. Requirements are the specifications of what the software should do and how it should do it. Testing can help to validate that the requirements are met by the software, and verify that the software is implemented according to the requirements.

  References: ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 10 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 11 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 12 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 13 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 97 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 98 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 14 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 15 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 16 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 17 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 18 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 19

• Question 347:

  Which of the following would be LEAST appropriate as part of an incident report covering the observation of a failure during testing?

  A. SOL injection into the username entry field allowed a variety of SQL commands to be executed by the application without the appropriate authority.
  B. The user interface was complicated and confusing and I found It quite difficult to follow the test script.
  C. The updates made as part of the add new member' function did not reflect the expected change as the name was written into the address field.
  D. The expected result for the `list friends' response time was less than 10 seconds, whereas the average response time obtained was 13 seconds.
  B. The user interface was complicated and confusing and I found It quite difficult to follow the test script.

  ---

  Explanation

  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.

• Question 348:

  Consider a review for a high-level architectural document written by a software architect. The architect does most of the review preparation work, including distributing the document to reviewers before the review meeting. However, reviewers are not required to analyze the document in advance, and during the review meeting the software architect explains the document step by step. The only goal of this review is to establish a common understanding of the software architecture that will be used in a software development project.

  Which of the following review types does this review refer to?

  A. Inspection
  B. Audit
  C. Walkthrough
  D. Informal review
  C. Walkthrough

  ---

  Explanation

  This answer is correct because a walkthrough is a type of review where the author of the work product leads the review process and explains the work product to the reviewers. The reviewers are not required to prepare for the review in advance, and the main objective of the walkthrough is to establish a common understanding of the work product and to identify any major defects or issues. A walkthrough is usually informal and does not follow a defined process or roles. In this case, the review for a high-level architectural document written by a software architect matches the characteristics of a walkthrough.

  References: ISTQB Glossary of Testing Terms v4.0, ISTQB Foundation Level Syllabus v4.0, Section

• Question 349:

  Which of the following is an example of the absence-of-errors fallacy?

  A. Repeating the same test cases will continue to find new defects, even after dozens of executions
  B. A small number of modules contains the most defects
  C. Since testing found very few defects, the system certainly will be successful
  D. Other than trivial cases, it is not feasible to test all combinations of inputs and preconditions
  C. Since testing found very few defects, the system certainly will be successful

  ---

  Explanation

  The absence-of-errors fallacy, as explained in the ISTQB syllabus, is the erroneous belief that having fewer defects found in testing equates to a system being more successful upon release. This misconception can lead stakeholders to undervalue thorough testing. Answer C illustrates this fallacy perfectly: assuming that because few defects were found, the system will be successful, neglects the many other factors that contribute to system success, including user satisfaction and fit-for-purpose.

  References:ISTQB Certified Tester Foundation Level Syllabus v4.0, Section 1.1.5 "Absence-of-errors fallacy".

• Question 350:

  Which pair correctly matches tool type and support activity?

  A. Test management tool ?static code analysis
  B. Static analysis tool ?detect security vulnerabilities before execution
  C. Performance testing tool ?requirements traceability
  D. Defect management tool ?test data generation
  B. Static analysis tool ?detect security vulnerabilities before execution

  ---

  Explanation

  Static analysis tools detect potential defects without running the code.