ISTQB ISTQB-CTFL Online Practice Questions and Exam Preparation

ISTQB ISTQB-CTFL Online Questions & Answers

• Question 261:

  Which of the following statements is NOT true about Configuration management and software testing?

  A. Configuration management helps maintain consistent versions of software artifacts.
  B. Configuration management supports the build process, which is essential for delivering a test release into the test environment.
  C. When testers report defects, they need to reference version-controlled items.
  D. Version controlled test ware increases the chances of finding defects in the software under test.
  D. Version controlled test ware increases the chances of finding defects in the software under test.

  ---

  Explanation

  While configuration management is crucial for maintaining consistent versions of software artifacts and supporting the build process, it does not directly increase the chances of finding defects in the software under test. Version-controlled test ware ensures that the correct versions of test cases and other test artifacts are used, but it is the quality and thoroughness of the tests that determine the effectiveness of defect detection.

  ISTQB CTFL Syllabus V4.0, Section 5.4

• Question 262:

  What role in a formal or technical review should mediate between different opinions to ensure an effective review?

  A. Scribe (or recorder)
  B. Manager
  C. Moderator (or facilitator)
  D. Reviewer
  C. Moderator (or facilitator)

  ---

  Explanation

• Question 263:

  Which of the following definitions is NOT true?

  A. Test data preparation tools fill databases, create files or data transmissions to set up test data to be used during the execution of tests.
  B. Test execution tools execute test objects using automated test scripts.
  C. Test Management tools monitor and report on how a system behaves during the testing activities.
  D. Test comparators determine differences between files, databases or test results.
  C. Test Management tools monitor and report on how a system behaves during the testing activities.

  ---

  Explanation

  Test Management tools are designed to support the planning, execution, and monitoring of the testing process. They provide features for managing test cases, test runs, tracking defects, and reporting on testing activities. However, the

  statement in option C describes Test Management tools as monitoring and reporting on the system's behavior during testing activities, which is not accurate. Test Management tools focus on the testing process itself rather than on the

  behavior of the system under test.

  Test data preparation tools (A) indeed create and manage test data for use during test execution.

  Test execution tools (B) automate the execution of test cases and the comparison of actual outcomes against expected results.

  Test comparators (D) are tools that compare actual outcomes with expected outcomes, highlighting discrepancies.

  Therefore, option C is the correct answer as it inaccurately describes the function of Test Management tools.

• Question 264:

  Which of the following characterizations applies to a test tool used for the analysis of a developer's code prior to its execution?

  A. Tool support for test design and implementation.
  B. Tool support for static testing.
  C. Tool support for test execution and logging.
  D. Tool support for performance measurement and dynamic analysis.
  B. Tool support for static testing.

  ---

  Explanation

  A test tool used for the analysis of a developer's code prior to its execution falls under the category of static testing tools. Static testing involves examining the code and documentation without executing the code. These tools are used to

  perform static analysis, which helps in identifying potential defects and code quality issues early in the development process. The ISTQB CTFL syllabus specifies that static analysis tools are essential for finding defects that do not manifest

  themselves during the execution of the program.

  References: ISTQB CTFL Syllabus, Section 3.1, "Static Testing."

• Question 265:

  Which of the following is NOT a typical debugging activity when a failure is triggered by dynamic testing?

  A. Fixing the cause
  B. Reproducing the failure
  C. Diagnosing the root cause
  D. Adding new test cases
  D. Adding new test cases

  ---

  Explanation

• Question 266:

  In branch testing, what is the significance of a conditional branch in a software program?

  A. It indicates a decision point where the program can follow different paths based on specific conditions.
  B. It marks a point where the program's execution will terminate bringing the program to a halt.
  C. It represents a programming error and therefore a conditional branch should be avoided
  D. It signifies a comment or documentation within the code and it doesn't indicate a defect.
  A. It indicates a decision point where the program can follow different paths based on specific conditions.

  ---

  Explanation

• Question 267:

  Consider the following testing levels:

  1) Component Testing 2) Integration Testing 3) System Testing 4) Acceptance Testing

  Which of the following statements is true?

  A. Integration and system testing are applicable when V-model is used. Component and acceptance testing are applicable when iterative development models are used.
  B. All the testing levels are applicable to V-model for software development. Only acceptance testing is applicable for iterative models.
  C. Acceptance testing is applicable for all software development models. Component and system testing are applicable only for the V-model.
  D. All testing levels are applicable, independent of which software development life-cycle process (V- model. iterative, incremental) is used.
  D. All testing levels are applicable, independent of which software development life-cycle process (V- model. iterative, incremental) is used.

  ---

  Explanation

  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.

• Question 268:

  Which review type, also known as a "buddy check", is commonly used in Agile development?

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

  ---

  Explanation

  In Agile development, an informal review, often referred to as a "buddy check," is a common review type. Informal reviews are unstructured and involve a pair of colleagues reviewing each other's work to identify defects early and provide immediate feedback. This type of review is less formal than inspections or walkthroughs and is particularly suitable for Agile environments where rapid feedback and flexibility are essential.

  References: ISTQB CTFL Syllabus, Section 3.2.4, "Types of Reviews" and Section 2.1.4, "Agile Testing Practices."

• Question 269:

  Which of the following is MOST likely to be an example of a PROJECT risk?

  A. A computation is not always performed correctly in some situations
  B. A system architecture may not support some non-functional requirements
  C. Team members' skills may not be sufficient for the assigned work
  D. Specific modules do not adequately meet their intended functions according to the user
  C. Team members' skills may not be sufficient for the assigned work

  ---

  Explanation

  A project risk relates to potential issues that could affect the overall success of the project. Among the options provided, the risk that "Team members' skills may not be sufficient for the assigned work" is clearly a project risk because it

  pertains to the potential failure of the project due to inadequate skillsets among the team. This risk affects the entire project's ability to meet its objectives.

  References:

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

• Question 270:

  Which of the following BEST describes checklist-based testing?

  A. Checklist-based testing includes formal tests from detailed lists of test conditions, allowing much repeatability
  B. Checklist-based testing may involve a list of tests based on what is important to the user as well as an understanding of why and how software fails
  C. Checklist-based testing, while popular, provides little consistency and few guidelines concerning test case development
  D. Checklist-based testing is restricted to non-functional testing, including usability, performance, and security test
  B. Checklist-based testing may involve a list of tests based on what is important to the user as well as an understanding of why and how software fails

  ---

  Explanation

  Checklist-based testing involves using checklists that contain items, such as potential test conditions, that should be tested. These checklists are often based on insights into what is important to the user, potential areas where software might

  fail, and specific aspects that need to be tested. It provides a structured yet flexible approach to testing, ensuring key areas are covered while allowing testers to use their experience and understanding of the system. Checklist-based testing is

  not limited to non-functional testing but can be applied to various types of testing, including functional testing.

  References:

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