CTFL4 Free Practice Test

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

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

Correct Answer: D
Reference:ISTQB CTFL Syllabus V4.0, Section 5.4

Which of the following statements about error guessing is true?

1. A. Error guessing is a system that adopts artificial intelligence to predict whether software components are likely to contain defects or not
2. 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
3. C. Error guessing refers to the ability of a system or component to continue normal operation despite the presence of erroneous inputs
4. 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
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. References: ISTQB Glossary of Testing Terms v4.0, ISTQB Foundation Level Syllabus v4.0, Section 2.3.2.5

Which of the following statements about the value of maintaining traceability between the test basis and test work products is not true?

1. A. Traceability can be useful for assessing the impact of a change to a test basis item on the corresponding tests
2. B. Traceability can be useful for determining how many test basis items are covered by the corresponding tests
3. C. Traceability can be useful for determining the most suitable test techniques to be used in a testing project
4. D. Traceability can be useful to support the needs required by the auditing of testing

Correct Answer: C
Traceability is the ability to trace the relationships between the items of the test basis, such as the requirements, the design, the risks, etc., and the test artifacts, such as the test cases, the test results, the defects, etc. Traceability can provide various benefits for the testing process, such as improving the test coverage, the test quality, the test efficiency, and the test communication. However, not all the statements given are true about the value of maintaining traceability between the test basis and test work products. The statement that is not true is option C, which says that test objectives should be the same for all test levels, although the number of tests designed at various levels can vary significantly. This statement is false, because test objectives are the goals or the purposes of testing, which can vary depending on the test level, the test type, the test technique, the test environment, the test stakeholder, etc. Test objectives can be defined in terms of the test basis, the test coverage, the test quality, the test risk, the test cost, the test time, etc. Test objectives should be specific, measurable, achievable, relevant, and time-bound, and they should be aligned with the project objectives and the quality characteristics. Test objectives should not be the same for all test levels, as different test levels have different focuses, scopes, and perspectives of testing, such as component testing, integration testing, system testing, and acceptance testing. The other statements are true about the value of maintaining traceability between the test basis and test work products, such as:
✑ Traceability can be useful for assessing the impact of a change to a test basis item on the corresponding tests: This statement is true, because traceability can help to identify which tests are affected by a change in the test basis, such as a new requirement, a modified design, a revised risk, etc., and to determine the necessary actions to update, re-execute, or re-evaluate the tests. Traceability can also help to estimate the effort, the cost, and the time needed to implement the change and to verify its impact on the software system.
✑ Traceability can be useful for determining how many test basis items are covered by the corresponding tests: This statement is true, because traceability can help to measure the test coverage, which is the degree to which the test basis is exercised by the test cases. Traceability can help to identify which test basis items are covered, partially covered, or not covered by the tests, and to evaluate the adequacy, the completeness, and the effectiveness of the testing process.Traceability can also help to identify the gaps, the overlaps, or the redundancies in the test coverage, and to prioritize, optimize, or improve the test cases.
✑ Traceability can be useful to support the needs required by the auditing of testing:
This statement is true, because traceability can help to provide evidence, documentation, and justification for the testing activities, results, and outcomes. Traceability can help to demonstrate that the testing process follows the standards, the regulations, the policies, and the best practices that are applicable to the software system, the project, or the organization. Traceability can also help to verify that the testing process meets the expectations, the needs, and the satisfaction of the users and the stakeholders. References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:
✑ ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 1.2.2, Testing
Policies, Strategies, and Test Approaches1
✑ ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.1, Test Planning1
✑ ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.2, Test Monitoring and Control1
✑ ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.3, Test Analysis and Design1
✑ ISTQB® Glossary of Testing Terms v4.0, Traceability, Test Basis, Test Artifact, Test Objective, Test Level, Test Coverage, Test Quality, Test Risk, Test Cost, Test Time2

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

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

Correct Answer: C
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."

The following state transition diagram describes the functionality involved in a system using fingerprint and password authentication to log onto a system.

How many distinct states of the system are visible in the above diagram?

1. A. 1
2. B. 2
3. C. 3
4. D. 4

Correct Answer: C
The state transition diagram provided shows three distinct states:
✑ Waiting for fingerprint
✑ Waiting for PIN
✑ Valid PIN/ask menu selection
Each state represents a different stage in the system's operation, with transitions based on user actions and system responses.