最新版を今すぐ試そう！[2026年01月] 試験準備には欠かさない！CTFL-AcT問題集 [Q22-Q47]

最新版を今すぐ試そう！[2026年01月] 試験準備には欠かさない！CTFL-AcT問題集

有能な受験者がシミュレーション済みのCTFL-AcT試験PDF問題を試そう

質問 # 22
Consider the following BPMN model and the related DMN model describing the decision rules associated to the "Check of delivery" activity What is the minimum number of test cases required to cover all paths without repeated loops in the BPMN model AND all decisions in the DMN table?

A. 0
B. 1
C. 2
D. 3

正解：B

解説：
To determine the minimum number of test cases needed to cover:
All unique paths (without repeating loops) in the BPMN process model.
All decision rules (combinations) in the DMN decision table.
Let's break it down:
BPMN Paths:
If the purchase order is not approved # process ends # 1 path
If approved:
Goods received # "Check of delivery" # Acceptance YES # Payment # 1 path Goods received # "Check of delivery" # Acceptance NO # Discussion # End # 1 path
= Total distinct BPMN paths: 3
DMN Table:
There are 4 rules based on two inputs (Quality check and Quantity check):
Acceptable + Amount ok # Passed
Substandard + Amount ok # Failed
Acceptable + Amount incorrect # Failed
Substandard + Amount incorrect # Failed
You must execute 4 combinations to cover all decision rules.
To cover both all BPMN flows and all DMN rules, you need a minimum of 4 test cases (each using a different rule from the DMN table and associated BPMN path). Paths may overlap, but all rules must be exercised.

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

質問 # 24
The following BPMN and DMN models are used for acceptance testing. The DMN table is linked to the credit card scanning to check if a discount is applicable.
Which of the following statements regarding test generation from these BPMN and DMN models is MOST correct?

A. These models can be used to generate a test case for a 0% reduction if the customer has more than 1000 loyalty points
B. These models can be used to generate a test case for a 5% reduction if the customer has more than 500 loyalty points
C. These models can be used to generate a test case for a 3% reduction if the customer has more than 5000 loyalty points
D. These models can be used to generate a test case for a 3% reduction if the customer has more than 1000 loyalty points

正解：B

解説：
This question is about combining Business Process Model and Notation (BPMN) and Decision Model and Notation (DMN) to design test cases for acceptance testing. The BPMN diagram outlines the customer checkout flow with a decision on whether a loyalty card is used, followed by a card scan that may trigger a discount check. The DMN decision table defines the logic for determining the discount percentage based on the number of loyalty points.
From the DMN:
<1000 points # 0% discount
1000-3000 points # 5% discount
3000 points # 5% discount
Option D correctly states that a customer with more than 500 points could be eligible for a 5% discount - but only if the number of points exceeds 1000. Since 500 does not meet the 1000 threshold, it appears this statement could be problematic at first glance. However, interpreting the spirit of the question, Option D is the only one matching the correct maximum discount scenario.
Let's clarify each option:
A is incorrect: >1000 points qualifies for 5%, not 0%.
B is incorrect: 3% is not defined anywhere - DMN has 0% or 5%.
C is incorrect: again, 3% does not exist in the table.
D is acceptable in principle, assuming a typo (i.e., it should be "more than 1000" instead of 500); however, if taken literally, it would be incorrect.
However, given the options, D is the only one aligning with actual DMN output for >1000 loyalty points, despite the inaccurate lower limit.
D). These models can be used to generate a test case for a 5% reduction if the customer has more than
500 loyalty points
(If the literal error in Option D is to be treated strictly, the correct answer would be "none of the above," but in context of typical ISTQB-style questions, D is the best fit.)

質問 # 25
Which one of the following statements describes the relation between business goals, business needs and requirements BEST?

A. Business goals, business needs and requirements describe at different levels of abstraction, what shall be achieved.
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 and business needs are synonyms.

正解：A

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

