ISQI CTFL-AT Online Practice Questions and Exam Preparation

ISQI CTFL-AT Online Questions & Answers

• Question 41:

  You have been asked to explain to your client how to define acceptance criteria that are fully testable. Which of the following is the BEST EXAMPLE for testable acceptance criteria?

  A. The ID field must accept input value of a length between 2 and 10 characters.
  B. The interface to External System shall be specified.
  C. Action Reopen must be available only for a user with a specific authorization level.
  D. The program's icon should be clear and attractive.
  A. The ID field must accept input value of a length between 2 and 10 characters.

  ---

  According to the ISTQB Tester Foundation Level Agile Tester syllabus, acceptance criteria are a set of conditions that a user story must satisfy to be accepted by the customer or stakeholder. Acceptance criteria should be testable, meaning that they can be verified by objective measurements or observations. Testable acceptance criteria should be clear, unambiguous, complete, and consistent. Therefore, option A is the best example for testable acceptance criteria, as it specifies a clear and measurable

  condition for the input value of the ID field.

  Option B is not a good example for testable acceptance criteria, as it is vague and does not define any specific condition or expectation for the interface to External System.

  Option C is not a good example for testable acceptance criteria, as it is incomplete and does not specify what the specific authorization level is or how it is determined.

  Option D is not a good example for testable acceptance criteria, as it is subjective and not measurable. What is clear and attractive for one user may not be for another.

  References:

  ISTQB Tester Foundation Level Agile Tester syllabus, section 1.1.1, page 7; ISTQB Tester Foundation Level Agile Tester syllabus, section 1.1.2, page 8; ISTQB Tester Foundation Level Agile Tester syllabus, section 3.1.1, page 23; ISTQB Tester Foundation Level Agile Tester syllabus, section 3.1.2, page 24.

