ISTQB-CTFL Dumps PDF New [2024] Ultimate Study Guide [Q42-Q61]

QUESTION 42
A Test Manager conducts risk assessment for a project. One of the identified risks is: The sub-contractor may fail to meet his commitment”. If this risk materializes. it will lead to delay in completion of testing required for the current cycle.
Which of the following sentences correctly describes the risk?

It is a product risk since any risk associated with development timeline is a product risk.

It is no longer a risk for the Test Manager since an independent party (the sub-contractor) is now managing it

It is a object risk since successful completion of the object depends on successful and timely completion of the tests

It is a product risk since default on part of the sub-contractor may lead to delay in release of the product

A product risk is a risk that affects the quality or timeliness of the software product being developed or tested1. Product risks are related to the requirements, design, implementation, verification, and maintenance of the software product2.
The risk of the sub-contractor failing to meet his commitment is a product risk, as it could cause a delay in the completion of the testing required for the current cycle, which in turn could affect the release date of the product. The release date is an important aspect of the product quality, as it reflects the customer satisfaction and the market competitiveness of the product3.
The other options are not correct because:
A) It is not true that any risk associated with development timeline is a product risk. Some risks could be project risks, which are risks that affect the management or control of the software project, such as budget, resources, schedule, or communication1. For example, a risk of losing a key project stakeholder is a project risk, not a product risk.
B) It is not true that the risk is no longer a risk for the Test Manager since an independent party is managing it. The Test Manager is still responsible for ensuring that the testing activities are completed according to the test plan and the quality objectives4. The Test Manager should monitor and control the sub-contractor’s performance and communicate with him regularly to identify and mitigate any potential issues or deviations5.
C) It is not clear what is meant by “object” in this option, but it could be interpreted as the software system under test or the test object6. In any case, the risk is not an object risk, as it does not affect the successful completion of the object, but rather the successful completion of the testing of the object. An object risk could be a risk that affects the functionality, reliability, usability, efficiency, maintainability, or portability of the software system under test2. For example, a risk of the software system having a high complexity or a low testability is an object risk, not a product risk.
Reference =
1 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 97
2 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 98
3 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 99
4 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 100
5 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 101
6 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 102

QUESTION 43
Which of the following can be considered a VALID exit criterion?
I Estimates of defect density or reliability measures.
II. The completion and publication of an exhaustive Test Report.
III. Accuracy measures, such as code, functionality or risk coverage.
IV Residual risks such as lack of code coverage in certain areas.

I, III, IV

I, II, III

III, IV

II, III, IV

QUESTION 44
The following incident report that was generated during test of a web application.
What would you suggest asthe most importantreport improvement?
Defect detected date: 15 8.2010
Defect detected by: Joe Smith
Test level System test
Test case: Area 5/TC 98
Build version: 2011-16.2
Defect description After having filled out all required fields in screen 1, t click ENTER to continue to screen2 Nothing happens, no system response at all.

Add information about which web browser was used

Add information about which developer should fix the bug

Add the time stamp when the incident happened

Add an impact analysis

QUESTION 45
Given the following review process main activities and specific review activities:
a.Planning
b.Initiate review
c.Issue communication and analysis
d.Fixing and reporting
1.Creating defect reports
2.Estimating effort and timeframe
3.Recording updated status of defects
4.Selecting the people to participate
5.Distributing the work product and other material
6.Evaluating the review findings
Which of the following BEST matches the review process main activities with the appropriate specific review activities?

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

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

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

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

QUESTION 46
A test engineer finds a defect while testing. After the developer has fixed the defect, the test engineer decides to re-run a complete section of the tests. Which of the following is correct?

The test engineer should re-run the tests, in order to ensure that new defects have not been introduced by the fix.

The lest engineer should not re-run the tests, as they have already been run, and results recorded.

The test engineer should not re-run the tests, they should be part of the developer tests.

The test engineer should re-run the tests, because the defect shows that the test cases need to be updated.

QUESTION 47
A software module to be used in a mission critical application incorporates an algorithm for secure transmission of data.
Which review type is most appropriate to ensure high quality and technical correctness of the algorithm?