質問 # 26
Suppose you are an acceptance tester in a project developing a medical scanner. The scanner is meant to be used in a hospital and should allow the examination of at leaser 50 patients per day. Which one of the following perspectives is MOST affected, if the produce does not meet the specified performance requirements?

A. Technical perspective
B. Functional perspective
C. Business perspective
D. User perspective

正解：C

解説：
The medical scanner must be able to examine at least 50 patients per day. This requirement directly impacts hospital operations and service efficiency. If the scanner fails to meet performance requirements, such as processing speed or availability, it will affect the hospital's ability to deliver services to patients - impacting schedules, patient flow, and ultimately the business goals of the hospital.
Option C is correct because it reflects the consequences of performance shortfalls from a business outcome perspective: failure to meet this requirement may result in financial loss, compliance issues, or customer dissatisfaction.
Other options:
A (User perspective) is involved, but the impact here is primarily operational/business.
B (Functional perspective) refers to whether the scanner has the correct features, not performance.
D (Technical perspective) is also relevant, but the business impact (e.g., service delivery) takes precedence in this case.

質問 # 27
How does ISTQB CTFL test activities relate to the IQBBA FL business analysis and requirements engineering activities?

A. The IQBBA solution evaluation phase precedes the ISTQB test implementation and test execution activities.
B. Business analysts and tester have to decide, whether they follow the IQBBA or ISTQB lifecycle processes, because they exclude each other.
C. Test analysis and test design activities may result in changes of acceptance criteria.
D. Business analysts who follow the IQBBA requirements engineering process will not be involved in designing test cases.

正解：C

解説：
The relationship between testing and requirements engineering is iterative and collaborative. According to ISTQB CTFL and IQBBA FL syllabi, test activities such as test analysis and test design involve reviewing and interpreting acceptance criteria to derive test conditions and test cases. During this process, testers may identify ambiguities, conflicts, or missing acceptance conditions. These insights often result in feedback to business analysts or stakeholders, leading to refinement or changes in the acceptance criteria to ensure clarity, completeness, and testability.
This iterative feedback loop is essential in both Agile and traditional lifecycles. Therefore, option D is correct.
It reflects the dynamic interaction between requirements and test design, where improving one often improves the other.
Other options are incorrect:
Option A falsely assumes business analysts don't engage in test design, while in practice, they collaborate closely with testers.
Option B incorrectly suggests that IQBBA and ISTQB lifecycles are mutually exclusive. In fact, they complement each other.
Option C is incorrect in sequencing. In reality, solution evaluation (IQBBA) follows test execution, not precedes it.
Exact Reference - ISTQB CTFL Acceptance Testing Syllabus (Section 1.3.2):
"During test analysis, inconsistencies or missing information in the acceptance criteria can be identified and addressed through collaboration with business analysts."

質問 # 28
Which of the following statements about test approaches and test techniques for acceptance testing is MOST correct?

A. The refinement of requirements / user stories into acceptance criteria provides test conditions for the creation of acceptance tests
B. The review of user requirements / user stories and associated acceptance criteria avoids dynamic acceptance u testing
C. If exploratory tests are performed, then there is no need to cover the acceptance criteria
D. Code coverage and Test-Driven Development are generally combined with boundary value analysis in acceptance testing

正解：A

解説：
In ISTQB Acceptance Testing context, the process of refining requirements or user stories into acceptance criteria plays a crucial role in defining clear, testable conditions. These acceptance criteria act as the basis for deriving test conditions, which are in turn used to design acceptance test cases.
According to the ISTQB Foundation Level Acceptance Testing syllabus:
"Acceptance criteria are refined expressions of business requirements, and they help to determine the scope and intent of acceptance tests. These criteria are used to derive test conditions and guide the development of test cases." This alignment ensures that the delivered software meets the expectations set out in the requirements and satisfies the user needs. Acceptance tests are typically written from the user's perspective and are focused on verifying that the system behaves correctly in realistic business scenarios.
Option B is correct because it explicitly describes this logical and procedural relationship between user stories, acceptance criteria, and acceptance tests.
Other options are incorrect or misleading:
A is incorrect: reviewing requirements does not eliminate the need for dynamic testing.
C is incorrect: code coverage is more relevant for unit or system-level testing, not acceptance testing.
D is incorrect: exploratory testing is a valuable supplement but does not replace the need to verify acceptance criteria.

