[2026] Valid CTFL_Syll_4.0 test answers & ISQI CTFL_Syll_4.0 exam pdf [Q87-Q105]

The unscripted tests produced by the tester’s experience during the two-hour test session belong to the testing quadrant Q3. The testing quadrants are a classification of testing types based on two dimensions: the test objectives (whether the testing is focused on supporting the team or critiquing the product) and the test basis (whether the testing is based on the technology or the business). The testing quadrants are labeled as Q1, Q2, Q3, and Q4, and each quadrant represents a different testing perspective, such as unit testing, acceptance testing, usability testing, or performance testing. The testing quadrant Q3 corresponds to the testing types that have the objective of critiquing the product from the business perspective, such as exploratory testing, usability testing, user acceptance testing, alpha testing, beta testing, etc. The unscripted tests performed by the tester in the given scenario are examples of exploratory testing and usability testing, as they are based on the tester’s experience, intuition, and learning of the web application, and they focus on some specific usability issues, such as the user interface, the user satisfaction, the user feedback, etc. The other options are incorrect, because:
* The testing quadrant Q1 corresponds to the testing types that have the objective of supporting the team from the technology perspective, such as unit testing, component testing, integration testing, system testing, etc. These testing types are usually performed by developers or testers who have access to the source code, the design, the architecture, or the configuration of the software system, and they aim to verify the functionality, the quality, and the reliability of the software system at different levels of integration.
* The testing quadrant Q2 corresponds to the testing types that have the objective of supporting the team from the business perspective, such as functional testing, acceptance testing, story testing, scenario testing, etc. These testing types are usually performed by testers or customers who have access to the requirements, the specifications, the user stories, or the business processes of the software system, and they aim to validate that the software system meets the expectations and the needs of the users and the stakeholders.
* The testing quadrant Q4 corresponds to the testing types that have the objective of critiquing the product from the technology perspective, such as performance testing, security testing, reliability testing, compatibility testing, etc. These testing types are usually performed by testers or specialists who have access to the tools, the metrics, the standards, or the benchmarks of the software system, and they aim to evaluate the non-functional aspects of the software system, such as the efficiency, the security, the reliability, or the compatibility of the software system under different conditions or environments. References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:
* ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 1.3.1, Testing in Software Development Lifecycles
* ISTQB Glossary of Testing Terms v4.0, Testing Quadrant, Exploratory Testing, Usability Testing, Unit Testing, Component Testing, Integration Testing, SystemTesting, Functional Testing, Acceptance Testing, Story Testing, Scenario Testing, Performance Testing, Security Testing, Reliability Testing, Compatibility Testing

The statement that the shift-left approach can only be implemented with test automation is false. The shift-left approach emphasizes early testing activities in the software development lifecycle to detect and address defects as soon as possible. While test automation can support shift-left practices, it is not the only method.
The shift-left approach can also involve practices such as static analysis, early requirement reviews, and integrating security vulnerability assessments early in the development process.

The unscripted tests produced by the tester’s experience during the two-hour test session belong to the testing quadrant Q3. The testing quadrants are a classification of testing types based on two dimensions: the test objectives (whether the testing is focused on supporting the team or critiquing the product) and the test basis (whether the testing is based on the technology or the business). The testing quadrants are labeled as Q1, Q2, Q3, and Q4, and each quadrant represents a different testing perspective, such as unit testing, acceptance testing, usability testing, or performance testing. The testing quadrant Q3 corresponds to the testing types that have the objective of critiquing the product from the business perspective, such as exploratory testing, usability testing, user acceptance testing, alpha testing, beta testing, etc. The unscripted tests performed by the tester in the given scenario are examples of exploratory testing and usability testing, as they are based on the tester’s experience, intuition, and learning of the web application, and they focus on some specific usability issues, such as the user interface, the user satisfaction, the user feedback, etc. The other options are incorrect, because:
The testing quadrant Q1 corresponds to the testing types that have the objective of supporting the team from the technology perspective, such as unit testing, component testing, integration testing, system testing, etc. These testing types are usually performed by developers or testers who have access to the source code, the design, the architecture, or the configuration of the software system, and they aim to verify the functionality, the quality, and the reliability of the software system at different levels of integration.
The testing quadrant Q2 corresponds to the testing types that have the objective of supporting the team from the business perspective, such as functional testing, acceptance testing, story testing, scenario testing, etc. These testing types are usually performed by testers or customers who have access to the requirements, the specifications, the user stories, or the business processes of the software system, and they aim to validate that the software system meets the expectations and the needs of the users and the stakeholders.
The testing quadrant Q4 corresponds to the testing types that have the objective of critiquing the product from the technology perspective, such as performance testing, security testing, reliability testing, compatibility testing, etc. These testing types are usually performed by testers or specialists who have access to the tools, the metrics, the standards, or the benchmarks of the software system, and they aim to evaluate the non-functional aspects of the software system, such as the efficiency, the security, the reliability, or the compatibility of the software system under different conditions or environments. Reference: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:
ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 1.3.1, Testing in Software Development Lifecycles ISTQB® Glossary of Testing Terms v4.0, Testing Quadrant, Exploratory Testing, Usability Testing, Unit Testing, Component Testing, Integration Testing, System Testing, Functional Testing, Acceptance Testing, Story Testing, Scenario Testing, Performance Testing, Security Testing, Reliability Testing, Compatibility Testing

