Pass Authentic ISQI CTFL-AT with Free Practice Tests and Exam Dumps
New CTFL-AT Exam Questions Real ISQI Dumps
NEW QUESTION # 18
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. Performance Testing
- B. Exploratory Testing
- C. Prototype Testing
- D. Functional Testing
Answer: B
Explanation:
Explanation
Exploratory testing is a type of testing that involves simultaneous learning, test design, and test execution. It is suitable for Quadrant 3 because it is business facing and product critique, meaning that it focuses on the user's perspective and the quality attributes of the product. Exploratory testing can help discover new risks, requirements, and defects that may not be covered by other test levels and test types. It can also provide feedback on the usability, functionality, and reliability of the product. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 2.3.2, page 17; ISTQB Glossary of Testing Terms2, version 4.0, page 23.
NEW QUESTION # 19
Which of the following statements is FALSE regarding early and frequent feedback?
- A. Early feedback promotes early discovery and resolution of quality problems.
- B. Early feedback decreases the amount of time needed for system testing.
- C. Early feedback provides the Agile team with information on its productivity.
- D. Early feedback helps to deliver a product that better reflects what the customer wants.
Answer: C
NEW QUESTION # 20
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. 2, 3
- B. 1, 5
- C. 4, 5
- D. 1, 4
Answer: A
NEW QUESTION # 21
Which ONE of the following is an example of a typical "Business-oriented work product"?
- A. The released product.
- B. A user manual.
- C. Acceptance testing entry criteria.
- D. Usability testing test results.
Answer: B
Explanation:
Explanation
Business-oriented work products are those that describe what is needed (e.g., requirements specifications) and how to use it (e.g., user documentation). A user manual is an example of a business-oriented work product, as it provides instructions and guidance on how to use the product from the user's perspective. A user manual may also contain information about the product's features, benefits, and limitations. A user manual is typically written by technical writers, who may collaborate with developers, testers, and business analysts to ensure the accuracy and clarity of the content. A user manual may be delivered in various formats, such as printed, online, or interactive. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 1.2.1, page 10; ASTQB Agile Tester Certification Resources2, Section 1.2.1, page 10.
NEW QUESTION # 22
Which statement about an Agile task board is CORRECT?
- A. It is a detailed visual representation of the status of testing.
- B. It provides detailed visual representation of the whole team's status.
- C. It is updated once at the end of each iteration.
- D. Only "in progress" tasks are shown on the task board.
Answer: B
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 # 23
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. Conversation should include the acceptance criteria discussion.
- C. The card should contain requirements not the user story.
- D. Product owner has written a user story and confirmation is not needed.
Answer: B
NEW QUESTION # 24
Which of the following is a risk that continuous integration introduces?
- A. Teams sometimes over-rely on unit tests and exclude some important system and acceptance tests.
- B. Testers sometimes have too many builds to test, which reduces the quality of testing.
- C. Teams no longer have the ability to run manual tests, as all tests must be automated.
- D. Developer's workload is increased, which can result in a reduction of output.
Answer: D
NEW QUESTION # 25
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. 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. Early and frequent feedback enables the team to deliver the features that represent the highest business value to the customer first.
Answer: A
NEW QUESTION # 26
Which of the following is the BEST way for a test team to keep its independence when working in an Agile development environment?
- A. Share the Test Strategy with the Agile development team, but not the details of the Test Cases.
- B. Assign testers to be members of the Agile team, but ensure the testers report to a different manager than the developers.
- C. Locate the team that develops the test automation framework in a different location to the Agile development team.
- 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: B
Explanation:
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 # 27
Which one of the following is a testable acceptance criterion?
- A. The solution shall support business processes.
- B. The system shall be easy to use.
- C. The tools for testing are tested before use and are meeting the requirements.
- D. The response time to confirm a customer submission must not exceed 5 seconds.
Answer: D
Explanation:
Explanation
A testable acceptance criterion is a condition that can be verified or measured objectively by the tester, customer, or stakeholder. It should be specific, measurable, achievable, relevant, and time-bound (SMART). A testable acceptance criterion should also be written from the user's perspective, achievable within the sprint, and written before development begins1.
Among the four options, only option C meets these criteria. It is specific (the response time to confirm a customer submission), measurable (must not exceed 5 seconds), achievable (within the technical and business constraints), relevant (to the user's needs and expectations), and time-bound (must be met in every sprint). It is also written from the user's perspective, testable (by measuring the response time), and written before development (as part of the user story definition).
Option A is not testable because it is vague and subjective. What does it mean to support business processes?
How can this be verified or measured? Option B is also not testable because it is subjective and ambiguous.
What does it mean to be easy to use? How can this be verified or measured? Option D is not testable because it is not written from the user's perspective. It is an internal quality criterion for the testing team, not an acceptance criterion for the product or feature.
References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.3.2, page 182; ISTQB Foundation Level Agile Tester Sample Exam Questions, Question 2.3.2-2, page 93
NEW QUESTION # 28
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, 2, 4 and 5
- B. Acceptance test criteria are 1, 2, 3 and 6
- C. Acceptance test criteria are 2, 4, 5 and 6
- D. Acceptance test criteria are 1, 3, 4 and 5
Answer: A
Explanation:
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.
References: 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 # 29
You are a tester in an agile team. The user story you are due to test is still under development so your tests are blocked. The main issue holding progress on this user story is that the developer's unit tests are constantly failing.
As an agile tester, which of the following actions should you take?
- A. Use the time to improve and automate existing test cases of other user stories.
- B. Review the design of the problematic user story and improve it where possible.
- C. Create a bug report for each of your blocked tests.
- D. Work together with the developer, suggesting reasons why the tests are failing.
Answer: D
NEW QUESTION # 30
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 easy to identify when the work is divided into user stories.
- B. Risk-based testing fits well in Agile development processes, as risks are analyzed twice - during release and iteration planning.
- C. Risk-based testing does not fit in Agile development processes, as each iteration focuses on limited parts of the product.
- D. Risk-based testing does not fit well in Agile development processes, as short iterations mandate short test times.
Answer: A
NEW QUESTION # 31
Why is regression of software a high risk in agile projects?
- A. Test-driven development means that existing functionality is not considered.
- B. There is code churn due to change in business needs over several sprints.
- C. Regression is built into software as a safeguard against unexpected failures.
- D. Test automation can cause regression of software in the test environment.
Answer: B
Explanation:
Explanation
Regression of software is the risk that a change in one part of the software causes a defect in another part of the software that was previously working correctly. Regression of software is a high risk in agile projects because there is code churn due to change in business needs over several sprints. Code churn is the amount of code that is added, modified, or deleted in a software project over time. Code churn can indicate the volatility and complexity of the software, and the frequency and magnitude of the changes. In agile projects, code churn can be high because the business needs and the user requirements can change rapidly and frequently over several sprints, which are short iterations of development and testing. This means that the software is constantly evolving and adapting to the changing needs, and that the existing functionality and quality may be affected by the new or modified code. Therefore, regression of software is a high risk in agile projects, and it requires effective testing strategies and techniques to prevent, detect, and fix the regression defects. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 2.3.2, page 17; ISTQB Glossary of Testing Terms2, version 4.0, pages 36 and 55
NEW QUESTION # 32
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, 3 and 5
- B. Activities 1, 4 and 6
- C. Activities 1, 3 and 6
- D. Activities 2 and 4
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 # 33
Which one of the following is a testable acceptance criterion?
- A. The solution shall support business processes.
- B. The system shall be easy to use.
- C. The tools for testing are tested before use and are meeting the requirements.
- D. The response time to confirm a customer submission must not exceed 5 seconds.
Answer: D
NEW QUESTION # 34
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. 3, 4
- C. 2, 5
- D. 1, 3
Answer: C
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 # 35
Which of the following statements would you expect to be the MOST direct advantage of the whole-team approach?
- A. Having at least once a day an automated build and test process that detects integration errors early and quickly.
- B. Reducing the involvement of business representatives because of the increased communication and collaboration between testers and developers.
- C. Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.
- D. Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.
Answer: D
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 # 36
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. Performance Testing
- B. Exploratory Testing
- C. Prototype Testing
- D. Functional Testing
Answer: B
NEW QUESTION # 37
Which of the following is NOT a typical task performed by the tester within an Agile team?
- A. Working with business stakeholders to clarify requirements.
- B. Suggesting improvements in team retrospectives.
- C. Ensuring all project status meetings are held according to the plan.
- D. Ensuring the appropriate testing tasks are scheduled during iteration planning.
Answer: C
Explanation:
Explanation
The tester within an Agile team is not responsible for ensuring all project status meetings are held according to the plan. This is typically a task for the Scrum Master, who facilitates the meetings and ensures that the team follows the Agile principles and practices. The tester within an Agile team is responsible for ensuring the appropriate testing tasks are scheduled during iteration planning, suggesting improvements in team retrospectives, and working with business stakeholders to clarify requirements. These are all tasks that contribute to the quality of the software and the testing process, as well as the collaboration and communication within the team and with the customers. References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.3.1, page 171; ISTQB Foundation Level Agile Tester Sample Exam Questions, Question
2.3.1-1, page 82
NEW QUESTION # 38
......
CTFL-AT Exam Info and Free Practice Test Professional Quiz Study Materials: https://www.braindumpquiz.com/CTFL-AT-exam-material.html
Course 2024 CTFL-AT Test Prep Training Practice Exam Download: https://drive.google.com/open?id=1UGskXdWlm4DhuDu5_Ky9PGXpGPEeIz16