ISQI CTFL-AT Online Practice Questions and Exam Preparation

ISQI CTFL-AT Online Questions & Answers

• Question 91:

  During a sprint, which activity MOST aligns with the purpose of the daily stand-up?

  A. Planning acceptance test criteria
  B. Identifying blockers that prevent progress
  C. Conducting root-cause analysis
  D. Writing automated regression tests
  B. Identifying blockers that prevent progress

  ---

  CTFL-AT Section 5.2 defines stand-ups as short meetings to report progress, plans, and impediments.

  Options A, C, and D are done outside stand-ups.

  References:

  CTFL-AT Syllabus v4.0, Section 5.2

• Question 92:

  During a planning meeting, the team identifies that a user story includes several complex business rules. Which test design technique is MOST appropriate?

  A. Boundary value analysis
  B. Decision table testing
  C. Use case testing
  D. Error guessing
  B. Decision table testing

  ---

  From CTFL-AT Section 3.1:

  Decision tables are ideal where multiple rules combine to determine outcomes.

  Option A applies to numeric ranges.

  Option C applies to workflow scenarios.

  Option D is intuitive but not systematic.

  References:

  CTFL-AT Syllabus v4.0, Section 3.1

• Question 93:

  Which of the following statements about Agile retrospectives is CORRECT?

  A. During Agile retrospectives, testers should be encouraged to provide constructive suggestions only on non-testing activities.
  B. In an Agile retrospective the moderator can encourage and make sure that good practices are kept by the team, by asking what the team is doing well.
  C. Agile retrospectives should be focused mainly on impediments that are outside the control of the team because these issues are more challenging.
  D. Unlike working sessions or meetings held in non-Agile projects, Agile retrospectives do not require follow-up activities.
  B. In an Agile retrospective the moderator can encourage and make sure that good practices are kept by the team, by asking what the team is doing well.

  ---

  An Agile retrospective is a regular meeting where the team reflects on their work process and identifies the areas for improvement. The following statements about Agile retrospectives are correct:

  During Agile retrospectives, testers should be encouraged to provide constructive suggestions on both testing and non-testing activities, as testing is an integral part of the Agile team and testers can contribute to the overall quality of the product and the process.

  In an Agile retrospective, the moderator can encourage and make sure that good practices are kept by the team, by asking what the team is doing well. This helps to reinforce the positive aspects of the team s work and to appreciate the team members efforts and achievements.

  Agile retrospectives should be focused mainly on impediments that are within the control of the team because these issues are more actionable and can be resolved by the team. Impediments that are outside the control of the team should also be discussed, but they may require the involvement of other stakeholders or external parties to be addressed.

  The following statement about Agile retrospectives is incorrect:

  Unlike working sessions or meetings held in non-Agile projects, Agile retrospectives do require follow.up activities. The team should agree on the action items that result from the retrospective and assign them to the responsible team members. The team should also monitor the progress and effectiveness of the action items in the next iteration and review them in the next retrospective.

  Therefore, the correct answer is B, as it is the only statement that is correct about Agile retrospectives.

  References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 24;

• Question 94:

  Based on the skills required for testers in Agile teams, which of the following activities would you expect least likely to be performed by testers in Agile projects?

  A. Tracking the failures of the unit tests that are written when using the Test-Driven Development practice
  B. Identifying and updating test cases from previous iterations that are affected by the changes made in the current iteration
  C. Working collaboratively with a developer to develop and test a feature
  D. Actively participating in specification workshops aimed at clarifying user stories through examples that will be transformed into tests
  A. Tracking the failures of the unit tests that are written when using the Test-Driven Development practice

  ---

  From CTFL-AT Syllabus v4.0, Section 3.2 Test-Driven Development, and 1.3 The Whole-Team Approach, testers:

  "Collaborate in test-related activities including test case creation, exploratory testing, and user story clarification."

  "Unit tests are typically the responsibility of developers, especially in TDD practices."

  Therefore, Option A is least likely, as unit test tracking in TDD is primarily adeveloper responsibility, not a tester's routine task.

  Options B, C, and D all describekey Agile tester activities, such as maintaining regression tests, collaborating with developers, and participating in specification workshops (BDD/ATDD practices) .

  References:

  CTFL-AT Syllabus v4.0, Sections 1.3, 3.2 Learning Objective (K2) . Understand tester roles and responsibilities in Agile

