Agile Tester CTFL-AT完全版問題集には無料PDF問題で合格させる
100%更新されたのはISQI CTFL-AT限定版PDF問題集
ISQI CTFL -AT（ISTQB認定テスター - 基礎レベル拡張 - アジャイルテスター）認定試験は、アジャイル開発環境でのテストに焦点を当てた世界的に認められた認定です。この認定は、アジャイルテスト技術、ツール、および方法論における知識とスキルを実証したい専門家向けに設計されています。 CTFL-AT認定試験は、個人がキャリアの見通しを強化し、アジャイルテストの専門知識を実証するのに最適な方法です。
CTFL-AT認定試験は、テスター、テストアナリスト、テストマネージャー、開発者など、アジャイル環境で活動のテストに関与している人に適しています。この認証は、アジャイルテストを初めて使用し、アジャイルテストの原則と実践をより深く理解したい人にとっても有益です。この認定は、ソフトウェアテストの分野でキャリアを進めたい人にとっても有益です。
質問 # 23
Which of the following is a benefit of a whole-team approach?
- A. Enables reduction in test duplication as the testers and test engineers function as a single team.
- B. Enables the various skill sets within the team to be leveraged to the benefit of the project.
- C. Enables the team to focus on solely their separate areas of expertise and responsibility.
- D. Enables testers to execute their responsibility for quality for the combined team.
正解：B
解説：
Explanation
A whole-team approach is a way of working in agile projects where all team members share the responsibility for delivering high-quality software that meets the customer's needs. This means that testers, developers, business analysts, and other roles collaborate closely throughout the project lifecycle, and use their different skills and perspectives to contribute to the quality of the product. A benefit of this approach is that it enables the team to leverage the various skill sets within the team to the benefit of the project, such as testing skills, coding skills, domain knowledge, user experience, etc. This can lead to faster feedback, better communication, higher productivity, and more innovation. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 1.1.1, page 7; ASTQB Agile Tester Certification Resources, Section 1.1.1, page 7.
質問 # 24
During a retrospective, which of the following items would be the LEAST effective to generate discussions on process improvement?
- A. The build process was slow and this often caused delays waiting for the build to complete.
- B. The automation tests failed frequently without any logs to help in debugging the failure reason.
- C. One of the testers was regarded as being both disruptive and lazy and did not contribute to team success.
- D. For the last sprint the estimated and actual effort were much higher than the team capacity.
正解：C
解説：
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.
質問 # 25
Which of the following is NOT a typical task performed by the tester within an Agile team?
- A. Ensuring all project status meetings are held according to the plan.
- B. Suggesting improvements in team retrospectives.
- C. Working with business stakeholders to clarify requirements.
- D. Ensuring the appropriate testing tasks are scheduled during iteration planning.
正解：A
質問 # 26
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. Equivalence partitioning - test with low, medium and high income.
- B. State transition testing - test all states of income entry.
- C. Statement testing - test all statements in income calculation.
- D. User story testing - test that the user can enter an income amount and get a result.
正解：A
質問 # 27
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. Create a bug report for each of your blocked tests.
- C. Work together with the developer, suggesting reasons why the tests are failing.
- D. Review the design of the problematic user story and improve it where possible.
正解：C
解説：
Explanation
As an agile tester, you should work together with the developer, suggesting reasons why the tests are failing.
This is an example of the agile principle of collaboration and communication within the team, as well as the agile testing practice of early and frequent feedback. By working together with the developer, you can help to identify and resolve the root causes of the test failures, as well as share your testing knowledge and perspective. This can lead to faster and better quality delivery of the user story, as well as improved team relationships and trust.
Option A is not a good action, because reviewing and improving the design of the user story is not the tester's responsibility, and it may not address the test failures. Option B is also not a good action, because creating bug reports for blocked tests is not an agile way of handling issues, and it may create unnecessary overhead and waste. Option D is not a good action, because it does not help to unblock the current user story, and it may distract you from the sprint goal and the team's focus.
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-2, page 82
質問 # 28
A calculator application is being developed. The third sprint has been planned to add functionality to the calculator to allow scientific calculations.
Which TWO examples below represent activities that would likely be managed on an agile task board for the third sprint?
1) A task to design the features planned for the next sprint.
2) A task to run an acceptance test for a user story.
3) A task to automate regression tests.
4) A task to participate in training in preparation for the fourth sprint.
5) A task to produce a daily progress report for the agile team members.
- A. 4, 5
- B. 1, 4
- C. 2, 3
- D. 1, 5
正解：C
質問 # 29
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. Co-locate only some of the testers with the Agile development team, while the rest of the testers are in a different location.
- C. Assign testers to be members of the Agile team, but ensure the testers report to a different manager than the developers.
- D. Locate the team that develops the test automation framework in a different location to the Agile development team.
正解：C
質問 # 30
Which of the following statements about the benefits of the Agile processes promoting early and frequent feedback is NOT true?
- A. In Agile projects where feedback is provided early and frequently, defects and incorrect requirements are caught earlier and those problems can be fixed faster.
- B. Increasing the frequency of feedback and communication between all the stakeholders involved in Agile projects eliminates all communication problems.
- C. Early and frequent feedback enables the team to deliver the features that represent the highest business value to the customer first.
- D. Feedback from well-conducted Agile retrospectives can be used to positively affect the development process over the course of the next iteration.
正解：B
質問 # 31
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. 1, 3, 4
- C. 2, 4, 5
- D. 1, 2, 5
正解：B
解説：
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?.
質問 # 32
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. An untrained customer will attempt to use the coffee machine. Probability: High. Impact: High
- B. The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High
- C. A small child may try to steam milk. Probability: High. Impact: Low
- D. Operators will not read the instructions and will try various switches and buttons until something works.
Probability: Low. Impact: Low
正解：B
質問 # 33
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. An untrained customer will attempt to use the coffee machine. Probability: High. Impact: High
- B. The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High
- C. A small child may try to steam milk. Probability: High. Impact: Low
- D. Operators will not read the instructions and will try various switches and buttons until something works.
Probability: Low. Impact: Low
正解：B
解説：
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.
質問 # 34
Why is regression of software a high risk in agile projects?
- A. Regression is built into software as a safeguard against unexpected failures.
- B. There is code churn due to change in business needs over several sprints.
- C. Test automation can cause regression of software in the test environment.
- D. Test-driven development means that existing functionality is not considered.
正解：B
質問 # 35
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 way of developing software where the test cases are developed, and often automated, before the software under test is developed.
- D. 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
解説：
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
質問 # 36
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. Developers write acceptance criteria and test cases, together with testers.
- C. While developers develop automated unit test scripts, testers write automated system level tests.
- D. Developers and testers may work as a pair to develop and test a feature.
正解：A
解説：
Explanation
Testers replace developers in writing unit test automation scripts. Comprehensive Explanation: The integration of development and testing activities in Agile projects is based on the principle of cross-functional teamwork, where all team members collaborate and share their skills and knowledge to achieve a common goal. In the context of testing, this means that testing is not seen as a separate activity or phase, but as an integral part of the development process. Therefore, the following sentences are correct:
While developers develop automated unit test scripts, testers write automated system level tests. This is an example of how developers and testers can work in parallel and complement each other's testing efforts. Developers can focus on testing the internal quality of the code, while testers can focus on testing the external quality of the product.
Developers write acceptance criteria and test cases, together with testers. This is an example of how developers and testers can work together to define and verify the user requirements and expectations.
Developers can provide their technical expertise and input, while testers can provide their business and user perspective and feedback.
Developers and testers may work as a pair to develop and test a feature. This is an example of how developers and testers can work closely and interactively to deliver a feature. Developers and testers can exchange ideas, suggestions, and information, and support each other in the coding and testing tasks.
The following sentence is incorrect:
Testers replace developers in writing unit test automation scripts. This is not a valid example of the integration of development and testing activities in Agile projects, because it implies that testers take over the responsibility of developers, rather than collaborate with them. Testers should not replace developers in writing unit test automation scripts, because developers have more knowledge and experience in coding and debugging, and because unit testing is an essential part of the development process. Testers should instead work with developers to ensure that the unit test automation scripts are adequate, effective, and maintainable. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 1.2.1, page 9; ISTQB Glossary of Testing Terms2, version 4.0, pages 16 and 55.
質問 # 37
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. Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.
- C. Reducing the involvement of business representatives because of the increased communication and collaboration between testers and developers.
- D. Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.
正解：D
質問 # 38
Which of the following statements is FALSE regarding early and frequent feedback?
- A. Early feedback provides the Agile team with information on its productivity.
- B. Early feedback promotes early discovery and resolution of quality problems.
- 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.
正解：A
質問 # 39
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, 3, 5
- C. 1, 2, 4
- D. 1, 2, 3
正解：B
解説：
Explanation
Planning poker is a consensus-based technique for agile estimation, using a deck of cards with predefined numerical values, usually based on the Fibonacci sequence or a modified version12. Therefore, statement 1 is correct. A high test estimate usually means that the user story or task is too complex, ambiguous, or risky, and should be broken down into multiple smaller stories that are easier to understand and estimate13. Therefore, statement 3 is correct. The risk level of each backlog item should be decided before the poker session, as it can affect the estimation process and the prioritization of the work14. Therefore, statement 5 is correct. Statement
2 is incorrect, as a low test estimate usually means that the user story or task is simple, clear, and well-defined, and does not need to be broken down further13. Statement 4 is incorrect, as planning poker can involve multiple rounds of estimation, reveal, and discussion, until the team reaches a consensus or agrees to defer the item12. 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; 3: Planning Poker: An Agile Estimating and Planning Technique3; 4: Planning poker: The all-in strategy for Agile estimation - Asana4
質問 # 40
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, 5
- B. 2, 3
- C. 1, 3
- D. 3, 4
正解：A
質問 # 41
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. 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. - B. 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.
- 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.
正解：A
質問 # 42
Which statement about an Agile task board is CORRECT?
- A. It provides detailed visual representation of the whole team's status.
- B. It is updated once at the end of each iteration.
- C. Only "in progress" tasks are shown on the task board.
- D. It is a detailed visual representation of the status of testing.
正解：A
解説：
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
質問 # 43
......
有効な試験問題を試そうCTFL-ATは無料サイトで限定お試しチャンス：https://jp.fast2test.com/CTFL-AT-premium-file.html
無料Agile Tester CTFL-AT公式認定ガイドPDFダウンロード：https://drive.google.com/open?id=1o2S5L7WEAxbKc9VzcvzMUOezmBzdWpBo