[Jan-2024] Updated and Accurate CTFL-AT Questions & Answers for passing the exam Quickly
Download Real CTFL-AT Exam Dumps for candidates. 100% Free Dump Files
ISQI CTFL-AT (ISTQB Certified Tester - Foundation Level Extension - Agile Tester) Certification Exam is designed to test the knowledge and skills of individuals in agile testing methodologies. ISTQB Certified Tester - Foundation Level Extension - Agile Tester certification exam is based on the ISTQB syllabus for the foundation level extension and covers topics such as agile software development, agile testing, and agile testing methods and techniques. The CTFL-AT certification is recognized globally and is highly valued by both employers and professionals in the industry.
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. Functional Testing
- B. Exploratory Testing
- C. Performance Testing
- D. Prototype 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
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, 3 and 6
- B. Acceptance test criteria are 1, 3, 4 and 5
- C. Acceptance test criteria are 2, 4, 5 and 6
- D. Acceptance test criteria are 1, 2, 4 and 5
Answer: D
NEW QUESTION # 21
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. State transition testing - test all states of income entry.
- 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. Statement testing - test all statements in income calculation.
Answer: B
NEW QUESTION # 22
Which of the following is NOT a statement of value from the Agile Manifesto?
- A. Working software over comprehensive documentation
- B. Customer collaboration over contract negotiation.
- C. Processes and tools over individuals and interactions.
- D. Responding to change over following a plan.
Answer: C
Explanation:
Explanation
The Agile Manifesto is a declaration of four values and twelve principles that guide the Agile software development approach12. The four values of the Agile Manifesto are12:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
These values emphasize the importance of human collaboration, working product, customer feedback, and adaptability over rigid processes, extensive documentation, fixedcontracts, and predefined plans. The values do not imply that the items on the right are not important, but rather that the items on the left are more important and should be prioritized.
Therefore, the statement that is NOT a value from the Agile Manifesto is B, as it contradicts the first value of the Agile Manifesto. The correct statement should be "Individuals and interactions over processes and tools". References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 10; ISTQB Agile Tester Sample Exam2, question 1.
NEW QUESTION # 23
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. State transition testing - test all states of income entry.
- 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. Statement testing - test all statements in income calculation.
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 # 24
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 1, 3 and 6
- B. Activities 1, 4 and 6
- C. Activities 2, 3 and 5
- D. Activities 2 and 4
Answer: A
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 # 25
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 fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories.
- 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: B
NEW QUESTION # 26
Which tasks are typically performed by a tester on an Agile project?
1) Implementing test strategy.
2) Documenting business requirements.
3) Measuring and reporting test coverage.
4) Coaching development team in relevant aspects of testing.
5) Executing test-driven development tests.
- A. 2, 5
- B. 1, 3
- C. 1, 3, 4
- D. 2, 4, 5
Answer: D
NEW QUESTION # 27
You are developing the code that controls an industrial Espresso machine which will be operated by waiting staff in restaurants.
The machine is rather complicated and has lots of switches and buttons, so in the next iteration instructions will be provided to the operator on a small LCD screen.
A User Story for the Operator-Instructions module is as follows:
"As an operator of the Espresso machine, I would like to know how to steam milk, so I can add steamed milk to the coffee."
The following is a list of risks identified for this story, with assigned probability and impact.
- A. The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High
- B. A small child may try to steam milk. Probability: High. Impact: Low
- C. An untrained customer will attempt to use the coffee machine. Probability: High. Impact: High
- D. Operators will not read the instructions and will try various switches and buttons until something works.
Probability: Low. Impact: Low
Answer: A
Explanation:
Explanation
Risk-based testing is a technique that prioritizes testing activities based on the level of risk associated with each feature or requirement. The level of risk is usually calculated by multiplying the probability and impact of each risk. The higher the risk level, the more testing effort should be allocated to mitigate the risk. In this case, the risk level for each option is as follows:
A). Risk level = Low x Low = Low
B). Risk level = Low x High = Medium
C). Risk level = High x High = High
D). Risk level = High x Low = Medium
Therefore, the highest risk level is C, followed by B and D, and then A.
The User Story for the Operator-Instructions module should be tested according to this risk order, starting with C, then B, then D, and finally A.
Hence, the answer is B, as it is the second highest risk level and should be tested after C.
References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 16; ISTQB Agile Tester Sample Exam2, question 18.
NEW QUESTION # 28
Which of the following is a benefit of a whole-team approach?
- A. Enables the team to focus on solely their separate areas of expertise and responsibility.
- B. Enables testers to execute their responsibility for quality for the combined team.
- C. Enables reduction in test duplication as the testers and test engineers function as a single team.
- D. Enables the various skill sets within the team to be leveraged to the benefit of the project.
Answer: D
NEW QUESTION # 29
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 fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories.
- 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: B
Explanation:
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 # 30
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. 2, 5
- B. 4, 5
- C. 1, 3
- D. 3, 4
Answer: D
Explanation:
Explanation
The acceptance criteria for a sprint are the conditions that must be met for the user stories to be considered done and deliver value to the customer1. The acceptance criteria should be specific, measurable, achievable, relevant, and testable2. In this case, the plan for the sprint is to increase performance of the system, so the acceptance criteria should reflect that goal. Therefore, the acceptance criteria that would be expected for Sprint
5 are:
100% of the existing regression test suite has passed. This criterion ensures that the system has not introduced any new defects or broken any existing functionality while improving performance3.
System is responding in less than 3 seconds, 90% of the time. This criterion defines a clear and quantifiable performance target that can be verified by testing4.
The other options are not relevant or appropriate acceptance criteria for Sprint 5:
User access for all roles has been validated. This criterion is not related to the performance of the system, but rather to the security or functionality of the system. It might be an acceptance criterion for a different sprint or user story, but not for Sprint 55.
A static analysis tool has been executed for all code. This criterion is not a customer
NEW QUESTION # 31
Which ONE of the following is an example of a typical "Business-oriented work product"?
- A. Acceptance testing entry criteria.
- B. A user manual.
- C. The released product.
- D. Usability testing test results.
Answer: A
NEW QUESTION # 32
What is the main benefit of the Test Pyramid?
- A. It helps in evaluating the amount of test cases needed.
- B. It shows complexity of testing activities.
- C. It means testing is involved early in the development cycle.
- D. It acts as a metric for testing progress.
Answer: A
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 # 33
Which of the following statements about a test charter are CORRECT?
1) It is used mainly in exploratory tests.
2) It is used to monitor a test process.
3) It may make reference to user stories.
4) It contains notes taken during a test session.
5) It is used to outline the company test policy.
- A. 1, 2, 5
- B. 1, 3, 4
- C. 2, 4, 5
- D. 2, 3, 4
Answer: B
Explanation:
Explanation
A test charter is a document that describes the scope, objective, and approach of an exploratory testing session.
It is used mainly in exploratory tests to guide the tester's actions and record the findings. A test charter may make reference to user stories, requirements, risks, or other sources of information that are relevant to the testing mission. A test charter also contains notes taken during a test session, such as test ideas, test results, bugs, issues, and observations. A test charter is not used to monitor a test process, as it is not a formal metric or report. It is also not used to outline the company test policy, as it is specific to a particular test session and context. References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.2.3, page 18; ASTQB Agile Tester Certification Resources, Section 2.2.3, page 18; How to Write an Exploratory Test Charter, Creating an Exploratory Testing Charter, What is Exploratory Testing?.
NEW QUESTION # 34
Which ONE of the following is an example of a typical "Business-oriented work product"?
- A. Acceptance testing entry criteria.
- B. A user manual.
- C. The released product.
- 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 # 35
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. 2, 5
- B. 4, 5
- C. 1, 3
- D. 3, 4
Answer: D
NEW QUESTION # 36
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. Action "Reopen" must be available only for a user with a specific authorization level.
- B. The program's icon should be clear and attractive.
- C. The interface to External System shall be specified.
- D. The "ID" field must accept input value of a length between 2 and 10 characters.
Answer: A
NEW QUESTION # 37
What is the definition of agile software development?
- A. 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.
- B. A framework to describe the software development lifecycle activities from requirements specification to maintenance where test planning of the various test levels is done as soon as the test basis is ready
- C. 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.
- D. A way of developing software where the test cases are developed, and often automated, before the software under test is developed.
Answer: C
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. 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. Feedback from well-conducted Agile retrospectives can be used to positively affect the development process over the course of the next iteration.
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
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. Action "Reopen" must be available only for a user with a specific authorization level.
- B. The "ID" field must accept input value of a length between 2 and 10 characters.
- C. The program's icon should be clear and attractive.
- D. The interface to External System shall be specified.
Answer: B
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 # 40
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 1, 3 and 6
- B. Activities 1, 4 and 6
- C. Activities 2, 3 and 5
- D. Activities 2 and 4
Answer: A
NEW QUESTION # 41
......
Prepare Important Exam with CTFL-AT Exam Dumps: https://pass4sure.pdf4test.com/CTFL-AT-actual-dumps.html
