ISQI CTFL-AT Study Guide Archives Updated on Dec 06, 2025
Download CTFL-AT Mock Test Study Material
NEW QUESTION # 42
You are working in a software development company which, for many years, used a sequential development model and was organized into separate departments for each functional group (e.g. business analysts, developers, testers) located within their own office space. Your organization has recently changed to a SCRUM agile framework. Which of the following is an important organizational and behavioral best practice for a tester in the SCRUM team that should have also been practiced when using the sequential model?
- A. Cross-functional teamwork means that all team members contribute to testing in various ways. For example, involving people with the test strategy, test planning and execution as well as test reporting.
- B. Co-located teamwork means that all team members, including developers and testers, must sit together in the same office, so they can quickly communicate face-to-face.
- C. Credibility means that the tester must share information with the stakeholders about the test process so that they find the selected test strategy and testing activities trustworthy.
- D. Resilient testing means that the testing process is capable of dealing with rapid changes throughout the development process with test plans being updated during each iteration.
Answer: A
Explanation:
Cross-functional teamwork is an important organizational and behavioral best practice for a tester in the SCRUM team that should have also been practiced when using the sequential model. Cross-functional teamwork means that all team members, regardless of their functional roles, collaborate and share their skills and knowledge to achieve a common goal. In the context of testing, this means that testing is not seen as a separate activity or phase, but as an integral part of the development process. All team members contribute to testing in various ways, such as:
* Involving people with the test strategy, test planning and execution as well as test reporting. This can help ensure that the testing activities are aligned with the business objectives, the user needs, and the technical requirements. It can also help improve the test coverage, the test quality, and the test efficiency.
* Sharing the responsibility for testing among the team members. This can help reduce the workload and the dependency on a single tester or a testing team. It can also help increase the feedback and the communication among the team members, and foster a culture of quality and learning.
* Leveraging the diverse skills and perspectives of the team members. This can help enhance the test design and the test execution by applying different techniques, tools, and approaches. It can also help identify and address the risks, the issues, and the opportunities for improvement from various angles. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 1.2.1, page 9; ISTQB Glossary of Testing Terms2, version 4.0, page 16.
NEW QUESTION # 43
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. 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.
- C. 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.
- D. 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
Answer: C
Explanation:
Explanation
Agile software development is a term that encompasses a group of software development methodologies that are based on iterative incremental development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. Agile methods promote adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourage rapid and flexible response to change. Some examples of agile methods are Scrum, Extreme Programming (XP), Kanban, and Lean Software Development. References:
1: ISTQB Foundation Level Agile Tester Syllabus, Version 2014, Section 1.1.1
2: ASTQB Agile Tester Certification Resources, Agile Testing Foundations, Chapter 1, Section 1.1.1
NEW QUESTION # 44
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. Payment for parking ticket is restricted to cash only (no credit card supported).
- D. Price for a bus ticket was calculated incorrectly.
Answer: C
NEW QUESTION # 45
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. An untrained customer will attempt to use the coffee machine. Probability: High. Impact: High
- B. The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High
- C. A small child may try to steam milk. Probability: High. Impact: Low
- D. Operators will not read the instructions and will try various switches and buttons until something works.
Probability: Low. Impact: Low
Answer: B
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 # 46
Which of the following statements about Agile retrospectives is CORRECT?
- A. Unlike working sessions or meetings held in non-Agile projects, Agile retrospectives do not require follow-up activities.
- B. During Agile retrospectives, testers should be encouraged to provide constructive suggestions only on non-testing activities.
- C. 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.
- D. Agile retrospectives should be focused mainly on impediments that are outside the control of the team because these issues are more challenging.
Answer: C
NEW QUESTION # 47
Which of the following is a risk that continuous integration introduces?
- A. Developer's workload is increased, which can result in a reduction of output.
- B. Teams no longer have the ability to run manual tests, as all tests must be automated.
- C. Testers sometimes have too many builds to test, which reduces the quality of testing.
- D. Teams sometimes over-rely on unit tests and exclude some important system and acceptance tests.
Answer: C
Explanation:
Continuous integration is a practice of integrating code changes frequently and automatically into a shared repository, and running automated tests to verify the integration. Continuous integration can introduce some risks to the testing process, such as:
* Testers sometimes have too many builds to test, which reduces the quality of testing. This can happen when the code changes are too frequent or too large, and the testers do not have enough time or resources to test each build thoroughly. This can lead to missed defects, incomplete test coverage, and reduced confidence in the product quality.
* Testers sometimes have to deal with unstable or broken builds, which affects the testability of the product. This can happen when the code changes introduce errors or conflicts that cause the build to fail or malfunction. This can waste the testers' time and effort, and delay the feedback cycle.
* Testers sometimes have to cope with changing requirements and priorities, which affects the test planning and execution. This can happen when the stakeholders or customers provide new or modified requirements or feedback during the development cycle. This can require the testers to adapt their test strategy, test cases, and test data accordingly, and to balance the testing of new features and regression testing of existing features. References: ISTQB Foundation Level Agile Tester Syllabus1, Section
2.2.3, page 14; ISTQB Glossary of Testing Terms2, version 4.0, page 15.
NEW QUESTION # 48
Which of the following statements would you expect to be the MOST direct advantage of the whole-team approach?
- A. Reducing the involvement of business representatives because of the increased communication and collaboration between testers and developers.
- B. Having at least once a day an automated build and test process that detects integration errors early and quickly.
- C. Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.
- D. Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.
Answer: C
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 # 49
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. State transition testing - test all states of income entry.
- B. Equivalence partitioning - test with low, medium and high income.
- C. User story testing - test that the user can enter an income amount and get a result.
- D. Statement testing - test all statements in income calculation.
Answer: B
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 # 50
Which of the following statements about the test pyramid is true?
- A. The test pyramid concept states that every software system consists always of four different test levels (unit, integration, system, acceptance)
- 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 consists of four test levels with business-facing tests at the bottom of the pyramid and technology-facing tests at the top
- D. The test pyramid concept is based on the principle of eliminating defects as early as possible in the software lifecycle
Answer: D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 4.1The 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 Ais correct - thetest pyramid supports early defect detectionthrougha high volume of lower-level automated tests.
* Option Bis incorrect - thetest pyramid emphasizes more tests at lower levels, not higher.
* Option Cis incorrect - Agile doesn't mandate four specific levels in every system.
* Option Dmisrepresents the pyramid -technology-facing tests (e.g., unit tests)areat the bottom, not the top.
References:
CTFL-AT Syllabus v4.0, Section 4.1
Learning Objective (K2) - Understand the purpose of the test pyramid
NEW QUESTION # 51
During a retrospective, which of the following items would be the LEAST effective to generate discussions on process improvement?
- A. The automation tests failed frequently without any logs to help in debugging the failure reason.
- B. One of the testers was regarded as being both disruptive and lazy and did not contribute to team success.
- C. The build process was slow and this often caused delays waiting for the build to complete.
- D. For the last sprint the estimated and actual effort were much higher than the team capacity.
Answer: B
Explanation:
Explanation
According to the ISTQB Tester Foundation Level Agile Tester syllabus, a retrospective is a meeting held at the end of each iteration or release, where the agile team reflects on what went well and what can be improved in their processes, practices, and interactions. The purpose of a retrospective is to identify and implement actions for continuous improvement, and to foster a culture of learning and collaboration. Therefore, the items that would be the most effective to generate discussions on process improvement are those that are related to the team's performance, challenges, feedback, and suggestions. Option D is the least effective item to generate discussions on process improvement, as it is a personal attack on one of the team members, and it does not offer any constructive feedback or solution. This kind of item can create a negative and hostile atmosphere in the retrospective, and damage the trust and respect among the team members. Option A is an effective item to generate discussions on processimprovement, as it identifies a problem with the build process that affects the team's efficiency and quality, and it can lead to finding ways to optimize the build process or to mitigate the delays. Option B is also an effective item to generate discussions on process improvement, as it reveals a discrepancy between the team's estimation and actual effort, and it can lead to analyzing the root causes of the deviation and to improving the estimation techniques or the team's capacity. Option C is also an effective item to generate discussions on process improvement, as it highlights a weakness in the automation tests that hinders the team's ability to debug and fix the failures, and it can lead to enhancing the automation tests with better logging mechanisms or to reviewing the automation strategy. References: ISTQB Tester Foundation Level Agile Tester syllabus, section 2.1.1, page 14; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.1.2, page 15; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.2.1, page 16; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.2.2, page 17.
NEW QUESTION # 52
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. Payment for parking ticket is restricted to cash only (no credit card supported).
- D. Price for a bus ticket was calculated incorrectly.
Answer: C
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 # 53
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. 2, 4, 5
- B. 2, 5
- C. 1, 3, 4
- D. 1, 3
Answer: C
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 # 54
Which of the following statements about the benefits of the Agile processes promoting early and frequent feedback is NOT true?
- A. Early and frequent feedback enables the team to deliver the features that represent the highest business value to the customer first.
- B. Feedback from well-conducted Agile retrospectives can be used to positively affect the development process over the course of the next iteration.
- C. Increasing the frequency of feedback and communication between all the stakeholders involved in Agile projects eliminates all communication problems.
- D. In Agile projects where feedback is provided early and frequently, defects and incorrect requirements are caught earlier and those problems can be fixed faster.
Answer: C
NEW QUESTION # 55
Which of the following statements about the testing quadrants model is true?
- A. 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
- 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) 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
Answer: A
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 # 56
Which of the following is a risk that continuous integration introduces?
- A. Developer's workload is increased, which can result in a reduction of output.
- B. Teams no longer have the ability to run manual tests, as all tests must be automated.
- C. Testers sometimes have too many builds to test, which reduces the quality of testing.
- D. Teams sometimes over-rely on unit tests and exclude some important system and acceptance tests.
Answer: C
Explanation:
Explanation
Continuous integration is a practice of integrating code changes frequently and automatically into a shared repository, and running automated tests to verify the integration. Continuous integration can introduce some risks to the testing process, such as:
Testers sometimes have too many builds to test, which reduces the quality of testing. This can happen when the code changes are too frequent or too large, and the testers do not have enough time or resources to test each build thoroughly. This can lead to missed defects, incomplete test coverage, and reduced confidence in the product quality.
Testers sometimes have to deal with unstable or broken builds, which affects the testability of the product. This can happen when the code changes introduce errors or conflicts that cause the build to fail or malfunction. This can waste the testers' time and effort, and delay the feedback cycle.
Testers sometimes have to cope with changing requirements and priorities, which affects the test planning and execution. This can happen when the stakeholders or customers provide new or modified requirements or feedback during the development cycle. This can require the testers to adapt their test strategy, test cases, and test data accordingly, and to balance the testing of new features and regression testing of existing features. References: ISTQB Foundation Level Agile Tester Syllabus1, Section
2.2.3, page 14; ISTQB Glossary of Testing Terms2, version 4.0, page 15.
NEW QUESTION # 57
......
The CTFL-AT Exam is targeted towards professionals who are involved in software development and testing, including testers, test analysts, test engineers, and quality assurance professionals. CTFL-AT exam is ideal for individuals who are already familiar with the Agile development process and want to gain a better understanding of Agile testing methodologies. It is also suitable for those who want to advance their careers in software testing or wish to demonstrate their expertise in Agile testing to prospective employers.
CTFL-AT Questions Prepare with Learning Information: https://www.freecram.com/ISQI-certification/CTFL-AT-exam-dumps.html
Practice Material for CTFL-AT Exam Question Preparation: https://drive.google.com/open?id=1cHoKfc4elNp34eqEJTkGIWVPu6JBL84d