ISQI CTFL-AT Online Practice Questions and Exam Preparation

ISQI CTFL-AT Online Questions & Answers

• Question 51:

  Iteration planning for Sprint 5 of your current project is complete. The plan for the sprint is to increase performance of the system, which of the following acceptance criteria would you expect for Sprint 5?

  1) User access for all roles has been validated.

  2) A static analysis tool has been executed for all code.

  3) 100% of the existing regression test suite has passed.

  4) System is responding in less than 3 seconds, 90% of the time.

  5) A new version of internet Explorer has been included.

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

  ---

  The acceptance criteria for a sprint are the conditions that must be met for the user stories to be considered done and deliver value to the customer. The acceptance criteria should be specific, measurable, achievable, relevant, and testable. In this case, the plan for the sprint is to increase the performance of the system, so the acceptance criteria should reflect that goal.

  Therefore, the acceptance criteria that would be expected for Sprint 5 are:

  100% of the existing regression test suite has passed.

  This criterion ensures that the system has not introduced any new defects or broken any existing functionality while improving performance.

  System is responding in less than 3 seconds, 90% of the time.

  This criterion defines a clear and quantifiable performance target that can be verified by testing.

  The other options are not relevant or appropriate acceptance criteria for Sprint 5:

  User access for all roles has been validated.

  This criterion is not related to the performance of the system, but rather to the security or functionality of the system. It might be an acceptance criterion for a different sprint or user story, but not for Sprint 5.

  A static analysis tool has been executed for all code.

  This criterion is not a customer-facing requirement and does not directly reflect performance improvements.

• Question 52:

  Which of the following statements about Agile retrospectives is true?

  A. Agile retrospectives should focus exclusively on improving negative aspects, without wasting time in discussions on what worked well during the iteration
  B. All of the improvements identified in an Agile retrospective must be implemented as soon as possible during the next iteration
  C. Metrics such as burndown charts, velocity, and number of stories completed could be effectively used during Agile retrospectives for process improvement
  D. An Agile retrospective should be held at the end of an iteration only when the number of story points completed by the team in that iteration is lower than the team velocity
  C. Metrics such as burndown charts, velocity, and number of stories completed could be effectively used during Agile retrospectives for process improvement

  ---

  From the CTFL-AT Syllabus v4.0, Section 5.1 Agile Retrospectives and Process Improvement, it states: "Retrospectives are used to reflect on what went well and what could be improved. They should include qualitative insights and quantitative measures such as velocity, burndown charts, and number of stories completed."

  Therefore, Option C is correct, as using metrics to support process improvement is arecommended best practicein retrospectives.

  Option A is incorrect, retrospectives should include what went well, not just negatives.

  Option B is inaccurate, not all improvements must be implemented immediately; they are prioritized and planned based on capacity and impact.

  Option D is false, retrospectives are held at the end of every iteration, regardless of story points completed.

  References:

  CTFL-AT Syllabus v4.0, Section 5.1 Learning Objective (K2) . Understand the purpose and outcomes of retrospectives

• Question 53:

  An Agile project is aimed at developing an e-commerce website that will allow registered users to purchase digital books. During the checkout process, only credit card payments, with supported credit card types, will be accepted.

  Consider the following acceptance criterion for a given user story of this Agile project:

  "Check that the number of steps required to complete a purchase order during the checkout process is minimized, in order to reduce the risk that the customers will leave the website without completing their orders."

  Which of the following information would you expect to be the most relevant to create a test aimed at covering this acceptance criterion?

  A. The maximum number of digital books that can be purchased in a single order
  B. The supported credit card types
  C. The maximum number of steps to complete the registration process
  D. The maximum number of steps to complete the checkout process
  D. The maximum number of steps to complete the checkout process

  ---

  From CTFL-AT Syllabus v4.0, Section 2.1 Acceptance Criteria and Testability, it states: "Tests should directly address the acceptance criteria defined for a user story. Testers evaluate if the implemented feature meets the criteria, often using quantitative data like number of steps, time taken, or interaction patterns."

  The acceptance criterion specifically refers to minimizing steps during checkout, so Option D is most directly aligned with what needs to be tested.

  Options A, B, and Care unrelated to the acceptance criterion's goal of reducing abandonment due to complex checkout.

  References:

  CTFL-AT Syllabus v4.0, Section 2.1 Learning Objective (K2) . Understand testability of acceptance criteria

