Agile Tester CTFL-AT最新問題集で2024年08月07日
2024年最新の問題をマスター！Agile Tester合格目指そう！CTFL-ATリアル試験問題集！
CTFL-AT認定試験では、アジャイルソフトウェア開発、アジャイルテスト、アジャイルテスト方法、アジャイルテスト技術、アジャイルテストツール、アジャイルプロジェクト管理など、幅広いトピックをカバーしています。この試験では、アジャイルマニフェスト、アジャイルの原則、アジャイル価値、アジャイルプラクティスなどのトピックもカバーしています。認定試験は、アジャイル開発とテストのさまざまな側面で個人の知識とスキルをテストするように設計されています。 CTFL-AT認定は、アジャイルテストと開発のキャリアを促進しようとする専門家にとって貴重な資産です。
ISQI CTFL-AT認定試験は、アジャイルテストのすべての側面をカバーする包括的な試験です。複数選択問題が含まれており、試験時間はタイム制限が設けられています。試験はオンラインで受験することも、テストセンターで受験することもできます。
CTFL-ATの認証試験は、アジャイルソフトウェア開発プロジェクトに関与しているソフトウェアテスター、開発者、プロジェクトマネージャー、その他のプロフェッショナルに適しています。認証試験は、プロフェッショナルがアジャイルテストの専門知識を証明し、スキルと知識を認められる理想的な方法です。CTFL-ATの認証試験は世界中の雇用主に高く評価され、ソフトウェアテスト業界でのキャリアアップを支援することができます。認証試験は複数の言語で利用可能であり、候補者はオンラインまたは認可された試験センターで試験を受けることができます。
質問 # 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, 4 and 5
- B. Acceptance test criteria are 1, 2, 3 and 6
- C. Acceptance test criteria are 2, 4, 5 and 6
- D. Acceptance test criteria are 1, 3, 4 and 5
正解：A
質問 # 21
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. One of the testers was regarded as being both disruptive and lazy and did not contribute to team success.
- D. The build process was slow and this often caused delays waiting for the build to complete.
正解：C
質問 # 22
What is the definition of agile software development?
- A. A way of developing software where the test cases are developed, and often automated, before the software under test is developed.
- B. 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.
- C. 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.
- D. 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
正解：B
解説：
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
Which ONE of the following is an example of a typical "Business-oriented work product"?
- A. Usability testing test results.
- B. A user manual.
- C. The released product.
- D. Acceptance testing entry criteria.
正解：B
解説：
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.
質問 # 24
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. Product owner has written a user story and confirmation is not needed.
- C. Conversation should include the acceptance criteria discussion.
- D. The conversation is not required and the team should start developing.
正解：C
質問 # 25
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, 4, 5
- B. 2, 5
- C. 1, 3
- D. 1, 3, 4
正解：D
解説：
Explanation
A tester on an Agile project typically performs the following tasks12:
Implementing test strategy: A tester helps to define and implement the test strategy for the Agile project, which includes the test approach, test levels, test types, test techniques, test tools, test environment, test data, test metrics, and test documentation.
Measuring and reporting test coverage: A tester measures and reports the test coverage of the product features and quality attributes, such as functionality, usability, performance, security, etc. Test coverage can be expressed in terms of test cases, test scenarios, test sessions, test conditions, test data, code, etc.
Coaching development team in relevant aspects of testing: A tester coaches the development team in relevant aspects of testing, such as test design, test execution, test automation, test-driven development, behavior-driven development, exploratory testing, etc. A tester also helps the development team to improve their testing skills and practices.
The following tasks are not typically performed by a tester on an Agile project:
Documenting business requirements: Business requirements are usually documented by the product owner or the business analyst, not by the tester. The tester may review and provide feedback on the business requirements, but the tester is not responsible for documenting them.
Executing test-driven development tests: Test-driven development tests are usually executed by the developers, not by the tester. The tester may assist the developers in creating and reviewing the test-driven development tests, but the tester is not responsible for executing them.
Therefore, the correct answer is C, as it contains the tasks that are typically performed by a tester on an Agile project. References: ISTQB Foundation Level Agile Tester Extension Syllabus1, pages 14-15, 18-19, 22-23; ISTQB Agile Tester Sample Exam2, question 17.
質問 # 26
Which of the following is NOT a statement of value from the Agile Manifesto?
- A. Responding to change over following a plan.
- B. Working software over comprehensive documentation
- C. Processes and tools over individuals and interactions.
- D. Customer collaboration over contract negotiation.
正解：C
質問 # 27
Which one of the following is a testable acceptance criterion?
- A. The solution shall support business processes.
- B. The system shall be easy to use.
- C. The response time to confirm a customer submission must not exceed 5 seconds.
- D. The tools for testing are tested before use and are meeting the requirements.
正解：C
解説：
Explanation
A testable acceptance criterion is a condition that can be verified or measured objectively by the tester, customer, or stakeholder. It should be specific, measurable, achievable, relevant, and time-bound (SMART). A testable acceptance criterion should also be written from the user's perspective, achievable within the sprint, and written before development begins1.
Among the four options, only option C meets these criteria. It is specific (the response time to confirm a customer submission), measurable (must not exceed 5 seconds), achievable (within the technical and business constraints), relevant (to the user's needs and expectations), and time-bound (must be met in every sprint). It is also written from the user's perspective, testable (by measuring the response time), and written before development (as part of the user story definition).
Option A is not testable because it is vague and subjective. What does it mean to support business processes?
How can this be verified or measured? Option B is also not testable because it is subjective and ambiguous.
What does it mean to be easy to use? How can this be verified or measured? Option D is not testable because it is not written from the user's perspective. It is an internal quality criterion for the testing team, not an acceptance criterion for the product or feature.
References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.3.2, page 182; ISTQB Foundation Level Agile Tester Sample Exam Questions, Question 2.3.2-2, page 93
質問 # 28
Which one of the following is a testable acceptance criterion?
- A. The solution shall support business processes.
- B. The system shall be easy to use.
- C. The response time to confirm a customer submission must not exceed 5 seconds.
- D. The tools for testing are tested before use and are meeting the requirements.
正解：C
質問 # 29
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 1, 3 and 6
- C. Activities 1, 4 and 6
- D. Activities 2, 3 and 5
正解：B
解説：
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
質問 # 30
Which of the following statements about Agile retrospectives is CORRECT?
- A. During Agile retrospectives, testers should be encouraged to provide constructive suggestions only on non-testing activities.
- B. 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.
- 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.
正解：B
解説：
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,
質問 # 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. 1, 2, 5
- B. 2, 4, 5
- C. 1, 3, 4
- D. 2, 3, 4
正解：B
質問 # 32
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. Scrum
- D. Kanban
正解：C
質問 # 33
Which of the following describes the main purpose of a task management tool in agile projects?
- A. A task management tool is used to store source code and automated tests.
- B. A task management tool allows developers to continuously integrate their code.
- C. A task management tool is used to manage and track user stories, tests and other tasks.
- D. A task management tool is used by team members to share ideas and collaborate on assigned tasks.
正解：C
質問 # 34
Which of the following statements about the benefits of the Agile processes promoting early and frequent feedback is NOT true?
- A. Feedback from well-conducted Agile retrospectives can be used to positively affect the development process over the course of the next iteration.
- 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. 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
質問 # 35
Which ONE of the following is an example of a typical "Business-oriented work product"?
- A. A user manual.
- B. Usability testing test results.
- C. The released product.
- D. Acceptance testing entry criteria.
正解：D
質問 # 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 and testers may work as a pair to develop and test a feature.
- C. While developers develop automated unit test scripts, testers write automated system level tests.
- D. Developers write acceptance criteria and test cases, together with testers.
正解：A
質問 # 37
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. 3, 4
- B. 2, 3
- C. 2, 5
- D. 1, 3
正解：C
解説：
Explanation
Test automation is essential for agile projects, as it enables fast and frequent feedback on the quality of the product. Without test automation, it would be very difficult to ensure high quality in an agile project, as manual testing would be too slow and costly to keep up with the pace of development12. Automated acceptance tests are one of the key types of test automation on agile projects, as they verify that the user stories are implemented correctly and that the product meets the customer's expectations. Automated acceptance tests are run regularly as part of the continuous integration full system build, and the results provide feedback on the overall product quality12. Therefore, statements 2 and 5 are correct with regards to test automation on agile projects. References: 1: ISTQB Foundation Level Agile Tester Syllabus, Section 3.3.1, Test Automation1; 2:
ASTQB Agile Tester Certification Resources, Section 3.3.1, Test Automation2
質問 # 38
Which of the following would provide the MOST independence for testers working with agile teams?
- A. Testers are fully embedded in each Agile team to perform many of the testing tasks.
- B. 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.
- C. 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.
- D. Testers from an independent test team are assigned on-demand for the final days of each sprint.
正解：C
質問 # 39
You are working in a team preparing a bank loan application. Your task is the preparation of acceptance tests for the following user story:
"IF a customer needs a loan for less than 50,000 Euros and they have made repayments regularly (without any delay) and the customer's monthly income is more than 3000 Euros for the last year, THEN the bank will accept the loan request; in other cases, the bank will not accept the request. A customer assistant is responsible for preparing data for approval but the approval is done by the bank manager." Which of the following test cases can be treated as acceptance test criteria for the above user story?
1) As a customer assistant I can log in to the system and check the history of the customer account for the last year.
2) As a customer assistant I can log in to the system and check the history of the customer debts and repayments.
3) As a customer assistant I can log in to the system and change my password.
4) As a bank manager I can log in to the system and receive the information of all requests waiting for approval.
5) As a bank manager I can log in to the system and decide whether to approve a loan for a customer.
6) As a bank manager I can log in to the system within 10 seconds.
- A. Acceptance test criteria are 1, 2, 4 and 5
- B. Acceptance test criteria are 1, 2, 3 and 6
- C. Acceptance test criteria are 2, 4, 5 and 6
- D. Acceptance test criteria are 1, 3, 4 and 5
正解：A
解説：
Explanation
Acceptance test criteria are the conditions that a user story must satisfy to be accepted by the customer or the stakeholder. They are usually derived from the user story and its acceptance scenarios, and they should cover the functional and non-functional requirements of the user story. Acceptance test criteria should be clear, concise, testable, and agreed upon by the team and the customer or the stakeholder.
In this case, the user story describes the business rule for approving a loan request based on the customer's income, repayment history, and loan amount. The user story also specifies the roles of the customer assistant and the bank manager in the process. Therefore, the acceptance test criteria should verify that the user story is implemented correctly and that the system behaves as expected for different scenarios and inputs.
The following test cases can be treated as acceptance test criteria for the above user story:
As a customer assistant I can log in to the system and check the history of the customer account for the last year. This test case verifies that the customer assistant can access the system and view the customer's income information, which is one of the factors for approving the loan request.
As a customer assistant I can log in to the system and check the history of the customer debts and repayments. This test case verifies that the customer assistant can access the system and view the customer's repayment history, which is another factor for approving the loan request.
As a bank manager I can log in to the system and receive the information of all requests waiting for approval. This test case verifies that the bank manager can access the system and see the list of loan requests that have been prepared by the customer assistant, and that the system provides the necessary information for each request.
As a bank manager I can log in to the system and decide whether to approve a loan for a customer. This test case verifies that the bank manager can access the system and perform the approval action for a loan request, and that the system applies the business rule correctly and updates the status of the request accordingly.
The following test cases cannot be treated as acceptance test criteria for the above user story:
As a customer assistant I can log in to the system and change my password. This test case is not related to the user story, as it does not verify any of the functional or non-functional requirements of the user story. It is a generic test case that applies to any user of the system, not specific to the customer assistant role or the loan approval process.
As a bank manager I can log in to the system within 10 seconds. This test case is not related to the user story, as it does not verify any of the functional or non-functional requirements of the user story. It is a performance test case that applies to any user of the system, not specific to the bank manager role or the loan approval process.
References: ISTQB Foundation Level Agile Tester Syllabus1, Section 2.3.1, pages 15-16; ISTQB Glossary of Testing Terms2, version 4.0, pages 2 and 3.
質問 # 40
......
完全版は2024年最新のCTFL-AT試験問題集テストガイドはトレーニング専門JPNTest：https://www.jpntest.com/shiken/CTFL-AT-mondaishu
合格準備CTFL-ATにはJPNTestが提供するあなたをISTQB Certified Tester - Foundation Level Extension - Agile Tester試験合格させます顕著練習問題：https://drive.google.com/open?id=1ZIzWG-u1LNDyA_eiONAa0oz-Melt-zE8