Get Ready with CTFL-AT Exam Dumps (2025) [Q17-Q33]

5/5 - (1 vote)

Get Ready with CTFL-AT Exam Dumps (2025)

Realistic CTFL-AT Dumps are Available for Instant Access

The CTFL-AT exam is a multiple-choice, computer-based exam that consists of 40 questions. Candidates are given 60 minutes to complete the exam, and a passing score of 65% is required. CTFL-AT exam covers a range of topics, including Agile development methodologies, Agile testing techniques, and testing in Agile projects. It is recommended that candidates have at least six months of experience working in Agile development projects before taking the exam.

Q17. An Agile team uses a burndown chart and a task board to track progress within each iteration. In the burndown chart, the x-axis represents the days of iteration, while the y-axis represents the story points.
The task board uses columns: “To Do”, “Ongoing”, “Done”.
A user story for the current iteration has 20 story points and 4 tasks (T1, T2, T3, T4). At the end of Day 5, all are in “Ongoing”. At the end of Day 6, T1 and T2 move to “Done”, while T3 and T4 remain “Ongoing”.
Which of the following statements would you expect most likely to be true at the end of Day 6?

The burndown chart should be updated with a number of 10 burned story points

The burndown chart must be changed to represent the unit of work in hours because story points cannot be used

The burndown chart should not be updated because T3 and T4 are not “Done” yet

Q18. Which of the following statements is FALSE regarding early and frequent feedback?

Early feedback decreases the amount of time needed for system testing.

Early feedback promotes early discovery and resolution of quality problems.

Early feedback provides the Agile team with information on its productivity.

Early feedback helps to deliver a product that better reflects what the customer wants.

Q19. Which of the following statements is true in Agile projects?

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

Shorter timeframes and frequent changes require the adoption of good practices for test design and implementation, which should be defined during release planning

The risk of regression tends to decrease when code that worked in previous iterations gets modified due to new features in subsequent iterations

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

Q20. Which one of the following is a testable acceptance criterion?

The solution shall support business processes.

The system shall be easy to use.

The response time to confirm a customer submission must not exceed 5 seconds.

The tools for testing are tested before use and are meeting the requirements.

Q21. Which of the following tools would you expect to be the most useful to report defects found during exploratory testing sessions in Agile projects?

Tools that generate data to populate an application’s database

Continuous integration and build distribution tools

Application lifecycle management (ALM) and task management tools

Tools that capture and log activities performed on an application during its use

Q22. Why is regression of software a high risk in agile projects?

Test-driven development means that existing functionality is not considered.

Test automation can cause regression of software in the test environment.

Regression is built into software as a safeguard against unexpected failures.

There is code churn due to change in business needs over several sprints.

Q23. During a retrospective, which of the following items would be the LEAST effective to generate discussions on process improvement?

The build process was slow and this often caused delays waiting for the build to complete.

For the last sprint the estimated and actual effort were much higher than the team capacity.

The automation tests failed frequently without any logs to help in debugging the failure reason.

One of the testers was regarded as being both disruptive and lazy and did not contribute to team success.

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 process improvement, 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.

Q24. Which of the following is a risk that continuous integration introduces?

Teams sometimes over-rely on unit tests and exclude some important system and acceptance tests.

Testers sometimes have too many builds to test, which reduces the quality of testing.

Teams no longer have the ability to run manual tests, as all tests must be automated.

Developer’s workload is increased, which can result in a reduction of output.

Q25. Which of the following is NOT a statement of value from the Agile Manifesto?

Working software over comprehensive documentation

Processes and tools over individuals and interactions.

Responding to change over following a plan.

Customer collaboration over contract negotiation.

Q26. Which of the following is a benefit of a whole-team approach?

Enables reduction in test duplication as the testers and test engineers function as a single team.

Enables testers to execute their responsibility for quality for the combined team.

Enables the team to focus on solely their separate areas of expertise and responsibility.

Enables the various skill sets within the team to be leveraged to the benefit of the project.

Q27. What is the main benefit of the Test Pyramid?

It means testing is involved early in the development cycle.

It helps in evaluating the amount of test cases needed.

It shows complexity of testing activities.

It acts as a metric for testing progress.

Q28. Which of the following is a benefit of a whole-team approach?

Enables reduction in test duplication as the testers and test engineers function as a single team.

Enables testers to execute their responsibility for quality for the combined team.

Enables the team to focus on solely their separate areas of expertise and responsibility.

Enables the various skill sets within the team to be leveraged to the benefit of the project.

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

A task management tool is used by team members to share ideas and collaborate on assigned tasks.

A task management tool is used to manage and track user stories, tests and other tasks.

A task management tool is used to store source code and automated tests.

A task management tool allows developers to continuously integrate their code.

Q30. What is the definition of agile software development?

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.

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.

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

A way of developing software where the test cases are developed, and often automated, before the software under test is developed.

Q31. 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.

1, 3

3, 4

4, 5

2, 5

Q32. Which of the following would provide the MOST independence for testers working with agile teams?

Testers are fully embedded in each Agile team to perform many of the testing tasks.

Testers from an independent test team who do not get involved with the Agile team, but are assigned to do System Testing once all sprints are completed.

Testers from an independent test team are assigned on-demand for the final days of each sprint.

Testers from an independent test team are assigned to the Agile team at the beginning of the project, returning for re-assignment to a new agile team.

Q33. 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.

1, 3

3, 4

4, 5

2, 5