• Question 54:

  Consider the following user story for an Agile project aimed at developing an application that calculates the reimbursement of medical visits:

  "As an owner of the application, I want the reimbursement of medical visits to be calculated based on the following rules:

  There are two types of reimbursable visits: Doctor's Office Visits (DOCVs) and Hospital Visits (HVs).

  The reimbursement for DOCVs is 33%, while the reimbursement for HVs depends on the type of the specialist visits. Two types (A, B) of specialist visits exist and the associated reimbursements are 45% for A and 90% for B."

  Which of the following would you expect to be the most suitable black-box test design technique for the user story?

  A. Decision table testing
  B. Equivalence partition testing
  C. Use case testing
  D. State transition testing
  A. Decision table testing

  ---

  From CTFL-AT Syllabus v4.0, Section 3.1 Testing Techniques and Agile, it states: "Decision table testing is useful when the outcome depends on combinations of inputs or rules."

  In this case,different reimbursement percentagesare determined based ontypes of visits and subtypes, making Option A (Decision Table Testing) the ideal technique.

  Option B focuses on single input ranges, less suitable here.

  Option C suits end-to-end scenarios but not logic-driven calculations.

  Option D applies to state-based systems, which this is not.

  References:

  CTFL-AT Syllabus v4.0, Section 3.1 Learning Objective (K3) . Apply appropriate test design techniques in Agile

• Question 55:

  Which of the following statements is TRUE about test automation in Agile?

  A. Only testers write automated tests
  B. Automation should support fast feedback loops
  C. Automation replaces all exploratory testing
  D. Automation must be implemented only at the UI level
  B. Automation should support fast feedback loops

  ---

  CTFL-AT Section 4.3 states that automation is essential to accelerate feedback in Agile iterations.

  Option A is incorrect - whole team contributes.

  Option C is false - exploratory testing remains valuable.

  Option D contradicts the test pyramid.

  References:

  CTFL-AT Syllabus v4.0, Section 4.3

