ISTQB ISTQB-CTFL Real Exam Questions Guaranteed Updated Dump from PracticeMaterial [Q225-Q245]

NO.225 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

NO.226 Which of the following statements describes regression testing?
I. Retesting of a fixed defect
II. Testing of an already tested program
III. Testing of new functionality in a program
IV. Regression testing applies only to functional testing
V Tests that do not nave to be repeatable, because They are only used once

II, IV, V

I, III, IV

II

I, IV

NO.227 Which of the following statements is CORRECT?

Test cases are made up of input values, expected results and actual results developed to cover test objectives

Test cases describe items or events to test that are derived from the test basis during the test analysis activity

Test cases are sequences of actions for test execution specified during the test implementation activity D. Test cases are derived during the test design activity to cover test objectives or test conditions

NO.228 Which statement about use case testing is true?

The lest cases are designed to find defects in the data flew.

The test cases are designed to be used by real users, not by professional testers

The test cases are always designed by customers or end users.

The test cases are designed to find defects in the process flow.

NO.229 What is typically NOT included in a test progress report?

Information about test obstacles during a test period

Statistics on the success of each tester in finding bugs

Changed risks within the test period

Test status in relation to defined test metrics (including exit criteria)

NO.230 Given the following state model of sales order software:
* PLACED -> IN PRODUCTION
* IN PRODUCTION -> CANCELLED
* IN PRODUCTION -> SHIPPED
* SHIPPED -> INVOICED
* INVOICED -> CANCELLED
* CANCELLED -> PLACED
Which of the following sequences of transitions provides the highest level of transition coverage for the model (assuming you can start in any state)?

IN PRODUCTION -> CANCELLED -> PLACED -> IN PRODUCTION -> CANCELLED -> PLACED

IN PRODUCTION -> SHIPPED -> INVOICED -> CANCELLED -> PLACED -> IN PRODUCTION

PLACED -> IN PRODUCTION -> SHIPPED -> CANCELLED -> PLACED

PLACED -> CANCELLED -> PLACED -> CANCELLED -> PLACED -> IN PRODUCTION -> CANCELLED

NO.231 For withdrawing money tram an Automated Teller Machine (ATM), the following conditions are required:
– The bank card is valid
– The PIN code is correct
– Money is available in the user’s account
The following are some possible interactions between the user and the ATM:
– The entered card is invalid The card is rejected
– The PIN code is wrong The ATM asks for another PIN code
– The requested amount is more than available in the user’s account: The ATM asks for another amount
– The requested amount is available in the user’s account The ATM dispenses the money Which test design technique should be used to cover all possible combinations of the in put conditions?

Use case based testing

Decision table

Boundary value analysis

Equivalence class partitioning

A decision table is a technique that should be used to cover all possible combinations of input conditions for withdrawing money from an Automated Teller Machine (ATM). A decision table shows combinations of inputs and/or stimuli (causes) with their associated outputs and/or actions (effects). A decision table consists of four quadrants: conditions (inputs), actions (outputs), condition entries (values) and action entries (results). A decision table can be used to test components that have multiple inputs and outputs that depend on logical combinations of conditions. For example, for testing the ATM, we can identify three input conditions: the bank card is valid, the PIN code is correct, and money is available in the user’s account. We can also identify four output actions: the card is rejected, the ATM asks for another PIN code, the ATM asks for another amount, and the ATM dispenses the money. A decision table can show all possible combinations of these conditions and actions in a systematic way.
Use case based testing is not a technique that can cover all possible combinations of input conditions for withdrawing money from an ATM. Use case based testing is a technique that verifies that a software product or system meets its specified requirements or user stories by executing realistic scenarios or workflows. Use case based testing can be used to test components that have complex or dynamic interactions with users or other systems. For example, for testing the ATM, we can identify several use cases, such as withdraw money, check balance, transfer money, etc.Each use case can have one or more scenarios that describe the steps and outcomes of the interaction. However, use case based testing may not cover all possible combinations of input conditions, as some scenarios may be omitted or overlooked.
Boundary value analysis is not a technique that can cover all possible combinations of input conditions for withdrawing money from an ATM. 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 test components that have input values that can be divided into partitions of equivalent data. For example, for testing the ATM, we can identify boundary values for the input amount, such as the minimum and maximum amount allowed by the system or the user’s account. However, boundary value analysis may not cover all possible combinations of input conditions, as some conditions may not have boundary values or may not be related to input values.
Equivalence class partitioning is not a technique that can cover all possible combinations of input conditions for withdrawing money from an ATM. Equivalence class 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 class partitioning can be used to test components that have input values that can be divided into partitions of equivalent data. For example, for testing the ATM, we can identify equivalence partitions for the input amount, such as valid amount (within the range allowed by the system and the user’s account) and invalid amount (outside the range allowed by the system or the user’s account). However, equivalence class partitioning may not cover all possible combinations of input conditions, as some conditions may not be related to input values or may have more than two partitions. Verified References: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus – Springer], Chapter 4, page 34-46.

NO.232 Which of the following does MOT describe a reason why testing is necessary?

The customer decided that 100% branch coverage shall be achieved

The acquisition of test automation tools was based on the assumption that it will be used m all projects

For avionics and pharmaceutical systems software testing is mandated by standards

The risks associated with delivering the system are far higher than the cost of testing