Error guessing is a testing technique where experienced testers anticipate potential defects based on their knowledge of the application and past experiences. Fault attacks, which involve focusing on areas where defects are likely to occur based on previous failures, are a practical implementation of error guessing.
References:
* ISTQB CTFL Syllabus V4.0, Section 4.4.1 on error guessing and fault attacks, explaining how testers use their experience to anticipate and target likely defects.

Explanation
The correct outcome of a two-value boundary value analysis applied to the password length is the set of test cases represented by option D. Boundary value analysis is a test design technique that focuses on the values at the boundaries of an equivalence partition, such as the minimum and maximum values, or the values just above and below the boundaries. A two-value boundary value analysis uses two values for each boundary, one representing the valid value and one representing the invalid value. For example, if the valid range of values is from 4 to 7, then the two values for the lower boundary are 3 and 4, and the two values for the upper boundary are 7 and 8. The test cases in option D use these values for the password length, while also satisfying the other requirements of the password, such as containing at least one numeric character, one capital letter, and one lowercase letter. The test cases in option D are:
1RhT: a 4-character password that is valid
rSp53: a 5-character password that is valid
3N3e10: a 6-character password that is valid
8sBdby: an 8-character password that is invalid The test cases in the other options are incorrect, because they either use values that are not at the boundaries of the password length, or they do not meet the other requirements of the password. For example, the test cases in option A are:
1xA: a 3-character password that is invalid, but it does not contain a capital letter aB11: a 4-character password that is valid Pq1ZZab: a 7-character password that is valid
7iDD0a1x: an 8-character password that is invalid References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:
ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.2.1, Black-box Test Design Techniques1 ISTQB Glossary of Testing Terms v4.0, Boundary Value Analysis, Equivalence Partition2

Non-functional testing includes testing of both technical and non-technical quality characteristics. Non-functional testing is the process of testing the quality attributes of a system, such as performance, usability, security, reliability, etc. Non-functional testing can be applied at any test level and can use both black-box and white-box test techniques. Non-functional testing can cover both technical aspects, such as response time, throughput, resource consumption, etc., and non-technical aspects, such as user satisfaction, accessibility, compliance, etc. Therefore, option B is the correct answer.

