ISTQB ISTQB-CTFL Online Practice Questions and Exam Preparation

ISTQB ISTQB-CTFL Online Questions & Answers

• Question 241:

  For each of the test cases to be executed, the following table specifies the priority order and dependencies on other test cases

  

  Which of the following test execution schedules is compatible with the logical dependencies and allows executing the test cases in priority order?

  A. TC4, TC3, TC2, TC6, TC5. TC1
  B. TC4, TC6, TC3, TC2, TC5, TC1
  C. TC3, TC5, TC6, TC1, TC4, TC3
  D. TC4, TC3, TC2, TC6, TC1, TC5
  D. TC4, TC3, TC2, TC6, TC1, TC5

  ---

  Explanation

  This answer is correct because it follows the logical dependencies and allows executing the test cases in priority order. TC4, TC3, and TC2 are executed first because they have the highest priority. TC6 is executed next because it has a logical dependency on TC2. TC1 is executed next because it has a logical dependency on TC5. Finally, TC5 is executed last because it has the lowest priority.

  References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 documents

• Question 242:

  Which principle of testing states that testing is context dependent?

  A. Testing shows presence of defects
  B. Exhaustive testing is impossible
  C. Defects cluster together
  D. Testing is context dependent
  D. Testing is context dependent

  ---

  Explanation

  Testing approach depends on product risk, business domain, and objectives.

• Question 243:

  Which of the following is a function of a dynamic analysis tool?

  A. Provide support for traceability of tests, test results and incidents to source documents
  B. Monitor the allocation, use and de-allocation of memory during run-time of a program
  C. Execute programs step-by-step in order to reproduce failures and find corresponding defects
  D. Provide support for release of baselines consisting of configuration items
  B. Monitor the allocation, use and de-allocation of memory during run-time of a program

  ---

  Explanation

  A dynamic analysis tool is a tool that performs analysis of a software product based on its behavior during execution. A dynamic analysis tool can monitor various aspects of a program's run-time performance, such as memory usage, CPU load, response time, or resource leaks. A dynamic analysis tool can monitor the allocation, use and de-allocation of memory during run-time of a program, which can help detect defects such as memory leaks, buffer overflows, or memory corruption. A dynamic analysis tool cannot provide support for traceability of tests, test results and incidents to source documents, as this is a function of a test management tool. A dynamic analysis tool cannot execute programs step-by-step in order to reproduce failures and find corresponding defects, as this is a function of a debugging tool. A dynamic analysis tool cannot provide support for release of baselines consisting of configuration items, as this is a function of a configuration management tool. Verified

  References: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 6, page 56-57.

• Question 244:

  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?

  A. TC1 - TC3 - TC2 - TC4 - TC6 - TC5
  B. TC3 - TC4 - TC2 - TC6 - TC1 - TC5
  C. TC1 - TC3 - TC2 - TC4 - TC5 - TC6
  D. TC2 - TC4 - TC1 - TC3 - TC5 - TC6
  C. TC1 - TC3 - TC2 - TC4 - TC5 - TC6

  ---

  Explanation

  When scheduling test cases, priorities and dependencies must be considered. The best execution order will respect both the logical dependencies and the priorities assigned to each test case.

  Given the options, the correct order considering the priorities and dependencies is:

  TC1 (Priority 1)

  **TC (ISTQB not-for-profit association)ity 2, dependent on TC1)

  TC2 (Priority 3, dependent on TC1)

  TC4 (Priority 4)

  TC5 (Priority 5)

  TC6 (Priority 6, dependent on TC4)

  According to the ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, understanding dependencies and scheduling tests accordingly is crucial for effective test execution#6source#.

  References:

  Certified Tester Foundation Level v4.0

  ISTQB Foundation Level Syllabus 4.0 (2023)

