ISTQB ISTQB-CTFL Online Practice Questions and Exam Preparation

ISTQB ISTQB-CTFL Online Questions & Answers

• Question 1:

  Which of the following is a white-box testing technique?

  A. Decision table testing
  B. Statement coverage
  C. Equivalence partitioning
  D. State transition testing
  B. Statement coverage

  ---

  Explanation

  Statement coverage measures executed lines of code, a structural technique.

• Question 2:

  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?

  A. No maintenance testing is required as this system will not be replaced.
  B. Data migration testing is required as part of maintenance testing
  C. Confirmation testing is required as part of maintenance testing.
  D. Regression testing is required as part of maintenance testing
  B. Data migration testing is required as part of maintenance testing

  ---

  Explanation

  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 3:

  Which of the following statements best describes the difference between product risk and project risk in software testing?

  A. Product risk refers to the risk associated with the project's schedule, budget, and resources, while project risk refers to the risk associated with the quality and functionality of the software product.
  B. Product risk refers to the risk associated with issues such as delays in work product deliveries, inaccurate estimates, while project risk refers to the risk associated with the project's schedule, budget, and resources.
  C. Product risk and project risk are essentially the same and can be used interchangeably.
  D. Product risk refers to the risk associated with delays in elements such as work product deliveries and inaccurate estimates, while project risk refers to the risk associated with issues such as user dissatisfaction.
  B. Product risk refers to the risk associated with issues such as delays in work product deliveries, inaccurate estimates, while project risk refers to the risk associated with the project's schedule, budget, and resources.

  ---

  Explanation

  Product risk involves the potential issues that can affect the quality and functionality of the software product, such as defects, performance problems, and usability issues. Project risk, on the other hand, relates to the risks that can impact the project's schedule, budget, and resources, such as delays, cost overruns, and resource constraints. Understanding both types of risks is crucial for managing and mitigating potential problems in software projects.

  References: ISTQB CTFL Syllabus, Section 5.2.1, "Risk Management in Testing."

• Question 4:

  Out of the following. what is not needed to specify in defect report?

  A. Test environment details
  B. How to reproduce the defect
  C. How to fix the defect
  D. Seventy and priority
  C. How to fix the defect

  ---

  Explanation

  A defect report is a document that records the details of a defect found during testing. A defect report typically contains the following items:

  Identifier: A unique identifier for the defect report Summary: A concise summary of the defect Description: A detailed description of the defect, including the steps to reproduce it, the expected and actual results, and any relevant screenshots or logs Severity: The degree of impact that the defect has on the system Priority: The level of urgency for resolving the defect Status: The current state of the defect, such as new, open, resolved, closed, etc. Resolution: The action taken to resolve the defect, such as fix, workaround, reject, etc. Out of these items, the one that is not needed to specify in a defect report is how to fix the defect. How to fix the defect is a technical solution that is usually determined by the developer who is assigned to resolve the defect. How to fix the defect is not part of the defect report, but rather part of the code change or patch that is delivered to fix the defect. The other items are needed to specify in a defect report, as they provide essential information for identifying, tracking and resolving defects.

  Verified

  References: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 3, page 32-33.

