ISTQB ISTQB-CTFL Online Practice Questions and Exam Preparation

ISTQB ISTQB-CTFL Online Questions & Answers

• Question 81:

  Which ONE of the following options identifies the perspectives through which a collective authorship process generates a shared vision of user stories?

  A. Product owner, development, and testing
  B. Business, architecture, and testing
  C. Business, development, and testing
  D. Business, development, and acceptance testing
  C. Business, development, and testing

  ---

  Explanation

  Comprehensive and Detailed In-Depth Explanation:

  Business, development, and testing (C) are the three key perspectives in agile user story refinement :

  Business (Product Owner, Stakeholders) ?Ensures the story aligns with user needs and business goals.

  Development (Developers) ?Provides insights on feasibility and technical constraints.

  Testing (Testers, QA) ?Ensures testability, acceptance criteria, and risk identification.

  (A)

  is incorrect because the product owner is part of business stakeholders.

  (B)

  is incorrect because architecture is part of development, but not the primary driver of user stories.

  (D)

  is incorrect because acceptance testing is a process, not a stakeholder group .

  A cross-functional team collaboration ensures well-defined, testable, and feasible user stories.

  ISTQB CTFL v4.0 Syllabus, Section 2.1.1 ?Agile Team Collaboration in Testing

• Question 82:

  Your organization's test strategy states that it is desirable to use more than one method for estimating test effort . You are responsible for estimating test effort for the next project. Based on historical data, the development-to-test effort ratio is

  5:3 .

  The initial estimate for the development effort is 450 person-days .

  Which ONE of the following options corresponds to the estimated test effort using the ratio-based method?

  A. 750 person-days
  B. 180 person-days
  C. 720 person-days
  D. 270 person-days
  D. 270 person-days

  ---

  Explanation

• Question 83:

  Which of the following is NOT an experience-based technique?

  A. Boundary value analysis.
  B. Error guessing
  C. Exploratory testing
  D. Fault attack
  A. Boundary value analysis.

  ---

  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

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

• Question 84:

  You are an experienced tester on a project with incomplete requirements and under pressure to deploy.

  What type of testing should you do?

  A. Decision-based testing.
  B. Checklist-based testing.
  C. Error guessing.
  D. Exploratory testing.
  D. Exploratory testing.

  ---

  Explanation

  When working on a project with incomplete requirements and under pressure to deploy, exploratory testing is particularly suitable. This type of testing allows testers to use their expertise and intuition to explore the system's functionality and identify defects without needing detailed specifications. Exploratory testing is flexible and can quickly adapt to changes and gaps in the requirements.

• Question 85:

  Determining the schedule for each testing activity and test milestones for a test project, using activity estimates, available resources, and other constraints is a typical task performed during

  A. Test execution
  B. Test design.
  C. Test analysis.
  D. Test planning
  D. Test planning

  ---

  Explanation

  Test planning involves defining the overall approach to testing, including scheduling, resources, and milestones. It is during this phase that the detailed schedule for each testing activity is determined based on estimates, resource availability, and constraints. The ISTQB CTFL Syllabus v4.0 outlines that test planning encompasses the creation of test plans and schedules to ensure that testing activities are properly managed and controlled.

• Question 86:

  Select which of the following statements describe the key principles of software testing?

  i:. Testing shows the presence of defects, not their absence.

  ii:. Testing everything Is possible.

  iii:. Early testing Is more expensive and is a waste of time.

  iv:. Defects cluster together.

  v:. Testing is context dependent.

  vi:. Beware of the pesticide paradox.

  vii:. Absence of errors is a fallacy.

  Select the correct answer:

  A. i, iv, v, vi and vii
  B. I, ii, v. vi and vii
  C. iii. iv, v. vi and vii
  D. ii, iii, iv, v and vi
  A. i, iv, v, vi and vii

  ---

  Explanation

  The key principles of software testing include: i. Testing shows the presence of defects, not their absence. iv. Defects cluster together. v. Testing is context dependent. vi. Beware of the pesticide paradox. vii. Absence of errors is a fallacy. These principles highlight the importance of recognizing the limitations and context of testing, as well as the potential for repeated tests to become less effective.

