ISTQB ISTQB-CTFL Online Practice Questions and Exam Preparation

ISTQB ISTQB-CTFL Online Questions & Answers

• Question 311:

  Which of the following statements about static testing and dynamic testing is true?

  A. Unlike dynamic testing, which can be also performed manually, static testing cannot be performed without specialized tools
  B. Static testing is usually much less cost-effective than dynamic testing
  C. Unlike dynamic testing, which focuses on detecting potential defects, static testing focuses on detecting failures which may be due to actual defects
  D. Both static testing and dynamic testing can be used to highlight issues associated with non-functional characteristics
  D. Both static testing and dynamic testing can be used to highlight issues associated with non-functional characteristics

  ---

  Explanation

  This answer is correct because static testing and dynamic testing are both types of testing that can be used to highlight issues associated with non-functional characteristics, such as usability, performance, security, reliability, etc. Static testing is a type of testing that involves the analysis of software work products, such as requirements, design, code, or test cases, without executing them. Dynamic testing is a type of testing that involves the execution of software work products, such as code or test cases, using inputs and verifying outputs. Both static testing and dynamic testing can be applied to different test levels and test types, and can use different test techniques and tools, to evaluate the non-functional characteristics of the software product.

  References: ISTQB Glossary of Testing Terms v4.0, ISTQB Foundation Level Syllabus v4.0, Section 2.2.1.1, Section 2.2.1.2

• Question 312:

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

  A. The project manager's preference
  B. Tester skill level with the software development lifecycle model
  C. The project team's overall familiarity with the model
  D. The type of product being developed
  D. The type of product being developed

  ---

  Explanation

  The choice of a software development lifecycle (SDLC) model is primarily influenced by the type of product being developed. Different products and project requirements may demand different SDLC models to address specific challenges and needs efficiently. For instance, a complex, safety-critical product might best be served by a Waterfall model due to its structured nature and phase dependencies, while a more iterative and incremental model might be suited for projects requiring frequent feedback and changes.

  References:ISTQB Certified Tester Foundation Level Syllabus v4.0, Section 2.1 "Software Development Lifecycles".

• Question 313:

  In a museum there are staggered entrance fees:

  1.Free admission: children under 14 years

  2.Reduced admission: young people aged 14 and under 18, retiree, students and welfare recipients

  3.Regular price: all other persons

  Which of the following four options describes the minimum set of test data that reaches 100% coverage of all valid equivalence classes for the admission fees?

  A. Child (12 years), student (23 years), retiree (68 years)
  B. Youth (16 years), adult (35 years), adult (60 years)
  C. Child (12 years), welfare recipient (45 years), retiree (68 years)
  D. Child (12 years), adult (35 years), retiree (68 years)
  D. Child (12 years), adult (35 years), retiree (68 years)

  ---

  Explanation

• Question 314:

  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 tran-sitions provides the highest level of tran-sition coverage for the model (assuming you can start in any state)?

  A. IN PRODUCTION -> CANCELLED -> PLACED -> IN PRODUCTION -> CANCELLED -> PLACED
  B. IN PRODUCTION -> SHIPPED -> INVOICED -> CANCELLED -> PLACED -> IN PRODUCTION
  C. PLACED -> IN PRODUCTION -> SHIPPED -> CANCELLED -> PLACED
  D. PLACED -> CANCELLED -> PLACED -> CANCELLED -> PLACED -> IN PRODUCTION -> CANCELLED
  B. IN PRODUCTION -> SHIPPED -> INVOICED -> CANCELLED -> PLACED -> IN PRODUCTION

  ---

  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.

• Question 315:

  The following diagram displays the logical dependencies between requirements and the individual requirement priorities. For example, "R2->R3" means that R3 is dependent on R2. Priority is indicated by the number next to the letter "P" i.e.

  P1 has a higher priority than P2. Which one of the following options best describes the test execution sequence using both requirement dependency and priority?

  A. R2. R1, R3. R4. R5, R6. R7, R8.
  B. R1, R2, R3, R4, R5, R6, R7, R8.
  C. R2, R4. R8, R5, R1, R6, R3, R7.
  D. . R2, R1,R3,R7,R6,R5,R4,R8.
  D. . R2, R1,R3,R7,R6,R5,R4,R8.

  ---

  Explanation

  The correct test execution sequence should consider both the dependencies between the requirements and their priorities. According to the diagram, the sequence begins with R2 (P1) as it is a prerequisite for R3 (P4). Then R1 (P3) can be tested. R3 follows as it depends on R2. Next, R7 (P4) should be tested before R6 (P3) and R5 (P2), as indicated by their dependencies. Finally, R4 (P1) and R8 (P1) can be tested. Therefore, the best sequence is R2, R1, R3, R7, R6, R5, R4, R8.

  ISTQB CTFL Syllabus V4.0, Section 5.1.5

