無料提供中のCTFL-AT試験問題集で（2025年最新のPDF問題集）信頼度の高いテストエンジン [Q30-Q52]

無料提供中のCTFL-AT試験問題集で（2025年最新のPDF問題集）信頼度の高いテストエンジン

CTFL-ATのPDFで最近更新された問題です集試験点数を伸ばそう

質問 # 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. Equivalence partitioning. Test the annual car tax value for the following partitions:
[power of the vehicle<20 kW ; 20 kW #power of the vehicles#150 kW; power of the vehicle>150 kW]
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. 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

正解：A

解説：
Equivalence partitioning is a black-box test design technique that divides the input domain of a system into classes of data from which test cases can be derived. The idea is that if a system works correctly for a representative value from an equivalence class, it will work correctly for all values from that class, and vice versa. Equivalence partitioning reduces the number of test cases by eliminating redundant ones. For the given user story, equivalence partitioning is the most suitable technique because it can test the different outcomes of the annual car tax calculation based on the power of the vehicle, which is the main input for the system. By testing one value from each partition, the tester can verify the functionality of the system and detect any errors in the calculation logic. The other techniques are not as suitable because they do not focus on the input domain of the system, but rather on the conditions, transitions, or scenarios that are not directly related to the user story. References:
* : ISTQB Foundation Level Agile Tester Syllabus, Version 2014, Section 2.2.2
* : ASTQB Agile Tester Certification Resources, Agile Testing Foundations, Chapter 3, Section 3.2.2
* : 3

質問 # 31
Which of the following statements describes Configuration Management?

A. Configuration management aims to identify and document some characteristics of a configuration item, control changes to those characteristics, and record and report change processing and implementation status
B. Configuration management consists of all of the test design techniques in which test cases are designed to execute all possible discrete combinations of any set of a specified number of configuration elements
C. Configuration management represents a method for measuring and managing session-based testing, where a session is an uninterrupted period of testing which could last from 60 to 120 minutes
D. Configuration management is a test management task that deals with developing and applying a set of corrective actions to get a test project on track when monitoring shows a deviation from what was planned

正解：A

解説：
Comprehensive and Detailed Explanation From Exact Extract:
FromISTQB Glossary (also referenced in CTFL-AT):
"Configuration management is a discipline applying technical and administrative direction and surveillance to: identify and document the functional and physical characteristics of a configuration item, control changes to those characteristics, record and report change processing and implementation status, and verify compliance." Thus,Option Dis the formal and accurate definition ofConfiguration Management.
* Option Adescribestest control, not configuration management.
* Option Brefers tosession-based testing, unrelated to configuration management.
* Option Crefers tocombinatorial test design, not configuration control.
References:
ISTQB Glossary (aligned with CTFL-AT)
Learning Objective (K1) - Recall basic concepts of configuration management

質問 # 32
In Agile projects, which of the following approaches would result in the best compromise for preserving independence of testers and for allowing testers to have a good understanding of the product as well as good relationships with other team members?

A. Having independent separate test teams where all of the testers work separately from developers without being assigned to Agile teams
B. Having independent separate test teams where testers are assigned to Agile teams on a long-term basis, at the beginning of an Agile project
C. Having independent separate test teams where testers are assigned to Agile teams on-demand during the final days of each iteration
D. Having only Agile teams where testers are integral parts and where they perform many of the testing tasks, without having an independent test team

正解：B

解説：
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 2.5Testers and Independence, it states:
"Testers may be assigned to Agile teams on a permanent or rotating basis. While full independence is compromised, this setup allows for better collaboration and understanding of the product, while still maintaining some degree of independence." Thus,Option Bis the most accurate -long-term embedded testerssupport Agile collaboration while preservingpartial independence.
* Option Aleads tolate involvement, which contradicts Agile principles.
* Option Csacrifices independence entirely.
* Option Dis traditional and contrary to Agile values of collaboration.
References:
CTFL-AT Syllabus v4.0, Section 2.5
Learning Objective (K2) - Understand approaches to preserving test independence in Agile

質問 # 33
Which of the following statements about the whole-team approach would you expect most likely to be true?

A. The whole-team approach tends to advocate the idea of team members being "generalists" without having deep skills in specific disciplines
B. The whole-team approach helps ensure testers, developers and the business work together to ensure that the desired quality levels are achieved
C. The whole-team approach is consistent with the "power of three" concept for which a user story is the conjunction of three elements (card, conversation, confirmation)
D. The whole-team approach is a consensus-based approach for estimating, mostly used to estimate the relative size of user stories

正解：B

解説：
Comprehensive and Detailed Explanation From Exact Extract:
From theCTFL-AT Syllabus v4.0, Section 1.3The Whole-Team Approach, it states:
"The whole-team approach involves all team members (including developers, testers, and business representatives) working together as a team, sharing responsibility for the quality of the product." It also says:
"In Agile projects, the whole-team approach promotes collaboration and communication across roles to achieve common goals, including quality assurance." Thus,Option Bis correct, as it captures thecollaborative nature and shared responsibilitythat the whole- team approach aims to foster.
* Option Arefers toPlanning Poker or relative estimation, not directly the whole-team concept.
* Option Cdescribes the"Three Cs" (Card, Conversation, Confirmation)model of user stories, not the whole-team approach specifically.
* Option Dmisinterprets Agile; while team members are encouraged to becross-functional, deep expertise is still valued, and "generalist only" is not a requirement of the whole-team approach.
References:
CTFL-AT Syllabus v4.0, Section 1.3
Learning Objective (K2) - Understand benefits of the whole-team approach

質問 # 34
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 the appropriate testing tasks are scheduled during iteration planning.
C. Ensuring all project status meetings are held according to the plan.
D. Working with business stakeholders to clarify requirements.

正解：C

質問 # 35
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. 2, 5
D. 3, 4

正解：D

質問 # 36
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. 2, 3, 4
C. 1, 3, 5
D. 1, 2, 3

正解：C

解説：
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

質問 # 37
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 the appropriate testing tasks are scheduled during iteration planning.
C. Ensuring all project status meetings are held according to the plan.
D. Working with business stakeholders to clarify requirements.

正解：C

解説：
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 clarifyrequirements. 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

質問 # 38
Which of the following statements best describes Agile software development?

A. Agile software development tends to break a project into a number of iterations, where each iteration represents a separate phase of sequential development and thus in which testing is performed during the last iteration
B. Agile software development tends to break a project into a series of increments, each of which delivers a portion of functionality through a series of mini-Waterfalls where all phases of the Waterfall are completed before proceeding to the next increment
C. Agile software development tends to adopt an iterative incremental lifecycle, where requirements and solutions evolve through collaboration between self-organizing and cross-functional teams
D. Agile software development is a software development approach whereby lines of code (production and
/or test) of a component are written by two programmers sitting at a single computer

正解：C

解説：
Comprehensive and Detailed Explanation From Exact Extract:
From theISTQB CTFL-AT Syllabus v4.0, Section 1.1Agile Software Development and the Agile Manifesto, the Agile approach is described as:
"Agile software development uses iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing and cross-functional teams." Option C reflects this exact concept, highlighting both theiterative-incremental lifecycleand the collaborative natureof Agile teams.
* Option A refers specifically topair programming, a practice used inExtreme Programming (XP), but it's not a definition of Agile as a whole.
* Option B mistakenly describes asequential (Waterfall-like)iteration structure where testing is delayed.
* Option D describes ahybrid or phased approach, not consistent with core Agile principles.
References:
CTFL-AT Syllabus v4.0, Section 1.1
Agile Manifesto Principles
Learning Objective (K1) - Identify Agile Software Development Approaches

質問 # 39
Which of the following statements about a test charter are CORRECT?
1) It is used mainly in exploratory tests.
2) It is used to monitor a test process.
3) It may make reference to user stories.
4) It contains notes taken during a test session.
5) It is used to outline the company test policy.

