ISQI CTFL-AT試験問題集で[2024年最新] 有効な試験練習問題集解答
CTFL-AT問題集で掴み取れ！[最新2024]ISQI試験合格させます
ISQI CTFL-AT認定試験の準備には、アジャイルな原則と実践を確実に理解する必要があります。これは、自習、オンラインコース、または教室でのトレーニングを通じて達成できます。多くのトレーニングプロバイダーは、試験のコンテンツを詳細にカバーするCTFL-ATの準備コースを提供し、候補者が準備できるように練習の質問と模擬試験を提供しています。
ISQI CTFL -AT（ISTQB認定テスター - 基礎レベル拡張 - アジャイルテスター）認定試験は、アジャイル開発環境でのテストに焦点を当てた世界的に認められた認定です。この認定は、アジャイルテスト技術、ツール、および方法論における知識とスキルを実証したい専門家向けに設計されています。 CTFL-AT認定試験は、個人がキャリアの見通しを強化し、アジャイルテストの専門知識を実証するのに最適な方法です。
質問 # 19
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. Action "Reopen" must be available only for a user with a specific authorization level.
- D. The "ID" field must accept input value of a length between 2 and 10 characters.
正解：C
質問 # 20
Iteration planning for Sprint 5 of your current project is complete. The plan for the sprint is to increase performance of the system, which of the following acceptance criteria would you expect for Sprint 5?
1) User access for all roles has been validated.
2) A static analysis tool has been executed for all code.
3) 100% of the existing regression test suite has passed.
4) System is responding in less than 3 seconds, 90% of the time.
5) A new version of internet Explorer has been included.
- A. 1, 3
- B. 4, 5
- C. 3, 4
- D. 2, 5
正解：C
解説：
Explanation
The acceptance criteria for a sprint are the conditions that must be met for the user stories to be considered done and deliver value to the customer1. The acceptance criteria should be specific, measurable, achievable, relevant, and testable2. In this case, the plan for the sprint is to increase performance of the system, so the acceptance criteria should reflect that goal. Therefore, the acceptance criteria that would be expected for Sprint
5 are:
100% of the existing regression test suite has passed. This criterion ensures that the system has not introduced any new defects or broken any existing functionality while improving performance3.
System is responding in less than 3 seconds, 90% of the time. This criterion defines a clear and quantifiable performance target that can be verified by testing4.
The other options are not relevant or appropriate acceptance criteria for Sprint 5:
User access for all roles has been validated. This criterion is not related to the performance of the system, but rather to the security or functionality of the system. It might be an acceptance criterion for a different sprint or user story, but not for Sprint 55.
A static analysis tool has been executed for all code. This criterion is not a customer
質問 # 21
Your agile team is using the Testing Quadrants to ensure that all important test levels and test types are covered in the test plan.
In relation to Quadrant 3 - business facing and product critique, what should be considered for the plan?
- A. Prototype Testing
- B. Exploratory Testing
- C. Performance Testing
- D. Functional Testing
正解：B
解説：
Explanation
Exploratory testing is a type of testing that involves simultaneous learning, test design, and test execution. It is suitable for Quadrant 3 because it is business facing and product critique, meaning that it focuses on the user's perspective and the quality attributes of the product. Exploratory testing can help discover new risks, requirements, and defects that may not be covered by other test levels and test types. It can also provide feedback on the usability, functionality, and reliability of the product. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 2.3.2, page 17; ISTQB Glossary of Testing Terms2, version 4.0, page 23.
質問 # 22
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. 1, 5
- C. 4, 5
- D. 2, 3
正解：D
解説：
Explanation
According to the ISTQB Tester Foundation Level Agile Tester syllabus, an agile task board is a visual tool that displays the status of the work items in an agile sprint. The task board typically shows the user stories, tasks, and their progress from "to do" to "done". The task board helps the agile team to monitor and coordinate their work, and to communicate with stakeholders. Therefore, the examples that represent activities that would likely be managed on an agile task board for the third sprint are those that are related to the user stories, tasks, and their progress in the current sprint. Option A is the correct answer, as it contains two examples of such activities: running an acceptance test for a user story, and automating regression tests. These are both tasks that are part of the testing process in the current sprint, and their status can betracked on the task board. Option B is not a correct answer, as it contains two examples of activities that are not related to the current sprint:
designing the features planned for the next sprint, and participating in training in preparation for the fourth sprint. These are both activities that are part of the planning or learning process for the future sprints, and they are not managed on the task board. Option C is also not a correct answer, as it contains two examples of activities that are not related to the current sprint: participating in training in preparation for the fourth sprint, and producing a daily progress report for the agile team members. These are both activities that are part of the learning or reporting process, and they are not managed on the task board. Option D is also not a correct answer, as it contains two examples of activities that are not related to the current sprint: designing the features planned for the next sprint, and producing a daily progress report for the agile team members. These are both activities that are part of the planning or reporting process, and they are not managed on the task board. 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.
質問 # 23
Which of the following is the BEST way for a test team to keep its independence when working in an Agile development environment?
- A. Locate the team that develops the test automation framework in a different location to the Agile development team.
- B. Assign testers to be members of the Agile team, but ensure the testers report to a different manager than the developers.
- 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.
正解：B
質問 # 24
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. Create a bug report for each of your blocked tests.
- B. Review the design of the problematic user story and improve it where possible.
- C. Use the time to improve and automate existing test cases of other user stories.
- D. Work together with the developer, suggesting reasons why the tests are failing.
正解：D
質問 # 25
What is the main benefit of the Test Pyramid?
- A. It means testing is involved early in the development cycle.
- B. It shows complexity of testing activities.
- C. It helps in evaluating the amount of test cases needed.
- D. It acts as a metric for testing progress.
正解：D
質問 # 26
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 from an independent test team are assigned on-demand for the final days of each sprint.
- C. 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.
- D. Testers are fully embedded in each Agile team to perform many of the testing tasks.
正解：A
解説：
Explanation
Independence in testing is the degree of separation between the person who tests something and the person who developed it. Independence can help to reduce bias, increase objectivity, and provide different viewpoints. However, independence also has some drawbacks, such as increased communication overhead, reduced collaboration, and delayed feedback. In agile projects, testers are usually embedded in the agile teams to perform many of the testing tasks, such as unit testing, integration testing, acceptance testing, etc. This provides a high level of collaboration and fast feedback, but also reduces the independence of the testers.
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, would provide the most independence for testers working with agile teams. However, this would also introduce many disadvantages, such as lack of alignment with the agile principles, loss of context and domain knowledge, delayed defect detection and resolution, and increased risk of missing customer expectations. References: ISTQB Foundation Level Agile Tester Syllabus, Section
1.1.2, page 8; ASTQB Agile Tester Certification Resources, Section 1.1.2, page 8.
質問 # 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. Continuous Integration
- B. Kanban
- C. Extreme Programming
- D. Scrum
正解：D
解説：
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
質問 # 28
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. 1, 3
- B. 2, 5
- C. 1, 3, 4
- D. 2, 4, 5
正解：C
解説：
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.
質問 # 29
Your agile team is using the Testing Quadrants to ensure that all important test levels and test types are covered in the test plan.
In relation to Quadrant 3 - business facing and product critique, what should be considered for the plan?
- A. Prototype Testing
- B. Exploratory Testing
- C. Performance Testing
- D. Functional Testing
正解：B
質問 # 30
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 2, 4, 5 and 6
- B. Acceptance test criteria are 1, 2, 4 and 5
- C. Acceptance test criteria are 1, 3, 4 and 5
- D. Acceptance test criteria are 1, 2, 3 and 6
正解：B
解説：
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.
質問 # 31
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, 3, 5
- B. 1, 2, 4
- C. 2, 3, 4
- D. 1, 2, 3
正解：A
解説：
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
質問 # 32
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. In Agile projects where feedback is provided early and frequently, defects and incorrect requirements are caught earlier and those problems can be fixed faster.
- D. Early and frequent feedback enables the team to deliver the features that represent the highest business value to the customer first.
正解：B
解説：
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.
質問 # 33
What is the main benefit of the Test Pyramid?
- A. It means testing is involved early in the development cycle.
- B. It acts as a metric for testing progress.
- C. It shows complexity of testing activities.
- D. It helps in evaluating the amount of test cases needed.
正解：D
解説：
Explanation
The Test Pyramid is a model for organizing tests in a way to make the process of testing faster, efficient and cost-effective. This model focusses on getting maximum functional testing getting covered by faster and less brittle tests like Unit and API tests1. The main benefit of the Test Pyramid is that it helps in evaluating the amount of test cases needed for each level of testing. The Test Pyramid suggests that the number of test cases should decrease as we move up the pyramid, from unit tests to integration tests to end-to-end tests. This is because unit tests are more granular, isolated, and easy to write and maintain, while end-to-end tests are more complex, dependent, and brittle. The Test Pyramid also helps in balancing the test coverage and the test execution time, as unit tests provide high coverage and low execution time, while end-to-end tests provide low coverage and high execution time. By following the Test Pyramid, teams can optimize their testing efforts and resources, and ensure that they have a sufficient and effective test suite for their software. References:
ISTQB Foundation Level Agile Tester Syllabus, Section 2.2.1, page 16; ASTQB Agile Tester Certification Resources, Section 2.2.1, page 16; What is Test Pyramid : Getting started with Test Automation Pyramid, The Practical Test Pyramid - Martin Fowler, Testing Pyramid: What Is It and How To Use It | Solvd.
質問 # 34
Which of the following allows a developer to define accurate unit tests focused on business needs?
- A. Design-Driven Development
- B. Test-Driven Development
- C. Acceptance Test-Driven Development
- D. Behavior-Driven Development
正解：D
解説：
Explanation
Behavior-Driven Development (BDD) is a software development approach that allows a developer to define accurate unit tests focused on business needs. BDD uses a common language that is understandable by both technical and non-technical stakeholders, such as Given-When-Then scenarios.BDD helps to align the development and testing activities with the customer expectations and business goals . References:
1: ISTQB Foundation Level Agile Tester Syllabus, Version 2014, Section 2.2.2
2: ASTQB Agile Tester Certification Resources, Agile Testing Foundations, Chapter 3, Section 3.2.2
質問 # 35
Which of the following statements would you expect to be the MOST direct advantage of the whole-team approach?
- A. Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.
- B. Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.
- C. Having at least once a day an automated build and test process that detects integration errors early and quickly.
- D. Reducing the involvement of business representatives because of the increased communication and collaboration between testers and developers.
正解：B
質問 # 36
Which of the following is NOT a typical task performed by the tester within an Agile team?
- A. Suggesting improvements in team retrospectives.
- B. Ensuring all project status meetings are held according to the plan.
- C. Working with business stakeholders to clarify requirements.
- D. Ensuring the appropriate testing tasks are scheduled during iteration planning.
正解：B
解説：
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
質問 # 37
Which of the following allows a developer to define accurate unit tests focused on business needs?
- A. Design-Driven Development
- B. Test-Driven Development
- C. Behavior-Driven Development
- D. Acceptance Test-Driven Development
正解：D
質問 # 38
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. Continuous Integration
- B. Kanban
- C. Extreme Programming
- D. Scrum
正解：D
質問 # 39
......
CTFL-AT試験問題集PDF正確率保証と更新された問題：https://www.jpntest.com/shiken/CTFL-AT-mondaishu
合格させるCTFL-AT試験にはリアル試験エンジンPDFには40問題あります：https://drive.google.com/open?id=1C-LnACKPYhEAmnUAxAIir3_pNKnhur9Q