CTFL-AT PDF Dumps | Dec 01, 2025 Recently Updated Questions
CTFL-AT Exam Questions – Valid CTFL-AT Dumps Pdf
The CTFL-AT exam is a three-hour, multiple-choice exam that consists of 40 questions. It covers various topics related to agile testing, such as agile testing techniques, agile testing methodologies, testing in agile projects, and tools and automation in agile testing. CTFL-AT exam is designed to test the candidate's knowledge and understanding of agile testing concepts and their ability to apply these concepts in real-world scenarios.
NEW QUESTION # 36
Which of the following statements best describes test-driven development?
- A. A high-level description of the test levels to be performed and the testing within those levels for an organization or programme (one or more projects)
- B. A way of testing software where test design and test execution occur at the same time, guided by a test charter during time-boxed testing sessions
- C. A way of developing software where the test cases are developed, and often automated, before the software to run those test cases has been written
- D. An approach to software development based on iterative incremental development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 3.2Test-Driven Development, it states:
"Test-Driven Development (TDD) is a practice where test cases are written before the code is developed.
Typically, these tests are automated, and the code is written to make the tests pass." This directly matchesOption A, making it the correct and complete answer.
Let's review the other options:
* Option Bdescribes atest strategy, not TDD.
* Option Cis a definition ofAgile software development, not TDD.
* Option Ddescribesexploratory testing, not TDD.
References:
CTFL-AT Syllabus v4.0, Section 3.2
Learning Objective (K2) - Understand the principles of test-driven development
NEW QUESTION # 37
Which of the following describes the main purpose of a task management tool in agile projects?
- A. 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.
- C. A task management tool is used to store source code and automated tests.
- D. A task management tool is used by team members to share ideas and collaborate on assigned tasks.
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 # 38
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. The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High
- B. A small child may try to steam milk. Probability: High. Impact: Low
- C. An untrained customer will attempt to use the coffee machine. Probability: High. Impact: High
- D. Operators will not read the instructions and will try various switches and buttons until something works.
Probability: Low. Impact: Low
Answer: A
Explanation:
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 # 39
Which two of the following statements are CORRECT with regards to test automation on agile projects?
1) Every test developed for past iterations is kept and executed as part of a regression suite for each new release of code.
2) It would be very difficult to ensure high quality in an agile project without test automation.
3) Automated acceptance tests are run regularly as part of the continuous integration full system build.
4) Automated regression suites are only run for the final release of code.
5) In agile projects, the results from automated acceptance tests provide feedback on the overall product quality.
- A. 2, 3
- B. 2, 5
- C. 3, 4
- D. 1, 3
Answer: B
Explanation:
Explanation
Test automation is essential for agile projects, as it enables fast and frequent feedback on the quality of the product. Without test automation, it would be very difficult to ensure high quality in an agile project, as manual testing would be too slow and costly to keep up with the pace of development12. Automated acceptance tests are one of the key types of test automation on agile projects, as they verify that the user stories are implemented correctly and that the product meets the customer's expectations. Automated acceptance tests are run regularly as part of the continuous integration full system build, and the results provide feedback on the overall product quality12. Therefore, statements 2 and 5 are correct with regards to test automation on agile projects. References: 1: ISTQB Foundation Level Agile Tester Syllabus, Section 3.3.1, Test Automation1; 2:
ASTQB Agile Tester Certification Resources, Section 3.3.1, Test Automation2
NEW QUESTION # 40
In Agile projects, which of the following approaches would result in the best compromise for preserving independence of testers and for allowing testers to have a good understanding of the product as well as good relationships with other team members?
- A. Having independent separate test teams where testers are assigned to Agile teams on-demand during the final days of each iteration
- B. Having independent separate test teams where all of the testers work separately from developers without being assigned to Agile teams
- C. Having independent separate test teams where testers are assigned to Agile teams on a long-term basis, at the beginning of an Agile project
- D. Having only Agile teams where testers are integral parts and where they perform many of the testing tasks, without having an independent test team
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 2.5Testers and Independence, it states:
"Testers may be assigned to Agile teams on a permanent or rotating basis. While full independence is compromised, this setup allows for better collaboration and understanding of the product, while still maintaining some degree of independence." Thus,Option Bis the most accurate -long-term embedded testerssupport Agile collaboration while preservingpartial independence.
* Option Aleads tolate involvement, which contradicts Agile principles.
* Option Csacrifices independence entirely.
* Option Dis traditional and contrary to Agile values of collaboration.
References:
CTFL-AT Syllabus v4.0, Section 2.5
Learning Objective (K2) - Understand approaches to preserving test independence in Agile
NEW QUESTION # 41
In a sprint planning, the product owner presents a user story written on a card. The team starts having a discussion with the product owner to get an understanding on how the software should work.
The user story written on the card is:
"As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email." By applying the 3C concept, which ONE of the following statements is CORRECT?
- A. Product owner has written a user story and confirmation is not needed.
- B. The conversation is not required and the team should start developing.
- C. The card should contain requirements not the user story.
- D. Conversation should include the acceptance criteria discussion.
Answer: D
NEW QUESTION # 42
In a sprint planning, the product owner presents a user story written on a card. The team starts having a discussion with the product owner to get an understanding on how the software should work.
The user story written on the card is:
"As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email." By applying the 3C concept, which ONE of the following statements is CORRECT?
- A. Product owner has written a user story and confirmation is not needed.
- B. The conversation is not required and the team should start developing.
- C. The card should contain requirements not the user story.
- D. Conversation should include the acceptance criteria discussion.
Answer: D
Explanation:
The 3C concept of user stories consists of three elements: card, conversation, and confirmation12. The card is a written description of the user story that captures the essence of the feature or functionality from the user's perspective. The conversation is a dialogue between the product owner and the development team to clarify the details, assumptions, and expectations of the user story. The confirmation is a set of criteria or tests that verify that the user story is implemented correctly and meets the user's needs12. Therefore, by applying the
3C concept, the correct statement is A, as the conversation should include the acceptance criteria discussion. This will help the team to understand the scope, priority, and value of the user story, as well as the conditions of satisfaction that the product owner expects12. The other statements are incorrect, as they violate the 3C concept. Statement B is wrong, as the card should contain the user story, not the requirements. The user story is a brief and informal way of expressing the user's goal and benefit, while the requirements are more detailed and specific descriptions of how the software should work. The requirements can be added later as part of the conversation or confirmation12. Statement C is wrong, as the product owner has written a user story, but confirmation is still needed. The confirmation is a vital part of the 3C concept, as it ensures that the user story is testable, measurable, and verifiable. The confirmation also helps to avoid ambiguity, misunderstanding, or disagreement between the product owner and the development team12. Statement D is wrong, as the conversation is required and the team should not start developing without it. The conversation is an essential part of the 3C concept, as it allows the team to ask questions, share ideas, and collaborate with the product owner to refine the user story and reach a shared understanding. The conversation also helps to identify the dependencies, risks, and assumptions that may affect the implementation of the user story12. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 2.2.1, page 16-17; Effective User Stories - 3C's and INVEST Guide2, Section The 3 C's (Card, Conversation, Confirmation) of User Stories.
NEW QUESTION # 43
Which one of the following is a testable acceptance criterion?
- A. The tools for testing are tested before use and are meeting the requirements.
- B. The solution shall support business processes.
- C. The system shall be easy to use.
- D. The response time to confirm a customer submission must not exceed 5 seconds.
Answer: D
NEW QUESTION # 44
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, 5
- B. 1, 3, 4
- C. 2, 4, 5
- D. 1, 3
Answer: B
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 # 45
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. 4, 5
- B. 2, 5
- C. 3, 4
- D. 1, 3
Answer: C
Explanation:
Explanation
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 customer1. The acceptance criteria should be specific, measurable, achievable, relevant, and testable2. In this case, the plan for the sprint is to increase 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 performance3.
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 testing4.
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 55.
A static analysis tool has been executed for all code. This criterion is not a customer
NEW QUESTION # 46
Which of the following allows a developer to define accurate unit tests focused on business needs?
- A. Test-Driven Development
- B. Behavior-Driven Development
- C. Acceptance Test-Driven Development
- D. Design-Driven Development
Answer: C
NEW QUESTION # 47
Which of the following sentences about the integration of development and testing activities in Agile projects is INCORRECT?
- A. Developers write acceptance criteria and test cases, together with testers.
- B. Testers replace developers in writing unit test automation scripts.
- C. While developers develop automated unit test scripts, testers write automated system level tests.
- D. Developers and testers may work as a pair to develop and test a feature.
Answer: B
Explanation:
Testers replace developers in writing unit test automation scripts. Comprehensive Explanation: The integration of development and testing activities in Agile projects is based on the principle of cross-functional teamwork, where all team members 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. Therefore, the following sentences are correct:
* While developers develop automated unit test scripts, testers write automated system level tests. This is an example of how developers and testers can work in parallel and complement each other's testing efforts. Developers can focus on testing the internal quality of the code, while testers can focus on testing the external quality of the product.
* Developers write acceptance criteria and test cases, together with testers. This is an example of how developers and testers can work together to define and verify the user requirements and expectations.
Developers can provide their technical expertise and input, while testers can provide their business and user perspective and feedback.
* Developers and testers may work as a pair to develop and test a feature. This is an example of how developers and testers can work closely and interactively to deliver a feature. Developers and testers can exchange ideas, suggestions, and information, and support each other in the coding and testing tasks.
The following sentence is incorrect:
* Testers replace developers in writing unit test automation scripts. This is not a valid example of the integration of development and testing activities in Agile projects, because it implies that testers take over the responsibility of developers, rather than collaborate with them. Testers should not replace developers in writing unit test automation scripts, because developers have more knowledge and experience in coding and debugging, and because unit testing is an essential part of the development process. Testers should instead work with developers to ensure that the unit test automation scripts are adequate, effective, and maintainable. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 1.2.1, page 9; ISTQB Glossary of Testing Terms2, version 4.0, pages 16 and 55.
NEW QUESTION # 48
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
NEW QUESTION # 49
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. 4, 5
- B. 1, 5
- C. 2, 3
- D. 1, 4
Answer: C
Explanation:
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 to monitor and coordinate their work, and to 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 the 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 taskboard. 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 # 50
Why is regression of software a high risk in agile projects?
- A. Test automation can cause regression of software in the test environment.
- B. There is code churn due to change in business needs over several sprints.
- C. Test-driven development means that existing functionality is not considered.
- D. Regression is built into software as a safeguard against unexpected failures.
Answer: B
NEW QUESTION # 51
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, 3, 4 and 5
- B. Acceptance test criteria are 2, 4, 5 and 6
- C. Acceptance test criteria are 1, 2, 4 and 5
- D. Acceptance test criteria are 1, 2, 3 and 6
Answer: C
Explanation:
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 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 that have been 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 the functional or non-functional requirements of the user story. 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 the functional or non-functional requirements of the user story. 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.
1: ISTQB Foundation Level Agile Tester Syllabus1, Section 2.3.1, pages 15-16; ISTQB Glossary of Testing Terms2, version 4.0, pages 2 and 3.
NEW QUESTION # 52
Which of the following describes the frequency with which usually all changes made to the software are merged and all changed components are integrated regularly in a continuous integration process?
- A. At least once a month
- B. At least once a day
- C. At least once a week
- D. At least once per iteration
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
From theCTFL-AT Syllabus v4.0, Section 4.2Continuous Integration, it states:
"Continuous integration involves integrating code into a shared repository several times a day. Each integration is verified by an automated build and automated tests." Hence,Option D-at least once a day- correctly reflects best practice in continuous integration.
* Option A(once per iteration) andB,Care far too infrequent to meet the goals of CI.
* The objective is to detect integration issuesearly and often, which is only achievable throughdaily (or more frequent)integrations.
References:
CTFL-AT Syllabus v4.0, Section 4.2
Learning Objective (K2) - Understand frequency and purpose of continuous integration
NEW QUESTION # 53
What is the definition of agile software development?
- A. 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.
- 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 way of developing software where the test cases are developed, and often automated, before the software under test is developed.
Answer: A
NEW QUESTION # 54
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 5hours.
- 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 2hours.
Tests should be designed and executed within each session using heuristics, creativity and intuition.
Answer: D
NEW QUESTION # 55
......
CTFL-AT dumps Sure Practice with 82 Questions: https://simplilearn.actual4labs.com/ISQI/CTFL-AT-actual-exam-dumps.html