Statement coverage is a structural coverage metric that measures the percentage of executable statements in the source code that are executed by a test suite1. Decision coverage is another structural coverage metric that measures the percentage of decision outcomes (such as branches or conditions) in the source code that are executed by a test suite1. Decision coverage is a stronger metric than statement coverage, because it requires that every possible outcome of each decision is tested, while statement coverage only requires that every statement is executed at least once2. Therefore, if a test suite achieves 100% decision coverage, it also implies that it achieves 100% statement coverage, because every statement in every branch or condition must have been executed. However, the converse is not true: 100% statement coverage does not guarantee 100% decision coverage, because some branches or conditions may have multiple outcomes that are not tested by the test suite2. For example, consider the following pseudocode:
if (x > 0) then print(“Positive”) else print(“Non-positive”) end if
A test suite that executes this code with x = 1 and x = -1 will achieve 100% statement coverage, because both print statements are executed. However, it will not achieve 100% decision coverage, because the condition x
> 0 has only been tested with two outcomes: true and false. The third possible outcome, x = 0, has not been tested by the test suite. Therefore, the test suite may miss a potential bug or error in the condition or the branch.
The other options, such as stale transition coverage, equivalence class coverage, and boundary value coverage, are not guaranteed to be 100% by achieving 100% decision coverage. Stale transition coverage is a structural coverage metric that measures the percentage of transitions between states in a state machine that are executed by a test suite3. Equivalence class coverage is a functional coverage metric that measures the percentage of equivalence classes (or partitions) of input or output values that are tested by a test suite4. Boundary value coverage is another functional coverage metric that measures the percentage of boundary values (or extreme values) of input or output ranges that are tested by a test suite4. These metrics are independent of decision coverage, because they are based on different aspects of the system under test, such as its behavior, functionality, or specification. Therefore, achieving 100% decision coverage does not imply achieving 100% of any of these metrics, and vice versa. References = ISTQB Certified Tester Foundation Level Syllabus v4.0, Test Coverage in Software Testing – Guru99, Structural Coverage Metrics – MATLAB & Simulink – MathWorks India, Test Design Coverage in Software Testing – GeeksforGeeks.

The primary objectives of testing, as outlined in the ISTQB CTFL v4.0 syllabus, include verifying whether specified requirements are met (A), detecting failures and defects (B), and validating that the test object functions as expected (D). However, “finding errors” (C) is not a direct objective. Errors result from human mistakes, but testing primarily identifies defects, which are flaws in the system that cause failures. Testing aims to reveal defects rather than directly identify errors in the code.

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.

Comprehensive and Detailed Explanation From Exact Extract:
This is a classic application of theDecision Table Testingtechnique.
We are combining two conditions:
* Purchase Volume, which has3 equivalence classes:
* 1 to 100 units # 0%
* 101 to 1000 units # 5%
* More than 1000 units # 10%
* Customer Type, which has2 categories:
* Frequent Customer = YES # 5% extra
* Frequent Customer = NO # 0%
This gives:
3 (bulk discount levels) × 2 (frequent customer options) = 6 unique decision rules Each combination of these input conditions defines a separate test scenario with its own outcome.
“Decision table testing is used to identify the different combinations of inputs and their associated outputs.
Each unique combination of input values defines a rule.”
(ISTQB CTFL Syllabus v4.0, Section 4.2.3 – Decision Table Testing, Page 40) Thus,Option D (6 decision rules)is the correct answer.

The question is about marking the correct sentences among the given statements related to defects, failures, and mistakes. According to the ISTQB glossary, the definitions of these terms are1:
Defect: A flaw in a component or system that can cause the component or system to fail to perform its required function, e.g. an incorrect statement or data definition. A defect, if encountered during execution, may cause a failure of the component or system.
Failure: An event in which a component or system does not perform a required function within specified limits.
Mistake: A human action that produces an incorrect result.
Therefore, out of the five given statements, only two are correct, namely:
A human mistake may produce a defect: This is true, as a mistake is a source or cause of a defect, e.g. a programmer may make a mistake in writing a code statement, which results in a defect in the software component.
When a defect exists in a system it may result in a failure: This is true, as a defect is a potential or actual cause of a failure, e.g. a defect in the software component may cause the system to fail to perform a required function when the defect is encountered during execution.
The other three statements are incorrect, namely:
Defects are a result of environmental conditions and are also referred to as “Failures”: This is false, as defects are not a result of environmental conditions, but of mistakes or other factors, and defects are not the same as failures, but rather the causes of failures.
A system will totally fail to operate correctly when a failure exists in it: This is false, as a system may not necessarily fail completely or stop operating when a failure occurs, but may continue to operate with reduced functionality or performance, or with incorrect results.
Defects occur only as a result of technology changes: This is false, as defects can occur due to various reasons, not only technology changes, such as human mistakes, design flaws, requirement changes, hardware failures, etc.
Reference:
1: ISTQB Glossary of Testing Terms 4.0, 2023, available at ISTQB) and ASTQB).

