Free CTFL_Syll_4.0 Exam Braindumps
ISTQB Certified Tester Foundation Level (CTFL) v4.0 Questions 31–35 (page: 8)

Updated On: 10-Feb-2026

Following a risk-based testing approach you have designed 10 tests to cover a product risk with a high-risk level. You want to estimate, adopting the three-point test estimation technique, the test effort required to reduce the risk level to zero by executing those 10 tests. You made the following three initial estimates:

· most optimistic = 6 person hours

· most likely = 30 person hours

· most pessimistic = 54 person hours

Based only on the given information, which of the following answers about the three-point test estimation technique applied to this problem is true?

  1. The final estimate is between 22 person hours and 38 person hours
  2. The final estimate is exactly 30 person hours because the technique uses the initial most likely estimate as the final estimate
  3. The final estimate is between 6 person hours and 54 person hours
  4. The final estimate is exactly 30 person hours because the technique uses the arithmetic mean of the three initial estimates as the final estimate

Answer(s): A

Explanation:

The three-point test estimation technique is a method of estimating the test effort based on three initial estimates: the most optimistic, the most likely, and the most pessimistic. The technique uses a weighted average of these three estimates to calculate the final estimate, which is also known as the expected value. The formula for the expected value is:

Expected value = (most optimistic + 4 * most likely + most pessimistic) / 6

Using the given values, the expected value is:

Expected value = (6 + 4 * 30 + 54) / 6 Expected value = 30 person hours

However, the expected value is not the only factor to consider when estimating the test effort. The technique also calculates the standard deviation, which is a measure of the variability or uncertainty of the estimates. The formula for the standard deviation is:

Standard deviation = (most pessimistic - most optimistic) / 6

Using the given values, the standard deviation is:

Standard deviation = (54 - 6) / 6 Standard deviation = 8 person hours

The standard deviation can be used to determine a range of possible values for the test effort, based on a certain level of confidence. For example, using a 68% confidence level, the range is:

Expected value ± standard deviation

Using the calculated values, the range is:

30 ± 8 person hours

Therefore, the final estimate is between 22 person hours and 38 person hours, which is option A.


Reference:

ISTQB® Certified Tester Foundation Level Syllabus v4.01, Section 2.3.2, page 24-25; ISTQB® Glossary v4.02, page 33.



The acceptance criteria associated with a user story:

  1. are often written in a rule-oriented format using the template referred to as "Given/When/Then"
  2. are often documented following in rule-oriented format using the following template: "As a [role], I want [feature], so that I can [benefit]"
  3. can be written in different formats and represent an aspect of a user story referred to as confirmation' of the so called "3 C's"
  4. must be written in one of the two following formats: scenario-oriented or rule-oriented

Answer(s): C

Explanation:

The acceptance criteria associated with a user story are the conditions that must be met for the user story to be considered done and to deliver the expected value to the user. They are often written in different formats, such as rule-oriented, scenario-oriented, or table-oriented, depending on the nature and complexity of the user story. They represent an aspect of a user story referred to as confirmation, which is one of the so called "3 C's" of user stories. The other two aspects are card and conversation. Card refers to the concise and informal description of the user story, usually following the template: "As a [role], I want [feature], so that I can [benefit]". Conversation refers to the ongoing dialogue between the stakeholders and the team members to clarify and refine the user story and its acceptance criteria. Therefore, option C is the correct answer.


Reference:

ISTQB® Certified Tester Foundation Level Syllabus v4.01, Section 3.2.2, page 35-36; ISTQB® Glossary v4.02, page 37.



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?

  1. Inspection
  2. Audit
  3. Walkthrough
  4. Informal review

Answer(s): C

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.


Reference:

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



Which of the following statements about the shift-left approach is true?

  1. Shift-left in testing can be implemented only in Agile/DevOps frameworks, as it relies completely on automated testing activities performed within a continuous integration process
  2. Performance testing performed during component testing, is a form of shift-left in testing that avoids planning and executing costly end-to-end testing at the system test level in a production-like environment
  3. Shift-left in testing can be implemented in several ways to find functional defects early in the lifecycle, but it cannot be relied upon to find defects associated with non-functional characteristics
  4. Continuous integration supports shift-left in testing as it can reduce the time between the introduction of a defect and its detection, thereby reducing the cost to fix it

Answer(s): D

Explanation:

This answer is correct because shift-left in testing is an approach that aims to perform testing activities as early as possible in the software development lifecycle, in order to find and fix defects faster and cheaper, and to improve the quality of the software product. Continuous integration is a practice that supports shift-left in testing, as it involves integrating and testing the software components frequently, usually several times a day, using automated tools and processes. Continuous integration can reduce the time between the introduction of a defect and its detection, thereby reducing the cost to fix it and the risk of accumulating defects that could affect the functionality or performance of the software product.


Reference:

ISTQB Foundation Level Syllabus v4.0, Section 3.1.1.3, Section 3.2.1.3



The fact that defects are usually not evenly distributed among the various modules that make up a software application, but rather their distribution tend to reflect the Pareto principle:

  1. is a false myth
  2. is expressed by the testing principle referred to as Tests wear out'
  3. is expressed by the testing principle referred to as 'Defects cluster together'
  4. is expressed by the testing principle referred to as 'Bug prediction'

Answer(s): C

Explanation:

The fact that defects are usually not evenly distributed among the various modules that make up a software application, but rather their distribution tend to reflect the Pareto principle, is expressed by the testing principle referred to as `Defects cluster together'. This principle states that a small number of modules contain most of the defects detected, or that a small number of causes are responsible for most of the defects. This principle can be used to guide the test analysis and design activities, by prioritizing the testing of the most critical or risky modules, or by applying more rigorous test techniques to them. Therefore, option C is the correct answer.


Reference:

ISTQB® Certified Tester Foundation Level Syllabus v4.01, Section 1.2.1, page 11; ISTQB® Glossary v4.02, page 16.



Viewing page 8 of 32
Viewing questions 36 - 40 out of 200 questions


Post your Comments and Discuss iSQI CTFL_Syll_4.0 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!