Pass ISQI CTFL-AT Exam Quickly With PDFVCE
Prepare CTFL-AT Question Answers - CTFL-AT Exam Dumps
To prepare for the CTFL-AT exam, candidates can take advantage of the various training and study materials available. ISQI offers a range of training courses and study materials, such as the Agile Tester Extension Syllabus, Agile Tester Extension Sample Exam, and Agile Tester Extension Self-Study Course. Additionally, candidates can take advantage of online resources, such as forums and blogs, to learn from other professionals and gain insights into agile testing practices. With a CTFL-AT certification, professionals can demonstrate their expertise in agile testing and enhance their career prospects in the software testing industry.
NEW QUESTION # 23
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 easy to identify when the work is divided into user stories.
- D. Risk-based testing fits well in Agile development processes, as risks are analyzed twice - during release and iteration planning.
Answer: C
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 # 24
Which of the following statements would you expect to be the MOST direct advantage of the whole-team approach?
- A. Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.
- B. Having at least once a day an automated build and test process that detects integration errors early and quickly.
- C. Reducing the involvement of business representatives because of the increased communication and collaboration between testers and developers.
- D. Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.
Answer: A
NEW QUESTION # 25
What is the main benefit of the Test Pyramid?
- A. It shows complexity of testing activities.
- B. It acts as a metric for testing progress.
- C. It helps in evaluating the amount of test cases needed.
- D. It means testing is involved early in the development cycle.
Answer: C
Explanation:
Explanation
The Test Pyramid is a model for organizing tests in a way to make the process of testing faster, efficient and cost-effective. This model focusses on getting maximum functional testing getting covered by faster and less brittle tests like Unit and API tests1. The main benefit of the Test Pyramid is that it helps in evaluating the amount of test cases needed for each level of testing. The Test Pyramid suggests that the number of test cases should decrease as we move up the pyramid, from unit tests to integration tests to end-to-end tests. This is because unit tests are more granular, isolated, and easy to write and maintain, while end-to-end tests are more complex, dependent, and brittle. The Test Pyramid also helps in balancing the test coverage and the test execution time, as unit tests provide high coverage and low execution time, while end-to-end tests provide low coverage and high execution time. By following the Test Pyramid, teams can optimize their testing efforts and resources, and ensure that they have a sufficient and effective test suite for their software. References:
ISTQB Foundation Level Agile Tester Syllabus, Section 2.2.1, page 16; ASTQB Agile Tester Certification Resources, Section 2.2.1, page 16; What is Test Pyramid : Getting started with Test Automation Pyramid, The Practical Test Pyramid - Martin Fowler, Testing Pyramid: What Is It and How To Use It | Solvd.
NEW QUESTION # 26
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. 2, 3
- C. 1, 5
- D. 1, 4
Answer: B
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 # 27
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. 1, 3
- B. 3, 4
- C. 2, 5
- D. 2, 3
Answer: C
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 # 28
Which of the following would provide the MOST independence for testers working with agile teams?
- A. Testers are fully embedded in each Agile team to perform many of the testing tasks.
- B. 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.
- C. 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.
- D. Testers from an independent test team are assigned on-demand for the final days of each sprint.
Answer: C
Explanation:
Explanation
Independence in testing is the degree of separation between the person who tests something and the person who developed it. Independence can help to reduce bias, increase objectivity, and provide different viewpoints. However, independence also has some drawbacks, such as increased communication overhead, reduced collaboration, and delayed feedback. In agile projects, testers are usually embedded in the agile teams to perform many of the testing tasks, such as unit testing, integration testing, acceptance testing, etc. This provides a high level of collaboration and fast feedback, but also reduces the independence of the testers.
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, would provide the most independence for testers working with agile teams. However, this would also introduce many disadvantages, such as lack of alignment with the agile principles, loss of context and domain knowledge, delayed defect detection and resolution, and increased risk of missing customer expectations. References: ISTQB Foundation Level Agile Tester Syllabus, Section
1.1.2, page 8; ASTQB Agile Tester Certification Resources, Section 1.1.2, page 8.
NEW QUESTION # 29
Which of the following is a typical task performed by a tester within a Scrum team?
- A. Coaching other team members in self-organization and cross-functionality
- B. Suggesting improvements in sprint retrospectives
- C. Removing impediments to the Scrum team's progress
- D. Prioritizing the items in the product backlog
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 5.1 and 5.3:
"Testers, like all team members, participate in retrospectives and are encouraged to suggest improvements to team processes and product quality." SoOption Ais correct. Testersactively engagein retrospectives andsuggest improvementsbased on their testing experience.
* Option BandCrefer toScrum Master responsibilities.
* Option Dis the responsibility of theProduct Owner.
References:
CTFL-AT Syllabus v4.0, Sections 5.1 and 5.3
Scrum Guide - Scrum Roles and Responsibilities
Learning Objective (K1) - Recall tester tasks within Scrum teams
NEW QUESTION # 30
Which of the following statements would you expect to be the MOST direct advantage of the whole-team approach?
- A. Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.
- B. Having at least once a day an automated build and test process that detects integration errors early and quickly.
- C. Reducing the involvement of business representatives because of the increased communication and collaboration between testers and developers.
- D. Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.
Answer: A
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 # 31
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. While developers develop automated unit test scripts, testers write automated system level tests.
- C. Developers and testers may work as a pair to develop and test a feature.
- D. Testers replace developers in writing unit test automation scripts.
Answer: D
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 # 32
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. 1, 3
- C. 3, 4
- D. 2, 5
Answer: C
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 # 33
Which of the following is the BEST way for a test team to keep its independence when working in an Agile development environment?
- A. Assign testers to be members of the Agile team, but ensure the testers report to a different manager than the developers.
- B. Locate the team that develops the test automation framework in a different location to the Agile development team.
- C. Share the Test Strategy with the Agile development team, but not the details of the Test Cases.
- D. Co-locate only some of the testers with the Agile development team, while the rest of the testers are in a different location.
Answer: A
Explanation:
According to the ISTQB Tester Foundation Level Agile Tester syllabus, one of the key principles of agile testing is that testers are integrated into the agile team and work closely with developers and other stakeholders. However, this does not mean that testers lose their independence or objectivity. Testers should still be able to provide an unbiased view of the quality of the software and challenge the assumptions and decisions made by the team. Therefore, option C is the best way for a test team to keep its independence when working in an agile development environment, as it allows testers to be part of the agile team, but also report to a different manager than the developers, who can support their professional development and ensure their independence. Option A is not a good way to keep independence, as it limits the transparency and collaboration between testers and developers, which are essential for agile testing. Option B is also not a good way to keep independence, as it creates a physical and organizational barrier between the test automation team and the agile development team, which can hinder communication and feedback. Option D is also not a good way to keep independence, as it creates an inconsistency and imbalance between the testers who are co- located with the agile development team and those who are not, which can affect the quality and efficiency of the testing process. References: ISTQB Tester Foundation Level Agile Tester syllabus, section 1.2.1, page
91; ISTQB Tester Foundation Level Agile Tester syllabus, section 1.2.2, page 101; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.1.1, page 141; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.2.1, page 161; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.2.2, page 171.
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. Statement testing - test all statements in income calculation.
- 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. State transition testing - test all states of income entry.
Answer: B
NEW QUESTION # 35
Based on the skills required for testers in Agile teams, which of the following activities would you expect least likely to be performed by testers in Agile projects?
- A. Working collaboratively with a developer to develop and test a feature
- B. Identifying and updating test cases from previous iterations that are affected by the changes made in the current iteration
- C. Actively participating in specification workshops aimed at clarifying user stories through examples that will be transformed into tests
- D. Tracking the failures of the unit tests that are written when using the Test-Driven Development practice
Answer: D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 3.2Test-Driven Development, and 1.3The Whole-Team Approach, testers:
"Collaborate in test-related activities including test case creation, exploratory testing, and user story clarification."
"Unit tests are typically the responsibility of developers, especially in TDD practices." Therefore,Option Aisleast likely, asunit test tracking in TDDis primarily adeveloper responsibility, not a tester's routine task.
* Options B, C, and D all describekey Agile tester activities, such asmaintaining regression tests, collaborating with developers, andparticipating in specification workshops (BDD/ATDD practices)
.
References:
CTFL-AT Syllabus v4.0, Sections 1.3, 3.2
Learning Objective (K2) - Understand tester roles and responsibilities in Agile
NEW QUESTION # 36
Which of the following statements about the test pyramid is true?
- A. The test pyramid concept is based on the principle of eliminating defects as early as possible in the software lifecycle
- B. 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
- C. The test pyramid emphasizes having more automated tests at the higher test levels and a decreasing number of them at the lower test levels
- D. The test pyramid concept states that every software system consists always of four different test levels (unit, integration, system, acceptance)
Answer: A
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 # 37
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. 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.
- B. 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.
- C. 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.
- D. 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.
Answer: D
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 # 38
Which of the following statements about the benefits of the Agile processes promoting early and frequent feedback is NOT true?
- A. Increasing the frequency of feedback and communication between all the stakeholders involved in Agile projects eliminates all communication problems.
- B. Feedback from well-conducted Agile retrospectives can be used to positively affect the development process over the course of the next iteration.
- C. Early and frequent feedback enables the team to deliver the features that represent the highest business value to the customer first.
- 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: A
Explanation:
Explanation
The Agile processes promote early and frequent feedback from the customers, users, testers, developers, and other stakeholders involved in the project. This feedback helps to ensure that the product meets the expectations and needs of the customers and users, and that the development process is continuously improved and adapted to the changing requirements and environment. However, increasing the frequency of feedback and communication does not eliminate all communication problems, as there may still be issues such as misunderstandings, misinterpretations, conflicts, or cultural differences that need to be resolved. Therefore, the statement D is not true, as it implies that communication problems are completely avoided by the Agile processes. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 1.2.1, page 9; ISTQB Foundation Level Agile Tester Extension Sample Exam Questions2, Question 4, page 5.
NEW QUESTION # 39
Which of the following would provide the MOST independence for testers working with agile teams?
- A. Testers are fully embedded in each Agile team to perform many of the testing tasks.
- B. 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.
- C. 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.
- D. Testers from an independent test team are assigned on-demand for the final days of each sprint.
Answer: C
NEW QUESTION # 40
Which of the following statements is true within an Agile team?
- A. Each team member plays a role in performing test-related tasks but only testers are responsible for product quality
- B. Testers may have difficulty keeping pace with the incoming changes in time-boxed iterations
- C. Unlike traditional projects, testers are not asked to measure and report test coverage, and to report defects
- D. When adopting test-driven development, testers write all the tests while developers write all the code to make these tests pass
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 2.4 and 2.5:
"Due to frequent changes and short iterations, testers must be flexible and responsive. However, keeping up with pace can be a challenge." Thus,Option Dis correct -testers may strugglewith rapid changes and short feedback loops, which is a known challenge in Agile.
* Option Ais false - testers still measurecoverage and report defects.
* Option Bmisrepresents TDD -developerstypically write the unit tests in TDD.
* Option Cis incorrect -quality is a shared responsibilityin Agile.
References:
CTFL-AT Syllabus v4.0, Sections 2.4 and 2.5
Learning Objective (K2) - Understand tester challenges in Agile environments
NEW QUESTION # 41
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
- B. 2, 4, 5
- C. 2, 5
- D. 1, 3, 4
Answer: B
NEW QUESTION # 42
Which of the following activities would you expect most likely to be performed during daily stand-up meetings?
- A. Highlighting blocking issues that are impeding the test progress
- B. Discussing what did not work well during the previous iteration
- C. Creating acceptance tests for the user stories selected for the current iteration
- D. Identifying specific quality risks associated with the next iteration
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 5.2Daily Stand-Ups, it states:
"The daily stand-up is a short meeting used to discuss progress, plans for the day, and any impediments that are blocking progress." Therefore,Option Bis correct - highlightingimpediments/blockersis a key goal of thedaily stand-up.
* Option Ais aretrospectiveactivity.
* Option Cis done duringplanning or risk assessment, not the daily meeting.
* Option Dis part ofiteration planning, not the stand-up.
References:
CTFL-AT Syllabus v4.0, Section 5.2
Learning Objective (K1) - Recall daily stand-up purpose and format
NEW QUESTION # 43
......
Real ISQI CTFL-AT Exam Questions [Updated 2026]: https://certification-questions.pdfvce.com/ISQI/CTFL-AT-exam-pdf-dumps.html