BCS ISTQB Certified Tester Foundation Level 4.0 CTFL4 Exam Practice Test

Page: 1 / 14
Total 148 questions
Question 1

You are an experienced tester on a project with incomplete requirements and under pressure to deploy.

What type of testing should you do?



Answer : D

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.


Question 2

Which of the following is an advantage of the whole team approach?



Answer : D

The whole team approach, often advocated in Agile methodologies, emphasizes collaboration and collective responsibility among all team members. This approach enhances the relationships within the team and improves overall collaboration, which in turn benefits the project's success. According to the ISTQB CTFL Syllabus v4.0, the whole team approach fosters better communication and cooperation, leading to more effective problem-solving and higher-quality outcomes.


Question 3

Test automation allows you to:



Answer : B

Test automation allows you to produce tests that are less subject to human errors, as they can execute predefined test scripts or test cases with consistent inputs, outputs, and expected results. Test automation can also reduce the manual effort and time required to execute repetitive or tedious tests, such as regression tests, performance tests, or data-driven tests. Test automation does not demonstrate the absence of defects, as it can only verify the expected behavior of the system under test, not the unexpected or unknown behavior. Test automation does not avoid performing exploratory testing, as exploratory testing is a valuable technique to discover new information, risks, or defects that are not covered by automated tests. Test automation does not increase test process efficiency by facilitating management of defects, as defect management is a separate activity that involves reporting, tracking, analyzing, and resolving defects, which may or may not be related to automated tests.Reference: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:

ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 3.3.1, Test Automation1

ISTQB Glossary of Testing Terms v4.0, Test Automation2


Question 4

Which of the following issues cannot be identified by static analysis tools?



Answer : A

Static analysis tools are software tools that examine the source code of a program without executing it.They can detect various types of issues, such as syntax errors, coding standards violations, security vulnerabilities, and potential bugs12.However, static analysis tools cannot identify issues that depend on the runtime behavior or performance of the program, such as very low MTBF (Mean Time Between failure)3. MTBF is a measure of the reliability of a system or component. It is calculated by dividing the total operating time by the number of failures. MTBF reflects how often a system or component fails during its expected lifetime. Static analysis tools cannot measure MTBF because they do not run the program or observe its failures.MTBF can only be estimated by dynamic testing, which involves executing the program under various conditions and collecting data on its failures4. Therefore, very low MTBF is an issue that cannot be identified by static analysis tools. The other options, such as potentially endless loops, referencing a variable with an undefined value, and security vulnerabilities, are issues that can be identified by static analysis tools.Static analysis tools can detect potentially endless loops by analyzing the control flow and data flow of the program and checking for conditions that may never become false5.Static analysis tools can detect referencing a variable with an undefined value by checking the scope and initialization of variables and reporting any use of uninitialized variables6. Static analysis tools can detect security vulnerabilities by checking for common patterns of insecure code, such as buffer overflows, SQL injections, cross-site scripting, and weak encryption.Reference=What Is Static Analysis? Static Code Analysis Tools - Perforce Software,How Static Code Analysis Works | Perforce,Static Code Analysis: Techniques, Top 5 Benefits & 3 Challenges,What is MTBF? Mean Time Between Failures Explained | Perforce,Static analysis tools - Software Testing MCQs - CareerRide,ISTQB_Chapter3 | Quizizz, [Static Code Analysis for Security Vulnerabilities | Perforce].


Question 5

After being in operation for many years, a document management system must be decommissioned as it has reached its end of life. This system will not be replaced by any other new system. A legal obligation provides that all documents within the system must be kept for at least 20 years in a state archive. Which of the following statements about maintenance testing for decommissioning of this system is TRUE?



Answer : B

Data migration testing is a critical part of maintenance testing during the decommissioning of a system. When a system is decommissioned, data often needs to be transferred to another system or archived securely. This process ensures that the data remains intact, accessible, and secure in its new location. Therefore, statement B is true as it aligns with the ISTQB CTFL syllabus guidelines on handling system decommissioning and data preservation.


Question 6

Consider a review for a high-level architectural document written by a software architect. The architect does most of the review preparation work, including distributing the document to reviewers before the review meeting. However, reviewers are not required to analyze the document in advance, and during the review meeting the software architect explains the document step by step. The only goal of this review is to establish a common understanding of the software architecture that will be used in a software development project.

Which of the following review types does this review refer to?



Answer : C

This answer is correct because a walkthrough is a type of review where the author of the work product leads the review process and explains the work product to the reviewers. The reviewers are not required to prepare for the review in advance, and the main objective of the walkthrough is to establish a common understanding of the work product and to identify any major defects or issues. A walkthrough is usually informal and does not follow a defined process or roles. In this case, the review for a high-level architectural document written by a software architect matches the characteristics of a walkthrough.Reference: ISTQB Glossary of Testing Terms v4.0, ISTQB Foundation Level Syllabus v4.0, Section 2.4.2.2


Question 7

A requirement specifies that if the total amount of sales (TAS) made during the year by a corporate seller is 300,000 or more, the bonus that must be paid to the seller is 100% of a certain amount agreed upon at the beginning of the year. The software contains a fault as it implements this requirement with the decision "IF (TAS = 300,000)" instead of "IF (TAS >= 300.000)". The application of the 3-value boundary value analysis to this problem consists of the following three test cases (TAS is an integer variable):

TC1 = 299,999 TC2=300,000 TC=300,001

Which of the following statements is TRUE?



Answer : B

The requirement specifies that a bonus should be paid if the total amount of sales (TAS) made during the year is 300,000 or more. The software incorrectly implements this requirement with 'IF (TAS = 300,000)' instead of 'IF (TAS >= 300,000)'. Using boundary value analysis (BVA), which is a common technique in software testing, the three test cases provided (TC1 = 299,999, TC2 = 300,000, and TC3 = 300,001) cover the critical boundary values around the condition.

TC1 tests just below the boundary (299,999),

TC2 tests exactly at the boundary (300,000),

TC3 tests just above the boundary (300,001).

Since the software incorrectly checks for TAS equal to 300,000, only TC2 will fail because the condition is exactly met and highlights the incorrect implementation of the decision logic.


Page:    1 / 14   
Total 148 questions