• Question 316:

  For a mandatory input field "ZIP code" the following rules are given:

  1 - The valid ZIP code format is 5 numeric digits.

  2 - The code has to exist in the post office's official ZIP code list

  Using equivalence classes partitioning, how many test cases are required to test this field?

  A. 8
  B. 3
  C. 6
  D. 4
  D. 4

  ---

  Explanation

  Equivalence classes 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 classes partitioning can be used to reduce the number of test cases by selecting one representative value from each partition. For the ZIP code field, there are four equivalence classes based on the given rules:

  Valid ZIP code format and valid ZIP code value (e.g., 12345)

  Valid ZIP code format and invalid ZIP code value (e.g., 99999)

  Invalid ZIP code format and valid ZIP code value (e.g., 1234)

  Invalid ZIP code format and invalid ZIP code value (e.g., ABCDE) Therefore, four test cases are required to test this field, one for each equivalence class.

  Verified

  References: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 4, page 37-38.

• Question 317:

  Which of the following statements is incorrect regarding the involvement of testers in the software development lifecycle (SDLC)?

  A. Testers should contribute to all activities in the SDLC and participate in design discussions.
  B. Testers should be involved from the beginning of the SDLC to increase understanding of design decisions and detect defects early.
  C. Testers should only be involved during the testing phase.
  D. Testers' involvement is essential; developers find it difficult to be objective.
  C. Testers should only be involved during the testing phase.

  ---

  Explanation

  Involving testers only during the testing phase is incorrect as per the ISTQB CTFL syllabus. Effective involvement of testers is crucial throughout the entire software development lifecycle (SDLC). This includes early stages such as requirement analysis and design, which allows testers to understand the design decisions and detect defects early. Early involvement helps in better understanding the project and ensures that quality is built into the product from the beginning. Furthermore, the ISTQB syllabus emphasizes the importance of testers contributing to all activities in the SDLC, including design discussions, to enhance defect detection and prevention.

  References: ISTQB CTFL Syllabus, Section 2.1.1, "The Influence of Development Models on Testing" and Section 1.1.1, "Test Objectives."

• Question 318:

  Which of the following tools is most likely to detect defects in functions or methods in source code?

  A. configuration management tool
  B. unit test framework tool
  C. test design tool
  D. monitoring tool
  B. unit test framework tool

  ---

  Explanation

  A unit test framework tool is a tool that supports the creation, execution, and reporting of unit tests, which are tests that verify the functionality and quality of individual software components (such as functions or methods) in source code. A unit test framework tool can help to detect defects in functions or methods in source code by providing features such as test case generation, test case execution, test result comparison, test coverage measurement, etc. Some examples of unit test framework tools are JUnit, NUnit, TestNG, etc. The other options are not tools that are likely to detect defects in functions or methods in source code. A configuration management tool is a tool that supports the management and control of different versions and variants of software products or components. A test design tool is a tool that supports the design and generation of test cases based on some criteria or rules. A monitoring tool is a tool that monitors the behavior or performance of a system or component under test. Verified

  References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 10.

• Question 319:

  Pariksha labs is a mature software testing company. They are TMMi level 5 certified. Their testing processes are well defined. Which ONE of the following statements is likely to be CORRECT about them?

  A. The company uses same test strategy for all the projects doing minor changes based on test manager responsible for the project because their test strategy template is very mature and do not need to change
  B. They try to perform 100% automation for every project because automation is a must for efficiency
  C. Same set of testing processes are used by them without needing any tweaks because that is the hallmark of a mature testing company.
  D. The question about the test design techniques to be used is determined based on various factors such as the domain and expectations of the stakeholders
  D. The question about the test design techniques to be used is determined based on various factors such as the domain and expectations of the stakeholders

  ---

  Explanation

