ISQI CTFL-AT Online Practice Questions and Exam Preparation

ISQI CTFL-AT Online Questions & Answers

• Question 11:

  Consider an online application that allows registered users to pay the annual car tax based on the vehicle's engine power in kW. Given the following user story:

  "As a customer I need the online application to calculate the annual car tax amount that I need to pay for my car:

  If the power of the vehicle is less than 20 kW, then the annual car tax is free

  If the power of the vehicle is more or equal than 20 kW but less or equal than 150 kW, then the annual car tax is 250 Euros

  If the power of the vehicle is more than 150 kW, then the annual car tax is 750 Euros"

  What is the MOST suitable use of a black-box test design technique for this user story?

  A. Decision table testing. Test the following conditions: Conditions = registered user logged in; inserted power of the vehicle = 20 kW; Action = car tax paid
  B. State transition testing. Test the transitions between the following states: logging in, inserting the power of the vehicle, making payment, logging out
  C. Equivalence partitioning. Test the annual car tax value for the following partitions: [power of the vehicle < 20 kW; 20 kW ≤ power of the vehicle ≤ 150 kW; power of the vehicle > 150 kW]
  D. Use case testing. Test the following use case (Actor = registered user): Pre-condition = registered user logged in Scenario = registered user inserts the power of the vehicle, makes payment, and logs out Post-condition = car tax paid and registered user logged out
  C. Equivalence partitioning. Test the annual car tax value for the following partitions: [power of the vehicle < 20 kW; 20 kW ≤ power of the vehicle ≤ 150 kW; power of the vehicle > 150 kW]

  ---

  Equivalence partitioning is a black-box test design technique that divides the input domain of a system into classes of data from which test cases can be derived. The idea is that if a system works correctly for a representative value from an equivalence class, it will work correctly for all values from that class, and vice versa. Equivalence partitioning reduces the number of test cases by eliminating redundant ones.

  For the given user story, equivalence partitioning is the most suitable technique because it can test the different outcomes of the annual car tax calculation based on the power of the vehicle, which is the main input for the system. By testing one value from each partition, the tester can verify the functionality of the system and detect any errors in the calculation logic.

  The other techniques are not as suitable because they do not focus on the input domain of the system, but rather on conditions, transitions, or scenarios that are not directly related to the user story.

  References:

  ISTQB® Foundation Level Agile Tester Syllabus, Version 2014, Section 2.2.2; ASTQB Agile Tester Certification Resources, Agile Testing Foundations, Chapter 3, Section 3.2.2.

• Question 12:

  Which of the following activities are done in release planning?

  1) Identifying testable user stories with acceptance criteria.

  2) Elaborating the user stories into tasks.

  3) Prioritizing the user stories.

  4) Creating acceptance tests for the user stories.

  5) Analyzing risks for each of the user stories.

  6) Performing high level estimation for the release.

  A. Activities 1, 4 and 6
  B. Activities 2 and 4
  C. Activities 2, 3 and 5
  D. Activities 1, 3 and 6
  D. Activities 1, 3 and 6

  ---

  Release planning is a process of defining the scope and timeline for an iterative or incremental product development project. It is used in agile or hybrid projects where a mid- to long-term planning of the product or system development or integration is required. Release planning involves the following activities:

  Identifying testable user stories with acceptance criteria. User stories are short descriptions of the features or functionalities that the customer or user wants from the product. Acceptance criteria are the conditions that must be met for the user story to be considered done and acceptable. Identifying testable user stories with acceptance criteria helps to define the scope and quality of the release.

  Prioritizing the user stories. User stories are prioritized based on the value they deliver to the customer or user, as well as the dependencies, risks, and costs associated with them. Prioritizing the user stories helps to determine the order and frequency of the releases.

  Performing high level estimation for the release. High level estimation is a technique to estimate the effort, time, and resources needed to complete the user stories in the release. High level estimation can be done using various methods, such as analogy, expert judgment, planning poker, etc. Performing high level estimation for the release helps to set realistic and achievable goals and deadlines.

  Therefore, activities 1, 3 and 6 are done in release planning. Activities 2, 4 and 5 are done in iteration planning, which is a more detailed and short-term planning of the work to be done in each iteration or sprint.

  References:

  1: ISTQB. Foundation Level Agile Tester Syllabus, Section 2.2, Fundamental Agile Testing Principles, Practices and Processes;

  2: Agile Release Planning in Hybrid and Agile Projects;

  3: How to Create an Agile Release Plan