A. 2, 3, 4
B. 2, 4, 5
C. 1, 2, 5
D. 1, 3, 4

正解：D

解説：
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?.

質問 # 40
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

質問 # 41
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

解説：
Explanation
According to the ISTQB Tester Foundation Level Agile Tester syllabus, a retrospective is a meeting held at the end of each iteration or release, where the agile team reflects on what went well and what can be improved in their processes, practices, and interactions. The purpose of a retrospective is to identify and implement actions for continuous improvement, and to foster a culture of learning and collaboration. Therefore, the items that would be the most effective to generate discussions on process improvement are those that are related to the team's performance, challenges, feedback, and suggestions. Option D is the least effective item to generate discussions on process improvement, as it is a personal attack on one of the team members, and it does not offer any constructive feedback or solution. This kind of item can create a negative and hostile atmosphere in the retrospective, and damage the trust and respect among the team members. Option A is an effective item to generate discussions on processimprovement, as it identifies a problem with the build process that affects the team's efficiency and quality, and it can lead to finding ways to optimize the build process or to mitigate the delays. Option B is also an effective item to generate discussions on process improvement, as it reveals a discrepancy between the team's estimation and actual effort, and it can lead to analyzing the root causes of the deviation and to improving the estimation techniques or the team's capacity. Option C is also an effective item to generate discussions on process improvement, as it highlights a weakness in the automation tests that hinders the team's ability to debug and fix the failures, and it can lead to enhancing the automation tests with better logging mechanisms or to reviewing the automation strategy. References: ISTQB Tester Foundation Level Agile Tester syllabus, section 2.1.1, page 14; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.1.2, page 15; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.2.1, page 16; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.2.2, page 17.

