Download Exam ISTQB-CTFL Practice Test Questions with 100% Verified Answers [Q64-Q84]

Q64. Which of the following statements BEST describes how test cases are derived from a use case?

Test cases are derived based on non-functional requirements such as usability

Test cases are created using white-box test techniques to execute scenarios of use cases

Test cases are derived based on pair testing between a user and a tester to find defects

Test cases are designed to cover various user behaviors, including basic, exceptional or alternative and error behaviors associated with human users or systems

Q65. Which ONE of the following elements is TYPICALLY used to guide testing during exploratory testing?

A test charter that defines the testing objectives for the test session.

A comprehensive specification that must be fully available before testing begins.

A detailed test script that prescribes all the steps to be performed.

A predefined test case that must be executed exactly as documented.

Q66. Which of the following BEST describes exploratory testing?

Exploratory testing is a suitable test technique which may replace both black-box and white-box test techniques

Exploratory testing is a valid and useful black-box test technique since it focuses on test cases related to the architecture and design of a system

Exploratory testing requires both solid specifications and much project time available for test execution

Exploratory testing may be used within defined time periods, during which the tester may follow a test charter as a guide

Q67. Given the following review types and review characteristics:
a. Pair review
b. Walkthrough
c. Technical review
d. Inspection
1. Formal
2. Informal
3. Purposes include evaluating the quality of the work product under review and generating new ideas (e.g., brainstorming solutions)
4. Purposes include Improving the software product and training the review participants Which of the following BEST matches the review type with the review characteristic?

a-1. b-4, c-3. d-2

a-4, b-3. c-2. d-1

a-2, b-3, c-4, d-1

a-2, b-4, c-3. d-1

Q68. 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?

The final estimate is between 22 person hours and 38 person hours

The final estimate is exactly 30 person hours because the technique uses the initial most likely estimate as the final estimate

The final estimate is between 6 person hours and 54 person hours

The final estimate is exactly 30 person hours because the technique uses the arithmetic mean of the three initial estimates as the final estimate

Q69. For each test case to be executed, the following table specifies its dependencies and the required configuration of the test environment for running such test case:

Assume that C0NF1 is the initial configuration of the test environment Based on this assumption, which of the following is a test execution schedule that is compatible with the specified dependencies and allows minimising the number of switches between the different configurations of the test environment^

TC4, TC3, TC2, TC1, TC5.

TCI, TC5, TC4, TC3, TC2

TC4, TC3, TC2, TC5, TC1.

TC4, TC1, TC5, TC2, TC3

Q70. As the last stage of a test cycle of an embedded device, you are performing exploratory testing. You observed that some character. (A, X andZ)sent via a serial port to the device do not get registered on the device whereas they should be. You suspect that this could be due to a wrong configuration of the “bit parity” parameter.
Which of the following items of an incident report would you beUNABLEto write down based on this information?

Expected result

Test case identifier

Test setup details

Actual result

Q71. For each of the test cases to be executed, the following table specifies the priority order and dependencies on other test cases

Which of the following test execution schedules is compatible with the logical dependencies and allows executing the test cases in priority order?

TC4, TC3, TC2, TC6, TC5. TC1

TC4, TC6, TC3, TC2, TC5, TC1

TC3, TC5, TC6, TC1, TC4, TC3

TC4, TC3, TC2, TC6, TC1, TC5

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

Traceability can be useful for assessing the impact of a change to a test basis item on the corresponding tests

Traceability can be useful for determining how many test basis items are covered by the corresponding tests

Traceability can be useful for determining the most suitable test techniques to be used in a testing project

Traceability can be useful to support the needs required by the auditing of testing

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

Q73. The following chart represents metrics related to testing of a project that was competed. Indicate what is represented by tie lines A, B and the axes X.Y

A)

B)

C)

D)

Option A

Option B

Option C

Option D

Q74. Which of the following are valid testing principles?
I) Exhaustive testing is in general impossible.
II) Exhaustive testing should be executed for code intended to be reused.
III) Testing may guarantee that a program is correct.
IV) Testing cannot guarantee that a program is correct.
V) Defects cluster together in certain areas of the product.

I, IV, V

II,Iv

I, V

I, Ill

