
Free CTFL-AT Exam Braindumps - New 2024 ISQI Pratice Exam
Practice Test for CTFL-AT Certification Real 2024 Mock Exam
NEW QUESTION # 16
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
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
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 # 19
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
NEW QUESTION # 20
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 # 21
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 provides the Agile team with information on its productivity.
- C. Early feedback decreases the amount of time needed for system testing.
- D. Early feedback helps to deliver a product that better reflects what the customer wants.
Answer: C
Explanation:
Explanation
Early and frequent feedback is one of the core values of Agile development. It helps the Agile team to deliver features with the highest business value first, to discover and resolve quality problems as soon as possible, to provide information on the team's productivity and progress, and to ensure that the product meets the customer's expectations and needs. However, early feedback does not necessarily decrease the amount of time needed for system testing, as system testing is still an important activity in Agile projects to verify the integration and functionality of the whole system. Early feedback may reduce the number of defects found in system testing, but it does not eliminate the need for system testing. References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 10; ISTQB Agile Tester Sample Exam2, question 11.
NEW QUESTION # 22
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. Operators will not read the instructions and will try various switches and buttons until something works.
Probability: Low. Impact: Low - C. A small child may try to steam milk. Probability: High. Impact: Low
- D. An untrained customer will attempt to use the coffee machine. Probability: High. Impact: High
Answer: A
NEW QUESTION # 23
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
NEW QUESTION # 24
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
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 # 25
Which agile development approach incorporates the following practices:
* a project is divided into iterations called sprints
* each sprint results in a potentially releasable/shippable product?
- A. Extreme Programming
- B. Continuous Integration
- C. Kanban
- D. Scrum
Answer: D
NEW QUESTION # 26
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 # 27
Which agile development approach incorporates the following practices:
* a project is divided into iterations called sprints
* each sprint results in a potentially releasable/shippable product?
- A. Extreme Programming
- B. Continuous Integration
- C. Kanban
- D. Scrum
Answer: D
Explanation:
Explanation
Scrum is an agile development approach that incorporates the following practices:
a project is divided into iterations called sprints, which are typically 2-4 weeks long each sprint starts with a planning meeting, where the team selects a subset of user stories from the product backlog to work on each sprint ends with a review meeting, where the team demonstrates the potentially releasable/shippable product increment to the stakeholders and collects feedback each sprint also includes a retrospective meeting, where the team reflects on the process and identifies areas for improvement123 References: 1: ISTQB Foundation Level Agile Tester Syllabus, Section
2.1, Agile Software Development1; 2: ASTQB Agile Tester Certification Resources, Section 2.1, Agile Software Development2; 3: What is Agile? | Atlassian3
NEW QUESTION # 28
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. 2, 3, 4
- B. 2, 4, 5
- C. 1, 3, 4
- D. 1, 2, 5
Answer: C
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 # 29
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 # 30
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 # 31
During a retrospective, which of the following items would be the LEAST effective to generate discussions on process improvement?
- A. The automation tests failed frequently without any logs to help in debugging the failure reason.
- B. For the last sprint the estimated and actual effort were much higher than the team capacity.
- C. The build process was slow and this often caused delays waiting for the build to complete.
- D. One of the testers was regarded as being both disruptive and lazy and did not contribute to team success.
Answer: D
NEW QUESTION # 32
Which ONE of the following is an example of a typical "Business-oriented work product"?
- A. A user manual.
- B. Acceptance testing entry criteria.
- C. Usability testing test results.
- D. The released product.
Answer: B
NEW QUESTION # 33
Which of the following allows a developer to define accurate unit tests focused on business needs?
- A. Test-Driven Development
- B. Acceptance Test-Driven Development
- C. Behavior-Driven Development
- D. Design-Driven Development
Answer: B
NEW QUESTION # 34
During a retrospective, which of the following items would be the LEAST effective to generate discussions on process improvement?
- A. The automation tests failed frequently without any logs to help in debugging the failure reason.
- B. For the last sprint the estimated and actual effort were much higher than the team capacity.
- C. The build process was slow and this often caused delays waiting for the build to complete.
- D. One of the testers was regarded as being both disruptive and lazy and did not contribute to team success.
Answer: D
Explanation:
Explanation
According to the ISTQB Tester Foundation Level Agile Tester syllabus, a retrospective is a meeting held at the end of each iteration or release, where the agile team reflects on what went well and what can be improved in their processes, practices, and interactions. The purpose of a retrospective is to identify and implement actions for continuous improvement, and to foster a culture of learning and collaboration. Therefore, the items that would be the most effective to generate discussions on process improvement are those that are related to the team's performance, challenges, feedback, and suggestions. Option D is the least effective item to generate discussions on process improvement, as it is a personal attack on one of the team members, and it does not offer any constructive feedback or solution. This kind of item can create a negative and hostile atmosphere in the retrospective, and damage the trust and respect among the team members. Option A is an effective item to generate discussions on processimprovement, as it identifies a problem with the build process that affects the team's efficiency and quality, and it can lead to finding ways to optimize the build process or to mitigate the delays. Option B is also an effective item to generate discussions on process improvement, as it reveals a discrepancy between the team's estimation and actual effort, and it can lead to analyzing the root causes of the deviation and to improving the estimation techniques or the team's capacity. Option C is also an effective item to generate discussions on process improvement, as it highlights a weakness in the automation tests that hinders the team's ability to debug and fix the failures, and it can lead to enhancing the automation tests with better logging mechanisms or to reviewing the automation strategy. References: ISTQB Tester Foundation Level Agile Tester syllabus, section 2.1.1, page 14; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.1.2, page 15; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.2.1, page 16; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.2.2, page 17.
NEW QUESTION # 35
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. 1, 4
- B. 2, 3
- C. 4, 5
- D. 1, 5
Answer: B
NEW QUESTION # 36
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
NEW QUESTION # 37
......
The CTFL-AT certification exam covers a range of topics related to agile testing, including the fundamental principles of agile software development, the agile testing process, and the roles and responsibilities of team members in an agile project. It also covers topics such as test-driven development, continuous integration, and test automation. CTFL-AT exam consists of 40 multiple-choice questions and has a duration of 60 minutes. A passing score of 65% is required to earn the certification.
Prepare For Realistic CTFL-AT Dumps PDF - 100% Passing Guarantee: https://www.dumpsmaterials.com/CTFL-AT-real-torrent.html
Check the Available CTFL-AT Exam Dumps with 40 QA's: https://drive.google.com/open?id=1_8UL91Q2pBFMTPawdFWwCTDr7CNXidKw