• Question 42:

  Which one of the following is a testable acceptance criterion?

  A. The solution shall support business processes.
  B. The system shall be easy to use.
  C. The response time to confirm a customer submission must not exceed 5 seconds.
  D. The tools for testing are tested before use and are meeting the requirements.
  C. The response time to confirm a customer submission must not exceed 5 seconds.

  ---

  A testable acceptance criterion is a condition that can be verified or measured objectively by the tester, customer, or stakeholder. It should be specific, measurable, achievable, relevant, and time-bound (SMART). A testable acceptance criterion should also be written from the user's perspective, achievable within the sprint, and written before development begins.

  Among the four options, only option C meets these criteria. It is specific (the response time to confirm a customer submission), measurable (must not exceed 5 seconds), achievable (within the technical and business constraints), relevant (to the user's needs and expectations), and time-bound (must be met in every sprint). It is also written from the user's perspective, testable (by measuring the response time), and written before development (as part of the user story definition).

  Option A is not testable because it is vague and subjective. What does it mean to support business processes? How can this be verified or measured?

  Option B is also not testable because it is subjective and ambiguous. What does it mean to be easy to use? How can this be verified or measured?

  Option D is not testable because it is not written from the user's perspective. It is an internal quality criterion for the testing team, not an acceptance criterion for the product or feature.

  References:

  ISTQB Foundation Level Agile Tester Syllabus, Section 2.3.2, page 182;

• Question 43:

  Which of the following describes a direct benefit of early and frequent feedback associated with the adoption of continuous integration?

  A. Detecting and isolating code quality problems early
  B. Reducing the need of conducting retrospectives
  C. Making quality everyone's responsibility
  D. Eliminating communication problems within the team
  A. Detecting and isolating code quality problems early

  ---

  From the CTFL-AT Syllabus v4.0, Section 4.2 Continuous Integration, it describes:

  “A major benefit of continuous integration is the ability to detect integration problems, code defects, and broken builds early, allowing for faster resolution.”

  And:

  “Continuous integration allows frequent builds and tests to be performed, helping to identify and isolate problems soon after they are introduced.”

  This directly confirms that Option A is the correct answer, highlighting the core value of continuous integration: early detection and isolation of issues.

  Option B is incorrect - retrospectives remain essential in Agile regardless of CI.

  Option C is an Agile principle, but not a direct benefit tied specifically to CI.

  Option D overstates the impact of CI - while CI may help communication, it does not eliminate communication problems by itself.

  References:

  CTFL-AT Syllabus v4.0, Section 4.2, Learning Objective (K2): Understand the benefits of continuous integration in Agile.

• Question 44:

  An Agile team uses a burndown chart and a task board to track progress within each iteration. In the burndown chart, the x-axis represents the days of iteration, while the y-axis represents the story points. The task board uses columns: "To Do", "Ongoing", "Done".

  A user story for the current iteration has 20 story points and 4 tasks (T1, T2, T3, T4). At the end of Day 5, all are in "Ongoing". At the end of Day 6, T1 and T2 move to "Done", while T3 and T4 remain "Ongoing".

  Which of the following statements would you expect most likely to be true at the end of Day 6?

  A. The burndown chart should be updated with a number of 10 burned story points
  B. The burndown chart must be changed to represent the unit of work in hours because story points cannot be used
  C. The burndown chart should not be updated because T3 and T4 are not "Done" yet
  C. The burndown chart should not be updated because T3 and T4 are not "Done" yet

  ---

  From CTFL-AT Syllabus v4.0, Section 5.4 Progress Tracking, it explains: "Burndown charts track completed story points, which are only counted when the entire user story is 'done'."

  SinceT3 and T4 are not complete, and the user story is only complete when all its tasks are done, the story points are not yet burned. So, Option C is correct.

  Option A is incorrect partial completion does not burn partial story points.

  Option B misrepresents the chart's purpose 'story points remain the unit.

  References:

  CTFL-AT Syllabus v4.0, Section 5.4 Learning Objective (K2) . Understand how progress is tracked in Agile

• Question 45:

  Which agile development approach incorporates the following practices:

  a project is divided into iterations called sprints

  each sprint results in a potentially releasable/shippable product?

  A. Kanban
  B. Extreme Programming
  C. Continuous Integration
  D. Scrum
  D. Scrum

  ---

  Scrum is an agile development approach that incorporates the following practices:

  a project is divided into iterations called sprints, which are typically 2-4 weeks long each sprint starts with a planning meeting, where the team selects a subset of user stories from the product backlog to work on each sprint ends with a review meeting, where the team demonstrates the potentially releasable /shippable product increment to the stakeholders and collects feedback each sprint also includes a retrospective meeting, where the team reflects on the process and identifies areas for improvement.

  References:

  1: ISTQB® Foundation Level Agile Tester Syllabus, Section 2.1, Agile Software Development

  2: ASTQB Agile Tester Certification Resources, Section 2.1, Agile Software Development

  3: What is Agile? | Atlassian

• Question 46:

  You have been asked to execute an exploratory testing session on Park and Ride system. The test charter has been titled as Buy a bus ticket. As a result, a number of defects were reported, the titles of which are listed below. Which defect is out of scope for the given test charter?

  A. Price for a bus ticket was calculated incorrectly.
  B. Failed to buy a bus ticket after 18:00.
  C. Failed to buy a bus ticket when the network connection to the Central System is down.
  D. Payment for parking ticket is restricted to cash only (no credit card supported).
  D. Payment for parking ticket is restricted to cash only (no credit card supported).

  ---

  The test charter for the exploratory testing session is focused on buying a bus ticket, not a parking ticket. Therefore, any defect related to the payment for parking ticket is out of scope for the given test charter. The other defects are related to the functionality, usability, or reliability of buying a bus ticket, which are in scope for the test charter.

• Question 47:

  Which of the following statements about test automation and regression risk in Agile projects is true?

  A. Automated unit tests are generally not run with each code check-in as they take longer to run than automated acceptance tests and could slow down the code check-in process
  B. Regression risk is reduced when there is a high degree of code changes being applied from one iteration to the next
  C. Technical debt is due to manual testing and it cannot be present when the team implements test automation
  D. Test automation can help to manage regression risk since it allows the running of regression test suites within each iteration
  D. Test automation can help to manage regression risk since it allows the running of regression test suites within each iteration

  ---

  From CTFL-AT Syllabus v4.0, Section 4.3 Test Automation and Continuous Integration, it states: "Automated tests help detect regression defects quickly and can be run frequently during development, thus reducing regression risk."

  So, Option D is correct test automation supports regression testing within iterations, making it an essential Agile practice.

  Option A is false automated unit tests are designed to be fast and are ideally run with every check-in.

  Option B is incorrect more code changes increase, not reduce, regression risk.

  Option C is incorrect technical debt can still exist with automation if the automation is poorly designed or not maintained.

  References:

  CTFL-AT Syllabus v4.0, Section 4.3 Learning Objective (K2) . Understand how automation supports regression testing

• Question 48:

  Which of the following is the BEST way for a test team to keep its independence when working in an Agile development environment?

  A. Share the Test Strategy with the Agile development team, but not the details of the Test Cases.
  B. Locate the team that develops the test automation framework in a different location to the Agile development team.
  C. Assign testers to be members of the Agile team, but ensure the testers report to a different manager than the developers.
  D. Co-locate only some of the testers with the Agile development team, while the rest of the testers are in a different location.
  C. Assign testers to be members of the Agile team, but ensure the testers report to a different manager than the developers.

  ---

  According to the ISTQB Tester Foundation Level Agile Tester syllabus, one of the key principles of agile testing is that testers are integrated into the agile team and work closely with developers and other stakeholders. However, this does not mean that testers lose their independence or objectivity. Testers should still be able to provide an unbiased view of the quality of the software and challenge the assumptions and decisions made by the team. Therefore, option C is the best way for a test team to keep its

  independence when working in an agile development environment, as it allows testers to be part of the agile team, but also report to a different manager than the developers, who can support their professional development and ensure their independence.

  Option A is not a good way to keep independence, as it limits the transparency and collaboration between testers and developers, which are essential for agile testing.

  Option B is also not a good way to keep independence, as it creates a physical and organizational barrier between the test automation team and the agile development team, which can hinder communication and feedback.

  Option D is also not a good way to keep independence, as it creates an inconsistency and imbalance between the testers who are co-located with the agile development team and those who are not, which can affect the quality and efficiency of the testing process.

  References:

  ISTQB Tester Foundation Level Agile Tester syllabus, section 1.2.1, page 91;

  ISTQB Tester Foundation Level Agile Tester syllabus, section 1.2.2, page 101;

  ISTQB Tester Foundation Level Agile Tester syllabus, section 2.1.1, page 141;

  ISTQB Tester Foundation Level Agile Tester syllabus, section 2.2.1, page 161;

  ISTQB Tester Foundation Level Agile Tester syllabus, section 2.2.2, page 171.

• Question 49:

  Which of the following statements BEST reflects a key challenge of Agile regression testing?

  A. Regression tests never need maintenance
  B. Frequent changes increase regression risk
  C. Regression testing is unnecessary in Agile
  D. Regression testing is performed only once per release
  B. Frequent changes increase regression risk

  ---

  From CTFL-AT Section 4.3, rapid and frequent code changes elevate regression risk in Agile.

  Option B directly captures this challenge.

  Options A, C, and D are incorrect.

  References:

  CTFL-AT Syllabus v4.0, Section 4.3

• Question 50:

  User Story: As a user I want to be able to calculate tax percentage based on amount of income. What is the best black box test design technique for verifying the accuracy of this user story?

  A. Statement testing - test all statements in income calculation.
  B. User story testing - test that the user can enter an income amount and get a result.
  C. State transition testing - test all states of income entry.
  D. Equivalence partitioning - test with low, medium and high income.
  D. Equivalence partitioning - test with low, medium and high income.

  ---

  The best black-box test design technique for verifying the accuracy of this user story is equivalence partitioning. Equivalence partitioning is a technique that divides the input domain of a system into classes or groups that are expected to behave similarly. By testing one value from each class, the tester can reduce the number of test cases while still achieving good coverage.

  In this case, the input domain of the system is the amount of income, which can be divided into classes based on the tax percentage applied to different income ranges. For example, if the tax percentage is 10% for income below 10,000, 20% for income between 10,000 and 20,000, and 30% for income above 20,000, then the equivalence classes are: low income (<10,000), medium income (10,000–20,000), and high income (>20,000).

  By testing one value from each class, such as 5,000, 15,000, and 25,000, the tester can verify that the system calculates the correct tax percentage for each income range. This technique is more efficient and effective than testing all possible values of income, testing only one value of income, testing the states of income entry, or testing the statements in income calculation.