In the context of software testing roles, tasks typically performed by someone in a testing role include evaluating the test basis and test object, creating test completion reports, and assessing the testability of the test object. These tasks are directly related to ensuring the quality and effectiveness of the software testing process.
* Evaluate test basis and test object: This involves reviewing and analyzing the documents and artifacts that are used as the basis for testing. This is a fundamental task for testers to understand what needs to be tested and to ensure that the test objects are adequately covered by the test cases.
* Create test completion report: This is part of the test closure activities. Testers are responsible for summarizing the testing activities, outcomes, and lessons learned, which are compiled into a test completion report. This report is crucial for stakeholders to understand the test results and make informed decisions.
* Assess testability of test object: This task involves evaluating how easily a test object (such as a piece of software) can be tested. This includes considering aspects such as the availability of test data, the ability to isolate the object for testing, and the clarity of the requirements. Testers often perform this assessment to identify potential challenges and mitigate them before testing begins.
On the other hand:
* Define test environment requirements: While testers may provide input on the test environment, the primary responsibility for defining and setting up the test environment usually falls to roles such as system administrators or infrastructure specialists. They ensure that the necessary hardware, software, and network configurations are in place for testing to proceed. This task is less likely to be the sole responsibility of a tester.

In the ISTQB terminology:
* A defect (also known as a bug or fault) is an issue in the code that can cause a failure.
* A failure is the observable incorrect behavior or output of the software due to a defect.
In this scenario, the memory leak is the defect in the application code that causes the application not to release dynamically allocated memory properly. The observable effect of this defect, which is the slowdown in response time, is considered a failure because it is the manifestation of the defect that prevents the application from meeting its performance requirements.

In the V-model project described in the question, the tester can identify the following based on the provided information:
* Expected result (II): The requirements specification clearly states that the app should only ask for access permissions to the camera and photos stored on the device during and after installation. This expected behavior is defined by the requirements.
* Actual result (III): The tester observes that the app also requests access to all contacts on the device, which deviates from the expected result. This actual observation can be recorded accurately.
Given these details, the tester can specify the expected result (II) and the actual result (III) in the defect report.
However, without more information, the tester cannot determine the test environment (I), the test level (IV), or the root cause (V).
References:
* ISTQB CTFL Syllabus V4.0, Section 5.5 on Defect Reporting
* Typical contents of a defect report as mentioned in the syllabus include the expected result and the actual result observed during testing.