• Question 245:

  Which of the following statements refers to good testing practice to be applied regardless of the chosen software development model?

  A. Tests should be written in executable format before the code is written and should act as executable specifications that drive coding
  B. Test levels should be defined such that the exit criteria of one level are part of the entry criteria for the next level
  C. Test objectives should be the same for all test levels, although the number of tests designed at various levels can vary significantly
  D. Involvement of testers in work product reviews should occur as early as possible to take advantage of the early testing principle
  D. Involvement of testers in work product reviews should occur as early as possible to take advantage of the early testing principle

  ---

  Explanation

  The statement that refers to good testing practice to be applied regardless of the chosen software development model is option D, which says that involvement of testers in work product reviews should occur as early as possible to take advantage of the early testing principle. Work product reviews are static testing techniques, in which the work products of the software development process, such as the requirements, the design, the code, the test cases, etc., are examined by one or more reviewers, with or without the author, to identify defects, violations, or improvements. Involvement of testers in work product reviews can provide various benefits for the testing process, such as improving the test quality, the test efficiency, and the test communication. The early testing principle states that testing activities should start as early as possible in the software development lifecycle, and should be performed iteratively and continuously throughout the lifecycle. Applying the early testing principle can help to prevent, detect, and remove defects at an early stage, when they are easier, cheaper, and faster to fix, as well as to reduce the risk, the cost, and the time of the testing process. The other options are not good testing practices to be applied regardless of the chosen software development model, but rather specific testing practices that may or may not be applicable or beneficial for testing, depending on the context and the objectives of the testing activities, such as:

  Tests should be written in executable format before the code is written and should act as executable specifications that drive coding: This is a specific testing practice that is associated with test-driven development, which is an approach to software development and testing, in which the developers write automated unit tests before writing the source code, and then refactor the code until the tests pass. Test- driven development can help to improve the quality, the design, and the maintainability of the code, as well as to provide fast feedback and guidance for the developers. However, test-driven development is not a good testing practice to be applied regardless of the chosen software development model, as it may not be feasible, suitable, or effective for testing in some contexts or situations, such as when the requirements are unclear, unstable, or complex, when the test automation tools or skills are not available or adequate, when the testing objectives or levels are not aligned with the unit testing, etc.

  Test levels should be defined such that the exit criteria of one level are part of the entry criteria for the next level: This is a specific testing practice that is associated with sequential software development models, such as the waterfall model, the V-model, or the W-model, in which the software development and testing activities are performed in a linear and sequential order, with well-defined phases, deliverables, and dependencies. Test levels are the stages of testing that correspond to the levels of integration of the software system, such as component testing, integration testing, system testing, and acceptance testing. Test levels should have clear and measurable entry criteria and exit criteria, which are the conditions that must be met before starting or finishing a test level. In sequential software development models, the exit criteria of one test level are usually part of the entry criteria for the next test level, to ensure that the software system is ready and stable for the next level of testing. However, this is not a good testing practice to be applied regardless of the chosen software development model, as it may not be relevant, flexible, or efficient for testing in some contexts or situations, such as when the software development and testing activities are performed in an iterative and incremental order, with frequent changes, feedback, and adaptations, as in agile software development models, such as Scrum, Kanban, or XP, when the test levels are not clearly defined or distinguished, or when the test levels are performed in parallel or concurrently, etc.

  Test objectives should be the same for all test levels, although the number of tests designed at various levels can vary significantly: This is a specific testing practice that is associated with uniform software development models, such as the spiral model, the incremental model, or the prototyping model, in which the software development and testing activities are performed in a cyclical and repetitive manner, with similar phases, deliverables, and processes. Test objectives are the goals or the purposes of testing, which can vary depending on the test level, the test type, the test technique, the test environment, the test stakeholder, etc. Test objectives can be defined in terms of the test basis, the test coverage, the test quality, the test risk, the test cost, the test time, etc. Test objectives should be specific, measurable, achievable, relevant, and time-bound, and they should be aligned with the project objectives and the quality characteristics. In uniform software development models, the test objectives may be the same for all test levels, as the testing process is repeated for each cycle or iteration, with similar focus, scope, and perspective of testing. However, this is not a good testing practice to be applied regardless of the chosen software development model, as it may not be appropriate, realistic, or effective for testing in some contexts or situations, such as when the software development and testing activities are performed in a hierarchical and modular manner, with different phases, deliverables, and dependencies, as in sequential software development models, such as the waterfall model, the V-model, or the W-model, when the test objectives vary according to the test levels, such as component testing, integration testing, system testing, and acceptance testing, or when the test objectives change according to the feedback, the learning, or the adaptation of the testing process, as in agile software development models, such as Scrum, Kanban, or XP, etc.

  References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents: ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 1.1.1, Testing and the Software Development Lifecycle1 ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 1.2.1, Testing Principles1 ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 1.2.2, Testing Policies, Strategies, and Test Approaches1 ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 1.3.1, Testing in Software Development Lifecycles1 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, Work Product Review, Static Testing, Early Testing, Test- driven Development, Test Level, Entry Criterion, Exit Criterion, Test Objective, Test Basis, Test Coverage, Test Quality, Test Risk, Test Cost, Test Time