Q75. Which TWO of the following are benefits of continuous integration?
I. Allows earlier detection and easier root cause analysis of integration problems and conflicting changes.
II. Removes the need for manual test analysis, design and execution.
Hi. Removes the dependency on automated regression packs when integrating larger systems, or components.
iv. Gives the development team regular feedback on whether the code is working.
Select the correct answer:

i and iv

i and ii

i and iii

iii and iv

Q76. Which ONE of the following options CORRECTLY describes one of the seven principles of the testing process?

The objective of testing is to implement exhaustive testing and execute as many test cases as possible.

Exhaustive testing can only be carried out using behavior-based techniques.

It is impossible to test all possible combinations of inputs and preconditions of a system.

Automated testing enables exhaustive testing.

Q77. Which ONE of the following options BEST describes black-box test techniques?

Black-box testing techniques are based on experience with the test object without knowing the internal structure.

In black-box testing techniques, test cases are created based on the software’s implementation.

Black-box testing techniques are based on analyzing the test object’s specified and implied behavior without knowledge of its internal data structure.

Black-box testing techniques involve analyzing the specified behavior of the test object without knowledge of its internal structure.

Q78. Which of the following statements about TDD, BDD and ATDD is TRUE?

Refactonng is a practice that is an integral part of TDD and is applied both to tests and to code wntten to satisfy those tests.

ATDD is a black-box test design technique that is applicable exclusively at acceptance test level.

BDD is a developer practice where business stakeholders are not usually involved as the tests are directly written at unit/component test level.

ATDD is the practice of running the automated acceptance tests as part of a continuous integration process.

Q79. In maintenance testing, what is the relationship between impact analysis and regression testing?

Impact analysis requires a regression testing for only the tests that have detected faults in previous SW release

There is no relationship between impact analysis and regression testing.

Impact analysis requires a regression testing for all program elements which were newly integrated (new functionalities).

The impact analysis is used to evaluate the amount of regression testing to be performed.

Q80. An Incident Management tool implements the following defect states; Open, Assigned, Solved, Closed Consider the following defect report:
Id T000561
Test Object “Warehouse Management’ application
Tester name; John Bishop
Date: 10th. April 2010
Test Case MRT558I
Status OPEN
Severity Serious
Priority
Problem- After inputting the Total Quantity item = 450 in the SV034 screen, the system shows an unexpected Error message=47 Correction:
Developer name:
Closing date:
Which of the following is a valid criticism of this report?

The Priority, the Correction description and the Developer name are missing

The version of the application is missing

There is no link to the applicable requirement (traceability)

The description is not highlighting the source of the problem

A valid criticism of this report is that the version of the application is missing. The version of the application is an important piece of information that should be included in a defect report, as it helps to identify which release or build of the software product contains the defect. The version of the application can also help to reproduce and debug the defect, as different versions may have different behaviors or features. The other options are not valid criticisms of this report. The priority, the correction description and the developer name are not missing, but rather not applicable for this report. The priority is a measure of how urgently a defect needs to be fixed, which can be assigned by the project manager or the defect tracking system, not by the tester who reports the defect. The correction description and the developer name are information that are added after the defect has been resolved, not when it has been reported. There is no link to the applicable requirement (traceability) is not a valid criticism of this report, because traceability is not a mandatory attribute of a defect report, but rather an optional one.Traceability is a relationship between two or more entities (such as requirements, test cases, defects, etc.) that shows how they are related or dependent on each other. Traceability can help to verify that the requirements are met by the test cases and defects, but it is not essential for reporting a defect. The description is not highlighting the source of the problem is not a valid criticism of this report, because highlighting the source of the problem is not a responsibility of the tester who reports the defect, but rather of the developer who fixes the defect. The description should provide enough information to describe what happened when the defect occurred, such as input values, expected results, actual results, error messages, screenshots, etc., but it does not need to explain why or how it happened.
Verified References: A Study Guide to the ISTQB® Foundation Level 2018 Syllabus – Springer, page 140.

Q81. A virtual service emulating a real third-party service and the automated test scripts (aimed at testing the system under test) that interact with that service, are test work products that are typically created during:

Test monitoring and control

Test implementation

Test design

Test analysis

Q82. Which of the following lists factors That contribute to PROJECT risks?