• Question 13:

  Which of the following is a typical task performed by a tester within a Scrum team?

  A. Suggesting improvements in sprint retrospectives
  B. Coaching other team members in self-organization and cross-functionality
  C. Removing impediments to the Scrum team's progress
  D. Prioritizing the items in the product backlog
  A. Suggesting improvements in sprint retrospectives

  ---

  From CTFL-AT Syllabus v4.0, Section 5.1 and 5.3:

  "Testers, like all team members, participate in retrospectives and are encouraged to suggest improvements to team processes and product quality."

  So Option A is correct. Testers actively engage in retrospectives and suggest improvements based on their testing experience.

  Option B and C refer to Scrum Master responsibilities.

  Option D is the responsibility of the Product Owner.

  References:

  CTFL-AT Syllabus v4.0, Sections 5.1 and 5.3 Scrum Guide . Scrum Roles and Responsibilities Learning Objective (K1) . Recall tester tasks within Scrum teams

• Question 14:

  You are working in a team preparing a bank loan application. Your task is the preparation of acceptance tests for the following user story:

  "IF a customer needs a loan for less than 50,000 Euros and they have made repayments regularly (without any delay) and the customer's monthly income is more than 3000 Euros for the last year, THEN the bank will accept the loan request; in other cases, the bank will not accept the request. A customer assistant is responsible for preparing data for approval but the approval is done by the bank manager."

  Which of the following test cases can be treated as acceptance test criteria for the above user story?

  1) As a customer assistant I can log in to the system and check the history of the customer account for the last year.

  2) As a customer assistant I can log in to the system and check the history of the customer debts and repayments.

  3) As a customer assistant I can log in to the system and change my password.

  4) As a bank manager I can log in to the system and receive the information of all requests waiting for approval.

  5) As a bank manager I can log in to the system and decide whether to approve a loan for a customer.

  6) As a bank manager I can log in to the system within 10 seconds.

  A. Acceptance test criteria are 1, 2, 3 and 6
  B. Acceptance test criteria are 1, 3, 4 and 5
  C. Acceptance test criteria are 2, 4, 5 and 6
  D. Acceptance test criteria are 1, 2, 4 and 5
  D. Acceptance test criteria are 1, 2, 4 and 5

  ---

  Acceptance test criteria are the conditions that a user story must satisfy to be accepted by the customer or the stakeholder. They are usually derived from the user story and its acceptance scenarios, and they should cover the functional and non-functional requirements of the user story. Acceptance test criteria should be clear, concise, testable, and agreed upon by the team and the customer or the stakeholder.

  In this case, the user story describes the business rule for approving a loan request based on the customer's income, repayment history, and loan amount. The user story also specifies the roles of the customer assistant and the bank manager in the process. Therefore, the acceptance test criteria should verify that the user story is implemented correctly and that the system behaves as expected for different scenarios and inputs.

  The following test cases can be treated as acceptance test criteria for the above user story:

  As a customer assistant, I can log in to the system and check the history of the customer account for the last year.

  This test case verifies that the customer assistant can access the system and view the customer's income information, which is one of the factors for approving the loan request.

  As a customer assistant, I can log in to the system and check the history of the customer's debts and repayments.

  This test case verifies that the customer assistant can access the system and view the customer's repayment history, which is another factor for approving the loan request.

  As a bank manager, I can log in to the system and receive the information of all requests waiting for approval.

  This test case verifies that the bank manager can access the system and see the list of loan requests prepared by the customer assistant, and that the system provides the necessary information for each request.

  As a bank manager, I can log in to the system and decide whether to approve a loan for a customer.

  This test case verifies that the bank manager can access the system and perform the approval action for a loan request, and that the system applies the business rule correctly and updates the status of the request accordingly.

  The following test cases cannot be treated as acceptance test criteria for the above user story:

  As a customer assistant, I can log in to the system and change my password.

  This test case is not related to the user story, as it does not verify any of its functional or non-functional requirements. It is a generic test case that applies to any user of the system, not specific to the customer assistant role or the loan approval process.

  As a bank manager, I can log in to the system within 10 seconds.

  This test case is not related to the user story, as it does not verify any of its functional or non-functional requirements. It is a performance test case that applies to any user of the system, not specific to the bank manager role or the loan approval process.