• Question 56:

  You are working on an Agile project and have been asked to implement exploratory testing for the current sprint. Which one of the following is a correct approach to adopt?

  A. Allocate independent testers to design exploratory tests using test charters in time boxed sessions. Plan to run all sessions in parallel with each session lasting more than 5 hours.
  B. Ask experienced testers to try and find new defects by using the system without the constraint of documentation and tools.
  C. Use testers who have not been involved in the sprint to write new test cases from the user stories. These test cases are then executed in a time boxed session for the sprint.
  D. Ask experienced testers to prepare test charters for time boxed sessions lasting no more than 2 hours. Tests should be designed and executed within each session using heuristics, creativity and intuition.
  D. Ask experienced testers to prepare test charters for time boxed sessions lasting no more than 2 hours. Tests should be designed and executed within each session using heuristics, creativity and intuition.

  ---

  Exploratory testing is a testing approach that emphasizes learning, creativity, and adaptability. It involves simultaneous test design and test execution, where the tester uses heuristics, intuition, and experience to explore the system under test and discover new information. Exploratory testing can be performed in an Agile project to complement other testing activities, such as test-driven development, behavior-driven development, and acceptance test-driven development.

  The correct approach to adopt for exploratory testing in an Agile project is D, as it follows the best practices for exploratory testing:

  Ask experienced testers to prepare test charters for time-boxed sessions lasting no more than 2 hours:

  A test charter is a brief document that describes the scope, objective, and strategy of an exploratory testing session. A test charter helps guide the tester's exploration and document the results. A time box is a fixed period allocated for an exploratory session. It helps keep focus and limits scope. A time box should not be too long, as it may reduce concentration and creativity. A recommended duration is between 45 minutes and 2 hours.

  Tests should be designed and executed within each session using heuristics, creativity, and intuition:

  Exploratory testing is iterative and interactive. The tester designs and executes tests based on observations and feedback from the system. The tester uses heuristics (rules of thumb that help simplify complex problems), along with creativity and intuition, to generate test ideas and make informed decisions.

  The incorrect approaches to adopt for exploratory testing in an Agile project are A, B, and C, as they violate the principles and practices of exploratory testing:

  Option A: Allocate independent testers to design exploratory tests using test charters in time-boxed sessions. Plan to run all sessions in parallel with each session lasting more than 5 hours:

  This approach is incorrect because it separates test design from test execution, which contradicts the core of exploratory testing. It also uses excessively long time boxes, which can harm focus and creativity. Additionally, it reduces collaboration within the Agile team by isolating testers from developers and stakeholders.

  Option B: Ask experienced testers to try and find new defects by using the system without the constraint of documentation and tools:

  This approach is incorrect because it does not use test charters, which are essential for guiding and documenting exploratory testing sessions. It also overlooks heuristics, creativity, and intuition as structured methods for generating test ideas. It suggests that exploratory testing is random and unstructured, which is a misconception—exploratory testing is disciplined and systematic.

  Option C: Use testers who have not been involved in the sprint to write new test cases from the user stories. These test cases are then executed in a time-boxed session for the sprint:

  This approach is incorrect because it separates test design from execution. It also uses testers who were not part of the sprint, which may limit their understanding of the product and user needs. It does not use test charters and does not rely on heuristics, creativity, or intuition, all of which are essential to exploratory testing.

• Question 57:

  Consider an Agile team using a development practice with these steps:

  Write a failing test for a small piece of code Make the test pass by implementing minimal code Refactor the code Repeat the process with additional small functionality

  Which one of the following testing quadrants would the tests produced with this practice be part of?

  A. Q4 - Technology-facing tests that critique the product
  B. Q2 - Business-facing tests that support the team
  C. Q3 - Business-facing tests that critique the product
  D. Q1 - Technology-facing tests that support the team
  D. Q1 - Technology-facing tests that support the team

  ---

  From CTFL-AT Syllabus v4.0, Section 3.2 Test-Driven Development, and Section 3.4 Testing Quadrants:

  “TDD focuses on writing unit tests before code is implemented. These are technology-facing tests that support the team and are categorized under Q1.”

  Therefore, Option D is correct.

  Option A involves performance/security testing.

  Options B and C involve business-facing tests, not applicable to TDD.

  References:

  CTFL-AT Syllabus v4.0, Sections 3.2 and 3.4

  Learning Objective (K2) – Identify test types and quadrants.

• Question 58:

  Consider the estimation of a given user story performed separately by two different teams (Team A and Team B) using the Planning Poker technique. Both teams consist of five members and use a deck of cards (0, 1, 2, 3, 5, 8, 13, 20).

  Team A quickly decides on an estimate of 8 story points after four rounds, with no discussions between rounds.

  Team B arrives at 3 story points after three rounds, with discussions between the lowest and highest estimators after each round.

  Which of the following statements would you expect most likely to be true in this scenario?

  A. Team B estimates that the user story can be "done" with significantly less effort in absolute terms than what was estimated by Team A
  B. Team A has a better estimation process than Team B because at the end of the last round, all five team members estimates are an exact match
  C. In the estimation process, Team B, unlike Team A, can take advantage of the discussions that represent an important benefit of using Planning Poker
  D. Both Team A and B have an ineffective estimation process because the best estimate is the average of the results of the first round of estimation
  C. In the estimation process, Team B, unlike Team A, can take advantage of the discussions that represent an important benefit of using Planning Poker

  ---

  From CTFL-AT Syllabus v4.0, Section 2.2 Release and Iteration Planning, it describes Planning Poker as: "Planning Poker involves group discussion, especially from the highest and lowest estimators, to ensure that different perspectives and assumptions are aligned, which leads to more accurate and shared understanding of the effort involved."

  Thus, Option C is correct Team B uses discussion-based estimation, which is a core benefit of Planning Poker.

  Option A is speculative we cannot know the actual effort difference.

  Option B is incorrect convergence without discussion may indicate lack of engagement or pressure to agree.

  Option D is false Planning Poker is not based on averaging, but on consensus.

  References:

  CTFL-AT Syllabus v4.0, Section 2.2 Learning Objective (K2) . Understand the purpose and benefit of Planning Poker

