無料でゲット！最新の2024年最新の有効な練習Agile Tester CTFL-AT問題と解答でテストエンジン
CTFL-AT問題集PDFで100%合格保証付き
CTFL-AT認定試験は、アジャイルテストの基礎、アジャイルテスト方法、アジャイルチームでのテスト、アジャイルテストで使用されるツールと技術などのトピックをカバーしています。受験者は、アジャイル開発プロセスとそのテストへの適用についての良好な理解を持っていることが期待されています。また、彼らはテストケースを開発し、実行し、欠陥を特定し、開発チームと効果的に協力する能力を示す必要があります。
質問 # 15
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 card should contain requirements not the user story.
- B. The conversation is not required and the team should start developing.
- C. Conversation should include the acceptance criteria discussion.
- D. Product owner has written a user story and confirmation is not needed.
正解：C
質問 # 16
Which of the following statements about Agile retrospectives is CORRECT?
- A. 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.
- B. During Agile retrospectives, testers should be encouraged to provide constructive suggestions only on non-testing activities.
- C. Unlike working sessions or meetings held in non-Agile projects, Agile retrospectives do not require follow-up activities.
- D. Agile retrospectives should be focused mainly on impediments that are outside the control of the team because these issues are more challenging.
正解：A
解説：
Explanation
An Agile retrospective is a regular meeting where the team reflects on their work process and identifies the areas for improvement12. The following statements about Agile retrospectives are correct12:
During Agile retrospectives, testers should be encouraged to provide constructive suggestions on both testing and non-testing activities, as testing is an integral part of the Agile team and testers can contribute to the overall quality of the product and the process.
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. This helps to reinforce the positive aspects of the team's work and to appreciate the team members' efforts and achievements.
Agile retrospectives should be focused mainly on impediments that are within the control of the team because these issues are more actionable and can be resolved by the team. Impediments that are outside the control of the team should also be discussed, but they may require the involvement of other stakeholders or external parties to be addressed.
The following statement about Agile retrospectives is incorrect12:
Unlike working sessions or meetings held in non-Agile projects, Agile retrospectives do require follow-up activities. The team should agree on the action items that result from the retrospective and assign them to the responsible team members. The team should also monitor the progress and effectiveness of the action items in the next iteration and review them in the next retrospective.
Therefore, the correct answer is B, as it is the only statement that is correct about Agile retrospectives. References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 24; ISTQB Agile Tester Sample Exam2,
質問 # 17
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 card should contain requirements not the user story.
- B. The conversation is not required and the team should start developing.
- C. Conversation should include the acceptance criteria discussion.
- D. Product owner has written a user story and confirmation is not needed.
正解：C
解説：
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.
質問 # 18
Why is regression of software a high risk in agile projects?
- A. Regression is built into software as a safeguard against unexpected failures.
- B. Test automation can cause regression of software in the test environment.
- C. Test-driven development means that existing functionality is not considered.
- D. There is code churn due to change in business needs over several sprints.
正解：D
質問 # 19
Which of the following is a benefit of a whole-team approach?
- A. Enables testers to execute their responsibility for quality for the combined team.
- B. Enables the team to focus on solely their separate areas of expertise and responsibility.
- 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.
正解：D
質問 # 20
Which of the following statements about the Planning poker test estimate technique are CORRECT?
1) Planning poker is a consensus based technique using a deck of cards.
2) A low test estimate usually means the story should be broken down into multiple smaller stories.
3) A high test estimate usually means the story should be broken down into multiple smaller stories.
4) One poker round is played and then consensus has to be reached.
5) The risk level of each backlog item should be decided before the poker session.
- A. 1, 2, 4
- B. 1, 3, 5
- C. 1, 2, 3
- D. 2, 3, 4
正解：B
質問 # 21
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 the appropriate testing tasks are scheduled during iteration planning.
- D. Ensuring all project status meetings are held according to the plan.
正解：D
解説：
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
質問 # 22
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.
正解：C
解説：
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
質問 # 23
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. One of the testers was regarded as being both disruptive and lazy and did not contribute to team success.
- C. For the last sprint the estimated and actual effort were much higher than the team capacity.
- D. The build process was slow and this often caused delays waiting for the build to complete.
正解：B
質問 # 24
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. User story testing - test that the user can enter an income amount and get a result.
- C. State transition testing - test all states of income entry.
- D. Statement testing - test all statements in income calculation.
正解：A
解説：
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.
質問 # 25
Which of the following would provide the MOST independence for testers working with agile teams?
- A. Testers from an independent test team who do not get involved with the Agile team, but are assigned to do System Testing once all sprints are completed.
- B. Testers are fully embedded in each Agile team to perform many of the testing tasks.
- C. Testers from an independent test team are assigned on-demand for the final days of each sprint.
- D. Testers from an independent test team are assigned to the Agile team at the beginning of the project, returning for re-assignment to a new agile team.
正解：A
質問 # 26
Which of the following is a benefit of a whole-team approach?
- A. Enables testers to execute their responsibility for quality for the combined team.
- B. Enables the team to focus on solely their separate areas of expertise and responsibility.
- 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.
正解：D
解説：
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.
質問 # 27
Which of the following sentences about the integration of development and testing activities in Agile projects is INCORRECT?
- A. Developers write acceptance criteria and test cases, together with testers.
- B. While developers develop automated unit test scripts, testers write automated system level tests.
- C. Testers replace developers in writing unit test automation scripts.
- D. Developers and testers may work as a pair to develop and test a feature.
正解：C
解説：
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.
質問 # 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, 4, 5
- B. 1, 3, 4
- C. 1, 2, 5
- D. 2, 3, 4
正解：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?.
質問 # 29
Which of the following statements about Agile retrospectives is CORRECT?
- A. 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.
- B. During Agile retrospectives, testers should be encouraged to provide constructive suggestions only on non-testing activities.
- C. Unlike working sessions or meetings held in non-Agile projects, Agile retrospectives do not require follow-up activities.
- D. Agile retrospectives should be focused mainly on impediments that are outside the control of the team because these issues are more challenging.
正解：A
質問 # 30
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. 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 - B. State transition testing. Test the transitions between the following states:
logging in, inserting the power of the vehicle, making payment, logging out. - C. Decision table testing. Test the following conditions:
Conditions=registered user logged in; inserted power of the vehicle=20kW; Action=Car tax paid - 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]
正解：D
質問 # 31
You are working in a software development company which, for many years, used a sequential development model and was organized into separate departments for each functional group (e.g. business analysts, developers, testers) located within their own office space. Your organization has recently changed to a SCRUM agile framework.Which of the following is an important organizational and behavioral best practice for a tester in the SCRUM team that should have also been practiced when using the sequential model?
- A. Cross-functional teamwork means that all team members contribute to testing in various ways. For example, involving people with the test strategy, test planning and execution as well as test reporting.
- B. Co-located teamwork means that all team members, including developers and testers, must sit together in the same office, so they can quickly communicate face-to-face.
- C. Resilient testing means that the testing process is capable of dealing with rapid changes throughout the development process with test plans being updated during each iteration.
- D. Credibility means that the tester must share information with the stakeholders about the test process so that they find the selected test strategy and testing activities trustworthy.
正解：A
質問 # 32
Which statement about an Agile task board is CORRECT?
- A. It is a detailed visual representation of the status of testing.
- B. Only "in progress" tasks are shown on the task board.
- C. It provides detailed visual representation of the whole team's status.
- D. It is updated once at the end of each iteration.
正解：C
質問 # 33
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. Early and frequent feedback enables the team to deliver the features that represent the highest business value to the customer first.
- D. In Agile projects where feedback is provided early and frequently, defects and incorrect requirements are caught earlier and those problems can be fixed faster.
正解：A
解説：
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.
質問 # 34
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. Early and frequent feedback enables the team to deliver the features that represent the highest business value to the customer first.
- D. In Agile projects where feedback is provided early and frequently, defects and incorrect requirements are caught earlier and those problems can be fixed faster.
正解：A
質問 # 35
......
CTFL-ATブレーン問題集リアル試験最新問題2024年04月19日には40問題：https://jp.fast2test.com/CTFL-AT-premium-file.html
最新CTFL-AT問題集リアル無料テストPDF本日更新です：https://drive.google.com/open?id=1mA8NkCT279cjMAYCCTmurpmrz4a2gnvx