売れ筋トップクラスのCTFL-AcT最新試験問題2025年最新のISQI試験練習
ISTQB Foundation Level問題集でCTFL-AcT試験は完全版問題で試験学習ガイド
CTFL-ACT認定試験の準備をするために、専門家はさまざまなトレーニングおよび学習資料を活用できます。 ISQIは、インストラクター主導のトレーニング、eラーニングコース、自習資料など、さまざまなトレーニングコースを提供しています。さらに、専門家は、練習試験、学習ガイド、参照帳など、オンラインでの範囲の研究資料も見つけることができます。適切な準備により、専門家は自信を持ってCTFL-ACT認定試験を受講し、ソフトウェアテストでキャリアを進めることができます。
質問 # 36
Which one of the following statements describes the collaboration between business analysts and testers BEST?
- A. Testers participate in identifying business needs of stakeholders to better understand the business needs and related requirements.
- B. Business analysts collaborate on test planning and risk analysis to ensure that further on, appropriate test cases are developed and prioritized.
- C. Once the requirements and acceptance criteria have been defined, business analysts are no longer involved in testing activities.
- D. Business analysts usually cannot review acceptance tests, because they do not understand the technical details.
正解：B
質問 # 37
Which one of the following statements regarding ATDD / BDD is true?
- A. In both Acceptance-Test Driven Development (ATDD. and Behavior-Driven Development (BDD., test cases provide examples of product use.
- B. In Acceptance-Test Driven Development (ATDD., test cases are written prior to the acceptance criteria.
- C. In both Acceptance-Test Driven Development (ATDD. and Behavior-Driven Development (BDD., acceptance test cases are written by a test automation engineer as test automation code.
- D. Behavior-Driven Development (BDD. considers acceptance test design as an activity to be handled by the test team after requirements have been finalized.
正解：A
解説：
ATDD and BDD are agile development approaches that emphasize collaboration among stakeholders (such as business analysts, developers, testers, and customers) to define clear and testable acceptance criteria before or as requirements are being finalized. Both techniques promote using concrete examples to drive development and validate understanding.
In ATDD, acceptance test cases are derived directly from user stories or requirements and written before the actual implementation starts. In BDD, scenarios are expressed in natural language (often using Gherkin syntax) to describe behaviors the system should exhibit under specific conditions. In both cases, these tests serve not only as validation tools but also as executable specifications - i.e., shared understanding expressed through concrete examples.
Option B is correct because both methodologies use examples (scenarios/test cases) to describe how a system should behave - serving as acceptance criteria.
Incorrect options:
Option A wrongly suggests BDD defers testing until after requirements are finalized - it actually promotes early collaboration.
Option C is false - in ATDD, test cases are based on predefined acceptance criteria, not written beforehand.
Option D is inaccurate - acceptance tests in ATDD and BDD may be automated but are collaboratively written first, not by test automation engineers alone.
Exact Reference - ISTQB CTFL Acceptance Testing Syllabus (Section 2.2):
"Both ATDD and BDD involve the collaborative definition of test cases before implementation to clarify requirements and serve as product usage examples."
質問 # 38
As an acceptance tester you are analyzing the following user story for a computer web-based mass multiplayer role-playing game:
As an unregistered player
I want to be able to register myself by defining my e-mail, login and password in a registration form so that I become a registered player Consider the following propositions of the acceptance criteria:
i.a registration form is displayed on the screen.
ii.the form is written in the Groovy language; the cursor is initially set on the 'login' field; after pushing the TAB button the cursor switches to 'password', 'repeat password', 'mail', and 'repeat mail' forms.
iii.I cannot register myself if the login I choose is used by another player.
iv.after successful registration process I am informed about it by an e-mail.
Which of the above statements would you consider as well-written acceptance criteria?
- A. only ii)
- B. only i), iii) and iv)
- C. only i) and iii)
- D. only ii) and iv)
正解：B
質問 # 39
Which one of the following statements regarding performance testing is MOST correct?
- A. The performance of the system is measured in a context that reflects, as far as possible, representative operating conditions.
- B. Performance testing aims to determine a system's robustness against malicious attacks.
- C. The performance test results serve to determine hardware and software performance requirements.
- D. Depending on the model used to simulate the workload, performance tests are called load, stress or endurance / stability tests.
正解：A
質問 # 40
Which one of the following statements about the relation between business goals, business needs and requirements is true?
- A. Business goals can be extracted from product requirements
- B. Once the business requirements are elicited, business analysts start to formalize business goals for the project.
- C. Business requirements are generally developed by refining product requirements.vhbj
- D. Business goals, business needs and requirements describe, at different levels of abstraction, what shall be archived
正解：D
解説：
The relationship between business goals, business needs, and requirements is hierarchical and reflects increasing levels of specificity:
Business Goals: High-level strategic objectives.
Business Needs: Problems or opportunities that must be addressed to achieve those goals.
Requirements: Specific capabilities or conditions the system must satisfy to meet the needs.
Option B is correct because it accurately describes how these elements relate at different abstraction levels in the requirements hierarchy. This relationship is fundamental to business analysis and accepted by standards like BABOK and ISTQB.
Other options:
A is reversed - business goals usually precede and drive the elicitation of requirements.
C and D misrepresent the sequence - product requirements are derived from business goals and needs, not the other way around.
B). Business goals, business needs and requirements describe, at different levels of abstraction, what shall be achieved
質問 # 41
Which one of the following statements describes the relation between business goals, business needs and requirements BEST?
- A. Business goals and business needs are synonyms.
- B. To derive the business needs, the business analyst first has to understand the business goals and requirements.
- C. Business needs address the business solution whereas business requirements define the business problem or opportunity.
- D. Business goals, business needs and requirements describe at different levels of abstraction, what shall be achieved.
正解：D
解説：
According to ISTQB and the Business Analysis Body of Knowledge (BABOK) standards, the terms business goals, business needs, and requirements are related but represent different levels of abstraction in defining what an organization aims to achieve.
* Business Goals represent the high-level strategic objectives an organization wants to accomplish.
These are broad statements of intent and typically reflect long-term ambitions.
* Business Needs specify what the business must address to meet its goals; these are more focused descriptions of the problems or opportunities that justify the business change. They provide a rationale for why a project or initiative is undertaken.
* Requirements are detailed specifications that describe the features, functions, or qualities the solution must have to fulfill the business needs.
The relationship is hierarchical and increasingly specific: business goals set the overarching purpose, business needs interpret these goals into actionable problem statements or opportunities, and requirements specify the solution details.
ISTQB glossary and syllabus excerpts confirm this layered approach, clarifying that these terms are not synonymous but instead describe the same concept at varying levels of detail and abstraction. Therefore, option B best captures this nuanced relationship.
Exact Extract from ISTQB Foundation Level Syllabus (Business Analysis Section):
"Business goals, business needs, and requirements describe, at different levels of abstraction, what shall be achieved by the business change. Business goals are high-level statements; business needs are statements of problems or opportunities to be addressed, and requirements define the detailed attributes of the solution to meet those needs."
質問 # 42
In a project to develop an online booking system, the team decided to strengthen collaborative work between the business analyst and the testers working on the project. Several concrete joint activities have been identified.
- A. Development of acceptance criteria for user stories
- B. Definition of Beta Testing sessions
- C. Review of risk to prioritize acceptance test
- D. Business needs assessment
正解：A
解説：
Collaboration between business analysts and testers is critical in Agile and acceptance testing environments.
One of the most effective areas of cooperation is the joint development and review of acceptance criteria for user stories. This ensures that criteria are testable, clearly defined, and aligned with stakeholder expectations.
Option B is correct because creating acceptance criteria is where both business analysts (who understand the business needs) and testers (who ensure testability and clarity) contribute effectively.
Other options:
A (Business needs assessment) is typically a responsibility of business analysts, not a joint activity with testers.
C (Review of risk to prioritize acceptance tests) is a valuable activity but comes after criteria are defined.
While it can be collaborative, it's more specific to test planning.
D (Definition of Beta Testing sessions) is less relevant to ongoing collaborative work between testers and BAs - this involves users and release planning.
B). Development of acceptance criteria for user stories
質問 # 43
You are leading a brand new project team whose members are coming from all over the organization and have no former experience in working together. You need to build a common vision and team spirit. What workshop would fit BEST:
- A. You invite every member in turn to describe his/her past experience and his/her major achievements in the organization or in their former job.
- B. You ask every member in turn to write down three things he/she likes and dislikes in the organization and to post them on a wall. A volunteer is then chosen to read randomly some posts that are then discussed with the group.
- C. You invite the team members and ask them to design their own (team-wise) emblem representing their values, beliefs, goals, tasks together than a common motto.
- D. You draw a staircase with 11 steps, each of them representing a major milestone of the project. The bottom of the stairs corresponds to the first day of the project and the upper step means that the project is released. You locate the present situation in the top of the stairs. The team is asked to identify and discuss the major steps downwards.
正解：C
解説：
Comprehensive Detailed Explanation (Approx. 200 words):
Building a new team with members from diverse backgrounds requires activities that foster shared values, identity, and trust. Designing a team emblem with values, goals, and a motto is a well-known team-building technique often used in Agile kick-offs. It engages creativity, sparks discussion about shared purpose, and reinforces a collective team identity.
Option A is correct because it supports both vision and team spirit - crucial for newly formed teams.
Other options:
B focuses on individual backgrounds but may not build a collective vision.
C risks highlighting negative views about the organization and may not foster trust at the early stage.
D uses a "staircase" metaphor but incorrectly locates the team at the top of the stairs - potentially signaling an endpoint rather than a beginning, making it inappropriate for a new team.
A). You invite the team members and ask them to design their own emblem...
質問 # 44
Which one of the following test design techniques fits accepting testing purposes BEST?
- A. static code analysis
- B. input validation
- C. defect-based test design
- D. equivalence partitioning
正解：D
質問 # 45
The project team is currently facing a difficult situation originating from their difficulty in envisioning the future and the necessary steps to reach it together with a certain loss of motivation due to a strong feeling of stagnation. You try to unlock the situation by proposing a workshop. Which one would fit the best?
- A. You draw a staircase with 11 steps, each of them representing a major milestone of the project. The bottom of the stairs corresponds to the first day of the project and the upper step means that the project is released. You locate the present situation in the middle of the stairs. The team is asked to identify and discuss the major steps down and up.
- B. You ask two volunteers to play a part in front of the team. One will try to defend the project and propose positive arguments and ways forward. The other will do the opposite. You then recapitulate the major arguments of both sides and debate them openly with the team.
- C. You visualize all remaining major milestones of the project, starting with today and ending with project release. Then, you ask the team to identify and discuss the necessary actions to move forward from the present situation and to reach the milestones.
- D. You organize a day out with challenging physical exercises practiced in teams followed by an afterwork dinner and drink. After all, nothing is best for motivation than hard times together, strong common objectives and a promise of good time.
正解：A
質問 # 46
Your company wants to establish a new human resources management application. As tester, you propose to use an ATDD approach and to use business process models for test case design.
Which of the following statements is the LEAST meaningful argument for this approach?
- A. Testers will be able to show test coverage directly within the graphical representation of business processes.
- B. Business process models will make it easier to detect defects in the application code.
- C. As business process models will be updated to maintain the tests, they will be a living documentation of the product.
- D. The process models will help testers to understand the use cases to be tested.
正解：B
質問 # 47
As a tester you are part of a development team for a health monitoring system to record and synchronize various health parameters, calculate health score and provide practical advice on how to maintain and improve health Consider the following User Story and related acceptance criterion:
US 34: As a user of the system, I can measure my blood sugar by using a blood glucose meter connected device, in order to adjust my diet and medication dosage if I am diabetic Acceptance criteria # 1 - Once a blood sugar measurement using the blood glucose meter is done by logged-in user, the measurement result is displayed in less than four seconds.
Which of the following test cases written in Gherkin language is BEST for this user story and acceptance criterion?
- A. GIVEN I am diabetic 3 WHEN I measure my blood sugar with a blood glucose meter connected device THEN I can see the result on my personal dashboard in less than 4 seconds
- B. GIVEN I am logged in on the system 3 WHEN I measure my blood sugar with a blood glucose meter connected device THEN I can see the result on the my personal dashboard in less than 4 seconds
- C. WHEN I measure my blood sugar with a blood glucose meter connected device THEN I can see the result on the personal dashboard in less than 4 seconds and obtain an alert if the risk of hypoglycemia or hypoglycemia is high
- D. GIVEN I am logged in on the system 3 WHEN I measure my blood pressure THEN I can see the result on the my personal dashboard in less than 4 seconds
正解：B
解説：
This user story is about a logged-in user measuring their blood sugar using a connected glucose meter and seeing the result quickly. The acceptance criterion specifies that the result should be displayed in less than four seconds.
Option B is correct because:
It starts with a valid GIVEN precondition ("I am logged in").
The WHEN step matches the functionality described in the user story (blood sugar measurement using a connected device).
The THEN step explicitly includes the performance expectation ("less than 4 seconds"), aligning directly with the acceptance criterion.
Other options:
A is incorrect - while it mentions the correct functionality, "I am diabetic" is not a necessary system precondition.
C refers to blood pressure instead of blood sugar - mismatched with the user story.
D introduces additional functionality (alerts for hypo-/hyperglycemia), which is not part of the specified acceptance criteria.
B). GIVEN I am logged in on the system ... THEN I can see the result ... in less than 4 second
質問 # 48
Which of the following sentences explains BEST how acceptance test cases can be derived from the acceptance criteria
- A. Test design should start with non-functional acceptance criteria and only then with functional aspects
- B. Risk-based testing is not a good practice for designing and prioritizing tests because the objective is to cover only the acceptance criteria
- C. Acceptance criteria are not useful for creating acceptance test cases because experience-based techniques should be preferred
- D. Test techniques such as business process-based testing or use case testing can be used to create acceptance tests from the acceptance criteria
正解：D
解説：
Acceptance criteria describe the conditions under which a requirement or user story is considered fulfilled.
These criteria serve as the basis for deriving acceptance test cases. To transform them into concrete tests, testers apply test design techniques such as:
Business process-based testing (deriving tests from modeled workflows)
Use case testing (based on user interactions with the system)
Option B is correct because it clearly describes how structured techniques are applied to translate acceptance criteria into actionable test cases, ensuring traceability and relevance.
Other options:
A is incorrect - experience-based techniques may supplement, but structured methods are foundational in deriving test cases from defined criteria.
C is misleading - risk-based testing is a well-established and effective practice for prioritizing test efforts, including acceptance testing.
D is incorrect - both functional and non-functional criteria are important; there's no fixed rule to prioritize one over the other.
B). Test techniques such as business process-based testing or use case testing can be used to create acceptance tests from the acceptance criteria
質問 # 49
Which one of the following combinations between high-level security requirements and security testing techniques matches BEST?
- A. Static vulnerability analysis to test authentication and authorization mechanisms
- B. Penetration testing to test the validation and sanitization of input data
- C. Fuzzing to test the performance of cryptographic algorithms
- D. Threat modeling to test the organizational security policy
正解：A
解説：
Security testing ensures the system protects data and maintains intended behavior under potential attacks.
Different techniques address specific security goals.
Option A is correct: Static vulnerability analysis inspects code or architecture without executing it, identifying weaknesses in mechanisms such as authentication (e.g., login controls) and authorization (e.g., access permissions). These mechanisms are foundational security requirements.
Other options:
B is misleading - penetration testing simulates attacks, but input validation is more often verified with fuzzing or code review.
C is incorrect - fuzzing tests input handling, not the performance of cryptographic algorithms.
D is incorrect - threat modeling is a design-time activity to identify risks; it's not used to test policies directly.
A). Static vulnerability analysis to test authentication and authorization mechanisms
質問 # 50
As an acceptance tester you want to test the $100 withdrawal process described by the following Business Process Model and Notation (BPMN) model.
You would like to achieve the following coverage criterion "execute all possible process tasks". Consider the following test cases:
Test 1: balance = $100, receipt = YES
Test 2: balance = $120, receipt = NO
Test 3: balance = $85
Test 4: balance = $20, receipt = YES
Which of the following is the minimal set of test cases allowing to achieve required coverage?
- A. Test 1, Test 2, Test 3
- B. Test 2, Test 4
- C. Test 1, Test 3
- D. Test 1, Test 2, Test 4
正解：C
質問 # 51
Which of the following information is most likely part of an acceptance test summary report?
- A. Information to evaluate the level of risk for product release.
- B. Technical details on defect fixes.
- C. Test procedure information.
- D. Test strategy and test design methods.
正解：A
解説：
An acceptance test summary report is a high-level document produced at the end of acceptance testing. It provides stakeholders (especially business owners and decision-makers) with essential information to determine whether the system meets the acceptance criteria and whether it is ready for release.
Option A is correct because understanding the residual risk - based on test results, open defects, and coverage - is critical for release decisions. The summary report includes test execution status, significant findings, defect summaries, and an overall risk assessment.
Other options:
B (technical details on defect fixes) belong more in defect or technical reports, not in the acceptance summary.
C (test strategy/design methods) are part of the test plan, not the summary report.
D (test procedure info) is operational detail, not suited for a high-level summary report.
A). Information to evaluate the level of risk for product release.
質問 # 52
Which one of the following statements regarding the relationship between acceptance testing activities and business analysis activities is true?
- A. Test analysis activities generally produce business requirements.
- B. In Agile, requirements engineering activities are removed and replaced by solution evaluation
- C. It is important to keep testing activities and business analysis activities as separate as possible to ensure test ^ independence
- D. The join work of business analyst and testers on acceptance criteria and acceptance test cases contributes to v u the "Early Testing" best practice
正解：D
解説：
"Early Testing" is a well-known best practice in software testing, promoting the involvement of testers early in the project - ideally during requirements definition - to identify ambiguities, risks, and inconsistencies.
Option B is correct because involving both testers and business analysts in defining acceptance criteria helps ensure those criteria are clear, testable, and aligned with business needs from the outset. This leads to fewer misunderstandings and defects later in the lifecycle.
Other options:
A is incorrect - Agile does not eliminate requirements engineering; it adapts it with user stories, refinement, and just-in-time elaboration.
C is incorrect - test analysis interprets existing requirements; it doesn't produce them.
D is false - while some level of test independence is valuable, Agile promotes collaboration between roles to achieve shared understanding.
B). The joint work of business analyst and testers on acceptance criteria and acceptance test cases contributes to the "Early Testing" best practice
質問 # 53
Which one of the following arguments is the BEST reason to add additional information to BPMN diagrams?
- A. Links to requires test equipment facilitate test case reviews of stakeholders
- B. Link to risks provide input to testers for selecting regression tests
- C. Link to priorities help test case authors to write comprehensive test cases
- D. Link to requirements / user stories enable testers to execute the tests
正解：B
解説：
In BPMN models, additional annotations such as links to requirements, test data, or risks improve the value of the diagram for downstream stakeholders like testers. When BPMN tasks or flows are linked to known risks, testers can prioritize regression test cases accordingly - a key principle in risk-based testing.
Option D is correct because linking risks to business processes gives testers meaningful input for deciding which parts of the system require deeper or repeated testing.
Other options:
A: Priority links are useful, but less impactful than risk-based test selection.
B: Links to test equipment are not commonly embedded in process diagrams and are more relevant to hardware or system integration testing.
C: Linking to requirements helps traceability, but execution readiness is more closely tied to test cases and data than to BPMN.
D). Link to risks provide input to testers for selecting regression tests
質問 # 54
Which one of the following acceptance criteria relates to security requirements?
- A. The system's response time shall not exceed 3 seconds.
- B. Normal users shall have restricted access to private data.
- C. The system shall be web-based.
- D. The graphical user interface shall comply with corporate style guides.
正解：B
質問 # 55
For a project to migrate an employee qualification management system to web technologies, the following requirement has been defined REQ 3-12 The system must be able to manage 3 types of users: HR team member with full rights, department manager with consultation and update rights only for members of his/her department, and employee with read-only access to his/her data Which of the following sentences BEST reflects an acceptable acceptance criterion?
- A. The list of employees who are members of a department can only be updated by a person logged as HR
- B. Since I am logged in as a department manager, when I try to access the file of an employee who is not in my department then a message telling me that I do not have access rights is displayed
- C. The database must use MangoDB
- D. Security test must be performed to demonstrate that the authentication and rights management system is working properly
正解：B
解説：
Acceptance criteria should define how the system behaves for a given user story or requirement. They must be precise, testable, and directly traceable to the requirement being verified.
REQ 3-12 describes access control for three user types. Option B is a concrete, scenario-based acceptance criterion that tests the enforcement of access rights - making it an ideal match.
Other options:
A is irrelevant - database technology (MongoDB) is an implementation detail, not a functional criterion.
C is too vague - stating that security tests must be performed doesn't specify expected behavior or outcome.
D is plausible, but option B more directly demonstrates how an actual system behavior validates the requirement.
B). Since I am logged in as a department manager, when I try to access the file of an employee who is not in my department then a message telling me that I do not have access rights is displayed
質問 # 56
Assume you are testing functionality of the interface of an elevator. One of the requirements is that the elevator can work only if the total weight of the passengers does not exceed 200 kg. The elevator can reach the following floors: Ground Floor, 1st floor and 2nd floor. You want to create an acceptance test using the Gherkin language. You can use the following phrases for this purpose:
i.the total weight of passengers is greater than 200 kg
ii.the elevator is on the Ground Floor
iii.a button '1st floor' was pressed
iv.the elevator goes to the 1st floor
v.a passenger standing at the 2nd floor calls the elevator
vi.a message 'too many passengers' is displayed on the screen
Which of the following statements correctly matches constructs of Given/When/Then with a relevant phrase in order to create a correct test case for the given requirement?
- A. GIVEN ii)
WHEN iv)
THEN v) - B. GIVEN ii)
WHEN v) AND vi) THEN i) - C. GIVEN iii)
WHEN ii)
THEN iv) - D. GIVEN ii)
WHEN i)
THEN vi)
正解：D
質問 # 57
Why can it be a good practice to draw business process models that only partially cover the behavior of related software systems?
- A. The model will contain too many model elements
- B. They should be exactly one model per requirement
- C. The model should focus on what is to be tested
- D. It is impossible to describe the complete workflow
正解：C
解説：
In business process modeling for testing purposes, especially in acceptance testing, it is not always necessary or practical to model the entire system or process in exhaustive detail. ISTQB and the CTFL-BAT (Business Analysis Testing) extension emphasize that test models - including business process models - should serve specific testing objectives.
Focusing the model on what needs to be tested allows the test team to:
Avoid unnecessary complexity,
Highlight relevant paths and decisions,
Derive precise and efficient test cases,
Facilitate stakeholder understanding and validation.
According to the ISTQB Foundation Level Extension - Business Analysis syllabus:
"Process models used in testing should represent the business behavior relevant to the test scope. Including too many irrelevant paths and decisions can lead to inefficient test case design and may distract from the core validation goals." Therefore, Option A is correct because limiting the scope of the business process model to the parts that are relevant for testing is a best practice, especially in acceptance testing where focus is on verifying that business needs are met.
Options B, C, and D are not strong justifications:
B suggests avoiding complexity but not purpose-driven modeling.
C incorrectly implies impossibility rather than pragmatic scope.
質問 # 58
What is a common way to use business process modeling for ATDD?
- A. Business analysts automatically generate requirements / user stories from the graphical workflow
- B. Testers define acceptance criteria for requirements / user stories to provide input for BPMN model
- C. Tester use business process models to write test cases that cover the different paths
- D. Business analysts use workflow descriptions to derive testing rules from the business process model
正解：C
解説：
In ATDD (Acceptance Test-Driven Development), business process modeling (e.g., using BPMN) is a powerful way to visualize workflows and system behavior from the user's perspective. Testers can use these models to derive acceptance test cases by covering different business paths, including normal flows, alternate flows, and exception conditions.
Option A is correct because it reflects this practical usage: testers analyze the business process model and create test cases to ensure coverage of the different paths the system might take. This aligns acceptance testing directly with business logic and enhances traceability.
Other options:
B is partially valid but less direct; business analysts help define rules, but test case creation is a tester's role.
C reverses the correct flow; BPMN models are often created first and used to define or validate acceptance criteria, not the other way around.
D is incorrect - requirements/user stories are usually defined through stakeholder collaboration, not auto- generated from BPMN diagrams.
A). Testers use business process models to write test cases that cover the different paths.
質問 # 59
As a tester you participate in the project of the decision support system for granting a loan. You are asked to review the acceptance criteria for the following requirement:
REQ 3.28. The automated system records critical credit application data (CCAD. needed to support application screening.
Assume that it is well known what kind of data CCAD are. Which of the following would be the BEST example of an acceptance criterion for this requirement?
- A. The CCAD are stored in the MySQL relational database after each successful data entry procedure.
- B. The CCAD is not recorded if it is incomplete and a message is displayed.
- C. The process for collecting CCAD meets corporate usability guidelines.
- D. The CCAD record process is quick and reversible.
正解：A
解説：
Acceptance criteria must be concrete, testable, and focused on observable system behavior. They define what the system must do to satisfy a requirement and help determine whether the requirement has been successfully implemented.
REQ 3.28 states: "The automated system records critical credit application data (CCAD) needed to support application screening." From this, we infer that the system must persistently store this data after data entry.
Option A is the best match because it provides a specific, observable behavior (CCAD being stored in a MySQL database after a successful entry) that can be verified through acceptance testing. It's a measurable outcome, aligned with the requirement's objective.
Other options are less suitable:
Option B introduces new behavior (displaying a message) not directly tied to the original requirement.
Option C is vague ("quick and reversible") and lacks measurable criteria.
Option D refers to usability guidelines, which is not directly relevant to the storage functionality stated in the requirement.
Exact Reference - ISTQB CTFL Acceptance Testing Syllabus (Section 1.3.2):
"Well-written acceptance criteria are unambiguous, testable, and focused on observable results."
質問 # 60
Which of the following information is most likely part of an acceptance test summary report?
- A. Information to evaluate the level of risk for product release.
- B. Technical details on defect fixes.
- C. Test procedure information.
- D. Test strategy and test design methods.
正解：A
質問 # 61
......
最善な方法で問題集を使おう！練習テストならこれISQI CTFL-AcT：https://www.goshiken.com/ISQI/CTFL-AcT-mondaishu.html
CTFL-AcT問題集を無料提供しております！試験問題と解答：https://drive.google.com/open?id=1sCQYp1OifO_9jrMnWwdk2CZSY8eQtmc0