[May-2024] Verified ISQI Exam Dumps with CTFL-AT Exam Study Guide
Best Quality ISQI CTFL-AT Exam Questions TrainingQuiz Realistic Practice Exams [2024]
The CTFL-AT certification exam is suitable for software testers who have some experience in agile testing and want to demonstrate their knowledge and skills in this area. ISTQB Certified Tester - Foundation Level Extension - Agile Tester certification is also beneficial for individuals who are planning to work in agile testing projects or teams. By earning the CTFL-AT certification, candidates can enhance their career prospects and increase their earning potential.
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.
ISQI CTFL-AT (ISTQB Certified Tester - Foundation Level Extension - Agile Tester) Certification Exam is a globally recognized certification for software testers that focuses on agile methodologies. ISTQB Certified Tester - Foundation Level Extension - Agile Tester certification is designed to help professionals develop a thorough understanding of agile testing principles and practices. It is ideal for individuals who want to expand their knowledge and skills in agile testing and improve their career prospects in the software testing industry.
NEW QUESTION # 16
Which of the following is a risk that continuous integration introduces?
- A. Teams no longer have the ability to run manual tests, as all tests must be automated.
- B. Developer's workload is increased, which can result in a reduction of output.
- C. Teams sometimes over-rely on unit tests and exclude some important system and acceptance tests.
- D. Testers sometimes have too many builds to test, which reduces the quality of testing.
Answer: D
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 # 17
Why is regression of software a high risk in agile projects?
- A. Test-driven development means that existing functionality is not considered.
- B. Regression is built into software as a safeguard against unexpected failures.
- C. Test automation can cause regression of software in the test environment.
- D. There is code churn due to change in business needs over several sprints.
Answer: D
NEW QUESTION # 18
User Story: As a user I want to be able to calculate tax percentage based on amount of income.
What is the best black box test design technique for verifying the accuracy of this user story?
- A. User story testing - test that the user can enter an income amount and get a result.
- B. Equivalence partitioning - test with low, medium and high income.
- C. Statement testing - test all statements in income calculation.
- D. State transition testing - test all states of income entry.
Answer: B
Explanation:
Explanation
The best black box test design technique for verifying the accuracy of this user story is equivalence partitioning. Equivalence partitioning is a technique that divides the input domain of a system into classes or groups that are expected to behave similarly. By testing one value from each class, the tester can reduce the number of test cases while still achieving good coverage. In this case, the input domainof the system is the amount of income, which can be divided into classes based on the tax percentage applied to different income ranges. For example, if the tax percentage is 10% for income below 10,000, 20% for income between 10,000 and 20,000, and 30% for income above 20,000, then the equivalence classes are: low income (<10,000), medium income (10,000-20,000), and high income (>20,000). By testing one value from each class, such as
5,000, 15,000, and 25,000, the tester can verify that the system calculates the correct tax percentage for each income range. This technique is more efficient and effective than testing all possible values of income, or testing only one value of income, or testing the states of income entry, or testing the statements in income calculation. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 2.3.1, page 19; ISTQB Foundation Level Agile Tester Extension Sample Exam Questions2, Question 5, page 6.
NEW QUESTION # 19
Which of the following statements about the benefits of the Agile processes promoting early and frequent feedback is NOT true?
- A. Feedback from well-conducted Agile retrospectives can be used to positively affect the development process over the course of the next iteration.
- B. Early and frequent feedback enables the team to deliver the features that represent the highest business value to the customer first.
- C. In Agile projects where feedback is provided early and frequently, defects and incorrect requirements are caught earlier and those problems can be fixed faster.
- D. Increasing the frequency of feedback and communication between all the stakeholders involved in Agile projects eliminates all communication problems.
Answer: D
NEW QUESTION # 20
Which of the following statements about the Planning poker test estimate technique are CORRECT?
1) Planning poker is a consensus based technique using a deck of cards.
2) A low test estimate usually means the story should be broken down into multiple smaller stories.
3) A high test estimate usually means the story should be broken down into multiple smaller stories.
4) One poker round is played and then consensus has to be reached.
5) The risk level of each backlog item should be decided before the poker session.
- A. 2, 3, 4
- B. 1, 2, 4
- C. 1, 3, 5
- D. 1, 2, 3
Answer: C
NEW QUESTION # 21
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. 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.
- B. 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. - C. 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.
- D. Ask experienced testers to try and find new defects by using the system without the constraint of documentation and tools.
Answer: B
NEW QUESTION # 22
You have been asked to explain to your client how to define acceptance criteria that are fully testable. Which of the following is the BEST EXAMPLE for testable acceptance criteria?
- A. The interface to External System shall be specified.
- B. The program's icon should be clear and attractive.
- C. The "ID" field must accept input value of a length between 2 and 10 characters.
- D. Action "Reopen" must be available only for a user with a specific authorization level.
Answer: C
Explanation:
Explanation
According to the ISTQB Tester Foundation Level Agile Tester syllabus, acceptance criteria are a set of conditions that a user story must satisfy to be accepted by the customer or stakeholder. Acceptance criteria should be testable, meaning that they can be verified by objective measurements or observations. Testable acceptance criteria should be clear, unambiguous, complete, and consistent. Therefore, option A is the best example for testable acceptance criteria, as it specifies a clear and measurable condition for the input value of the ID field. Option B is not a good example for testable acceptance criteria, as it is vague and does not define any specific condition or expectation for the interface to External System. Option C is not a good example for testable acceptance criteria, as it is incomplete and does not specify what the specific authorization level is or how it is determined. Option D is not a good example for testable acceptance criteria, as it is subjective and not measurable. What is clear and attractive for one user may not be for another. References: ISTQB Tester Foundation Level Agile Tester syllabus, section 1.1.1, page 7; ISTQB Tester Foundation Level Agile Tester syllabus, section 1.1.2, page 8; ISTQB Tester Foundation Level Agile Tester syllabus, section 3.1.1, page 23; ISTQB Tester Foundation Level Agile Tester syllabus, section 3.1.2, page 24.
3of30
NEW QUESTION # 23
Which statement about an Agile task board is CORRECT?
- A. It provides detailed visual representation of the whole team's status.
- B. It is a detailed visual representation of the status of testing.
- C. Only "in progress" tasks are shown on the task board.
- D. It is updated once at the end of each iteration.
Answer: A
Explanation:
Explanation
An Agile task board is a visual framework to display and sync up on the tasks moving between production steps. It is usually applied to the two most popular Agile development frameworks - Kanban and Scrum. Used by software developers and project managers, an Agile board helps manage workloads in a flexible, transparent, and iterative way1. An Agile task board provides a detailed visual representation of the whole team's status, showing which tasks remain to be started, which are in progress, and which are done. It also helps to track the progress of the current sprint, identify bottlenecks, and facilitate collaboration and communication among team members2. References:
1: ISTQB Foundation Level Agile Tester Syllabus, Version 2014, Section 2.1.1
2: ASTQB Agile Tester Certification Resources, Agile Testing Foundations, Chapter 2, Section 2.1.1: 6
NEW QUESTION # 24
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. 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.
- 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. 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.
Answer: A
Explanation:
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 # 25
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. 3, 4
- C. 2, 5
- D. 1, 3
Answer: B
NEW QUESTION # 26
Which of the following sentences related to Risk-based testing is CORRECT?
- A. Risk-based testing fits well in Agile development processes, as risks are analyzed twice - during release and iteration planning.
- 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 does not fit in Agile development processes, as each iteration focuses on limited parts of the product.
Answer: C
NEW QUESTION # 27
Consider an online application that allows registered users to pay the annual car tax based on the vehicle's engine power in kW. Given the following user story:
"As a customer I need the online application to calculate the annual car tax amount that I need to pay for my car:
* If the power of the vehicle is less than 20 kW, then the annual car tax is free
* If the power of the vehicle is more or equal than 20 kW but less or equal than 150 kW, then the annual car tax is 250 Euros
* If the power of the vehicle is more than 150 kW, then the annual car tax is 750 Euros" What is the MOST suitable use of a black-box test design technique for this user story?
- A. Decision table testing. Test the following conditions:
Conditions=registered user logged in; inserted power of the vehicle=20kW; Action=Car tax paid - B. State transition testing. Test the transitions between the following states:
logging in, inserting the power of the vehicle, making payment, logging out. - C. Use case testing Test the following use case (Actor=registered user):Pre-condition=registered user logged in Scenario=registered user inserts the power of the vehicle, making payment and logs out Post-condition=car tax paid and registered user logged out
- D. Equivalence partitioning. Test the annual car tax value for the following partitions:
[power of the vehicle<20 kW ; 20 kW power of the vehicles150 kW; power of the vehicle>150 kW]
Answer: D
Explanation:
Explanation
Equivalence partitioning is a black-box test design technique that divides the input domain of a system into classes of data from which test cases can be derived. The idea is that if a system works correctly for a representative value from an equivalence class, it will work correctly for all values from that class, and vice versa. Equivalence partitioning reduces the number of test cases by eliminating redundant ones. For the given user story, equivalence partitioning is the most suitable technique because it can test the different outcomes of the annual car tax calculation based on the power of the vehicle, which is the main input for the system. By testing one value from each partition, the tester can verify the functionality of the system and detect any errors in the calculation logic. The other techniques are not as suitable because they do not focus on the inputdomain of the system, but rather on the conditions, transitions, or scenarios that are not directly related to the user story. References:
1: ISTQB Foundation Level Agile Tester Syllabus, Version 2014, Section 2.2.2
2: ASTQB Agile Tester Certification Resources, Agile Testing Foundations, Chapter 3, Section 3.2.2: 3
NEW QUESTION # 28
Which of the following activities are done in release planning?
1) Identifying testable user stories with acceptance criteria.
2) Elaborating the user stories into tasks.
3) Prioritizing the user stories.
4) Creating acceptance tests for the user stories.
5) Analyzing risks for each of the user stories.
6) Performing high level estimation for the release.
- A. Activities 2 and 4
- B. Activities 2, 3 and 5
- C. Activities 1, 3 and 6
- D. Activities 1, 4 and 6
Answer: C
Explanation:
Explanation
Release planning is a process of defining the scope and timeline for an iterative or incremental product development project. It is used in agile or hybrid projects where a mid- to long-term planning of the product or system development or integration is required12. Release planning involves the following activities:
Identifying testable user stories with acceptance criteria. User stories are short descriptions of the features or functionalities that the customer or user wants from the product. Acceptance criteria are the conditions that must be met for the user story to be considered done and acceptable. Identifying testable user stories with acceptance criteria helps to define the scope and quality of the release13.
Prioritizing the user stories. User stories are prioritized based on the value they deliver to the customer or user, as well as the dependencies, risks, and costs associated with them. Prioritizing the user stories helps to determine the order and frequency of the releases13.
Performing high level estimation for the release. High level estimation is a technique to estimate the effort, time, and resources needed to complete the user stories in the release. High level estimation can be done using various methods, such as analogy, expert judgment, planning poker, etc. Performing high level estimation for the release helps to set realistic and achievable goals and deadlines13.
Therefore, activities 1, 3 and 6 are done in release planning. Activities 2, 4 and 5 are done in iteration planning, which is a more detailed and short-term planning of the work to be done in each iteration or sprint13. References: 1: ISTQB Foundation Level Agile Tester Syllabus, Section 2.2, Fundamental Agile Testing Principles, Practices and Processes1; 2: Agile Release Planning in Hybrid and Agile Projects4; 3: How to Create an Agile Release Plan5
NEW QUESTION # 29
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. Payment for parking ticket is restricted to cash only (no credit card supported).
- C. Price for a bus ticket was calculated incorrectly.
- D. Failed to buy a bus ticket after 18:00.
Answer: B
NEW QUESTION # 30
Which of the following sentences about the integration of development and testing activities in Agile projects is INCORRECT?
- A. Testers replace developers in writing unit test automation scripts.
- B. While developers develop automated unit test scripts, testers write automated system level tests.
- C. Developers write acceptance criteria and test cases, together with testers.
- D. Developers and testers may work as a pair to develop and test a feature.
Answer: A
NEW QUESTION # 31
What is the main benefit of the Test Pyramid?
- A. It acts as a metric for testing progress.
- B. It means testing is involved early in the development cycle.
- C. It helps in evaluating the amount of test cases needed.
- D. It shows complexity of testing activities.
Answer: A
NEW QUESTION # 32
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. Agile retrospectives should be focused mainly on impediments that are outside the control of the team because these issues are more challenging.
- D. 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.
Answer: D
NEW QUESTION # 33
Which of the following would provide the MOST independence for testers working with agile teams?
- A. 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.
- B. Testers are fully embedded in each Agile team to perform many of the testing tasks.
- C. Testers from an independent test team are assigned on-demand for the final days of each sprint.
- D. 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.
Answer: A
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 # 34
What is the definition of agile software development?
- A. A way of developing software where the test cases are developed, and often automated, before the software under test is developed.
- B. A 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.
- C. 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
- D. 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.
Answer: B
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 # 35
Your agile team is using the Testing Quadrants to ensure that all important test levels and test types are covered in the test plan.
In relation to Quadrant 3 - business facing and product critique, what should be considered for the plan?
- A. Prototype Testing
- B. Performance Testing
- C. Exploratory Testing
- D. Functional Testing
Answer: C
NEW QUESTION # 36
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. The conversation is not required and the team should start developing.
- B. Product owner has written a user story and confirmation is not needed.
- C. The card should contain requirements not the user story.
- D. Conversation should include the acceptance criteria discussion.
Answer: D
Explanation:
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 # 37
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: B
Explanation:
Explanation
Behavior-Driven Development (BDD) is a software development approach that allows a developer to define accurate unit tests focused on business needs. BDD uses a common language that is understandable by both technical and non-technical stakeholders, such as Given-When-Then scenarios.BDD helps to align the development and testing activities with the customer expectations and business goals . References:
1: ISTQB Foundation Level Agile Tester Syllabus, Version 2014, Section 2.2.2
2: ASTQB Agile Tester Certification Resources, Agile Testing Foundations, Chapter 3, Section 3.2.2
NEW QUESTION # 38
Which of the following statements about the benefits of the Agile processes promoting early and frequent feedback is NOT true?
- A. Feedback from well-conducted Agile retrospectives can be used to positively affect the development process over the course of the next iteration.
- B. Early and frequent feedback enables the team to deliver the features that represent the highest business value to the customer first.
- C. In Agile projects where feedback is provided early and frequently, defects and incorrect requirements are caught earlier and those problems can be fixed faster.
- D. Increasing the frequency of feedback and communication between all the stakeholders involved in Agile projects eliminates all communication problems.
Answer: D
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 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 store source code and automated tests.
- C. A task management tool is used to manage and track user stories, tests and other tasks.
- D. A task management tool is used by team members to share ideas and collaborate on assigned tasks.
Answer: C
Explanation:
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 # 40
......
Authentic Best resources for CTFL-AT: https://www.trainingquiz.com/CTFL-AT-practice-quiz.html
CTFL-AT Test Engine Practice Exam: https://drive.google.com/open?id=1_ovtRhOIl9ceVsrWeQZZzzwltPicew3h