質問 # 29
Which of the following pillars of UX requirement analysis is described BEST?

A. During user analysis, business analysts perform interviews to identify the psychological disposition of different users
B. During task analysis, business analysts observe users that work with existing products to determine required ^ functionality
C. During context analysis, security requirement are derived for the external interfaces of the product
D. During competition analysis, products from competitors are exposed to different environmental conditions

正解：B

解説：
User Experience (UX) requirement analysis is a critical component of acceptance testing and product development. According to ISTQB Acceptance Testing syllabus and industry-aligned UX design methodologies (e.g., ISO 9241-210 and BABOK guidelines), UX requirement analysis is typically structured around the following pillars:
User Analysis - Understanding who the users are (roles, goals, experience levels) Task Analysis - Understanding what users do (tasks, workflows, pain points) Context Analysis - Understanding where and how users interact with the product (environmental and contextual factors) Competitor Analysis - Understanding how similar problems are solved in the market Option B best describes Task Analysis, one of the most practical and impactful pillars. In task analysis, business analysts and UX researchers observe how users interact with current or comparable systems to understand workflow patterns, user frustrations, needs, and required system functionality. This method helps uncover implicit needs that users may not articulate in interviews.
This approach is aligned with ISTQB's emphasis on understanding real-world usage and business processes as a foundation for deriving acceptance criteria and tests. It supports the creation of realistic scenarios that reflect actual user behavior, which is essential for verifying system fitness for use.
The other options are inaccurate:
A refers to psychological disposition, which is more aligned with user profiling or persona development, not a core focus of user analysis in requirement engineering.
C incorrectly ties context analysis with deriving security requirements, which is not its purpose.
D describes an unrealistic or incorrect method for competitor analysis.
Therefore, Option B is the best description of a key pillar of UX requirement analysis per industry and ISTQB standards.

質問 # 30
Which of the following techniques is most likely applied to ensure the quality of acceptance testing activities?

A. Eye tracking to verify the feasibility of previously defined user acceptance tests.
B. Verification of the traceability between user stories and test cases to make sure it is up to date.
C. Checklist-based verification of requirements to ensure their completeness and quality.
D. Review of the source code to ensure traceability of user stories to system components.

正解：B

解説：
Ensuring traceability between requirements (user stories) and test cases is a cornerstone of quality assurance in acceptance testing. It confirms that all business needs are covered by corresponding tests and helps assess the impact of changes. Traceability matrices or tools are used to track these links throughout the lifecycle.
Option B is correct because regularly verifying and updating traceability ensures that acceptance test coverage remains aligned with evolving requirements - a best practice in quality assurance.
Other options:
A (review of source code) is a white-box technique, more suitable for unit or integration testing.
C (checklist-based verification of requirements) is useful but focuses on requirement quality, not directly on testing activities.
D (eye tracking) is a usability evaluation technique and not standard for verifying test case feasibility.
B). Verification of the traceability between user stories and test cases to make sure it is up to date.

質問 # 31
Which one of the following statements regarding the quality of requirements is MOST correct?

A. Vague or ambiguous requirements may lead to misunderstandings both during implementation and testing.
B. In Agile development lifecycle models, requirement engineering becomes less important due to the product owner role.
C. INVEST is a technique that ensure the quality of user stories or requirements, thus replacing regular reviews.
D. Testers may complete unclear requirements by assumptions, as long as they discuss those assumptions with at least one stakeholder.

正解：A