skill and staff shortages; problems in defining the right requirements, contractual issues.

skill and staff shortages; software does not perform its intended functions; problems in defining the right requirements.

problems in defining the right requirements; contractual issues; poor software quality characteristics.

poor software quality characteristics; software does not perform its intended functions.

Project risks are the uncertainties or threats that may affect the project objectives, such as scope, schedule, cost, and quality. According to the ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, some of the factors that contribute to project risks are:
* Skill and staff shortages: This factor refers to the lack of adequate or qualified human resources to perform the project tasks. This may result in delays, errors, rework, or low productivity.
* Problems in defining the right requirements: This factor refers to the difficulties or ambiguities in eliciting, analyzing, specifying, validating, or managing the requirements of the project. This may result in misalignment, inconsistencies, gaps, or changes in the requirements, affecting the project scope and quality.
* Contractual issues: This factor refers to the challenges or disputes that may arise from the contractual agreements between the project parties, such as clients, suppliers, vendors, or subcontractors. This may result in legal, financial, or ethical risks, affecting the project delivery and satisfaction.
The other options are not correct because they list factors that contribute to PRODUCT risks, not project risks.
Product risks are the uncertainties or threats that may affect the quality or functionality of the software product or system. Some of the factors that contribute to product risks are:
* Poor software quality characteristics: This factor refers to the lack of adherence or compliance to the quality attributes or criteria of the software product or system, such as reliability, usability, security, performance, or maintainability. This may result in defects, failures, or dissatisfaction of the users or stakeholders.
* Software does not perform its intended functions: This factor refers to the deviation or discrepancy between the expected and actual behavior or output of the software product or system. This may result in errors, faults, or malfunctions of the software product or system.
References = ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, Chapter 1: Fundamentals of Testing, Section 1.5: Risks and Testing, Pages 14-16.

Q83. Mark the correct sentences:
* Defects are a result of environmental conditions and are also referred to as “Failures”
* A human mistake may produce a defect
* A system mil totally fail to operate correctly when a failure exists in it
* When a defect exists in a system it may result in a failure
* Defects occur only as a result of technology changes

II, IV

I, II

IV, V

II, III, IV

* 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.
References:
* 1: ISTQB Glossary of Testing Terms 4.0, 2023, available at ISTQB) and ASTQB).

Q84. Which of the following lists factors That contribute to PROJECT risks?

skill and staff shortages; problems in defining the right requirements, contractual issues.

skill and staff shortages; software does not perform its intended functions; problems in defining the right requirements.

problems in defining the right requirements; contractual issues; poor software quality characteristics.

poor software quality characteristics; software does not perform its intended functions.

Project risks are the uncertainties or threats that may affect the project objectives, such as scope, schedule, cost, and quality. According to the ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, some of the factors that contribute to project risks are:
* Skill and staff shortages: This factor refers to the lack of adequate or qualified human resources to perform the project tasks. This may result in delays, errors, rework, or low productivity.
* Problems in defining the right requirements: This factor refers to the difficulties or ambiguities in eliciting, analyzing, specifying, validating, or managing the requirements of the project. This may result in misalignment, inconsistencies, gaps, or changes in the requirements, affecting the project scope and quality.
* Contractual issues: This factor refers to the challenges or disputes that may arise from the contractual agreements between the project parties, such as clients, suppliers, vendors, or subcontractors. This may result in legal, financial, or ethical risks, affecting the project delivery and satisfaction.
The other options are not correct because they list factors that contribute to PRODUCT risks, not project risks.
Product risks are the uncertainties or threats that may affect the quality or functionality of the software product or system. Some of the factors that contribute to product risks are:
* Poor software quality characteristics: This factor refers to the lack of adherence or compliance to the quality attributes or criteria of the software product or system, such as reliability, usability, security, performance, or maintainability. This may result in defects, failures, or dissatisfaction of the users or stakeholders.
* Software does not perform its intended functions: This factor refers to the deviation or discrepancy between the expected and actual behavior or output of the software product or system. This may result
* in errors, faults, or malfunctions of the software product or system.
References = ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, Chapter 1: Fundamentals of Testing, Section 1.5: Risks and Testing, Pages 14-16.

Leave a Reply Cancel reply