Testing is necessary for various reasons, such as:
* To detect defects and failures that may affect the quality, performance, reliability or security of a software product or system
* To verify that a software product or system meets its specified requirements, expectations and standards
* To validate that a software product or system fulfills its intended purpose and satisfies its stakeholders’ needs
* To provide information and feedback about the status and risks of a software product or system
* To comply with regulations or contractual obligations that mandate testing for certain types of software products or systems The following statements describe some reasons why testing is necessary:
* A) The customer decided that 100% branch coverage shall be achieved. This is a reason why testing is necessary, as it reflects a contractual obligation or a quality standard that requires testing to measure and achieve a certain level of code coverage.
* C) For avionics and pharmaceutical systems software testing is mandated by standards. This is a reason why testing is necessary, as it reflects a regulation or a compliance requirement that mandates testing for certain types of software products or systems that have high safety or security risks.
* D) The risks associated with delivering the system are far higher than the cost of testing. This is a reason why testing is necessary, as it reflects a risk-based approach that considers testing as an investment to reduce the probability andimpact of potential failures or defects. The following statement does not describe a reason why testing is necessary:
* B) The acquisition of test automation tools was based on the assumption that it will be used m all projects. This is not a reason why testing is necessary, as it reflects a business decision or a resource allocation that does not justify the need or purpose of testing. Test automation tools are not always suitable or beneficial for all projects, and testing can be performed with or without test automation tools. Verified References: [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus – Springer], Chapter 1, page 5-6.

NO.233 Why should you choose a test technique?

Because you need to match the way you test to the content of the product under test

Because of the time constraints that usually accompany a test project

Because this way you cover the full scope of the product’s functionality

Because choosing a test technique is a common practice in software testing

NO.234 Which of the following is NOT a common objective of testing?

Finding defects in the software

Preventing defects

Debugging the software to find the reason for defects

Providing information on the status of the system

NO.235 Consider the following examples of risks identified in different software development projects:
[I]. The contrast color ratio for both normal text and large text of a website does not comply with the applicable accessibility guidelines, making it difficult for many users to read the content on the pages
[II]. A development vendor fails to deliver their software system on time, causing significant delays to system integration testing activities that have been planned as part of a development project for a system of systems
[III]. People in the test team do not have sufficient skills to automate tests at the test levels required by the test automation strategy which does not allow production of an effective regression test suite
[IV]. In a web application, data from untrusted sources is not subject to proper input validation, making the application vulnerable to several security attacks Which of the following statements is true?

[I] and [III] are product risks; [II] and [IV] are project risks

[I] and [IV] are product risks. [II] and [III] are project risks

[II], [III] and [IV] are product risks; [I] is a project risk

[IV] is a product risk; [I]. [II] and [III] are project risks

NO.236 Which of the following statements contradicts the general principles of testing?

Most defects are found in a small subset of a system’s modules.

If new defects are to be found we should run the same test set more often.

Testing is better if it starts at the beginning of a project.

How testing is done, is based on the situation in a particular project.

NO.237 Given the following priorities and dependencies for these test cases:

Which of the following test execution schedules BEST takes into account the priorities and technical and logical dependencies?

TC1 – TC3 – TC2 – TC4 – TC6 – TC5

TC3 – TC4 – TC2 – TC6 – TC1 – TC5

TC1 – TC3 – TC2 – TC4 – TC5 – TC6

TC2 – TC4 – TC1 – TC3 – TC5 – TC6

NO.238 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).

NO.239 Which one of the following statements IS NOT a valid objective of testing?

To build confidence in the level of quality of the test object.

To find all defects in a product, ensuring the product is defect free.

To find failures and defects

To evaluate work products such as requirements, user stories, design, and code.

NO.240 Consider the following table, which contains information about test cases from the test management system:

Which ONE of the following options organizes the test cases based on the statement coverage strategy, while considering practical constraints?

{TC 20; TC 30; TC 10; TC 40; TC 50; TC 70; TC 60; TC 80; TC 90}

{TC 10; TC 30; TC 20; TC 60; TC 40; TC 80; TC 90; TC 50; TC 70}

{TC 80; TC 70; TC 50; TC 60; TC 20; TC 30; TC 10; TC 40; TC 90}

{TC 60; TC 80; TC 40; TC 90; TC 50; TC 10; TC 70; TC 30; TC 20}

NO.241 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

NO.242 Which of the following BEST describes a benefit of test automation?

More subjective assessment

Reduction in repetitive manual work

Availability of the test automation tool vendor

Negligible effort to maintain the test assets generated by the tool

NO.243 Your organization’s test strategy states that it is desirable to use more than one method for estimating test effort. You are responsible for estimating test effort for the next project. Based on historical data, the development-to-test effort ratio is 5:3.
The initial estimate for the development effort is 450 person-days.
Which ONE of the following options corresponds to the estimated test effort using the ratio-based method?

750 person-days

180 person-days

720 person-days

270 person-days

NO.244 Which of the following isNOTan experience-based technique?

Boundary value analysis.

Error guessing

Exploratory testing

Fault attack

NO.245 Which of the following is a typical potential risk of using test automation tools?

Reduced feedback times regarding software quality compared to manual testing.

Reduced test execution limes compared to manual testing.

Reduced repeatability and consistency of tests compared to manual testing

Underestimation of effort required to maintain test scripts.

Leave a Reply Cancel reply