ISTQB ISTQB-CTFL Online Practice Questions and Exam Preparation

ISTQB ISTQB-CTFL Online Questions & Answers

• Question 271:

  The following open incident report provided:

  1.Date: 01.01.01

  2.Description: When pressing the stop button the application status remain in "Attention"

  3.instead of "Ready'.

  4.Severity: High

  5.Life Cycle: Integration

  Which of the following details are missing in the giving incident report?

  I- Identification or configuration of the application II- The name of the developer III- Recommendation of the developer IV The actions and/or conditions that came before the pressing of the button

  A. IV
  B. I. IV
  C. I. II
  D. II, III
  B. I. IV

  ---

  Explanation

  In an incident report, essential details provide context and facilitate the investigation and resolution of the incident. The missing elements in the given incident report are:

  I. Identification or configuration of the application: This detail is crucial as it specifies which version or configuration of the application is affected, helping in reproducing the issue. IV. The actions and/or conditions that came before pressing the button: Understanding the sequence of actions leading to the issue is vital for replicating and diagnosing the problem.

  The name of the developer (II) and the recommendation of the developer (III) are not typically included in an incident report as they do not contribute to identifying or resolving the incident. The focus is on the incident's details, reproduction steps, and the system's state rather than on personnel or proposed solutions at this stage. Therefore, option B, which includes both I and IV, is the correct answer.

• Question 272:

  The following table shows six test cases TC01 to TC06 with their priorities and dependencies.

  

  Schedule the test execution of the specified test case set according to the priorities and dependencies. Since the test time is very tight, the number of test cases should be minimized as much as possible, but all very important test cases must be included.

  Which of the following statements is correct?

  A. TC04, TC05, and TC06 can be deleted.
  B. TC05 and TC06 can be deleted.
  C. TC04 and TC05 can be deleted.
  D. TC03, TC04 and TC05 can be deleted.
  B. TC05 and TC06 can be deleted.

  ---

  Explanation

• Question 273:

  Which of the following statements is NOT an objective of testing?

  A. Create confidence in the quality of the test object.
  B. Check whether the test object fulfils the specified requirements.
  C. Provide sufficient information for stakeholders to make decisions.
  D. Fix defects after they have been found and analyzed.
  C. Provide sufficient information for stakeholders to make decisions.

  ---

  Explanation

• Question 274:

  Which sequence of stated in the answer choices is correct in accordance with the following figure depicting the life-cycle of a defect?

  

  A. S0->S1->S2->S3->S5->S1
  B. S0->S1->S2->S3->S5->S1->S2->S3
  C. S0->S1->S2~>S3->S4
  D. S0->S1 ->S2->S3->S5->S3->S4
  D. S0->S1 ->S2->S3->S5->S3->S4

  ---

  Explanation

  According to the ISTQB Certified Tester Foundation Level (CTFL) v4.0, the life cycle of a defect typically follows a sequence from its discovery to its closure. In the provided figure, it starts with S0 (New), moves to S1 (Assigned), then to S2 (Resolved), followed by S3 (Verified). If the defect is not fixed, it can be Re- opened (S5) and goes back for verification (S3). Once verified, it is Closed (S4).

  References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 Syllabus, Section 1.4.3, Page 17.

• Question 275:

  Which description reflects aspects of checklist-based testing?

  A. The checklist contains test cases that need to be executed in a certain order (e.g. defect-detecting test cases from previous projects).
  B. The checklist includes failure descriptions that have been found in the past which should be avoided.
  C. The checklist contains experience-based test conditions, mostly in the form of questions and based on causes of previous failures, which are used when creating the test.
  D. The checklist contains common testing techniques (e.g. equivalence class partitioning) and their uses to simplify the selection of the "appropriate" test techniques.
  C. The checklist contains experience-based test conditions, mostly in the form of questions and based on causes of previous failures, which are used when creating the test.

  ---

  Explanation