• Question 5:

  A Test Manager conducts risk assessment for a project. One of the identified risks is: The sub-contractor may fail to meet his commitment". If this risk materializes. it will lead to delay in completion of testing required for the current cycle.

  Which of the following sentences correctly describes the risk?

  A. It is a product risk since any risk associated with development timeline is a product risk.
  B. It is no longer a risk for the Test Manager since an independent party (the sub-contractor) is now managing it
  C. It is a object risk since successful completion of the object depends on successful and timely completion of the tests
  D. It is a product risk since default on part of the sub-contractor may lead to delay in release of the product
  D. It is a product risk since default on part of the sub-contractor may lead to delay in release of the product

  ---

  Explanation

  A product risk is a risk that affects the quality or timeliness of the software product being developed or tested. Product risks are related to the requirements, design, implementation, verification, and maintenance of the software product. The

  risk of the sub-contractor failing to meet his commitment is a product risk, as it could cause a delay in the completion of the testing required for the current cycle, which in turn could affect the release date of the product. The release date is an

  important aspect of the product quality, as it reflects the customer satisfaction and the market competitiveness of the product.

  The other options are not correct because:

  A. It is not true that any risk associated with development timeline is a product risk. Some risks could be project risks, which are risks that affect the management or control of the software project, such as budget, resources, schedule, or communication. For example, a risk of losing a key project stakeholder is a project risk, not a product risk.

  B. It is not true that the risk is no longer a risk for the Test Manager since an independent party is managing it. The Test Manager is still responsible for ensuring that the testing activities are completed according to the test plan and the quality objectives. The Test Manager should monitor and control the sub-contractor's performance and communicate with him regularly to identify and mitigate any potential issues or deviations.

  C. It is not clear what is meant by "object" in this option, but it could be interpreted as the software system under test or the test object. In any case, the risk is not an object risk, as it does not affect the successful completion of the object, but rather the successful completion of the testing of the object. An object risk could be a risk that affects the functionality, reliability, usability, efficiency, maintainability, or portability of the software system under test. For example, a risk of the software system having a high complexity or a low testability is an object risk, not a product risk.

  References: 1 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 97 2 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 98 3 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 99 4 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 100 5 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 101 6 ISTQB Certified Tester Foundation Level Syllabus v4.0, 2023, p. 102

• Question 6:

  Which is an advantage of using testers that are independent from the development team?

  A. Independent testers support the developers with their feedback on coding rules and architecture design.
  B. Developers can delegate their sense of responsibility for quality to testers.
  C. Independent testers have a different perspective and can find defects that developers miss.
  D. Independent testers will identify themselves more with the project and the project goals and have good relations with the development team.
  C. Independent testers have a different perspective and can find defects that developers miss.

  ---

  Explanation