Walkthrough

Informal Review

Technical Review

Management Review

QUESTION 48
Which of the following is the BEST reason for selecting a particular type of software development lifecycle model?

The project manager’s preference

Tester skill level with the software development lifecycle model

The project team’s overall familiarity with the model

The type of product being developed

QUESTION 49
A program got 100% decision coverage in a test. Which of the following statements is then guaranteed to be true?

Every executable statement Is covered.

Every output equivalence class has been tested.

Every input equivalence class has been tested.

The “dead” code has not been covered.

If a program got 100% decision coverage in a test, then it is guaranteed that every executable statement is covered. Decision coverage (also known as branch coverage) is a type of structural coverage (also known as white-box coverage) that measures how many decision outcomes have been exercised by a test suite. A decision outcome is a possible result of a decision point (such as an if-then-else statement) in a program’s code. Decision coverage requires that each decision point has both true and false outcomes executed at least once by a test suite. Decision coverage implies statement coverage, which is another type of structural coverage that measures how many executable statements have been executed by a test suite. Statement coverage requires that each executable statement is executed at least once by a test suite. Therefore, if a program got 100% decision coverage in a test, then it also got 100% statement coverage in a test, which means that every executable statement is covered. The other options are not guaranteed to be true if a program got
100% decision coverage in a test. Every output equivalence class has been tested and every input equivalence class has been tested are not guaranteed to be true if a program got 100% decision coverage in a test, because equivalence classes are based on functional requirements or specifications, not on code structure or logic.
Equivalence classes are used in specification-based testing (also known as black-box testing), which is a type of testing that does not consider the internal structure or implementation of the system under test. Decision coverage is used in structure-based testing (also known as white-box testing), which is a type of testing that considers the internal structure or implementation of the system under test. Therefore, achieving 100% decision coverage does not imply achieving 100% equivalence class coverage. The “dead” code has not been covered is not guaranteed to be true if a program got 100% decision coverage in a test, because dead code (also known as unreachable code) is code that can never be executed due to logical errors or design flaws.
Dead code can reduce readability and maintainability of the code, as well as increasecomplexity and size.
Decision coverage does not account for dead code, as it only considers the decision outcomes that are possible to execute. Therefore, achieving 100% decision coverage does not imply that the dead code has not been covered. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus – Springer, page 36.

QUESTION 50
Which of the following options cover the test types performed during typical system testing phase:
I Usability
II Requirements based scenarios
III Testing parts of the code in isolation
IV Correct order of parameters in API calls

I, Ill

I. II

II. IV

III. IV

QUESTION 51
Which of the following are the phases of the ISTQB fundamental test process?

Test planning and control, Test analysis and design, Test implementation and execution, Evaluating ex t criteria and reporting. Test closure activities

Test planning, Test analysis and design. Test implementation and control. Checking test coverage and reporting, Test closure activities

Test planning and control, Test specification and design. Test implementation and execution, Evaluating test coverage and reporting, Retesting and regression testing, Test closure activities

Test planning. Test specification and design. Test implementation and execution. Evaluating exit criteria and reporting. Retesting and test closure activities