• Question 87:

  Given the following examples of entry and exit criteria:

  1.A defined level of code coverage has been achieved 2.The test automation tool has been installed and properly configured 3.The number of unresolved defects is within the predefined limit 4.The performance test environment has been set-up and is available 5.The user stories have proper acceptance criteria defined 6.The testing budget has been spent and the project sponsor bears the risk of not testing any further

  Which of the following BEST categorizes them as entry and exit criteria:

  A. Entry criteria - 2, 4, 5 Entry criteria -1, 3, 4
  B. Entry criteria - 2, 4 Entry criteria - 2, 4, 5, 6
  C. Exit criteria -1,3,6 Exit criteria - 2, 5. 6
  D. Exit criteria -1,3,56 Exit criteria -1,3
  A. Entry criteria - 2, 4, 5 Entry criteria -1, 3, 4

  ---

  Explanation

  Entry and exit criteria are used to determine when to start and stop testing, respectively.

  Entry Criteria:

  These are conditions that should be met before testing begins.

  Examples:

  2. The test automation tool has been installed and properly configured

  4.The performance test environment has been set-up and is available

  5.The user stories have proper acceptance criteria defined

  Exit Criteria:

  These are conditions that should be met before testing concludes.

  Examples:

  1. A defined level of code coverage has been achieved

  3. The number of unresolved defects is within the predefined limit

  6. The testing budge ISTQB not-for-profit association spent and the project sponsor bears ( ) the risk of not testing any further

  According to the ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, these criteria help in effectively managing the testing process#6source#.

  References:

  Certified Tester Foundation Level v4.0

  ISTQB Foundation Level Syllabus 4.0 (2023)

• Question 88:

  Which ONE of the following elements is TYPICALLY used to guide testing during exploratory testing ?

  A. A test charter that defines the testing objectives for the test session.
  B. A comprehensive specification that must be fully available before testing begins.
  C. A detailed test script that prescribes all the steps to be performed.
  D. A predefined test case that must be executed exactly as documented.
  A. A test charter that defines the testing objectives for the test session.

  ---

  Explanation

  Comprehensive and Detailed In-Depth Explanation:

  Exploratory testing is an unscripted approach where testers actively design and execute tests based on their intuition, experience, and knowledge of the system. A test charter (A) provides a guideline on what areas to explore, defining test

  objectives but leaving room for dynamic adaptation.

  (B), (C), and (D) contradict exploratory testing principles, which focus on freedom rather than rigid documentation.

  Exploratory testing is especially useful in agile environments, usability testing, and uncovering unexpected defects.

  ISTQB CTFL v4.0 Syllabus, Section 4.4.2 ?Exploratory Testing

• Question 89:

  Which one of the following statements relating to the benefits of static testing is NOT correct?

  A. Static testing enables early detection of defects before dynamic testing is performed.
  B. Static testing reduces testing costs and time.
  C. Static testing increases development costs and time.
  D. Static testing identifies defects which are not easily found by dynamic testing.
  C. Static testing increases development costs and time.

  ---

  Explanation

  The statement that "static testing increases development costs and time" is NOT correct. Static testing actually helps to reduce development costs and time by identifying defects early in the development process before dynamic testing is performed. Early detection of defects reduces the cost and effort required to fix them and prevents the propagation of defects to later stages, thus reducing overall testing and development costs.

  References: ISTQB CTFL Syllabus, Section 3.1.2, "The Value of Static Testing."

• Question 90:

  Which of the following does MOT describe a reason why testing is necessary?

  A. The customer decided that 100% branch coverage shall be achieved
  B. The acquisition of test automation tools was based on the assumption that it will be used m all projects
  C. For avionics and pharmaceutical systems software testing is mandated by standards
  D. The risks associated with delivering the system are far higher than the cost of testing
  B. The acquisition of test automation tools was based on the assumption that it will be used m all projects

  ---

  Explanation

  Testing is necessary for various reasons, such as:

  To detect defects and failures that may affect the quality, performance, reliability or security of a software product or system To verify that a software product or system meets its specified requirements, expectations and standards To validate

  that a software product or system fulfills its intended purpose and satisfies its stakeholders' needs

  To provide information and feedback about the status and risks of a software product or system

  To comply with regulations or contractual obligations that mandate testing for certain types of software products or systems The following statements describe some reasons why testing is necessary:

  A) The customer decided that 100% branch coverage shall be achieved. This is a reason why testing is necessary, as it reflects a contractual obligation or a quality standard that requires testing to measure and achieve a certain level of code

  coverage.

  C) For avionics and pharmaceutical systems software testing is mandated by standards. This is a reason why testing is necessary, as it reflects a regulation or a compliance requirement that mandates testing for certain types of software

  products or systems that have high safety or security risks.

  D) The risks associated with delivering the system are far higher than the cost of testing. This is a reason why testing is necessary, as it reflects a risk-based approach that considers testing as an investment to reduce the probability and

  impact of potential failures or defects. The following statement does not describe a reason why testing is necessary:

  B) The acquisition of test automation tools was based on the assumption that it will be used m all projects. This is not a reason why testing is necessary, as it reflects a business decision or a resource allocation that does not justify the need

  or purpose of testing. Test automation tools are not always suitable or beneficial for all projects, and testing can be performed with or without test automation tools.

  Verified

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