• Question 15:

  Which of the following statements is true in Agile projects?

  A. Test automation is important to manage regression risk because it enables version control and ensures ease of access to the tests by all team members
  B. Shorter timeframes and frequent changes require the adoption of good practices for test design and implementation, which should be defined during release planning
  C. The risk of regression tends to decrease when code that worked in previous iterations gets modified due to new features in subsequent iterations
  D. The tests written for the features developed in earlier iterations are the most important and they should never be retired from the regression test suite
  B. Shorter timeframes and frequent changes require the adoption of good practices for test design and implementation, which should be defined during release planning

  ---

  From CTFL-AT Syllabus v4.0, Section 4.3 Test Automation and Continuous Integration, it states: "Short iterations and continuous integration require well-designed automated test suites, and teams should adopt good practices for test design and implementation from the start."

  Option B is correct because it highlights the need for proactive test design practices to handle frequent changes a key Agile challenge.

  Option A mixes concepts: version control relates to code, not directly to regression management.

  Option C is incorrect regression risk increases when code is modified.

  Option D is misleading tests may become obsolete or need refactoring, so no test is permanently untouchable.

  References:

  CTFL-AT Syllabus v4.0, Section 4.3 Learning Objective (K2) . Understand regression risk and automation best practices

• Question 16:

  Which of the following statements is true within an Agile team?

  A. Unlike traditional projects, testers are not asked to measure and report test coverage, and to report defects
  B. When adopting test-driven development, testers write all the tests while developers write all the code to make these tests pass
  C. Each team member plays a role in performing test-related tasks but only testers are responsible for product quality
  D. Testers may have difficulty keeping pace with the incoming changes in time-boxed iterations
  D. Testers may have difficulty keeping pace with the incoming changes in time-boxed iterations

  ---

  From CTFL-AT Syllabus v4.0, Section 2.4 and 2.5:

  "Due to frequent changes and short iterations, testers must be flexible and responsive. However, keeping up with pace can be a challenge."

  Thus, Option D is correct testers may struggle with rapid changes and short feedback loops, which is a known challenge in Agile.

  Option A is false, testers still measure coverage and report defects.

  Option B misrepresents TDD developers typically write the unit tests in TDD.

  Option C is incorrect quality is a shared responsibility in Agile.

  References:

  CTFL-AT Syllabus v4.0, Sections 2.4 and 2.5 Learning Objective (K2) . Understand tester challenges in Agile environments