• Question 59:

  A calculator application is being developed. The third sprint has been planned to add functionality to the calculator to allow scientific calculations.

  Which TWO examples below represent activities that would likely be managed on an agile task board for the third sprint?

  1) A task to design the features planned for the next sprint.

  2) A task to run an acceptance test for a user story.

  3) A task to automate regression tests.

  4) A task to participate in training in preparation for the fourth sprint.

  5) A task to produce a daily progress report for the agile team members.

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

  ---

  According to the ISTQB Tester Foundation Level Agile Tester syllabus, an agile task board is a visual tool that displays the status of the work items in an agile sprint. The task board typically shows the user stories, tasks, and their progress from to do to done. The task board helps the agile team monitor and coordinate their work, and communicate with stakeholders. Therefore, the examples that represent activities that would likely be managed on an agile task board for the third sprint are those that are

  related to the user stories, tasks, and their progress in the current sprint.

  Option A is the correct answer, as it contains two examples of such activities: running an acceptance test for a user story and automating regression tests. These are both tasks that are part of the testing process in the current sprint, and their status can be tracked on the task board.

  Option B is not a correct answer, as it contains two examples of activities that are not related to the current sprint: designing the features planned for the next sprint and participating in training in preparation for the fourth sprint. These are both activities that are part of the planning or learning process for future sprints, and they are not managed on the task board.

  Option C is also not a correct answer, as it contains two examples of activities that are not related to the current sprint: participating in training in preparation for the fourth sprint, and producing a daily progress report for the agile team members. These are both activities that are part of the learning or reporting process, and they are not managed on the task board.

  Option D is also not a correct answer, as it contains two examples of activities that are not related to the current sprint: designing the features planned for the next sprint, and producing a daily progress report for the agile team members. These are both activities that are part of the planning or reporting process, and they are not managed on the task board.

  References:

  ISTQB Tester Foundation Level Agile Tester syllabus, Section 2.1.1, page 14; Section 2.1.2, page 15; Section 2.2.1, page 16; Section 2.2.2, page 17.

• Question 60:

  Which of the following statements best describes a key benefit of involving testers early during backlog refinement?

  A. It ensures testers can create the complete regression test suite before development begins
  B. It helps identify unclear acceptance criteria and potential risks before development starts
  C. It prevents developers from estimating user stories until testers approve them
  D. It ensures all user stories are fully documented before entering the sprint
  B. It helps identify unclear acceptance criteria and potential risks before development starts

  ---

  Early tester involvement is emphasized in the CTFL-AT Syllabus (Section 2.1 and 2.2), which stresses collaboration to refine user stories, identify ambiguities, and clarify acceptance criteria.

  Option B aligns with this guidance by highlighting that testers contribute their quality and risk perspective early, helping the team reduce rework, identify unclear conditions, and ensure that acceptance criteria are testable.

  Option A is incorrect because regression tests evolve across iterations, not upfront.

  Option C is incorrect because testers do not “approve” estimation; the team decides estimates collaboratively.

  Option D is incorrect because Agile avoids excessive documentation; refinement aims for clarity, not full documentation.

  References:

  CTFL-AT Syllabus v4.0, Sections 2.1–2.2

  Learning Objective (K2) – Understand tester contributions during refinement