• Question 246:

  Which of the following is true about Oracles?

  A. Sometimes old version of a product can be used as an Oracle
  B. Oracles help in reproducing the irreproducible bugs
  C. Oracles are derived from the design
  D. Oracles can be generated automatically using data generators
  A. Sometimes old version of a product can be used as an Oracle

  ---

  Explanation

  An oracle is a mechanism or source that can provide the expected result for a given test input or situation. Sometimes old version of a product can be used as an oracle, if it is assumed that the old version behaves correctly for the test cases that are executed on the new version. This is also known as back-to-back testing. Oracles do not help in reproducing the irreproducible bugs, as they only provide the expected results, not the actual results. Oracles are not derived from the design, but from the requirements or specifications. Oracles cannot be generated automatically using data generators, as data generators only provide test inputs, not test outputs. Verified

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

• Question 247:

  An e-commerce site accepts credit cards for processing the payment. The payment processing form has a field for the amount of money to be deducted. The minimum amount of money that can be processed is $10. The credit cards have a limit of $5,000 (Five Thousand). Assume that only integers can be accepted as inputs. Which of the following set of boundary values you will choose for EFFICIENT testing for the amount of money that can be spent?

  A. 9.5001
  B. 10.5000
  C. 10, 11.4999, 5000r 5001
  D. 9. 10.5000,5001
  B. 10.5000

  ---

  Explanation

• Question 248:

  The following state transition diagram describes the functionality involved in a system using fingerprint and password authentication to log onto a system.

  How many distinct states of the system are visible in the above diagram?

  A. 1
  B. 2
  C. 3
  D. 4
  C. 3

  ---

  Explanation

  The state transition diagram provided shows three distinct states:

  1.Waiting for fingerprint

  2.Waiting for PIN

  3.Valid PIN/ask menu selection

  Each state represents a different stage in the system's operation, with transitions based on user actions and system responses.

• Question 249:

  During iteration planning, a scrum team uses an estimation technique called planning poker to estimate the effort required to deliver a critical user story. In advance of the estimation session, the team agreed on some ground rules to limit the number of poker rounds and save time.

  The team agreed on the following:

  1.They will use the following progression for estimation: Extra-small, Small, Medium, Large, Extra-large, and Extra-extra-large.

  2.If estimation values differ significantly, the highest score will be used for estimation purposes.

  The result of the first round of planning poker:

  1.Team MemberEstimation

  2.BusinessLarge

  3.DevelopmentExtra-extra-large

  4.TestingExtra-extra-large

  Which of the following options best represent the team's next actions?

  A. The fact that all estimations are high indicate that the user story is not well understood or should be broken down into multiple smaller stories.
  B. The pre-agreed rules state that the highest score should be used for estimation, resulting in the user story being categorised as Extra-extra-large.
  C. Since the business representative is likely to have the most informed view of the requirement, the user story is categorised as a Large.
  D. the team discusses the differences in the estimates and repeats the poker round until an agreemet is reached.
  D. the team discusses the differences in the estimates and repeats the poker round until an agreemet is reached.

  ---

  Explanation

  In a planning poker session, if there is a significant difference in the estimations, it indicates that there may be misunderstandings or different perspectives on the complexity of the user story. According to the agile principles, the team should discuss these differences to reach a common understanding. The goal is to ensure that all team members have a shared understanding of the user story's scope and complexity before finalizing the estimate.

• Question 250:

  A possible risk of introducing test automation is:

  A. the tool may not be fit-for-purpose.
  B. the tool may create additional development dependencies.
  C. the tool may not be compatible with the development platform.
  D. the tool will be owned and maintained by developers and replace testers.
  A. the tool may not be fit-for-purpose.

  ---

  Explanation

  One possible risk of introducing test automation is that the selected tool may not be fit-for-purpose. This means that the tool might not meet the specific needs and requirements of the project, leading to inefficiencies and possibly failing to provide the expected benefits. It is crucial to evaluate and select the appropriate tool based on the project's context and objectives. The ISTQB CTFL syllabus highlights the importance of careful tool evaluation and selection to ensure it aligns with the testing goals and the development environment.

  References: ISTQB CTFL Syllabus, Section 6.2, "Potential Benefits and Risks of Test Automation."