• Question 320:

  The four test levels used in ISTQB syllabus are:

  1.Component (unit) testing

  2.Integration testing

  3.System testing

  4.Acceptance testing

  An organization wants to do away with integration testing but otherwise follow V-model. Which of the following statements is correct?

  A. It is allowed as organizations can decide on men test levels to do depending on the context of the system under test
  B. It is allowed because integration testing is not an important test level arc! can be dispensed with.
  C. It is not allowed because integration testing is a very important test level and ignoring i: means definite poor product quality
  D. It is not allowed as organizations can't change the test levels as these are chosen on the basis of the SDLC (software development life cycle) model
  D. It is not allowed as organizations can't change the test levels as these are chosen on the basis of the SDLC (software development life cycle) model

  ---

  Explanation

  The V-model is a software development life cycle model that defines four test levels that correspond to four development phases: component (unit) testing with component design, integration testing with architectural design, system testing with system requirements, and acceptance testing with user requirements. The V-model emphasizes the importance of verifying and validating each phase of development with a corresponding level of testing, and ensuring that the test objectives, test basis, and test artifacts are aligned and consistent across the test levels. Therefore, an organization that wants to follow the V-model cannot do away with integration testing, as it would break the symmetry and completeness of the V-model, and compromise the quality and reliability of the software or system under test. Integration testing is a test level that aims to test the interactions and interfaces between components or subsystems, and to detect any defects or inconsistencies that may arise from the integration of different parts of the software or system. Integration testing is essential for ensuring the functionality, performance, and compatibility of the software or system as a whole, and for identifying and resolving any integration issues early in the development process. Skipping integration testing would increase the risk of finding serious defects later in the test process, or worse, in the production environment, which would be more costly and difficult to fix, and could damage the reputation and credibility of the organization. Therefore, the correct answer is

  D.

  The other options are incorrect because:

  A. It is not allowed as organizations can decide on the test levels to do depending on the context of the system under test. While it is true that the choice and scope of test levels may vary depending on the context of the system under test, such as the size, complexity, criticality, and risk level of the system, the organization cannot simply ignore or skip a test level that is defined and required by the chosen software development life cycle model. The organization must follow the principles and guidelines of the software development life cycle model, and ensure that the test levels are consistent and coherent with the development phases. If the organization wants to have more flexibility and adaptability in choosing the test levels, it should consider using a different software development life cycle model, such as an agile or iterative model, that allows for more dynamic and incremental testing approaches.

  B. It is not allowed because integration testing is not an important test level and can be dispensed with. This statement is false and misleading, as integration testing is a very important test level that cannot be dispensed with. Integration testing is vital for testing the interactions and interfaces between components or subsystems, and for ensuring the functionality, performance, and compatibility of the software or system as a whole. Integration testing can reveal defects or inconsistencies that may not be detected by component (unit) testing alone, such as interface errors, data flow errors, integration logic errors, or performance degradation. Integration testing can also help to verify and validate the architectural design and the integration strategy of the software or system, and to ensure that the software or system meets the specified and expected quality attributes, such as reliability, usability, security, and maintainability. Integration testing can also provide feedback and confidence to the developers and stakeholders about the progress and quality of the software or system development. Therefore, integration testing is a crucial and indispensable test level that should not be skipped or omitted.

  C. It is not allowed because integration testing is a very important test level and ignoring it means definite poor product quality. This statement is partially true, as integration testing is a very important test level that should not be ignored, and skipping it could result in poor product quality. However, this statement is too strong and absolute, as it implies that integration testing is the only factor that determines the product quality, and that ignoring it would guarantee a poor product quality. This is not necessarily the case, as there may be other factors that affect the product quality, such as the quality of the requirements, design, code, and other test levels, the effectiveness and efficiency of the test techniques and tools, the competence and experience of the developers and testers, the availability and adequacy of the resources and environment, the management and communication of the project, and the expectations and satisfaction of the customers and users. Therefore, while integration testing is a very important test level that should not be skipped, it is not the only test level that matters, and skipping it does not necessarily mean definite poor product quality, but rather a higher risk and likelihood of poor product quality.

  References:

  ISTQB Certified Tester Foundation Level Syllabus, Version 4.0, 2018, Section 2.3, pages 16- 18;

  ISTQB Glossary of Testing Terms, Version 4.0, 2018, pages 38-39;

  ISTQB CTFL 4.0 - Sample Exam - Answers, Version 1.1, 2023, question104, page 36.