• Question 95:

  Which of the following statements about the differences between testing activities in Agile projects and traditional projects is true?

  A. In traditional V-model projects, there is a system test level that usually involves executing functional tests as well as non-functional tests, while in Agile projects there is never a system test level
  B. Because Agile projects tend to adopt test-first approaches, test automation in Agile projects is performed at lower test levels, while test automation in traditional projects is performed at higher test levels
  C. Risk-based testing can be adopted both in Agile projects and traditional projects. In Agile projects, the specific risks for all of the iterations are identified and assessed during release planning
  D. In traditional V-model projects, the different test phases are performed sequentially, while in Agile projects these phases are performed parallel to one another within each iteration
  D. In traditional V-model projects, the different test phases are performed sequentially, while in Agile projects these phases are performed parallel to one another within each iteration

  ---

  From CTFL-AT Syllabus v4.0, Section 2.4 Testing and Iterations, it states: "In Agile projects, testing activities are conducted in parallel with development activities within an iteration, unlike traditional models where testing is done after development."

  Therefore, Option D is correct, Agile promotes parallel testing, while traditional projects (e.g., V-model) follows equential phases.

  Option A is incorrect Agile projects do perform system testing, but it's integrated within iterations.

  Option B is misleading while Agile emphasizes lower-level test automation, traditional projects also use automation at various levels.

  Option C is partially correct but oversimplifies the process risks are reassessed iteratively, not just once during release planning.

  References:

  CTFL-AT Syllabus v4.0, Section 2.4 Learning Objective (K2) . Compare Agile vs traditional testing activities

• Question 96:

  Which of the following statements about the test pyramid is true?

  A. The test pyramid concept is based on the principle of eliminating defects as early as possible in the software lifecycle
  B. The test pyramid emphasizes having more automated tests at the higher test levels and a decreasing number of them at the lower test levels
  C. The test pyramid concept states that every software system consists always of four different test levels (unit, integration, system, acceptance)
  D. The test pyramid consists of four test levels with business-facing tests at the bottom of the pyramid and technology-facing tests at the top
  A. The test pyramid concept is based on the principle of eliminating defects as early as possible in the software lifecycle

  ---

  From CTFL-AT Syllabus v4.0, Section 4.1 The Test Pyramid, it states: "The test pyramid concept encourages more tests at lower levels (e.g., unit tests), with fewer tests at higher levels (e.g., system or UI tests), in order to find and fix defects as early as possible."

  Therefore, Option A is correct, the test pyramid supports early defect detection through a high volume of lower-level automated tests.

  Option B is incorrect, the test pyramid emphasizes more tests at lower levels, not higher.

  Option C is incorrect, Agile doesn't mandate four specific levels in every system.

  Option D misrepresents the pyramid technology-facing tests (e.g., unit tests) are at the bottom, not the top.

  References:

  CTFL-AT Syllabus v4.0, Section 4.1

  Learning Objective (K2) . Understand the purpose of the test pyramid

• Question 97:

  Which of the following statements about iteration and release planning is true?

  A. Release planning defines and re-defines the product backlog and provides the basis for a test approach and test plan spanning all iterations
  B. During release planning, testers add value by breaking down user stories into tasks (particularly testing tasks)
  C. During release planning, testers establish and prioritize the user stories for the release and then participate in the quality risk analysis for these stories
  D. Release plans cannot change as an Agile project proceeds, but iteration plans may change to accommodate new needs
  C. During release planning, testers establish and prioritize the user stories for the release and then participate in the quality risk analysis for these stories

  ---

  From the CTFL-AT Syllabus v4.0, Section 2.2 Release and Iteration Planning, testers actively contribute

  during release planning:

  "During release planning, testers collaborate with the team to understand the scope of the release and help identify any high-level test considerations. They also participate in quality risk analysis and help in estimating test effort."

  Furthermore, it is noted:

  "Testers are involved in defining and refining user stories and acceptance criteria, and contribute to quality risk assessments."

  Therefore, Option C is accurate as it reflects the tester's involvement inprioritizing user stories and conducting quality risk analysis during release planning.

  Option A is incorrect because defining and redefining the product backlog is primarily the role of the Product Owner, and the test approach is iteration-specific, not fixed for the full release.

  Option B is inaccurate, breaking down stories into tasks is generally part ofiteration (Sprint) planning, not release planning.

  Option D is incorrect, release plans can change in Agile to accommodate changing business needs.

  References:

  CTFL-AT Syllabus v4.0, Section 2.2 Learning Objective (K2) . Understand the role of the tester in release and iteration planning

• Question 98:

  Which of the following statements best describes test execution automation?

  A. The use of software to control the execution of tests and the comparison of actual results to expected results
  B. An approach to testing in which test activities are planned as uninterrupted sessions of test design and execution
  C. A way of developing software where automated test cases are developed before the software is developed to run those test cases
  D. The execution of the test process against a single and identifiable release of the test object
  A. The use of software to control the execution of tests and the comparison of actual results to expected results

  ---

  From CTFL-AT Syllabus v4.0, Section 4.3 Test Automation and Continuous Integration, and the ISTQB Glossary:

  "Test automation involves using software to execute tests, compare actual outcomes to expected outcomes, and report the results automatically."

  Thus, Option A correctly definestest execution automation.

  Option B describes session-based testing, not automation.

  Option C describesTest-Driven Development (TDD).

  Option D refers to test execution, not specifically automation.

  References:

  CTFL-AT Syllabus v4.0, Section 4.3 ISTQB Glossary Learning Objective (K1) . Recall what test execution automation involves