The ISTQB fundamental test process consists of five main phases, as described in the ISTQB Foundation Level Syllabus, Version 4.0, 2018, Section 2.2, page 15:
* Test planning and control: This phase involves defining the test objectives, scope, strategy, resources, schedule, risks, and metrics, as well as monitoring and controlling the test activities and results throughout the test process.
* Test analysis and design: This phase involves analyzing the test basis (such as requirements, specifications, or user stories) to identify test conditions (such as features, functions, or scenarios) that need to be tested, and designing test cases and test procedures (such as inputs, expected outcomes, and execution steps) to cover the test conditions. This phase also involves evaluating the testability of the test basis and the test items (such as software or system components), and selecting and implementing test techniques (such as equivalence partitioning, boundary value analysis, or state transition testing) to achieve the test objectives and optimize the test coverage and efficiency.
* Test implementation and execution: This phase involves preparing the test environment (such as hardware, software, data, or tools) and testware (such as test cases, test procedures, test data, or test scripts) for test execution, and executing the test procedures or scripts according to the test plan and schedule. This phase also involves logging the outcome of test execution, comparing the actual results with the expected results, and reporting any discrepancies as incidents (such as defects, errors, or failures).
* Evaluating exit criteria and reporting: This phase involves checking if the planned test activities have been completed and the exit criteria (such as quality, coverage, or risk levels) have been met, and reporting the test results and outcomes to the stakeholders. This phase also involves making recommendations for the release or acceptance decision based on the test results and outcomes, and identifying any residual risks (such as known defects or untested areas) that need to be addressed or mitigated.
* Test closure activities: This phase involves finalizing and archiving the testware and test environment for future reuse, and evaluating the test process and the test project against the test objectives and the test plan. This phase also involves identifying any lessons learned and best practices, and communicating the findings and suggestions for improvement to the relevant parties.
References = ISTQB Certified Tester Foundation Level Syllabus, Version 4.0, 2018, Section 2.2, page 15; ISTQB Glossary of Testing Terms, Version 4.0, 2018, pages 37-38; ISTQB CTFL 4.0 – Sample Exam – Answers, Version 1.1, 2023, Question 88, page 32.

QUESTION 52
Software was found lo take much more time than the stated requirement of less than one second to save a file. Upon investigation it was found that there was an unnecessary check inside a loop which was slowing down the file-save operation. The software not being able to meet the desired response time is an example of

It is not a defect

Defect

Error

Failure

QUESTION 53
You need to test the login page of a web site. The page contains fields for user name and password. Which test design techniques are most appropriate for this case?

Decision table testing, state transition testing.

Equivalence partitioning, Boundary value analysis.

Exploratory testing, statement coverage.

Decision coverage, fault attack.

Equivalence partitioning and boundary value analysis are test design techniques that are most appropriate for testing the login page of a web site. The page contains fields for user name and password, which are input values that can be divided into partitions of equivalent data. Equivalence partitioning is a technique that divides the input data and output results of a software component into partitions of equivalent data. Each partition should contain data that is treated in the same way by the component.Equivalence partitioning can be used to reduce the number of test cases by selecting one representative value from each partition. Boundary value analysis is a technique that tests boundary values between partitions of equivalent data. Boundary values are values at the edge of an equivalence partition or at the smallest incremental distance on either side of an edge. Boundary value analysis can be used to detect defects caused by incorrect handling of boundary conditions. For example, for testing the user name field, we can identify two equivalence partitions: valid user name (existing and correct) and invalid user name (non-existing or incorrect). The boundary values for these partitions are the minimum and maximum length of user name allowed by the system.
Decision table testing and state transition testing are not suitable for testing the login page of a web site, as they are more applicable for testing components that have multiple inputs and outputs that depend on logical combinations of conditions or events. Decision table testing is a technique that shows combinations of inputs and/or stimuli (causes) with their associated outputs and/or actions (effects). State transition testing is a technique that models how a system transitions from one state to another depending on events or conditions.
Exploratory testing and statement coverage are not suitable for testing the login page of a web site, as they are more applicable for testing components that require learning, creativity and intuition or structural analysis.
Exploratory testing is an approach to testing that emphasizes learning, test design and test execution at the same time. Exploratory testing relies on the tester’s skills, creativity and intuition to explore the software under test and discover defects. Statement coverage is a type of structural testing that measures how many statements in a program have been executed by a test suite. Statement coverage can be used to assess the adequacy or completeness of a test suite.
Decision coverage and fault attack are not suitable for testing the login page of a web site, as they are more applicable for testing components that have complex logic or potential errors. Decision coverage is a type of structural testing that measures how many decision outcomes in a program have been executed by a test suite.
Decision coverage can be used to assess the adequacy or completeness of a test suite. Fault attack is a type of functional testing that deliberately introduces faults into a system in order to provoke failures or errors.
Verified References: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus – Springer], Chapter 4, page 34-46; Chapter 5, page 47-48.

QUESTION 54
During component testing of a program if 100% decision coverage is achieved, which of the following coverage criteria is also guaranteed to be 100%?

