Free Dec-2024 UPDATED ISTQB ISTQB-CTFL Certification Exam Dumps is Online
ISTQB Exam 2024 ISTQB-CTFL Dumps Updated Questions
NEW QUESTION # 87
Which of the following is the most important task of a typical test leader?
- A. To automate tests.
- B. To set up the test environment.
- C. To coordinate the test strategy with project managers.
- D. To prepare and acquire test data.
Answer: C
Explanation:
The most important task of a typical test leader is to coordinate the test strategy with project managers. The test strategy is a high-level document that defines the general approach and objectives of testing for a project or an organization. The test leader is responsible for defining, documenting, communicating, and implementing the test strategy in alignment with the project goals and constraints. The test leader also needs to coordinate with project managers and other stakeholders to ensure that the test strategy is feasible, effective, and efficient. The other options are not the most important tasks of a typical test leader. To automate tests is a task of a test automation engineer or a test automation specialist. To prepare and acquire test data is a task of a test analyst or a test engineer. To set up the test environment is a task of a test environment manager or a test environment specialist. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 13.
NEW QUESTION # 88
A software company decides to invest in reviews of various types. The thought process they have is that each artifact needs to be reviewed using only one of the review methods depending on the criticality of the artifact.
- A. The thought process is correct. The whole company should decide or the review method based on their CMM level.
- B. The thought process is incorrect. The whole company should adopt same standard for review of all artifacts.
- C. The thought process is correct. It wastes time to review same artifact using efferent review methods
- D. The thought process is incorrect. Same artifact can be reviewed using different review methods
Answer: D
Explanation:
The thought process of the software company is incorrect, because it assumes that each artifact can be reviewed using only one review method, and that the review method depends solely on the criticality of the artifact. This is a simplistic and rigid approach that does not consider the benefits and limitations of different review methods, the context and purpose of the review, and the feedback and improvement opportunities that can be gained from multiple reviews. According to the CTFL 4.0 Syllabus, the selection of review methods should be based on several factors, such as the type and level of detail of the artifact, the availability and competence of the reviewers, the time and budget constraints, the expected defects and risks, and the desired outcomes and quality criteria. Moreover, the same artifact can be reviewed using different review methods at different stages of the development lifecycle, to ensure that the artifact meets the changing requirements, standards, and expectations of the stakeholders.For example, a requirement specification can be reviewed using an informal review method, such as a walkthrough, to get an initial feedback from the users and developers, and then using a formal review method, such as an inspection, to verify the completeness, correctness, and consistency of the specification. Therefore, the software company should adopt a more flexible and context-sensitive approach to selecting and applying review methods for different artifacts, rather than following a fixed and arbitrary rule. References = CTFL 4.0 Syllabus, Section 3.2.1, page 31-32; Section
3.2.2, page 33-34; Section 3.2.3, page 35-36.
NEW QUESTION # 89
The following incident report that was generated during test of a web application.
What would you suggest as the most important report 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 screen 2 Nothing happens, no system response at all.
- A. Add information about which web browser was used
- B. Add an impact analysis
- C. Add information about which developer should fix the bug
- D. Add the time stamp when the incident happened
Answer: A
Explanation:
The most important report improvement for the given incident report would be to add information about which web browser was used when the defect was detected. This information is relevant for reproducing and debugging the defect, as different web browsers may have different behaviors or compatibility issues with the web application. The other options are less important or irrelevant for the incident report. The developer who should fix the bug can be assigned by the project manager or the defect tracking system, not by the tester who reports the defect. The time stamp when the incident happened is not very useful, as it does not indicate the cause or the frequency of the defect. The impact analysis is not part of the incident report, but rather of the risk assessment or prioritization process. Verified Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 140.
NEW QUESTION # 90
Confirmation testing is performed after:
- A. the execution of an automated regression test suite to confirm the absence of false positives in the test results
- B. a defect is fixed and after other tests do not find any side-effect introduced in the software as a result of such fix
- C. a defect is fixed, and if such testing is successful then the regression tests that are relevant for such fix can be executed
- D. a failed test, and aims to run that test again to confirm that the same behavior still occurs and thus appears to be reproducible
Answer: C
Explanation:
Confirmation testing is performed after a defect is fixed, and if such testing is successful then the regression tests that are relevant for such fix can be executed. Confirmation testing, also known as re-testing, is the process of verifying that a defect has been resolved by running the test case that originally detected the defect.
Confirmation testing is usually done before regression testing, which is the process of verifying that no new defects have been introduced in the software as a result of changes or fixes. Therefore, option D is the correct answer.
References: ISTQB Certified Tester Foundation Level Syllabus v4.01, Section 2.4.1, page 28; ISTQB Glossary v4.02, page 15.
NEW QUESTION # 91
The following requirement is given "Set X to be the sum of Y and Z".
All the following four implementations have bugs.
Which one of the following bugs can be caught by Static Analysis?
- A. int x = 1.
int y = 2.
int y = 3.
X = y=z; - B. int x = 1.
Int y = 2.
Int z = 3.
Z = x +y - C. int y = 2
Int z = 3.
Y = z+y - D. int x = 1.
int y = 2.
int z = 3.
X = z-y
Answer: A
Explanation:
Static analysis is a technique that analyzes the source code or other software artifacts without executing them. Static analysis can detect defects such as syntax errors, coding standards violations, potential security vulnerabilities, or logical flaws. Static analysis can catch the bug in the first implementation, as it contains two syntax errors: the variable y is declared twice, and the assignment statement X = y=z is invalid. Static analysis cannot catch the bugs in the other three implementations, as they are logical errors that do not violate any syntax rules, but produce incorrect results. Verified Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 3, page 25-26.
NEW QUESTION # 92
Consider the following statements about risk-based testing.
I) Risk-based testing has the objective to reduce the level of protect risks.
II) Tests should be prioritized to find tie critical detects as early as possible.
III) Non-testing activities may also help to reduce risk
IV) Risks have to bereassessedon a regular basis.
V) The project stakeholders can give useful input to determine the risks
- A. II, IIIIVandVarecorrect. I isfalse.
- B. I III IV and V are true. II is false.
- C. C. I, II and IV are true.IIIand V are false.
- D. II, Ill and V are true.1antsIv are false.
Answer: A
Explanation:
The following statements about risk-based testing are correct:
* II) Tests should be prioritized to find tie critical detects as early as possible. Risk-based testing involves prioritizing tests based on risk level, which reflects both the likelihood and impact of defects or failures.
Tests with higher risk level should be executed earlier than tests with lower risk level, in order to find and fix critical defects as soon as possible.
* III) Non-testing activities may also help to reduce risk. Risk-based testing does not only involve testing activities, but also other activities that can help mitigate risks, such as reviews, inspections, audits,
* simulations or prototyping.
NEW QUESTION # 93
Which of the following statements about how different types of test tools support testers is true?
- A. The support offered by a test data preparation tool is often leveraged by testers to run automated regression test suites
- B. The support offered by a performance testing tool is often leveraged by testers to run load tests
- C. The support offered by a continuous integration tool is often leveraged by testers to automatically generate test cases from a model
- D. The support offered by a bug prediction tool is often used by testers to track the bugs they found
Answer: B
Explanation:
The support offered by a performance testing tool is often leveraged by testers to run load tests, which are tests that simulate a large number of concurrent users or transactions on the system under test, in order to measure its performance, reliability, and scalability. Performance testing tools can help testers to generate realistic workloads, monitor system behavior, collect and analyze performance metrics, and identify performance bottlenecks. The other statements are false, because:
* A test data preparation tool is a tool that helps testers to create, manage, and manipulate test data, which are the inputs and outputs of test cases. Test data preparation tools are not directly related to running automated regression test suites, which are test suites that verify that the system still works as expected after changes or modifications. Regression test suites are usually executed by test execution tools, which are tools that can automatically run test cases and compare actual results with expected results.
* A bug prediction tool is a tool that uses machine learning or statistical techniques to predict the likelihood of defects in a software system, based on various factors such as code complexity, code churn, code coverage, code smells, etc. Bug prediction tools are not used by testers to track the bugs they found, which are the actual defects that have been detected and reported during testing. Bugs are
* usually tracked by defect management tools, which are tools that help testers to record, monitor, analyze, and resolve defects.
* A continuous integration tool is a tool that enables the integration of code changes from multiple developers into a shared repository, and the execution of automated builds and tests, in order to ensure the quality and consistency of the software system. Continuous integration tools are not used by testers to automatically generate test cases from a model, which are test cases that are derived from a representation of the system under test, such as a state diagram, a decision table, a use case, etc. Test cases can be automatically generated by test design tools, which are tools that support the implementation and maintenance of test cases, based on test design specifications or test models.
References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:
* ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 3.4.1, Types of Test Tools
* ISTQB Glossary of Testing Terms v4.0, Performance Testing Tool, Test Data Preparation Tool, Bug Prediction Tool, Continuous Integration Tool, Test Execution Tool, Defect Management Tool, Test Design Tool
NEW QUESTION # 94
You are performing the role of tester on an Agile project. Which of the following tasks would be your responsibility?
i. Understanding, implementing, and updating the test strategy.
II. Ensuring the proper use of testing tools.
Hi. Coaching other team members in the relevant aspects of testing.
iv. Actively collaborating with developers and business stakeholders to clarify requirements, especially in terms of testability, consistency, and completeness.
v. Participating proactively in team retrospective meeting, suggesting and implementing improvements.
Select the correct answer:
- A. i, iii and v
- B. i, iv and v
- C. iii. iv and v
- D. i, ii and iii
Answer: B
Explanation:
In an Agile project, a tester's responsibilities include understanding, implementing, and updating the test strategy (i), actively collaborating with developers and business stakeholders to clarify requirements, especially in terms of testability, consistency, and completeness (iv), and participating proactively in team retrospective meetings, suggesting and implementing improvements (v). These activities ensure that testing is integrated into the development process, promoting continuous feedback and improvement. The ISTQB CTFL syllabus underlines the collaborative nature of Agile testing and the tester's role in contributing to the team's overall quality goals.
References: ISTQB CTFL Syllabus, Section on Agile Testing Practices.
NEW QUESTION # 95
Which of the following BEST describes a test summary report for executive-level employees
- A. The report is detailed and includes specific information on defects and trends
- B. The report is high-level and includes a status summary of defects by priority or budget
- C. The report is high-level and includes specific information on defects and trends
- D. The report is detailed and includes a status summary of defects by priority or budget
Answer: B
Explanation:
For executive-level employees, a test summary report should be concise and focus on high-level information.
It typically includes a summary of defects categorized by priority or budget. Executives are generally interested in the overall status and the impact on critical business objectives rather than detailed technical information. The report should provide an overview of the most important aspects of testing, such as key issues, test progress, and any risks or concerns that could affect project outcomes.References:
* ISTQB Certified Tester Foundation Level Syllabus v4.0, Section 5.3.1.
NEW QUESTION # 96
Which of the following is an example of black-box dynamic testing?
- A. Functional Testing
- B. Checking memory leaks for a program by executing it
- C. Code inspection
- D. Coverage analysis
Answer: A
Explanation:
Functional testing is an example of black-box dynamic testing. Black-box testing (also known as specification-based testing) is a type of testing that does not consider the internal structure or implementation of the system under test, but rather its external behavior or functionality. Dynamic testing is a type of testing that involves executing the system under test with various inputs and observing its outputs. Functional testing is a type of black-box dynamic testing that verifies that the system under test performs its intended functions according to its requirements or specifications. Functional testing can be performed at various levels and scopes depending on the objectives and criteria of testing. The other options are not examples of black-box dynamic testing. Code inspection is an example of white-box static testing. White-box testing (also known as structure-based testing) is a type of testing that considers the internal structure or implementation of the system under test. Static testing is a type of testing that does not involve executing the system under test, but rather analyzing it for defects, errors, or violations of standards. Code inspection is a type of white-box static testing that involves examining the source code of the system under test for quality, readability, maintainability, etc.
Checking memory leaks for a program by executing it is an example of white-box dynamic testing. Memory leaks are defects that occur when a program fails to release memory that it has allocated but no longer needs.
Checking memory leaks for a program by executing it requires knowledge and access to the internal structure or implementation of the program, such as memory allocation and deallocation mechanisms, pointers, references, etc. Coverage analysis is an example of white-box static testing. Coverage analysis is a technique that measures how much of the code or structure of the system under test has been exercised by a test suite.
Coverage analysis requires knowledge and access to the internal structure or implementation of the system under test, such as statements, branches, paths, conditions, etc. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 7.
NEW QUESTION # 97
Manager responsibilities in formal review includes ad except one of the following:
- A. Planning the review
- B. Decide on the execution of reviews
- C. Determines if the review objectives have been met
- D. Allocate time for review
Answer: C
Explanation:
A formal review is a type of review that follows a defined process with formal entry and exit criteria and roles and responsibilities for participants. A formal review can have various roles involved, such as manager, moderator, author, reviewer and scribe. The manager responsibilities in formal review include all except one of the following:
Planning the review (correct responsibility)
Determines if the review objectives have been met (incorrect responsibility) Decide on the execution of reviews (correct responsibility) Allocate time for review (correct responsibility) The responsibility of determining if the review objectives have been met belongs to the moderator role, not to the manager role. Verified Reference: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 3, page 28-29.
NEW QUESTION # 98
For the following pseudo-code determine number of tests required for 100% statement coverage IF Gender = Boy If Age > 3 AND Age < 5 Shoe Size = 1 ELSE IF Age >=5 AND Age < 7 Shoe Size = 2 ENDIF ELSE IF Age > 3 AND Age < 5 Shoe Size = 0 ELSE IF Age >=5 AND Age < 7 Shoe Size = 1 ENDIF ENDIF
- A. 6
- B. 0
- C. 1
- D. 2
Answer: D
Explanation:
To achieve 100% statement coverage, we need to design test cases that ensure every statement in the given pseudo-code is executed at least once. Analyzing the pseudo-code, we notice that there are conditions based on two variables: Gender and Age. To cover all statements, we need to consider the paths that lead to each assignment of the Shoe Size variable.
Gender = Boy, Age <= 3 (Shoe Size assignment is not reached, but the condition is evaluated) Gender = Boy, Age > 3 AND Age < 5 (Shoe Size = 1) Gender = Boy, Age >= 5 AND Age < 7 (Shoe Size = 2) Gender != Boy, Age <= 3 (Again, Shoe Size assignment is not reached, but the condition is evaluated) Gender != Boy, Age > 3 AND Age < 5 (Shoe Size = 0) Gender != Boy, Age >= 5 AND Age < 7 (Shoe Size = 1) However, upon closer inspection, we see that tests 1 and 4 do not contribute to statement coverage as they do not lead to a Shoe Size assignment. Therefore, we only need 4 test cases to achieve 100% statement coverage, making option B the correct answer.
NEW QUESTION # 99
Which of the following statements is LEAST likely to be describing component testing?
- A. Simulators and stubs may be required.
- B. It identifies defects in modules and classes.
- C. It mainly tests interfaces and interaction between components.
- D. It may be applied using a test-first approach.
Answer: C
Explanation:
Component testing (also known as unit testing or module testing) is a level of testing that focuses on verifying the functionality and quality of individual software components (such as modules, classes, functions, methods, etc.). Component testing mainly tests interfaces and interaction between components, as well as internal logic and data structures of the components. Component testing may be applied using a test-first approach (such as test-driven development or behavior-driven development), where tests are written before the code is implemented. Component testing does not identify defects in modules and classes, as this is a result of component testing, not an objective. Simulators and stubs may be required for component testing, as they can simulate or replace missing or incomplete components or external systems that are needed for testing. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 19.
NEW QUESTION # 100
You are an experienced tester on a project with incomplete requirements and under pressure to deploy.
What type of testing should you do?
- A. Error guessing.
- B. Checklist-based testing.
- C. Exploratory testing.
- D. Decision-based testing.
Answer: C
Explanation:
When working on a project with incomplete requirements and under pressure to deploy, exploratory testing is particularly suitable. This type of testing allows testers to use their expertise and intuition to explore the system's functionality and identify defects without needing detailed specifications. Exploratory testing is flexible and can quickly adapt to changes and gaps in the requirements.
NEW QUESTION # 101
Which of the following statements best describes how configuration management supports testing?
- A. Configuration management helps ensure that all relevant project documentation and software items are uniquely identified in all their versions and therefore can be unambiguously referenced in test documentation
- B. Configuration management is an administrative discipline that includes change control, which is the process of controlling the changes to identified items referred to as Configuration Items'
- C. Configuration management is an approach to interoperability testing where tests are executed in the cloud, as the cloud can provide cost-effective access to multiple configurations of the test environments
- D. Configuration management helps reduce testing effort by identifying a manageable number of test environment configurations in which to test the software, out of all possible configurations of the environment in which the software will be released
Answer: A
Explanation:
This answer is correct because configuration management is a process of establishing and maintaining consistency of a product's performance, functional, and physical attributes with its requirements, design, and operational information throughout its life. Configuration management helps ensure that all relevant project documentation and software items are uniquely identified in all their versions and therefore can be unambiguously referenced in test documentation. This supports testing by providing traceability, consistency, and control over the test artifacts and the software under test. References: : ISTQB Glossary of Testing Terms v4.0, : ISTQB Foundation Level Syllabus v4.0, Section 2.2.2.2
NEW QUESTION # 102
Which of the following is an example of the absence-of-errors fallacy?
- A. A small number of modules contains the most defects
- B. Since testing found very few defects, the system certainly will be successful
- C. Repeating the same test cases will continue to find new defects, even after dozens of executions
- D. Other than trivial cases, it is not feasible to test all combinations of inputs and preconditions
Answer: B
Explanation:
The absence-of-errors fallacy, as explained in the ISTQB syllabus, is the erroneous belief that having fewer defects found in testing equates to a system being more successful upon release. This misconception can lead stakeholders to undervalue thorough testing. Answer C illustrates this fallacy perfectly: assuming that because few defects were found, the system will be successful, neglects the many other factors that contribute to system success, including user satisfaction and fit-for-purpose.References:ISTQB Certified Tester Foundation Level Syllabus v4.0, Section 1.1.5 "Absence-of-errors fallacy".
NEW QUESTION # 103
Which of the following lists factors That contribute to PROJECT risks?
- A. problems in defining the right requirements; contractual issues; poor software quality characteristics.
- B. poor software quality characteristics; software does not perform its intended functions.
- C. skill and staff shortages; software does not perform its intended functions; problems in defining the right requirements.
- D. skill and staff shortages; problems in defining the right requirements, contractual issues.
Answer: D
NEW QUESTION # 104
Which of the following is a test task that usually occurs during test implementation?
- A. Gather the metrics that are used to guide the test project
- B. Make sure the planned test environment is ready to be delivered
- C. Archive the testware for use in future test projects
- D. Find, analyze, and remove the causes of the failures highlighted by the tests
Answer: B
Explanation:
A test task that usually occurs during test implementation is to make sure the planned test environment is ready to be delivered. The test environment is the hardware and software configuration on which the tests are executed, and it should be as close as possible to the production environment where the software system will operate. The test environment should be planned, prepared, and verified before the test execution, to ensure that the test conditions, the test data, the test tools, and the test interfaces are available and functional. The other options are not test tasks that usually occur during test implementation, but rather test tasks that occur during other test activities, such as:
* Find, analyze, and remove the causes of the failures highlighted by the tests: This is a test task that usually occurs during test analysis and design, which is the activity of analyzing the test basis, designing the test cases, and identifying the test data. During this activity, the testers can use techniques such as root cause analysis, defect prevention, or defect analysis, to find, analyze, and remove the causes of the failures highlighted by the previous tests, and to prevent or reduce the occurrence of similar failures in the future tests.
* Archive the testware for use in future test projects: This is a test task that usually occurs during test closure, which is the activity of finalizing and reporting the test results, evaluating the test process, and identifying the test improvement actions. During this activity, the testers can archive the testware, which are the test artifacts produced during the testing process, such as the test plan, the test cases, the test data, the test results, the defect reports, etc., for use in future test projects, such as regression testing, maintenance testing, or reuse testing.
* Gather the metrics that are used to guide the test project: This is a test task that usually occurs during test monitoring and control, which is the activity of tracking and reviewing the test progress, status, and quality, and taking corrective actions when necessary. During this activity, the testers can gather the metrics, which are the measurements of the testing process, such as the test coverage, the defect density, the test effort, the test duration, etc., that are used to guide the test project, such as planning, estimating, scheduling, reporting, or improving the testing process. References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:
* 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, Test Environment, Test Condition, Test Data, Test Tool, Test Interface, Failure, Root Cause Analysis, Defect Prevention, Defect Analysis, Testware, Regression Testing, Maintenance Testing, Reuse Testing, Test Coverage, Defect Density, Test Effort, Test Duration2
NEW QUESTION # 105
Given the following state model of sales order software:
SEE ATTACHMENT
Which of the following sequences of tran-sitions provides the highest level of tran-sition coverage for the model (assuming you can start in any state)?
- A. PLACED -> IN PRODUCTION -> SHIPPED -> CANCELLED -> PLACED
- B. PLACED -> CANCELLED -> PLACED -> CANCELLED -> PLACED -> IN PRODUCTION -> CANCELLED
- C. IN PRODUCTION -> CANCELLED -> PLACED -> IN PRODUCTION -> CANCELLED -> PLACED
- D. IN PRODUCTION -> SHIPPED -> INVOICED -> CANCELLED -> PLACED -> IN PRODUCTION
Answer: D
Explanation:
To achieve the highest level of transition coverage, one must consider all the possible transitions between the states in the given state model of the sales order software. The transitions in the sequence provided in Option B - "IN PRODUCTION -> SHIPPED -> INVOICED -> CANCELLED -> PLACED -> IN PRODUCTION" cover all the states and transitions effectively. This covers the transitions from IN PRODUCTION to SHIPPED, SHIPPED to INVOICED, INVOICED to CANCELLED, CANCELLED to PLACED, and PLACED to IN PRODUCTION, thereby maximizing the transition coverage.References:
* ISTQB Certified Tester Foundation Level Syllabus v4.0, Section 4.3.5.
NEW QUESTION # 106
A company wants to reward each of its salespeople with an annual bonus that represents the sum of all the bonuses accumulated for every single sale made by that salesperson. The bonus for a single sale can take on the following four values: 3%, 5%, 7% and 10% (the percentage refers to the amount of the single sale). These values are determined on the basis of the type of customer (classified as "Basic" or "Premium") to which such sale was made, and on the amount of such sale classified into the following three groups G1, G2 and G3:
* [G1]: less than 300 euros
* [G2]: between 300 and 2000 euros
* [G3]: greater than 2000 euros
Which of the following is the minimum number of test cases needed to cover the full decision table associated with this scenario?
- A. 0
- B. 1
- C. 2
- D. 3
Answer: B
Explanation:
The minimum number of test cases needed to cover the full decision table associated with this scenario is 6.
This is because the decision table has 4 conditions (type of customer and amount of sale) and 4 actions (bonus percentage). The conditions have 2 possible values each (Basic or Premium, and G1, G2 or G3), so the total number of combinations is 2 x 2 x 2 x 2 = 16. However, not all combinations are valid, as some of them are contradictory or impossible. For example, a sale cannot be both less than 300 euros and greater than 2000 euros at the same time. Therefore, we need to eliminate the invalid combinations and keep only the valid ones.
The valid combinations are:
Type of customer
Amount of sale
Bonus percentage
Basic
G1
3%
Basic
G2
5%
Basic
G3
7%
Premium
G1
5%
Premium
G2
7%
Premium
G3
10%
These 6 combinations cover all the possible values of the conditions and actions, and they are the minimum number of test cases needed to cover the full decision table.
References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents,
NEW QUESTION # 107
Which of the following isNOTa common objective of testing?
- A. Providing information on the status of the system
- B. Debugging the software to find the reason for defects
- C. Preventing defects
- D. Finding defects in the software
Answer: B
Explanation:
Debugging the software to find the reason for defects is not a common objective of testing, but rather a task of development or maintenance. Debugging is a process of locating and fixing errors in the software code, while testing is a process of finding and reporting defects in the software behavior or quality. Testing does not aim to fix defects, but rather to provide information on their existence and impact. The other options are common objectives of testing. Finding defects in the software is one of the main objectives of testing, as it helps to improve the quality and reliability of the software. Preventing defects is another objective of testing, as it helps to avoid rework and reduce costs and risks. Providing information on the status of the system is another objective of testing, as it helps to support decision making and risk management. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 3.
NEW QUESTION # 108
Why should you choose a test technique?
- A. Because choosing a test technique is a common practice in software testing
- B. Because you need to match the way you test to the content of the product under test
- C. Because of the time constraints that usually accompany a test project
- D. Because this way you cover the full scope of the product's functionality
Answer: B
Explanation:
You should choose a test technique because you need to match the way you test to the content of the product under test. A test technique is a method or process for deriving and selecting test cases based on some criteria or rules. Different test techniques are suitable for different types of software products, depending on their characteristics, functionalities, requirements, specifications, risks, etc. Choosing a test technique helps to ensure that the test cases are relevant, effective, and efficient for the product under test. The other options are not correct reasons to choose a test technique. Time constraints are not a factor for choosing a test technique, but rather for prioritizing or optimizing testing activities. Covering the full scope of the product's functionality is not a guarantee of choosing a test technique, but rather a goal of testing. Choosing a test technique is not a common practice in software testing, but rather a professional skill and responsibility. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 31.
NEW QUESTION # 109
A test manager defined the following test levels in her test plan; Component, System and Acceptance.
Which Software Development lifecycle is the Test Manager most likely following?
- A. V-Model
- B. Prototyping
- C. Agile
- D. Waterfall
Answer: A
Explanation:
The test manager is most likely following the V-model for software development. The V-model is a software development model that defines four testing levels that correspond to four development phases: component testing corresponds to component design, integration testing corresponds to architectural design, system testing corresponds to system requirements specification, and acceptance testing corresponds to user requirements specification. The V-model also defines the test planning and test execution activities for each testing level. Agile is a software development model that follows an iterative and incremental approach, where testing is integrated into each iteration and adapts to changing requirements and feedback. Waterfall is a software development model that follows a sequential and linear approach, where testing is performed after the development phase is completed. Prototyping is a softwaredevelopment model that involves creating a simplified version of the software to elicit user feedback and validate requirements before developing the final product. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page
18.
NEW QUESTION # 110
......
ISTQB Certified ISTQB-CTFL Dumps Questions Valid ISTQB-CTFL Materials: https://www.examcollectionpass.com/ISTQB/ISTQB-CTFL-practice-exam-dumps.html
Get The Most Updated ISTQB-CTFL Dumps To Foundation Level Certification: https://drive.google.com/open?id=1Ce7iu1SDxJMaD6lQE-N0r5lN4CuNayAv