質問 # 42
An Agile team is developing a Pay-TV web portal. In Iteration 3, only PayPal and credit card payments are supported. A new user story in Iteration 4 adds payment using credit from a smartcard.
Which of the following would you expect to describe valid and relevant acceptance tests for this user story?

A. Tests to check that payments with insufficient credit charged on the smartcard are successful
B. Tests to check that payments with expired credit cards of supported credit card types are unsuccessful
C. Tests to check that payments with sufficient credit charged on the smartcard are given five percent discount are successful
D. Tests to check that payments with no credit charged on the smartcard will be unsuccessful

正解：D

解説：
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 2.1Acceptance Criteria and Testability, acceptance tests must be directly related to thenew functionalitydescribed in the user story.
* Option Dis correct - itvalidates the new featureof paying via smartcard credit, specificallyhandling edge cases(e.g., zero credit).
* Option Ais incorrect -payment should failwith insufficient credit.
* Option Bintroducesrequirements not mentionedin the story.
* Option Ctestscredit card logic, not the new smartcard functionality.
References:
CTFL-AT Syllabus v4.0, Section 2.1
Learning Objective (K3) - Derive acceptance tests from user stories

質問 # 43
Which of the following statements would you expect least likely to be true?

A. In Agile projects, where an independent test team works in parallel with Agile teams, the independent test team is usually expected to work on functional testing while Agile teams on non-functional testing
B. Having independent test teams working in parallel with Agile teams can be an option when scaling Agile software development, for example when an independent test team supports multiple Agile teams
C. In Agile projects where an independent test team works in parallel with Agile teams, the independent test team can work on long-term and/or non-sprint activities such as developing automated test tools
D. Having independent test teams working in parallel with Agile teams can be required for Agile projects that have to deal with regulatory compliance requirements and complex domains

正解：A

解説：
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 2.5Testers and Independence, it explains:
"An independent test team may be used in parallel to Agile teams to support non-sprint activities such as performance testing, test tool development, or testing in regulated environments." However, assigningfunctional testing to independent teamswhile Agile teams handlenon-functionalwork is theoppositeof common practice. Agile teams typically focus onfunctional testing, while specializednon- functionalor compliance testing may be handled externally.
Therefore,Option Ais least likely to be true.
References:
CTFL-AT Syllabus v4.0, Section 2.5
Learning Objective (K2) - Identify roles of independent test teams in Agile contexts

質問 # 44
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. Unlike working sessions or meetings held in non-Agile projects, Agile retrospectives do not require follow-up activities.
C. 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.
D. Agile retrospectives should be focused mainly on impediments that are outside the control of the team because these issues are more challenging.

正解：C

解説：
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,

質問 # 45
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. Work together with the developer, suggesting reasons why the tests are failing.
B. Use the time to improve and automate existing test cases of other user stories.
C. Review the design of the problematic user story and improve it where possible.
D. Create a bug report for each of your blocked tests.

正解：A

解説：
Explanation
As an agile tester, you should work together with the developer, suggesting reasons why the tests are failing.
This is an example of the agile principle of collaboration and communication within the team, as well as the agile testing practice of early and frequent feedback. By working together with the developer, you can help to identify and resolve the root causes of the test failures, as well as share your testing knowledge and perspective. This can lead to faster and better quality delivery of the user story, as well as improved team relationships and trust.
Option A is not a good action, because reviewing and improving the design of the user story is not the tester's responsibility, and it may not address the test failures. Option B is also not a good action, because creating bug reports for blocked tests is not an agile way of handling issues, and it may create unnecessary overhead and waste. Option D is not a good action, because it does not help to unblock the current user story, and it may distract you from the sprint goal and the team's focus.
References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.3.1, page 171; ISTQB Foundation Level Agile Tester Sample Exam Questions, Question 2.3.1-2, page 82