100% Stale transition coverage

100% Equivalence class coverage

100% Boundary value coverage

100% Statement coverage

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 thepercentage 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.

QUESTION 55
In what way do Configuration Management effects testing?

Without proper configuration management, test planning cannot proceed.

Proper configuration management ensures that testers can uniquely identity the tested item

Configuration management is important for developers, not for testers

There is very little influence of configuration management practices on the test project.

QUESTION 56
Which of the following BEST matches the descriptions with the different categories of test techniques?
1.Test cases are based on the test basis which may include the requirements, use cases and user stories
2.Test cases are based on the test basis which may include the software architecture or code
3.Test cases can show deviations from the requirements
4.These test techniques are applicable to both functional and non-functional testing
5.Tests are based on knowledge of developers, users and other stakeholders Black – Black-box test techniques White * White-box test techniques Experience – Experience-based test techniques

Black -1,3.4 White – 2 Experience – 5

Black – 2, 3 White -1 Experience – 4, 5

Black -1,2 White – 3, 4 Experience – 5

Black – 2, 3 White -1,5 Experience – 4

QUESTION 57
A software calculates the annual car tax using three inputs:
– E; the emission level of the vehicle
– P: the power of the vehicle
-T the type of the vehicle
The input value for P can be integer positive values between 15 and 350.
Which of the following answers contains a correct list of a boundary values for the P input?

14,351

14,15,350,351

15,350

5.175.500

QUESTION 58
Which of the following statements about re-testing and regression testing are TRUE?
I Re-testing should be performed after a defect is fixed.
II Regression testing should always be performed after a defect is fixed.
III. Re-testing and regression testing may be performed at any test level.
IV Regression testing may include functional, non-functional and structural testing.
V. Re-testing should be included in the debugging activity.

I, III. Iv

II, v

I, Ill

II. IV, V

The following statements about re-testing and regression testing are true:
* I) Re-testing should be performed after a defect is fixed. Re-testing is a type of testing that verifies that a defect has been successfully resolved by executing a test case that previously failed due to that defect.
Re-testing should be performed after a defect is fixed and delivered to ensure that it does not cause any new failures or side effects.
* III) Re-testing and regression testing may be performed at any test level. Re-testing and regression testing are not limited to a specific test level, but can be applied at any level depending on the context and objectives. For example, re-testing and regression testing can be performed at unit level, integration level, system level or acceptance level.
* IV) Regression testing may include functional, non-functional and structural testing. Regression testing is a type of testing that verifies that previously tested software still performs correctly after changes.
Regression testing may include various types of testing depending on the scope and purpose of the changes. For example, regression testing may include functional testing to check if the software meets its requirements, non-functional testing to check if the software meets its quality attributes, or structural testing to check if the software meets its design or code standards. The following statement about re-testing and regression testing is false:
* II) Regression testing should always be performed after a defect is fixed. Regression testing is not always necessary after a defect is fixed, as some defects may have a low impact or low likelihood of affecting other parts of the software. Regression testing should be performed after a defect is fixed only
* if there is a risk of introducing new defects or causing existing defects due to the changes made to fix the defect. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus – Springer, Chapter 2, page 19; Chapter 4, page 45.

QUESTION 59
Which of the following would be the LEAST likely to be used as the basis for a test exit criteria?

Test schedules

Cost of testing performed so far

Confidence of testers in tested code

Number of unfixed defects

QUESTION 60
In what way do Configuration Management effects testing?

Without proper configuration management, test planning cannot proceed.

Proper configuration management ensures that testers can uniquely identity the tested item

Configuration management is important for developers, not for testers

There is very little influence of configuration management practices on the test project.

QUESTION 61
Which of the following BEST explains a drawback of independent testing?

Having the business organization participate as an independent test team can hurt the overall testing effort since business participants are often not trained nor experienced in testing

Due to their differing backgrounds and perspectives, an independent test team may discover defects which the developers did not uncover

An independent test team may be isolated from the rest of the development and project team

An independent test team may possess specializations in specific test types such as usability or security which detract from the overall effectiveness of the test team

Leave a Reply Cancel reply