The statement that refers to good testing practice to be applied regardless of the chosen software development model is option D, which says that involvement of testers in work product reviews should occur as early as possible to take advantage of the early testing principle. Work product reviews are static testing techniques, in which the work products of the software development process, such as the requirements, the design, the code, the test cases, etc., are examined by one or more reviewers, with or without the author, to identify defects, violations, or improvements. Involvement of testers in work product reviews can provide various benefits for the testing process, such as improving the test quality, the test efficiency, and the test communication. The early testing principle states that testing activities should start as early as possible in the software development lifecycle, and should be performed iteratively and continuously throughout the lifecycle. Applying the early testing principle can help to prevent, detect, and remove defects at an early stage, when they are easier, cheaper, and faster to fix, as well as to reduce the risk, the cost, and the time of the testing process. The other options are not good testing practices to be applied regardless of the chosen software development model, but rather specific testing practices that may or may not be applicable or beneficial for testing, depending on the context and the objectives of the testing activities, such as:
Tests should be written in executable format before the code is written and should act as executable specifications that drive coding: This is a specific testing practice that is associated with test-driven development, which is an approach to software development and testing, in which the developers write automated unit tests before writing the source code, and then refactor the code until the tests pass. Test-driven development can help to improve the quality, the design, and the maintainability of the code, as well as to provide fast feedback and guidance for the developers. However, test-driven development is not a good testing practice to be applied regardless of the chosen software development model, as it may not be feasible, suitable, or effective for testing in some contexts or situations, such as when the requirements are unclear, unstable, or complex, when the test automation tools or skills are not available or adequate, when the testing objectives or levels are not aligned with the unit testing, etc.
Test levels should be defined such that the exit criteria of one level are part of the entry criteria for the next level: This is a specific testing practice that is associated with sequential software development models, such as the waterfall model, the V-model, or the W-model, in which the software development and testing activities are performed in a linear and sequential order, with well-defined phases, deliverables, and dependencies. Test levels are the stages of testing that correspond to the levels of integration of the software system, such as component testing, integration testing, system testing, and acceptance testing. Test levels should have clear and measurable entry criteria and exit criteria, which are the conditions that must be met before starting or finishing a test level. In sequential software development models, the exit criteria of one test level are usually part of the entry criteria for the next test level, to ensure that the software system is ready and stable for the next level of testing. However, this is not a good testing practice to be applied regardless of the chosen software development model, as it may not be relevant, flexible, or efficient for testing in some contexts or situations, such as when the software development and testing activities are performed in an iterative and incremental order, with frequent changes, feedback, and adaptations, as in agile software development models, such as Scrum, Kanban, or XP, when the test levels are not clearly defined or distinguished, or when the test levels are performed in parallel or concurrently, etc.
Test objectives should be the same for all test levels, although the number of tests designed at various levels can vary significantly: This is a specific testing practice that is associated with uniform software development models, such as the spiral model, the incremental model, or the prototyping model, in which the software development and testing activities are performed in a cyclical and repetitive manner, with similar phases, deliverables, and processes. 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. In uniform software development models, the test objectives may be the same for all test levels, as the testing process is repeated for each cycle or iteration, with similar focus, scope, and perspective of testing. However, this is not a good testing practice to be applied regardless of the chosen software development model, as it may not be appropriate, realistic, or effective for testing in some contexts or situations, such as when the software development and testing activities are performed in a hierarchical and modular manner, with different phases, deliverables, and dependencies, as in sequential software development models, such as the waterfall model, the V-model, or the W-model, when the test objectives vary according to the test levels, such as component testing, integration testing, system testing, and acceptance testing, or when the test objectives change according to the feedback, the learning, or the adaptation of the testing process, as in agile software development models, such as Scrum, Kanban, or XP, etc. Reference: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:
ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 1.1.1, Testing and the Software Development Lifecycle1 ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 1.2.1, Testing Principles1 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 1.3.1, Testing in Software Development Lifecycles1 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® Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.4, Test Implementation1 ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.5, Test Execution1 ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 2.1.6, Test Closure1 ISTQB® Glossary of Testing Terms v4.0, Work Product Review, Static Testing, Early Testing, Test-driven Development, Test Level, Entry Criterion, Exit Criterion, Test Objective, Test Basis, Test Coverage, Test Quality, Test Risk, Test Cost, Test Time2

Scenario-oriented acceptance criteria describe how a system should behave in a specific situation or scenario.
These criteria are typically written from the end-user’s perspective and focus on user interactions and system responses. Option D fits this description as it outlines a specific scenario where a user is already logged in and describes the expected behavior when the user navigates to a particular page, which is to show the report of the last test run. This type of criterion ensures that the system meets user expectations in that scenario.

A test plan serves multiple purposes, such as defining the scope, approach, resources, and schedule of the testing activities. It also helps in communicating important information and managing stakeholder expectations. In agile projects, test plans might be concise to align with agile principles of simplicity and flexibility. A one-page test plan can effectively communicate broad activities and strategic decisions, such as not writing detailed test cases due to the project’s agile nature. This approach ensures that essential information is conveyed without unnecessary documentation overhead, adhering to the agile manifesto’s value of “working software over comprehensive documentation”.

Statement coverage strategyprioritizestest cases with higher statement coverage first, whileresolving dependenciesbefore execution.
* TC60 (7%)has thehighest coveragebutdepends on REQ 1, so it should be executedafter its dependency is covered.
* TC80 (6%)depends onREQ 2, so it should be prioritizedafter TC40 (REQ 2).
* TC40 (5%)andTC90 (5%)should be executed early.
* Lower coverage test cases (TC10, TC70, TC30, TC20) should come last.
Thus, the correct order is{TC 60; TC 80; TC 40; TC 90; TC 50; TC 10; TC 70; TC 30; TC 20} (D).

During iteration planning, testers provide input on risk analysis, testability, and the feasibility of test automation.Participating in risk analysis (B)helps identify areas needing more extensive testing.
* (A) is incorrectbecause the test strategy is usually set at a higher level (project or release level).
* (C) is incorrectas release planning is broader than iteration planning.
* (D) is incorrectsince writing user stories is mainly the responsibility of theproduct owner, though testers contribute to defining acceptance criteria.
Risk-based test prioritizationensures testing efforts are aligned with business needs and software risks.