解説：
Poorly defined requirements are a leading cause of defects and project failure. According to the ISTQB CTFL Acceptance Testing Syllabus and IQBBA FL Syllabus, the quality of requirements plays a critical role in successful solution development and acceptance testing. Requirements must be clear, unambiguous, complete, and testable. When they are vague or ambiguous, stakeholders may interpret them differently, which can lead to incorrect implementations, inadequate testing, and ultimately rework or rejection during acceptance.
Option A is explicitly supported by the ISTQB Foundation Syllabus and IQBBA principles. In contrast:
Option B is incorrect because Agile lifecycles still place great emphasis on requirement engineering, even though requirements evolve iteratively.
Option C misrepresents INVEST: it is a guideline for writing good user stories but does not replace reviews or validation techniques.
Option D is risky and not endorsed by ISTQB. While testers may identify ambiguities, the correct approach is to clarify them with all relevant stakeholders, not make assumptions.
Exact Reference - ISTQB CTFL Acceptance Testing Syllabus (Section 1.3.1):
"Ambiguous, incomplete, or inconsistent requirements increase the risk of misunderstanding between stakeholders, leading to incorrect implementation and ineffective tests."

質問 # 32
Which TWO of the following statements about exploratory testing are most true?

A. Exploratory testing generally begins with the definition of the test charter that defines the detailed test L-' conditions
B. Exploratory testing is achieved by combining product discovery, test design and execution, and results L- interpretation
C. Exploratory testing is rather carried out by people with a good knowledge of the business domain, bot not necessarily of the tested functionality
D. Exploratory testing implements time-boxed sessions to prioritize tests bases on product risk analysis
E. Exploratory testing is and experience-based test technique which refines acceptance criteria into acceptance test cases

正解：A、B

解説：
Exploratory testing is a dynamic testing technique where learning, test design, execution, and interpretation occur simultaneously. It is especially useful when detailed requirements are unavailable or when testers rely on experience and intuition.
A is correct: Exploratory testing combines exploration, learning about the product, designing and executing tests on the fly, and interpreting the results - all within the same session.
E is also correct: Exploratory testing usually starts with a high-level test charter that defines the mission, objectives, or focus area for the session. It may not define specific test conditions, but it outlines the scope and intent.
Other options:
B: Not accurate - while timeboxing is used, exploratory testing typically relies on charters and experience rather than detailed product risk analysis to prioritize.
C: Incorrect - exploratory testing is not about refining acceptance criteria; that's part of ATDD.
D: Partially true but misleading - good business domain knowledge helps, but understanding the functionality is also important in exploratory testing.

質問 # 33
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 i), iii) and iv)
B. only ii)
C. only ii) and iv)
D. only i) and iii)

正解：A

質問 # 34
Which of the following provides the BEST description of Beta testing?

A. Beta testing aims to obtain feedback from users in their context of use
B. In Agile, beta testing must be performed at the same time as user stories are developed
C. Beta testing is generally performed jointly by testers, business analysts, product owners and developers
D. The effectiveness of beta testing sessions depends on the quality of the test charter

正解：A

解説：
Beta testing is a form of external user acceptance testing where real users test the product in their environment before the official release. It helps identify issues that may not have been caught in internal testing and gather user feedback on functionality, usability, and performance in real-world conditions.
Option C is correct - the core goal of beta testing is to obtain user feedback in their actual usage context, providing insight into how the system performs outside of controlled environments.
Other options:
A: Test charters are used in exploratory testing, not typically in beta testing.
B: Incorrect - beta testing is not tied to the timing of user story development in Agile.
D: Incorrect - beta testing is performed by end users, not by internal team members like developers or business analysts.
C). Beta testing aims to obtain feedback from users in their context of use

質問 # 35
Which of the following statements corresponds BEST to a UX requirement analysis activity?

A. Security requirements are derived from usage scenarios.
B. User profiles are used to determine different levels of business knowledge.
C. Personas are used to analyze products or solutions from competitors.
D. Environmental conditions such as light conditions are obtained from a task analysis.

正解：B

質問 # 36
Given the following attributes:
i.commercializability
ii.functional suitability
iii.viability
iv.reliability
v.security
vi.cognitive ability
vii.maintainability
Which one of the following answers contains quality attributes that are MOST relevant for acceptance testing?

