2024年最新の実際のCTFL-AT問題集最新ISQI練習テスト問題集ゲット
CTFL-AT問題集PDFでCTFL-ATリアル試験問題解答
CTFL-AT認定試験は、アジャイルソフトウェア開発、アジャイルテストのプラクティス、アジャイルテストの戦略、アジャイルテストの技術など、さまざまなトピックをカバーしています。試験は、アジャイルテストの方法論をソフトウェア開発プロジェクトに適用できる個人の能力を評価するように設計されています。試験はまた、アジャイルソフトウェア開発の原則、アジャイルの価値観、原則、およびプラクティスについてもカバーしています。
質問 # 19
Which of the following is NOT a statement of value from the Agile Manifesto?
- A. Responding to change over following a plan.
- B. Customer collaboration over contract negotiation.
- C. Processes and tools over individuals and interactions.
- D. Working software over comprehensive documentation
正解：C
解説：
Explanation
The Agile Manifesto is a declaration of four values and twelve principles that guide the Agile software development approach12. The four values of the Agile Manifesto are12:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
These values emphasize the importance of human collaboration, working product, customer feedback, and adaptability over rigid processes, extensive documentation, fixedcontracts, and predefined plans. The values do not imply that the items on the right are not important, but rather that the items on the left are more important and should be prioritized.
Therefore, the statement that is NOT a value from the Agile Manifesto is B, as it contradicts the first value of the Agile Manifesto. The correct statement should be "Individuals and interactions over processes and tools". References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 10; ISTQB Agile Tester Sample Exam2, question 1.
質問 # 20
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.
質問 # 21
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
質問 # 22
What is the definition of agile software development?
- A. 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. A way of developing software where the test cases are developed, and often automated, before the software under test is developed.
- 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 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
質問 # 23
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. 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.
- 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. 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.
- 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.
正解：C
解説：
Explanation
Cross-functional teamwork 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. Cross-functional teamwork means that all team members, regardless of their functional roles, 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. All team members contribute to testing in various ways, such as:
Involving people with the test strategy, test planning and execution as well as test reporting. This can help ensure that the testing activities are aligned with the business objectives, the user needs, and the technical requirements. It can also help improve the test coverage, the test quality, and the test efficiency.
Sharing the responsibility for testing among the team members. This can help reduce the workload and the dependency on a single tester or a testing team. It can also help increase the feedback and the communication among the team members, and foster a culture of quality and learning.
Leveraging the diverse skills and perspectives of the team members. This can help enhance the test design and the test execution by applying different techniques, tools, and approaches. It can also help identify and address the risks, the issues, and the opportunities for improvement from various angles. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 1.2.1, page 9; ISTQB Glossary of Testing Terms2, version 4.0, page 16.
質問 # 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. User story testing - test that the user can enter an income amount and get a result.
- B. Statement testing - test all statements in income calculation.
- C. Equivalence partitioning - test with low, medium and high income.
- D. State transition testing - test all states of income entry.
正解：C
解説：
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 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
質問 # 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 of the following sentences related to Risk-based testing is CORRECT?
- A. Risk-based testing does not fit well in Agile development processes, as short iterations mandate short test times.
- B. Risk-based testing does not fit in Agile development processes, as each iteration focuses on limited parts of the product.
- C. Risk-based testing fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories.
- D. Risk-based testing fits well in Agile development processes, as risks are analyzed twice - during release and iteration planning.
正解：C
質問 # 28
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
質問 # 29
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, 3, 4
- C. 1, 3, 4
- D. 2, 4, 5
正解：D
質問 # 30
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 the various skill sets within the team to be leveraged to the benefit of the project.
- D. Enables reduction in test duplication as the testers and test engineers function as a single team.
正解：C
質問 # 31
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.
質問 # 32
Which of the following sentences related to Risk-based testing is CORRECT?
- A. Risk-based testing does not fit well in Agile development processes, as short iterations mandate short test times.
- B. Risk-based testing does not fit in Agile development processes, as each iteration focuses on limited parts of the product.
- C. Risk-based testing fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories.
- D. Risk-based testing fits well in Agile development processes, as risks are analyzed twice - during release and iteration planning.
正解：C
解説：
Explanation
Risk-based testing fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories. User stories are short descriptions of features or functionalities that are valuable to the customers or users. They help to define the scope and priority of the work in each iteration. By breaking down the work into user stories, the Agile team can identify the potential risks associated with each story, such as technical complexity, business criticality, or user feedback. The team can then prioritize the testing effort based on the risk level of each story, ensuring that the most important and risky features are tested first and thoroughly. Risk-based testing also helps to optimize the testing time and resources, as the team can focus on testing the most relevant aspects of the software, rather than testing everything equally. References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.3.2, page 181; ISTQB Foundation Level Agile Tester Sample Exam Questions, Question 2.3.2-1, page 92
質問 # 33
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, 3 and 5
- B. Activities 2 and 4
- C. Activities 1, 4 and 6
- D. Activities 1, 3 and 6
正解：D
解説：
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
質問 # 34
......
CTFL-AT認定試験は、ソフトウェアテスト業界で世界的に認められ、高い評価を受けています。これは、候補者のアジャイルテストに関する知識とスキルを証明し、彼らのキャリアの展望を大いに向上させるものです。この認定試験は、ソフトウェアテスト分野でCTAL-TA（Certified Tester Advanced Level - Test Analyst）やCTAL-TM（Certified Tester Advanced Level - Test Manager）などの上級認定資格を追求する個人にとっても必須のものです。
CTFL-ATプレミアム試験エンジンPDFをダウンロード：https://jp.fast2test.com/CTFL-AT-premium-file.html
CTFL-AT試験 [2024] 問題集でISQIのPDF問題：https://drive.google.com/open?id=1o2S5L7WEAxbKc9VzcvzMUOezmBzdWpBo