Practice Free CTFL_SYLL_4.0 Exam Online Questions
Question #41
Which of the following statements is CORRECT about the value added by a tester to release planning?
- A . The tester estimates the testing effort for individual iterations
- B . The tester assesses the testability of the user stories
- C . The tester breaks down user stories into smaller testing tasks
- D . The tester writes acceptance criteria
Correct Answer: B
B
Explanation:
During release planning, a tester adds value by assessing the testability of user stories. This involves evaluating whether the user stories are clear, concise, and testable. The tester ensures that the acceptance criteria are well-defined and that the stories can be effectively tested within the given timeframe.
Reference: ISTQB CTFL Syllabus V4.0, Section 5.1.2 on the tester’s contribution to iteration and release planning, which includes assessing the testability of user stories.
B
Explanation:
During release planning, a tester adds value by assessing the testability of user stories. This involves evaluating whether the user stories are clear, concise, and testable. The tester ensures that the acceptance criteria are well-defined and that the stories can be effectively tested within the given timeframe.
Reference: ISTQB CTFL Syllabus V4.0, Section 5.1.2 on the tester’s contribution to iteration and release planning, which includes assessing the testability of user stories.
Question #42
A company wants to reward each of its salespeople with an annual bonus that represents the sum of all the bonuses accumulated for every single sale made by that salesperson. The bonus for a single sale can take on the following four values: 3%, 5%, 7% and 10% (the percentage refers to the amount of the single sale).
These values are determined on the basis of the type of customer (classified as "Basic" or "Premium") to which such sale was made, and on the amount of such sale classified into the following three groups G1, G2 and G3:
• [G1]: less than 300 euros
• [G2]: between 300 and 2000 euros
• [G3]: greater than 2000 euros
Which of the following is the minimum number of test cases needed to cover the full decision table associated with this scenario?
- A . 12
- B . 6
- C . 4
- D . 3
Correct Answer: B
B
Explanation:
The minimum number of test cases needed to cover the full decision table associated with this scenario is 6. This is because the decision table has 4 conditions (type of customer and amount of sale) and 4 actions (bonus percentage). The conditions have 2 possible values each (Basic or Premium, and G1, G2 or G3), so the total number of combinations is 2 x 2 x 2 x 2 = 16. However, not all combinations are valid, as some of them are contradictory or impossible. For example, a sale cannot be both less than 300 euros and greater than 2000 euros at the same time. Therefore, we need to eliminate the invalid combinations and keep only the valid ones.
The valid combinations are:
Type of customer
Amount of sale
Bonus percentage
Basic
G1
3%
Basic
G2
5%
Basic
G3
7%
Premium
G1
5%
Premium
G2
7%
Premium
G3
10%
These 6 combinations cover all the possible values of the conditions and actions, and they are the minimum number of test cases needed to cover the full decision table.
Reference: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents,
B
Explanation:
The minimum number of test cases needed to cover the full decision table associated with this scenario is 6. This is because the decision table has 4 conditions (type of customer and amount of sale) and 4 actions (bonus percentage). The conditions have 2 possible values each (Basic or Premium, and G1, G2 or G3), so the total number of combinations is 2 x 2 x 2 x 2 = 16. However, not all combinations are valid, as some of them are contradictory or impossible. For example, a sale cannot be both less than 300 euros and greater than 2000 euros at the same time. Therefore, we need to eliminate the invalid combinations and keep only the valid ones.
The valid combinations are:
Type of customer
Amount of sale
Bonus percentage
Basic
G1
3%
Basic
G2
5%
Basic
G3
7%
Premium
G1
5%
Premium
G2
7%
Premium
G3
10%
These 6 combinations cover all the possible values of the conditions and actions, and they are the minimum number of test cases needed to cover the full decision table.
Reference: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents,
Question #43
Which of the following statements is true?
- A . Unlike functional testing, non-functional testing can only be applied to conventional systems, not artificial intelligence-based system
- B . Functional testing focuses on what the system is supposed to do, while white-box testing focuses on how well the system does what it is supposed to do
- C . Functional testing can be applied to all test levels, while non-functional testing can be applied only to system and acceptance test levels
- D . Black-box test techniques and experience-based test techniques may be applicable to both functional testing and non-functional testing
Correct Answer: D
D
Explanation:
Both black-box test techniques and experience-based test techniques can be applied to functional and non-functional testing. Functional testing focuses on what the system does, while non-functional testing examines how the system performs. These techniques provide flexible and effective methods for assessing various aspects of the system.
Reference: ISTQB® CTFL Syllabus 4.0, Chapter 4.4, page 42: Experience-Based Testing Techniques
D
Explanation:
Both black-box test techniques and experience-based test techniques can be applied to functional and non-functional testing. Functional testing focuses on what the system does, while non-functional testing examines how the system performs. These techniques provide flexible and effective methods for assessing various aspects of the system.
Reference: ISTQB® CTFL Syllabus 4.0, Chapter 4.4, page 42: Experience-Based Testing Techniques
Question #44
An e-commerce site accepts credit cards for processing the payment. The payment processing form has a field for the amount of money to be deducted. The minimum amount of money that can be processed is $10. The credit cards have a limit of $5,000 (Five Thousand). Assume that only integers can be accepted as inputs.
Which of the following set of boundary values you will choose for EFFICIENT testing for the amount of money that can be spent?
- A . 9,5001
- B . 10,5000
- C . 9,10,11,4999,5000,5001
- D . 9,10,5000,5001
Correct Answer: C
C
Explanation:
Boundary value analysis involves testing at the boundaries between partitions.
The most efficient boundary values to test are those at the edge of the input ranges:
Just below the minimum value (9)
At the minimum value (10)
Just above the minimum value (11)
Just below the maximum value (4999)
At the maximum value (5000)
Just above the maximum value (5001)
Testing these values ensures that the program handles the boundaries correctly, covering both valid and invalid input scenarios.
Top of Form
Bottom of Form
C
Explanation:
Boundary value analysis involves testing at the boundaries between partitions.
The most efficient boundary values to test are those at the edge of the input ranges:
Just below the minimum value (9)
At the minimum value (10)
Just above the minimum value (11)
Just below the maximum value (4999)
At the maximum value (5000)
Just above the maximum value (5001)
Testing these values ensures that the program handles the boundaries correctly, covering both valid and invalid input scenarios.
Top of Form
Bottom of Form
Question #45
Which of the following answers describes a reason for adopting experience-based testing techniques?
- A . Experience-based test techniques provide more systematic coverage criteria than black-box and white-box test techniques
- B . Experience-based test techniques completely rely on the tester’s past experience for designing test cases
- C . Experience-based test techniques allow designing test cases that are usually easier to reproduce than those designed with black-box and white-box test techniques
- D . Experience-based test techniques tend to find defects that may be difficult to find with black-box and white-box test techniques and are often useful to complement these more systematic techniques
Correct Answer: D
D
Explanation:
Experience-based testing techniques are adopted for several reasons, most importantly because they can identify defects that might be missed by more systematic approaches like black-box and white-box testing. While systematic techniques follow predefined procedures and cover specific criteria, experience-based techniques leverage the tester’s knowledge, intuition, and experience, which can be especially effective in uncovering subtle and complex issues.
Experience-based testing techniques include methods such as error guessing and exploratory testing. These methods rely on the tester’s background and intuition to predict where defects might be located and how the system might fail. These techniques are particularly useful in situations where the requirements and specifications are incomplete or ambiguous, and where creative and ad-hoc approaches can provide significant value.
Reference: The official ISTQB® CTFL syllabus emphasizes that experience-based techniques can find defects that more systematic techniques might miss, which makes them valuable complements to other testing methods.
D
Explanation:
Experience-based testing techniques are adopted for several reasons, most importantly because they can identify defects that might be missed by more systematic approaches like black-box and white-box testing. While systematic techniques follow predefined procedures and cover specific criteria, experience-based techniques leverage the tester’s knowledge, intuition, and experience, which can be especially effective in uncovering subtle and complex issues.
Experience-based testing techniques include methods such as error guessing and exploratory testing. These methods rely on the tester’s background and intuition to predict where defects might be located and how the system might fail. These techniques are particularly useful in situations where the requirements and specifications are incomplete or ambiguous, and where creative and ad-hoc approaches can provide significant value.
Reference: The official ISTQB® CTFL syllabus emphasizes that experience-based techniques can find defects that more systematic techniques might miss, which makes them valuable complements to other testing methods.
Question #45
Which of the following answers describes a reason for adopting experience-based testing techniques?
- A . Experience-based test techniques provide more systematic coverage criteria than black-box and white-box test techniques
- B . Experience-based test techniques completely rely on the tester’s past experience for designing test cases
- C . Experience-based test techniques allow designing test cases that are usually easier to reproduce than those designed with black-box and white-box test techniques
- D . Experience-based test techniques tend to find defects that may be difficult to find with black-box and white-box test techniques and are often useful to complement these more systematic techniques
Correct Answer: D
D
Explanation:
Experience-based testing techniques are adopted for several reasons, most importantly because they can identify defects that might be missed by more systematic approaches like black-box and white-box testing. While systematic techniques follow predefined procedures and cover specific criteria, experience-based techniques leverage the tester’s knowledge, intuition, and experience, which can be especially effective in uncovering subtle and complex issues.
Experience-based testing techniques include methods such as error guessing and exploratory testing. These methods rely on the tester’s background and intuition to predict where defects might be located and how the system might fail. These techniques are particularly useful in situations where the requirements and specifications are incomplete or ambiguous, and where creative and ad-hoc approaches can provide significant value.
Reference: The official ISTQB® CTFL syllabus emphasizes that experience-based techniques can find defects that more systematic techniques might miss, which makes them valuable complements to other testing methods.
D
Explanation:
Experience-based testing techniques are adopted for several reasons, most importantly because they can identify defects that might be missed by more systematic approaches like black-box and white-box testing. While systematic techniques follow predefined procedures and cover specific criteria, experience-based techniques leverage the tester’s knowledge, intuition, and experience, which can be especially effective in uncovering subtle and complex issues.
Experience-based testing techniques include methods such as error guessing and exploratory testing. These methods rely on the tester’s background and intuition to predict where defects might be located and how the system might fail. These techniques are particularly useful in situations where the requirements and specifications are incomplete or ambiguous, and where creative and ad-hoc approaches can provide significant value.
Reference: The official ISTQB® CTFL syllabus emphasizes that experience-based techniques can find defects that more systematic techniques might miss, which makes them valuable complements to other testing methods.
Question #47
Which of the following statements about retrospectives is true?
- A . Only developers and testers should be involved in retrospectives, as involving people in other roles is very likely to prevent developers and testers from having open and constructive discussions that really help identify process improvements
- B . Retrospectives can be very effective in identifying process improvements and can also be very efficient and cost-effective especially since, unlike reviews, they do not require any follow-up activities
- C . On Agile projects, well-conducted retrospectives at the end of each iteration can help the team reduce and sometimes even eliminate the need for daily stand-up meetings
- D . During retrospectives, in addition to identifying relevant process improvements, participants should also consider how to implement these improvements and retain them based on the context of the project, such as the software development lifecycle
Correct Answer: D
D
Explanation:
Retrospectives are critical for continuous improvement in Agile projects. They involve not only identifying process improvements but also planning their implementation and ensuring they are retained, considering the specific context of the project, such as the software development lifecycle. This holistic approach ensures that improvements are practical and sustainable.
Reference: ISTQB® CTFL Syllabus 4.0, Chapter 2.1.6, page 26: Retrospectives and Process Improvement
D
Explanation:
Retrospectives are critical for continuous improvement in Agile projects. They involve not only identifying process improvements but also planning their implementation and ensuring they are retained, considering the specific context of the project, such as the software development lifecycle. This holistic approach ensures that improvements are practical and sustainable.
Reference: ISTQB® CTFL Syllabus 4.0, Chapter 2.1.6, page 26: Retrospectives and Process Improvement
Question #48
Which of the following statements about error guessing is true?
- A . Error guessing is a system that adopts artificial intelligence to predict whether software components are likely to contain defects or not
- B . Experienced testers, when applying error guessing, rely on the use of a high-level list of what needs to be tested as a guide to find defects
- C . Error guessing refers to the ability of a system or component to continue normal operation despite the presence of erroneous inputs
- D . Experienced testers, when applying error guessing technique, can anticipate where errors, defects and failures have occurred and target their tests at those issues
Correct Answer: D
D
Explanation:
This answer is correct because error guessing is a test design technique where the experience and intuition of the tester are used to anticipate where errors, defects and failures have occurred or are likely to occur, and to design test cases to expose them. Error guessing can be based on factors such as the complexity of the system or component, the known or suspected weaknesses of the system or component, the previous history of defects, or the common types of errors in the domain or technology. Error guessing can be used as a complementary technique to other more systematic or formal techniques, or when there is insufficient information or time to apply them.
Reference: ISTQB Glossary of Testing Terms v4.0, ISTQB Foundation Level Syllabus v4.0, Section 2.3.2.5
D
Explanation:
This answer is correct because error guessing is a test design technique where the experience and intuition of the tester are used to anticipate where errors, defects and failures have occurred or are likely to occur, and to design test cases to expose them. Error guessing can be based on factors such as the complexity of the system or component, the known or suspected weaknesses of the system or component, the previous history of defects, or the common types of errors in the domain or technology. Error guessing can be used as a complementary technique to other more systematic or formal techniques, or when there is insufficient information or time to apply them.
Reference: ISTQB Glossary of Testing Terms v4.0, ISTQB Foundation Level Syllabus v4.0, Section 2.3.2.5
Question #49
Which of the following issues cannot be identified by static analysis tools?
- A . Very low MTBF (Mean Time Between failure)
- B . Potentially endless loops
- C . Referencing a variable with an undefined value
- D . Security vulnerabilities
Correct Answer: A
A
Explanation:
Static analysis tools are software tools that examine the source code of a program without executing it. They can detect various types of issues, such as syntax errors, coding standards violations, security vulnerabilities, and potential bugs12. However, static analysis tools cannot identify issues that depend on the runtime behavior or performance of the program, such as very low MTBF (Mean Time Between failure)3. MTBF is a measure of the reliability of a system or component. It is calculated by dividing the total operating time by the number of failures. MTBF reflects how often a system or component fails during its expected lifetime. Static analysis tools cannot measure MTBF because they do not run the program or observe its failures. MTBF can only be estimated by dynamic testing, which involves executing the program under various conditions and collecting data on its failures4. Therefore, very low MTBF is an issue that cannot be identified by static analysis tools. The other options, such as potentially endless loops, referencing a variable with an undefined value, and security vulnerabilities, are issues that can be identified by static analysis tools. Static analysis tools can detect potentially endless loops by analyzing the control flow and data flow of the program and checking for conditions that may never become false5. Static analysis tools can detect referencing a variable with an undefined value by checking the scope and initialization of variables and reporting any use of uninitialized variables6. Static analysis tools can detect security vulnerabilities by checking for common patterns of insecure code, such as buffer overflows, SQL injections, cross-site scripting, and weak encryption.
Reference = What Is Static Analysis? Static Code Analysis Tools – Perforce Software, How Static Code Analysis Works | Perforce, Static Code Analysis: Techniques, Top 5 Benefits & 3 Challenges, What is MTBF? Mean Time Between Failures Explained | Perforce, Static analysis tools – Software Testing MCQs – CareerRide, ISTQB_Chapter3 | Quizizz, [Static Code Analysis for Security Vulnerabilities | Perforce].
A
Explanation:
Static analysis tools are software tools that examine the source code of a program without executing it. They can detect various types of issues, such as syntax errors, coding standards violations, security vulnerabilities, and potential bugs12. However, static analysis tools cannot identify issues that depend on the runtime behavior or performance of the program, such as very low MTBF (Mean Time Between failure)3. MTBF is a measure of the reliability of a system or component. It is calculated by dividing the total operating time by the number of failures. MTBF reflects how often a system or component fails during its expected lifetime. Static analysis tools cannot measure MTBF because they do not run the program or observe its failures. MTBF can only be estimated by dynamic testing, which involves executing the program under various conditions and collecting data on its failures4. Therefore, very low MTBF is an issue that cannot be identified by static analysis tools. The other options, such as potentially endless loops, referencing a variable with an undefined value, and security vulnerabilities, are issues that can be identified by static analysis tools. Static analysis tools can detect potentially endless loops by analyzing the control flow and data flow of the program and checking for conditions that may never become false5. Static analysis tools can detect referencing a variable with an undefined value by checking the scope and initialization of variables and reporting any use of uninitialized variables6. Static analysis tools can detect security vulnerabilities by checking for common patterns of insecure code, such as buffer overflows, SQL injections, cross-site scripting, and weak encryption.
Reference = What Is Static Analysis? Static Code Analysis Tools – Perforce Software, How Static Code Analysis Works | Perforce, Static Code Analysis: Techniques, Top 5 Benefits & 3 Challenges, What is MTBF? Mean Time Between Failures Explained | Perforce, Static analysis tools – Software Testing MCQs – CareerRide, ISTQB_Chapter3 | Quizizz, [Static Code Analysis for Security Vulnerabilities | Perforce].