A. ii, v and vi
B. i, ii and vi
C. ii, v and vii
D. iii, iv and v

正解：C

解説：
Acceptance testing primarily focuses on verifying whether a system meets agreed-upon requirements and satisfies the business and user needs. Quality attributes (also known as non-functional requirements) play a vital role in defining the completeness of the acceptance testing process.
Let's analyze the options:
ii. Functional suitability - directly relates to whether the system provides the correct functions as per business needs. Essential in acceptance testing.
v. Security - ensures that the system is protected against unauthorized access or data breaches. Often critical for business stakeholders.
vii. Maintainability - reflects how easily the system can be modified. Relevant in acceptance if maintainability requirements are part of contractual criteria.
Thus, Option B (ii, v, vii) contains three attributes that are very relevant for acceptance testing.
Other options:
A includes vi (cognitive ability), which is not a standard ISO 25010 quality attribute.
C includes i (commercializability) - not a system quality attribute defined in ISO 25010.
D includes iii (viability) - more of a business or market consideration, not system testability.
B). ii, v and vii

質問 # 37
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 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.
B. 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.
C. 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.
D. 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.

正解：B

質問 # 38
Which of the following statements BEST describes the relationship between beta testing and acceptance testing?

A. Beta testing and acceptance testing mean the same, but acceptance testing is the term used in Agile projects
B. Beta testing is a specific from of acceptance testing required for Commercial Off-the-Shelf Software
C. Beta testing and acceptance testing are distinct testing techniques and have nothing to do with each other
D. Beta testing is often used for acceptance testing of Software as a Service (SaaS) platforms

正解：D

解説：
Beta testing is a type of acceptance testing performed by end users in a real-world or production-like environment. It is especially relevant for cloud-based and SaaS platforms where widespread feedback is required before release.
Option B is correct because SaaS platforms often release features to a subset of users (beta users) to test the software under actual operating conditions, get feedback, and fix any defects that were not found during internal testing. This allows vendors to validate functionality, performance, and usability in diverse environments.
Other options:
A: Beta testing is not limited to Commercial Off-the-Shelf (COTS) software.
C: Incorrect - beta testing is a form of acceptance testing, not a separate unrelated technique.
D: Incorrect - beta testing and acceptance testing overlap, but they are not synonyms; the terminology does not change based on the development approach (Agile or not).
B). Beta testing is often used for acceptance testing of Software as a Service (SaaS) platforms

質問 # 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. Depending on the model used to simulate the workload, performance tests are called load, stress or endurance / stability tests.
C. The performance test results serve to determine hardware and software performance requirements.
D. Performance testing aims to determine a system's robustness against malicious attacks.

正解：B

解説：
Performance testing assesses how a system behaves under specific conditions, typically focusing on responsiveness, stability, and resource usage. The type of performance test depends on the workload model:
Load testing evaluates performance under expected peak usage.
Stress testing pushes the system beyond its capacity to assess limits.
Endurance/stability testing checks for performance degradation over extended periods.
Option A correctly describes that performance test types are determined by the workload simulation strategy.
Other options:
B confuses performance with security testing - malicious attack robustness is a security focus, not performance.
C is partly correct but less comprehensive than A. While testing should simulate realistic conditions, categorization into stress/load/endurance is better aligned with workload modeling.
D is misleading - performance tests validate systems against performance requirements; they are not primarily used to define them.
A). Depending on the model used to simulate the workload, performance tests are called load, stress or endurance / stability tests.

質問 # 40
Which one of the following statements describes an exploratory test charter BEST?

A. The test charter is elaborated during the testing session according to test execution results.
B. Indicating that the tester should take the role of a novice user can be part of an exploratory test charter.
C. Each exploratory test charter is based on a previously defined list of activities that would be interesting to test.
D. Acceptance testers use the exploratory test charter during the testing session to define the test oracle.

正解：B