• Question 17:

  Which of the following describes the main purpose of a task management tool in agile projects?

  A. A task management tool is used by team members to share ideas and collaborate on assigned tasks.
  B. A task management tool is used to manage and track user stories, tests and other tasks.
  C. A task management tool is used to store source code and automated tests.
  D. A task management tool allows developers to continuously integrate their code.
  B. A task management tool is used to manage and track user stories, tests and other tasks.

  ---

  A task management tool is a software application that helps agile teams plan, organize, and monitor their work. A task management tool typically allows the team to create, assign, prioritize, update, and track user stories, tests, and other tasks that are part of the agile project. A task management tool can also provide various views and reports to visualize the progress and status of the project, such as Kanban boards, burndown charts, velocity charts, etc. Some examples of task management tools are Jira,

  Trello, Asana, and Monday.com.

  References:

  ISTQB. Foundation Level Agile Tester Syllabus, Section 2.1.1, page 13; ASTQB Agile Tester Certification Resources, Section 2.1.1, page 13.

• Question 18:

  Which of the following BEST describes the tester's role during an iteration in Agile?

  A. Executing all test cases at the end of the iteration
  B. Supporting the team by participating in test design, execution, automation, and providing feedback continuously
  C. Writing only acceptance tests while developers write all other tests
  D. Waiting until developers complete coding before starting testing activities
  B. Supporting the team by participating in test design, execution, automation, and providing feedback continuously

  ---

  CTFL-AT Syllabus v4.0, Section 2.4 states that in Agile, development and testing occur in parallel, with testers actively collaborating within the team.

  Option B correctly reflects the whole-team approach: testers provide continuous feedback, participate in test design, automation, and exploratory testing.

  Option A is sequential, not Agile.

  Option C incorrectly limits testers’ responsibilities.

  Option D contradicts Agile principles of early and continuous testing.

  References:

  CTFL-AT Syllabus v4.0, Section 2.4

  Learning Objective (K2) – Understand testing within iterations

• Question 19:

  Which of the following statements correctly identifies a purpose of the Agile Testing Quadrants?

  A. To determine which test cases must be executed manually
  B. To categorize tests based on their purpose and value to the team
  C. To define the order in which test types must be executed
  D. To assign testing responsibilities exclusively to testers
  B. To categorize tests based on their purpose and value to the team

  ---

  From CTFL-AT Syllabus v4.0, Section 2.3, the Agile Testing Quadrants classify tests by:

  business-facing vs. technology-facing

  supporting the team vs. critiquing the product

  Option B accurately describes this.

  Option A is incorrect – quadrants do not specify automation vs. manual.

  Option C is incorrect – quadrants do not impose sequence.

  Option D contradicts Agile's whole-team responsibility for quality.

  References:

  CTFL-AT Syllabus v4.0, Section 2.3

• Question 20:

  An Agile team is working on a project to develop an image editing tool. In the current version, the 'settings GUI allows users to adjust exposure, contrast, and saturation. A session-based exploratory testing session is planned to find issues with parameter combinations that cause undesired image effects. Which of the following would you expect to be the best charter to support this exploratory testing session?

  A. Explore 'Settings' with many values of exposure, applied on different images, to discover unexpected effects on those images
  B. Explore 'Settings' with many combinations of the values of exposure, contrast, and saturation, applied on different images, to discover unexpected effects on those images
  C. Explore 'Settings' to discover unexpected effects on those images
  D. Explore 'Settings' working on different images by setting exposure, contrast, and saturation at their minimum, then setting exposure and contrast at maximum while keeping saturation at minimum, to discover unexpected effects
  B. Explore 'Settings' with many combinations of the values of exposure, contrast, and saturation, applied on different images, to discover unexpected effects on those images

  ---

  From the CTFL-AT Syllabus v4.0, Section 3.1 Exploratory Testing, it defines a test charter as:

  “A mission statement defining what to test, how it can be tested, and what issues to look for. Effective charters support focused yet flexible exploration.”

  Option B is the best because it specifies:

  the area of the system under test,

  the parameters involved,

  the approach (combinations),

  the goal (discover unexpected effects).

  Option A focuses only on one parameter.

  Option C is too vague.

  Option D is too prescriptive and limits exploration.

  References:

  CTFL-AT Syllabus v4.0, Section 3.1, Learning Objective (K3): Design effective exploratory test charters.