質問 # 46
Which of the following describes the frequency with which usually all changes made to the software are merged and all changed components are integrated regularly in a continuous integration process?

A. At least once a day
B. At least once a month
C. At least once a week
D. At least once per iteration

正解：A

解説：
Comprehensive and Detailed Explanation From Exact Extract:
From theCTFL-AT Syllabus v4.0, Section 4.2Continuous Integration, it states:
"Continuous integration involves integrating code into a shared repository several times a day. Each integration is verified by an automated build and automated tests." Hence,Option D-at least once a day- correctly reflects best practice in continuous integration.
* Option A(once per iteration) andB,Care far too infrequent to meet the goals of CI.
* The objective is to detect integration issuesearly and often, which is only achievable throughdaily (or more frequent)integrations.
References:
CTFL-AT Syllabus v4.0, Section 4.2
Learning Objective (K2) - Understand frequency and purpose of continuous integration

質問 # 47
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. Scrum
B. Continuous Integration
C. Kanban
D. Extreme Programming

正解：A

解説：
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

質問 # 48
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

解説：
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:
* : ISTQB Foundation Level Agile Tester Syllabus, Version 2014, Section 1.1.1
* : ASTQB Agile Tester Certification Resources, Agile Testing Foundations, Chapter 1, Section 1.1.1

質問 # 49
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.

質問 # 50
Which of the following statements would you expect to be the MOST direct advantage of the whole-team approach?

A. Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.
B. Having at least once a day an automated build and test process that detects integration errors early and quickly.
C. Reducing the involvement of business representatives because of the increased communication and collaboration between testers and developers.
D. Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.

正解：A

解説：
The whole-team approach is a principle of agile testing that involves everyone with different knowledge and skills to ensure project success. The whole-team approach means that the business representatives, testers, and developers work together in every step of the development process, from planning to delivery. The whole- team approach aims to enhance communication and collaboration within the team, leverage the various skill sets of the team members, and make quality everyone's responsibility12. Therefore, the statement C is the most direct advantage of the whole-team approach, as it captures the essence of the principle and its benefits.
The other statements are not directly related to the whole-team approach, or are incorrect. Statement A is about continuous integration, which is a practice of agile development that involves having at least once a day an automated build and test process that detects integration errors early and quickly. Continuous integration is not a direct consequence of the whole-team approach, although it may be facilitated by it13. Statement B is about avoiding requirements misunderstandings, which may be a benefit of the whole-team approach, but not the most direct one. The whole-team approach does not only focus on requirements, but also on design, implementation, testing, and delivery. Moreover, avoiding requirements misunderstandings may also depend on other factors, such as the quality of the user stories, the use of acceptance criteria, and the feedback from the customers and users14. Statement D is incorrect, as it contradicts the whole-team approach. The whole- team approach does not reduce the involvement of business representatives, but rather increases it. Business representatives are an integral part of the whole-team approach, as they provide the vision, the value, and the validation of the product. They collaborate with the testers and developers to define the features, prioritize the backlog, and verify the outcomes12. References: ISTQB Foundation Level Agile Tester Syllabus1, Section
1.2.1, page 9; What is Whole Team Approach in Agile Testing?2, Section What is Whole Team Approach?; Continuous Integration3, Section What is Continuous Integration?; Effective User Stories - 3C's and INVEST Guide4, Section The 3 C's (Card, Conversation, Confirmation) of User Stories.

質問 # 51
Which ONE of the following is an example of a typical "Business-oriented work product"?

A. Acceptance testing entry criteria.
B. The released product.
C. A user manual.
D. Usability testing test results.

正解：C

解説：
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.

質問 # 52
......

CTFL-AT完全版問題集には無料PDF問題で合格させる：https://www.passtest.jp/ISQI/CTFL-AT-shiken.html

無料Agile Tester CTFL-AT公式認定ガイドPDFダウンロード：https://drive.google.com/open?id=1geM4BrY8A5qV-nJBZhVv-Ukhf6_wBv1I

関するブログ

もっと

CTFL-AT 無料問題集