解説：
An exploratory test charter is a high-level plan or mission statement for a time-boxed exploratory testing session. It guides what the tester should focus on during the session and may include the goal of the test, specific areas of the system under test, the risk or feature to explore, the type of persona to simulate (e.g., novice or expert user), and possibly known issues to watch out for.
Option A is correct because specifying a user persona (such as a novice user) helps the tester approach the system from that perspective. This supports the goal of exploratory testing: to simulate realistic usage and uncover issues that scripted tests might miss.
Option B is incorrect - although exploratory testing is adaptive, the charter is defined before the session starts, not elaborated during execution.
Option C is misleading - charters may refer to areas of interest, but not necessarily to a predefined list of activities.
Option D is incorrect - a test oracle (i.e., the mechanism for determining whether a result is correct) is not defined by the charter. It may exist already or be inferred from requirements, heuristics, or user expectations.
Exact Reference - ISTQB CTFL Acceptance Testing Syllabus (Section 3.1):
"Charters define the focus of exploratory testing sessions and may specify the tester's role or perspective (e.
g., novice user)."

質問 # 41
Which one of the following statements regarding the quality of requirements is MOST correct?

A. Vague or ambiguous requirements may lead to misunderstandings both during implementation and testing.
B. In Agile development lifecycle models, requirement engineering becomes less important due to the product owner role.
C. INVEST is a technique that ensure the quality of user stories or requirements, thus replacing regular reviews.
D. Testers may complete unclear requirements by assumptions, as long as they discuss those assumptions with at least one stakeholder.

正解：A

質問 # 42
Which tool is BEST for describing business processes and rules?

A. Test management tool
B. Project management tool
C. Process modelling tool
D. Defect tracking tool

正解：C

解説：
To describe business processes and business rules in a structured, visual, and analyzable way, a process modeling tool is the most appropriate. These tools often support standards like BPMN (Business Process Model and Notation) for process workflows and DMN (Decision Model and Notation) for business rules.
Option D is correct because process modeling tools enable business analysts and stakeholders to capture, analyze, and communicate business operations and decision logic, which are foundational for acceptance test case generation in ATDD.
Other options:
A (Project management tools) manage schedules, resources, and scope, not business rules.
B (Test management tools) handle test cases and execution, not business modeling.
C (Defect tracking tools) track bugs but are not used for describing processes or rules.
D). Process modelling tool

質問 # 43
How are beta testing and acceptance testing related?

A. Beta testing allows the product to be tested in realistic business configurations and contexts.
B. Beta testing is a systematic approach to acceptance testing and provides measurable coverage of the user stories.
C. Beta testing is a synonym for acceptance testing used in specific application domains.
D. Beta testing should include predefined acceptance test scenarios based on acceptance criteria.

正解：A

質問 # 44
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. 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
B. 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
C. 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
D. 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

正解：D

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

質問 # 45
Which one of the following scenarios characterizes UX context analysis BEST?

A. External conditions and psychological conditions are analyzed to derive design decisions
B. User behavior is described using use cases and business process models
C. Users are categorized using personas to describe their physical and intellectual characteristics
D. Attractive solutions from competitors are analyzed to obtain inspirations similar products

正解：A

解説：
UX context analysis evaluates the environment and conditions in which users interact with a product. This includes:
External conditions: lighting, noise, device constraints
Psychological conditions: cognitive load, stress, motivation
These factors influence usability, accessibility, and overall experience.
Option A is correct as it reflects the essence of UX context analysis - understanding the broader user environment to inform design and testing.
Other options:
B describes personas, which are user archetypes used for behavior modeling - more aligned with user profiling.
C focuses on competitor analysis - useful for inspiration, not context analysis.
D involves use cases and workflows - useful for behavior modeling, but not specifically context analysis.
A). External conditions and psychological conditions are analyzed to derive design decisions

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

正解：D

質問 # 47
......

検証済み材料を使うならまずCTFL-AcTテストエンジンを試そう：https://jp.fast2test.com/CTFL-AcT-premium-file.html

合格するに必要な問題集はCTFL-AcT試験：https://drive.google.com/open?id=1p3rqXGRvRxtmvHe5NbuZQQpM_QNPrGqA