[2026] CTFL-AT Answers CTFL-AT Free Demo Are Based On The Real Exam
CTFL-AT [Feb-2026 Newly Released] Exam Questions For You To Pass
ISQI CTFL-AT (ISTQB Certified Tester - Foundation Level Extension - Agile Tester) Certification Exam is a globally recognized certification for professionals who want to enhance their knowledge and expertise in Agile methodology. ISTQB Certified Tester - Foundation Level Extension - Agile Tester certification is designed to provide an in-depth understanding of the Agile testing methodology, principles, and practices. It is an ideal certification for individuals who want to become proficient in Agile testing and want to advance their careers in this field.
NEW QUESTION # 18
What is the definition of agile software development?
- A. A way of developing software where the test cases are developed, and often automated, before the software under test is developed.
- B. A framework to describe the software development lifecycle activities from requirements specification to maintenance where test planning of the various test levels is done as soon as the test basis is ready
- C. Testing carried out informally where no formal test preparation or execution takes place, no recognized test design technique is used and there are no expectations for results.
- D. A group of software development methodologies based on iterative incremental development with self-organizing cross-functional teams who cooperate to define requirements and to implement the solution.
Answer: D
NEW QUESTION # 19
Which of the following statements would you expect to be the MOST direct advantage of the whole-team approach?
- A. Having at least once a day an automated build and test process that detects integration errors early and quickly.
- B. Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.
- C. Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.
- D. Reducing the involvement of business representatives because of the increased communication and collaboration between testers and developers.
Answer: C
Explanation:
Explanation
The whole-team approach is a principle of agile testing that involves everyone with different knowledge and skills to ensure project success. The whole-team approach means that the business representatives, testers, and developers work together in every step of the development process, from planning to delivery. The whole-team approach aims to enhance communication and collaboration within the team, leverage the various skill sets of the team members, and make quality everyone's responsibility12. Therefore, the statement C is the most direct advantage of the whole-team approach, as it captures the essence of the principle and its benefits.
The other statements are not directly related to the whole-team approach, or are incorrect. Statement A is about continuous integration, which is a practice of agile development that involves having at least once a day an automated build and test process that detects integration errors early and quickly. Continuous integration is not a direct consequence of the whole-team approach, although it may be facilitated by it13. Statement B is about avoiding requirements misunderstandings, which may be a benefit of the whole-team approach, but not the most direct one. The whole-team approach does not only focus on requirements, but also on design, implementation, testing, and delivery. Moreover, avoiding requirements misunderstandings may also depend on other factors, such as the quality of the user stories, the use of acceptance criteria, and the feedback from the customers and users14. Statement D is incorrect, as it contradicts the whole-team approach. The whole-team approach does not reduce the involvement of business representatives, but rather increases it.
Business representatives are an integral part of the whole-team approach, as they provide the vision, the value, and the validation of the product. They collaborate with the testers and developers to define the features, prioritize the backlog, and verify the outcomes12. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 1.2.1, page 9; What is Whole Team Approach in Agile Testing?2, Section What is Whole Team Approach?; Continuous Integration3, Section What is Continuous Integration?; Effective User Stories -
3C's and INVEST Guide4, Section The 3 C's (Card, Conversation, Confirmation) of User Stories.
NEW QUESTION # 20
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 interface to External System shall be specified.
- B. The "ID" field must accept input value of a length between 2 and 10 characters.
- 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.
Answer: C
NEW QUESTION # 21
Which one of the following is a testable acceptance criterion?
- A. The system shall be easy to use.
- B. The response time to confirm a customer submission must not exceed 5 seconds.
- C. The solution shall support business processes.
- D. The tools for testing are tested before use and are meeting the requirements.
Answer: B
Explanation:
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 begins1.
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; ISTQB Foundation Level Agile Tester Sample Exam Questions, Question 2.3.2-2, page 93
NEW QUESTION # 22
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 allows developers to continuously integrate their code.
- D. A task management tool is used to store source code and automated tests.
Answer: B
Explanation:
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.com12345. References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.1.1, page 13; ASTQB Agile Tester Certification Resources, Section 2.1.1, page 13.
NEW QUESTION # 23
You are developing the code that controls an industrial Espresso machine which will be operated by waiting staff in restaurants.
The machine is rather complicated and has lots of switches and buttons, so in the next iteration instructions will be provided to the operator on a small LCD screen.
A User Story for the Operator-Instructions module is as follows:
"As an operator of the Espresso machine, I would like to know how to steam milk, so I can add steamed milk to the coffee." The following is a list of risks identified for this story, with assigned probability and impact.
- A. A small child may try to steam milk. Probability: High. Impact: Low
- B. Operators will not read the instructions and will try various switches and buttons until something works.
Probability: Low. Impact: Low - C. The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High
- D. An untrained customer will attempt to use the coffee machine. Probability: High. Impact: High
Answer: C
Explanation:
Risk-based testing is a technique that prioritizes testing activities based on the level of risk associated with each feature or requirement. The level of risk is usually calculated by multiplying the probability and impact of each risk. The higher the risk level, the more testing effort should be allocated to mitigate the risk. In this case, the risk level for each option is as follows: A. Risk level = Low x Low = Low B. Risk level = Low x High = Medium C. Risk level = High x High = High D. Risk level = High x Low = Medium Therefore, the highest risk level is C, followed by B and D, and then A. The User Story for the Operator-Instructions module should be tested according to this risk order, starting with C, then B, then D, and finally A. Hence, the answer is B, as it is the second highest risk level and should be tested after C. References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 16; ISTQB Agile Tester Sample Exam2, question 18.
NEW QUESTION # 24
Which of the following sentences related to Risk-based testing is CORRECT?
- A. Risk-based testing does not fit in Agile development processes, as each iteration focuses on limited parts of the product.
- B. Risk-based testing does not fit well in Agile development processes, as short iterations mandate short test times.
- C. Risk-based testing fits well in Agile development processes, as risks are analyzed twice - during release and iteration planning.
- D. Risk-based testing fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories.
Answer: D
Explanation:
Risk-based testing fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories. User stories are short descriptions of features or functionalities that are valuable to the customers or users. They help to define the scope and priority of the work in each iteration. By breaking down the work into user stories, the Agile team can identify the potential risks associated with each story, such as technical complexity, business criticality, or user feedback. The team can then prioritize the testing effort based on the risk level of each story, ensuring that the most important and risky features are tested first and thoroughly. Risk-based testing also helps to optimize the testing time and resources, as the team can focus on testing the most relevant aspects of the software, rather than testing everything equally. References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.3.2, page 181; ISTQB Foundation Level Agile Tester Sample Exam Questions, Question 2.3.2-1, page 92
NEW QUESTION # 25
You have been asked to execute an exploratory testing session on Park & 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. Failed to buy a bus ticket when the network connection to the Central System is down.
- B. Failed to buy a bus ticket after 18:00.
- C. Price for a bus ticket was calculated incorrectly.
- D. Payment for parking ticket is restricted to cash only (no credit card supported).
Answer: D
Explanation:
Explanation
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. References: ISTQB Certified Tester Foundation Level Agile Tester Extension Syllabus, Version 2014, Section 2.3.2 Exploratory Testing1, Section 2.3.2.1 Test Charter2; ISTQB Glossary of Testing Terms, Version 3.2, 2017, Definition of Test Charter3
1: ISTQB Certified Tester Foundation Level Agile Tester Extension Syllabus, Version 2014, Section 2.3.2 Exploratory Testing 2: ISTQB Certified Tester Foundation Level Agile Tester Extension Syllabus, Version
2014, Section 2.3.2.1 Test Charter 3: [ISTQB Glossary of Testing Terms, Version 3.2, 2017, Definition of Test Charter]
NEW QUESTION # 26
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. The risk of regression tends to decrease when code that worked in previous iterations gets modified due to new features in subsequent iterations
- C. Shorter timeframes and frequent changes require the adoption of good practices for test design and implementation, which should be defined during release planning
- 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
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 4.3Test 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." OptionBis correct because it highlights theneed for proactive test design practicesto handle frequent changes - a key Agile challenge.
* Option Amixes concepts:version controlrelates to code, not directly to regression management.
* Option Cis incorrect - regressionrisk increaseswhen code is modified.
* Option Dis misleading - tests may becomeobsoleteor needrefactoring, sono test is permanently untouchable.
References:
CTFL-AT Syllabus v4.0, Section 4.3
Learning Objective (K2) - Understand regression risk and automation best practices
NEW QUESTION # 27
Which of the following allows a developer to define accurate unit tests focused on business needs?
- A. Design-Driven Development
- B. Behavior-Driven Development
- C. Acceptance Test-Driven Development
- D. Test-Driven Development
Answer: B
Explanation:
Behavior-Driven Development (BDD) is a software development approach that allows a developer to define accurate unit tests focused on business needs. BDD uses a common language that is understandable by both technical and non-technical stakeholders, such as Given-When-Then scenarios. BDD helps to align the development and testing activities with the customer expectations and business goals . 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
NEW QUESTION # 28
Which one of the following is a testable acceptance criterion?
- A. The system shall be easy to use.
- B. The response time to confirm a customer submission must not exceed 5 seconds.
- C. The solution shall support business processes.
- D. The tools for testing are tested before use and are meeting the requirements.
Answer: B
NEW QUESTION # 29
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 of8 story pointsafter four rounds, withno discussionsbetween rounds.
Team B arrives at3 story pointsafter three rounds, withdiscussionsbetween 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. 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
- 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. Team B estimates that the user story can be "done" with significantly less effort in absolute terms than what was estimated by Team A
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 2.2Release 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 Cis correct - Team B usesdiscussion-based estimation, which is a corebenefitof Planning Poker.
* Option Ais speculative - we cannot know the actual effort difference.
* Option Bis incorrect - convergence without discussion may indicatelack of engagement or pressure to agree.
* Option Dis false - Planning Poker isnot based on averaging, but onconsensus.
References:
CTFL-AT Syllabus v4.0, Section 2.2
Learning Objective (K2) - Understand the purpose and benefit of Planning Poker
NEW QUESTION # 30
Your agile team is using the Testing Quadrants to ensure that all important test levels and test types are covered in the test plan.
In relation to Quadrant 3 - business facing and product critique, what should be considered for the plan?
- A. Performance Testing
- B. Exploratory Testing
- C. Prototype Testing
- D. Functional Testing
Answer: B
NEW QUESTION # 31
Which tasks are typically performed by a tester on an Agile project?
1) Implementing test strategy.
2) Documenting business requirements.
3) Measuring and reporting test coverage.
4) Coaching development team in relevant aspects of testing.
5) Executing test-driven development tests.
- A. 1, 3, 4
- B. 1, 3
- C. 2, 5
- D. 2, 4, 5
Answer: A
Explanation:
Explanation
A tester on an Agile project typically performs the following tasks12:
Implementing test strategy: A tester helps to define and implement the test strategy for the Agile project, which includes the test approach, test levels, test types, test techniques, test tools, test environment, test data, test metrics, and test documentation.
Measuring and reporting test coverage: A tester measures and reports the test coverage of the product features and quality attributes, such as functionality, usability, performance, security, etc. Test coverage can be expressed in terms of test cases, test scenarios, test sessions, test conditions, test data, code, etc.
Coaching development team in relevant aspects of testing: A tester coaches the development team in relevant aspects of testing, such as test design, test execution, test automation, test-driven development, behavior-driven development, exploratory testing, etc. A tester also helps the development team to improve their testing skills and practices.
The following tasks are not typically performed by a tester on an Agile project:
Documenting business requirements: Business requirements are usually documented by the product owner or the business analyst, not by the tester. The tester may review and provide feedback on the business requirements, but the tester is not responsible for documenting them.
Executing test-driven development tests: Test-driven development tests are usually executed by the developers, not by the tester. The tester may assist the developers in creating and reviewing the test-driven development tests, but the tester is not responsible for executing them.
Therefore, the correct answer is C, as it contains the tasks that are typically performed by a tester on an Agile project. References: ISTQB Foundation Level Agile Tester Extension Syllabus1, pages 14-15, 18-19, 22-23; ISTQB Agile Tester Sample Exam2, question 17.
NEW QUESTION # 32
You are a tester in an agile team. The user story you are due to test is still under development so your tests are blocked. The main issue holding progress on this user story is that the developer's unit tests are constantly failing.
As an agile tester, which of the following actions should you take?
- A. Use the time to improve and automate existing test cases of other user stories.
- B. Create a bug report for each of your blocked tests.
- C. Review the design of the problematic user story and improve it where possible.
- D. Work together with the developer, suggesting reasons why the tests are failing.
Answer: D
NEW QUESTION # 33
Which of the following statements about the testing quadrants model is true?
- A. Each of the four testing quadrants (Q1, Q2, Q3, and Q4) represents a different test level (Q1 = Unit, Q2
= Integration, Q3 = System, and Q4 = Acceptance) and describes the different test types that shall be performed by Agile teams in that test level for an Agile project - B. Each of the four testing quadrants (Q1, Q2, Q3, and Q4) contains different test types and test levels, and these quadrants are numbered to describe the order in which the associated test types and test levels shall be performed in an Agile project (Q1 first, Q4 last)
- C. Each of the four testing quadrants (Q1, Q2, Q3, and Q4) contains different test types and test levels, and these quadrants are numbered to describe the risk level associated with the test types (Q1 = least risky, Q4 = most risky)
- D. Each of the four testing quadrants (Q1, Q2, Q3, and Q4) contains different test types and test levels, and these quadrants can be used by Agile teams and other stakeholders to ensure that all important test types and test levels are included in an Agile project
Answer: D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 3.4The Testing Quadrants, it states:
"The Agile testing quadrants are used to ensure that the team considers all important test types and levels during an Agile project. The quadrants categorize tests by their purpose (support development, critique the product) and by the type of feedback (business-facing vs technology-facing)." Thus,Option Ccorrectly reflects theuse and purposeof the quadrants as aguidance tool, not a fixed sequence or hierarchy.
* Option AandBare incorrect - the quadrants arenot mapped to strict levels or chronological order.
* Option Dis false -risk is not the basis for quadrant numbering.
References:
CTFL-AT Syllabus v4.0, Section 3.4
Learning Objective (K2) - Understand the Agile testing quadrants
NEW QUESTION # 34
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. User story testing - test that the user can enter an income amount and get a result.
- B. State transition testing - test all states of income entry.
- C. Equivalence partitioning - test with low, medium and high income.
- D. Statement testing - test all statements in income calculation.
Answer: C
Explanation:
Explanation
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 domainof 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, or testing only one value of income, or testing the states of income entry, or testing the statements in income calculation. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 2.3.1, page 19; ISTQB Foundation Level Agile Tester Extension Sample Exam Questions2, Question 5, page 6.
NEW QUESTION # 35
Consider the following acceptance criterion associated to a user story:
"A maximum of 0.0002 failures per hour in the specified operational conditions over at least ten days of testing must be achieved." Which of the following aspects of testability is best described in this acceptance criterion?
- A. Quality characteristics
- B. External interfaces
- C. Scenarios
- D. Functional behavior
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 2.1Acceptance Criteria and Testability, and Section 3.1:
"Acceptance criteria may also address non-functional quality characteristics such as reliability, performance, and usability." The criterion referencesfailure rate over time, which is areliability attribute, makingOption D (Quality characteristics)the correct answer.
* Option A(Scenarios) refers to usage paths.
* Option Brefers to functional correctness.
* Option Crefers to interface interaction points.
References:
CTFL-AT Syllabus v4.0, Sections 2.1, 3.1
Learning Objective (K2) - Understand testability related to quality characteristics
NEW QUESTION # 36
Which of the following is NOT a statement of value from the Agile Manifesto?
- A. Working software over comprehensive documentation
- B. Responding to change over following a plan.
- C. Customer collaboration over contract negotiation.
- D. Processes and tools over individuals and interactions.
Answer: D
Explanation:
The Agile Manifesto is a declaration of four values and twelve principles that guide the Agile software development approach12. The four values of the Agile Manifesto are12:
* Individuals and interactions over processes and tools
* Working software over comprehensive documentation
* Customer collaboration over contract negotiation
* Responding to change over following a plan
These values emphasize the importance of human collaboration, working product, customer feedback, and adaptability over rigid processes, extensive documentation, fixed contracts, and predefined plans. The values do not imply that the items on the right are not important, but rather that the items on the left are more important and should be prioritized.
Therefore, the statement that is NOT a value from the Agile Manifesto is B, as it contradicts the first value of the Agile Manifesto. The correct statement should be "Individuals and interactions over processes and tools". References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 10; ISTQB Agile Tester Sample Exam2, question 1.
NEW QUESTION # 37
......
New 2026 Realistic Free ISQI CTFL-AT Exam Dump Questions and Answer: https://www.prep4sureguide.com/CTFL-AT-prep4sure-exam-guide.html
ISQI CTFL-AT Exam: Basic Questions With Answers: https://drive.google.com/open?id=1WwNNPtCpUsd0fPejAVo3TB83XITkoJLL