• Question 7:

  Consider the following user story and its acceptance criteria :

  User Story:

  As a member of the "Agnotoly" association, I want to be able to pay the association's dues through an automatic payment method so that I can forget about payment deadlines.

  Acceptance Criteria:

  1.The member can only pay with `Agnesis Master' credit card .

  2.The member must register their cell phone number .

  3.The member must register the credit card in the payment system.

  4.The member must select a payment method (monthly or annual) .

  5.The member must accept the terms and conditions for the selected method.

  6.If terms and conditions are accepted, the system sends an OTP (one-time password) to the member's phone for verification.

  7.The payment method is registered only after OTP verification .

  8.Once the payment method is registered, the system will charge on the first business day of the following month.

  Test Cycle Results:

  1.Members successfully paid dues using the credit card.

  2.Payments were processed monthly and for over a year .

  Which ONE of the following options identifies the acceptance criteria that has NOT been fully covered?

  A. Acceptance criteria 8 has not been fully covered during the above test cycle.
  B. Acceptance criteria 4 has not been fully covered during the above test cycle.
  C. All acceptance criteria have been fully covered during the above test cycle.
  D. Acceptance criteria 6 has not been fully covered during the above test cycle.
  A. Acceptance criteria 8 has not been fully covered during the above test cycle.

  ---

  Explanation

  Comprehensive and Detailed In-Depth Explanation:

  Acceptance criteria 8 states that the system should charge the user on the first business day of the following month . However, the test cycle only verified monthly payments for over a year , without confirming whether payments were processed specifically on the first business day .

  (B)

  is incorrect because the test validated monthly and annual payment options .

  (C)

  is incorrect because not all criteria were fully validated.

  (D)

  is incorrect because OTP verification (6) was tested as part of registration.

  Ensuring timely execution of payments (Criteria 8) requires additional validation.

  ISTQB CTFL v4.0 Syllabus, Section 5.1.5 ?Test Prioritization and Acceptance Testing

• Question 8:

  A mid-size software product development company has analyzed data related to defects detected in its product and found out that detects fixed in earlier builds are getting re-opened after a few months.

  The company management now seeks your advice in order to reverse this trend and prevent re-opening of defects fixed earlier.

  What would be your FIRST recommendation to the company?

  A. Automate existing test suits so that lesser time is spent on execution of each test, and more tests can be executed m the available time thus leading to a lower probability of defects slipping by
  B. Verify existing regression test suite are adequate, and augment it, if required, in order to ensure that defects fixed earlier get re-tested in each subsequent build
  C. Analyze the product modules containing maximum defects, and get them thoroughly tested and defects fixed as a one-time activity
  D. If required, tram the teams responsible for development and testing of the modules containing maximum number of defects, and if this does not help, replace them with more knowledgeable people
  B. Verify existing regression test suite are adequate, and augment it, if required, in order to ensure that defects fixed earlier get re-tested in each subsequent build

  ---

  Explanation

  Regression testing is a type of testing that verifies that previously tested software still performs correctly after changes. Regression testing can help prevent re-opening of defects fixed earlier by ensuring that they do not cause any new failures or side effects. The first recommendation to the company is to verify existing regression test suite are adequate, and augment it, if required, in order to ensure that defects fixed earlier get re-tested in each subsequent build. This can help improve the coverage and effectiveness of regression testing and detect any regression defects as soon as possible. Automating existing test suites may also help reduce the time and effort required for regression testing, but this is not the first recommendation, as automation may not be feasible or cost-effective for all test cases. Analyzing the product modules containing maximum defects and getting them thoroughly tested and defects fixed as a one-time activity may also help reduce the defect density and improve the quality of those modules, but this is not the first recommendation, as it does not address the root cause of re-opening defects fixed earlier. Training or replacing the teams responsible for development and testing of the modules containing maximum number of defects may also help improve their skills or performance, but this is not the first recommendation, as it may not be necessary or appropriate for all teams. Verified

  References: [A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer], Chapter 2, page 19; Chapter 4, page 45.

• Question 9:

  Which of the following is an INCORRECT statement about the benefit of traceability between the test basis and test work products?

  A. Traceability may be required by IT governance rules
  B. Traceability may help evaluate the extent of test coverage
  C. Traceability may allow testing to be auditable
  D. Traceability may make it harder to understand the impact of changes
  D. Traceability may make it harder to understand the impact of changes

  ---

  Explanation

  The statement "Traceability may make it harder to understand the impact of changes" is incorrect. Traceability in testing actually facilitates understanding the impact of changes by linking test cases to requirements. This linkage helps ensure

  that any changes in the requirements are adequately reflected and verified in the test cases, thus supporting effective management of changes and maintaining the integrity of the system or product being developed (ISTQB not-for-profit

  association) (ISTQB Main Web).

  References:

  ISTQB Certified Tester Foundation Level Syllabus v4.0: https://istqb-main-web-prod.s3.amazonaws.com /media/documents/ISTQB_CTFL_Syllabus-v4.0.pdf ISTQB Official Website - CTFL Certification: https://www.istqb.org/certifications/

  certified-tester-foundation- level/

• Question 10:

  Which of the following statements about test reports are TRUE?

  I- Test reports shall be approved by the test team.

  II- Test reports shall give stakeholders information as basis for decisions.

  Ill- Test reports shall summarize what happened through a period of testing.

  IV- Test reports shall be approved by the development team, the test team and the customer

  V- Test reports shall include information about remaining risks.

  A. II, III, V
  B. I, II, IV
  C. I, III, V
  D. II, III, IV
  A. II, III, V

  ---

  Explanation

  Statements II, III and V are true about test reports. Test reports are documents that provide information on the results and status of testing activities for a given period or phase. Test reports should give stakeholders information as basis for decisions, such as whether to release the software product, whether to continue testing, whether to change the scope or priorities of testing, etc. Test reports should summarize what happened through a period of testing, such as what test cases were executed, what defects were found, what risks were identified, what issues were encountered, what achievements were made, etc. Test reports should include information about remaining risks, such as what defects are still open, what test cases are still pending, what functionalities are still untested, what uncertainties are still unresolved, etc. Statements I and IV are not true about test reports. Test reports do not need to be approved by the test team, the development team, or the customer, unless it is specified by the test policy or the test plan. Test reports only need to be reviewed and verified by the test leader or the test manager before being distributed to the intended recipients. Verified

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