• Question 276:

  Which statement about use case testing is true?

  A. The lest cases are designed to find defects in the data flew.
  B. The test cases are designed to be used by real users, not by professional testers
  C. The test cases are always designed by customers or end users.
  D. The test cases are designed to find defects in the process flow.
  D. The test cases are designed to find defects in the process flow.

  ---

  Explanation

  Use case testing is a technique that helps identify test cases that exercise the whole system on a transaction by transaction basis from start to finish. Use cases are descriptions of how users interact with the system to achieve a specific goal. Use case testing is not focused on data flow, but rather on process flow. Use case testing can be performed by professional testers, customers or end users, depending on the context. Use case testing does not require the test cases to be designed by customers or end users, but rather by anyone who has access to the use case specifications. Verified

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

• Question 277:

  Which of the following statements about test estimation approaches is CORRECT?

  A. The Wideband Delphi estimation technique is an example of the risk-based approach
  B. The Wideband Delphi estimation technique is an example of the expert-based approach
  C. Bumdown charts used in Agile development is an example of the risk-based approach
  D. Burndown charts used in Agile development is an example of the expert-based approach
  B. The Wideband Delphi estimation technique is an example of the expert-based approach

  ---

  Explanation

  There are two main approaches to test estimation:

  Expert-based approach:

  The Wideband Delphi estimation technique is an example of this approach.

  Involves consulting expert (ISTQB not-for-profit association)ate testing efforts.

  This technique gathers estimates from multiple experts, discusses their differences, and achieves consensus.

  Metrics-based approach:

  Relies on historical data and metrics to predict future testing efforts.

  According to the ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, the expert-based approach relies on experts' experience and knowledge, which aligns with the Wideband Delphi technique#6source#.

  References:

  Certified Tester Foundation Level v4.0

  ISTQB Foundation Level Syllabus 4.0 (2023)

• Question 278:

  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.
  C. The list of the product risks which have not been fully mitigated at the end of test execution.

  ---

  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.

  ISTQB CTFL Syllabus V4.0, Chapter 5.1.1, Test Planning.

• Question 279:

  Which of the following is a typical potential risk of using test automation tools?

  A. Reduced feedback times regarding software quality compared to manual testing.
  B. Reduced test execution limes compared to manual testing.
  C. Reduced repeatability and consistency of tests compared to manual testing
  D. Underestimation of effort required to maintain test scripts.
  D. Underestimation of effort required to maintain test scripts.

  ---

  Explanation

  One of the common risks associated with test automation tools is the underestimation of the effort required to maintain test scripts. Test scripts can become outdated or broken due to changes in the application, requiring significant effort to update and maintain them. This risk is highlighted in the ISTQB CTFL syllabus under the discussion of the benefits and risks of test automation.

  References: ISTQB CTFL Syllabus, Section on test tools and automation.

• Question 280:

  Which of the following statements about testware are correct?

  I: When closing the test activities, all the testware resources can be uninstalled and released

  II: All the testware should be subject to Configuration Management

  III: The testware. at the end of the project, should be transferred to the organization responsible for maintenance

  IV:

  The developers are responsible for the correct installation of the testware

  A. II, Ill
  B. I, Ill
  C. I, IV
  D. II, IV
  A. II, Ill

  ---

  Explanation

  Testware is a term that refers to all artifacts produced during the testing process, such as test plans, test cases, test scripts, test data, test results, defect reports, etc. The following statements about testware are correct: II) All the testware should be subject to Configuration Management. Configuration management is a process that establishes and maintains consistency among work products throughout their life cycle. Configuration management applies to all testware, as it helps ensure their quality and consistency, track their changes and defects, control their versions and access rights, and link them to other artifacts. III) The testware at the end of the project should be transferred to the organization responsible for maintenance. Maintenance testing is testing performed on a software product after delivery to correct defects or improve performance or other attributes. Maintenance testing requires testware from previous testing activities or phases, such as test cases, test data, test results, etc. Therefore, the testware at the end of the project should be transferred to the organization responsible for maintenance testing, such as support team or maintenance team. The following statements about testware are incorrect: I) When closing the test activities, all the testware resources can be uninstalled and released. This statement is incorrect, as some testware resources may still be needed for future testing activities or phases, such as maintenance testing or regression testing. Therefore, when closing the test activities, some testware resources should be archived and stored for future use, while others can be uninstalled and released. IV) The developers are responsible for the correct installation of the testware. This statement is incorrect, as the testers are responsible for the correct installation of the testware. The testers should ensure that they have access to all necessary testware resources and that they are installed and configured properly before starting the test execution. Verified

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