[Jun 07, 2026] Get New CTFL-AcT Certification – Valid Exam Dumps Questions [Q28-Q46]

Share

[Jun 07, 2026] Get New CTFL-AcT Certification – Valid Exam Dumps Questions

100% Passing Guarantee - Brilliant CTFL-AcT Exam Questions PDF


If you are a software tester looking to specialize in acceptance testing and want to prove your expertise in the field, the CTFL-AcT or ISTQB Foundation Level - Acceptance Testing Certification exam is the right certification for you. This internationally recognized qualification is an essential addition to your resume, as it demonstrates your skills and knowledge in the industry's best practices. Be sure to prepare adequately for the exam and earn your CTFL-AcT certification today.


ISQI CTFL-AcT exam covers a wide range of topics related to acceptance testing. It includes topics such as the principles of acceptance testing, the testing process, test design techniques, and defect management. CTFL-AcT exam also includes questions on the different types of acceptance testing, such as user acceptance testing and business acceptance testing. Candidates are required to have a good understanding of these topics to pass the exam.

 

NEW QUESTION # 28
As an acceptance tester, you are stuck between two stakeholders that demand contradicting acceptance criteria Which one of the following actions is MOST promising to resolve the conflict?

  • A. Together with the business analyst, you determine which stakeholders is more important to decide between them
  • B. After having collected the pros and cons of each solutions, you base your decision on those objective criteria
  • C. You organize a meeting of the two stakeholders so that they can solve the conflict personally
  • D. Instead of discussing conflicting technical solutions, you try to understand the underlying business needs

Answer: D

Explanation:
When stakeholders provide conflicting acceptance criteria, resolving the conflict effectively requires focusing on the underlying business goals rather than getting stuck in technical or solution-level disagreements.
Option D is correct because it aligns with the core role of a business analyst and an acceptance tester: to understand and validate business needs. By exploring the root business objectives, you can help stakeholders reframe the problem and reach a compromise based on what delivers the most value.
Other options:
A may lead to confrontation and unproductive discussion without proper facilitation.
B is risky - prioritizing stakeholders may escalate conflict or appear biased.
C assumes you can objectively resolve the conflict based only on pros and cons, but without understanding the business context, the decision may not meet stakeholder needs.
D). Instead of discussing conflicting technical solutions, you try to understand the underlying business needs


NEW QUESTION # 29
Suppose you are testing a new professional exam support system. As input the system takes two grades from two exams. For each exam the possible grade is 0 or 1 point. As output the system returns a single string - the decision about the entitlements: if the total score is 2, the candidate receives full entitlements. If the total score is 1, she receives partial entitlements. If the total score is 0, the candidate fails and receives no entitlements.
Which of the following is the correct Decision Model and Notation (DMN) model for this situation?

  • A. Option D
  • B. Option B
  • C. Option A
  • D. Option C

Answer: A

Explanation:
Decision Model and Notation (DMN) is a standardized approach used to model decision logic, often represented in decision tables that evaluate inputs and determine outputs. In this scenario, the entitlements granted to a candidate are based on the total score from two exams, where:
Each exam can be graded as either 0 or 1.
The combined score can be 0, 1, or 2.
The entitlements depend on the combined result:
0 # No entitlements
1 # Partial entitlements
2 # Full entitlements
Among the given diagrams:
Option A simply lists test cases but lacks explicit logic modeling.
Option B shows a mapping from total score to entitlements but doesn't model how the total is derived from the two exams.
Option C redundantly splits outputs into multiple Boolean fields and doesn't reflect how the decision is made from exam inputs.
Option D is the correct representation.
Option D uses:
e1 and e2 as inputs for Exam #1 and Exam #2.
Result as the sum of e1 + e2.
A final Output mapped based on the Result:
0 # No
1 # Partial
2 # Full
This structure accurately follows the DMN standard by expressing inputs, a derived result, and the corresponding decision output, making Option D the correct and most complete decision model.
Exact Reference - ISTQB CTFL Acceptance Testing Syllabus (Section 2.3):
"Decision tables are commonly used to express business rules that determine outputs based on combinations of inputs. DMN formalizes this structure to support automated reasoning."


NEW QUESTION # 30
How does ISTQB CTFL test activities relate to the IQBBA FL business analysis and requirements engineering activities?

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

Answer: D


NEW QUESTION # 31
Which one of the following test design techniques fits accepting testing purposes BEST?

  • A. defect-based test design
  • B. static code analysis
  • C. input validation
  • D. equivalence partitioning

Answer: D

Explanation:
Equivalence Partitioning (EP) is a black-box test design technique that divides input data into valid and invalid partitions, where each partition is expected to exhibit similar behavior. In the context of acceptance testing, EP is especially effective because it helps validate whether a system behaves correctly for representative input ranges defined in the acceptance criteria.
Acceptance testing aims to confirm that the system meets business requirements and handles inputs as expected. EP allows the tester to cover a large input space using fewer test cases while maintaining a high level of effectiveness. It supports efficiency, broad coverage, and relevance to user expectations.
Other options are less suitable:
A). Static code analysis is a white-box technique, more relevant to unit or integration testing.
B). Input validation is an objective or activity, not a test design technique.
D). Defect-based testing is more diagnostic, used after failures or during exploratory testing - less structured for planned acceptance testing.
Exact Reference - ISTQB CTFL Acceptance Testing Syllabus (Section 2.4):
"Black-box techniques such as equivalence partitioning and boundary value analysis are suitable for deriving acceptance tests from user stories or business rules."


NEW QUESTION # 32
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 ii) and iv)
  • C. only i), iii) and iv)
  • D. only i) and iii)

Answer: C


NEW QUESTION # 33
Which one of the following statements regarding ATDD / BDD is true?

  • A. In both Acceptance-Test Driven Development (ATD and Behavior-Driven Development (BD, acceptance test cases are written by a test automation engineer as test automation code.
  • B. In both Acceptance-Test Driven Development (ATDD. and Behavior-Driven Development (BDD., test cases provide examples of product use.
  • C. In Acceptance-Test Driven Development (ATDD., test cases are written prior to the acceptance criteria.
  • D. Behavior-Driven Development (BDD. considers acceptance test design as an activity to be handled by the test team after requirements have been finalized.

Answer: B


NEW QUESTION # 34
Which one of the following answers lists characteristic of quality in use according to the quality in use model defined in ISO 25010?

  • A. Freedom of interference
  • B. Satisfaction
  • C. User experience
  • D. Security

Answer: B

Explanation:
According to ISO/IEC 25010:2011, the "Quality in Use" model includes characteristics that measure the system's impact on stakeholders during actual usage in a specific context.
The four main characteristics of Quality in Use are:
Effectiveness
Efficiency
Satisfaction
Freedom from Risk
Option C is correct because "Satisfaction" is one of the core quality-in-use characteristics and refers to the degree to which user needs are fulfilled in context.
Other options:
A (User experience) is a broader term not formally defined as a Quality in Use characteristic in ISO 25010.
B (Security) is part of the product quality model, not quality in use.
D (Freedom of interference) is not a defined term in ISO 25010; it may be a misstatement of "freedom from risk."


NEW QUESTION # 35
Which tool is BEST for describing business processes and rules?

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

Answer: A

Explanation:
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


NEW QUESTION # 36
Which one of the following statements describes the relation between business goals, business needs and requirements BEST?

  • A. To derive the business needs, the business analyst first has to understand the business goals and requirements.
  • B. Business goals and business needs are synonyms.
  • C. Business goals, business needs and requirements describe at different levels of abstraction, what shall be achieved.
  • D. Business needs address the business solution whereas business requirements define the business problem or opportunity.

Answer: C

Explanation:
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."


NEW QUESTION # 37
Which of the following is the BEST example of a Gherkin-style test for a web-based banking application?

  • A. GIVEN I have $5000 on my personal account X AND I have $200 on my personal account Y WHEN I transfer $1000 from X to Y THEN I should have balance $4000 on my personal account X AND I should have balance $1200 on my personal account Y
  • B. GIVEN I have $5000 on my personal account X AND I have $200 on my personal account Y WHEN I click 'Make transfer' button AND I enter '3000' into 'Amount' field AND I enter 'X' into 'From which account' field AND I enter 'Y' into 'To which account' field AND I click 'Confirm transaction' button THEN I should have balance $2000 on my personal account X AND I should have balance $3200 on my personal account Y
  • C. GIVEN I have $5000 on my personal account X and $600 on my personal account Y WHEN I transfer
    $500 from Y to X
    THEN I should have balance $4500 on X and balance $1100 on Y
  • D. GIVEN I have $5000 on my personal account X WHEN I have $600 on my personal account Y THEN I have $5600 in total on my personal accounts X and Y

Answer: A

Explanation:
The best Gherkin-style acceptance tests are business-oriented, behavior-driven, and avoid unnecessary technical or UI details. They describe actions in a way stakeholders can understand, focusing on system behavior rather than implementation mechanics.
Option A follows Gherkin conventions:
GIVEN clearly describes the system state (account balances).
WHEN describes a user action (transferring funds).
THEN describes a verifiable outcome (account balances updated correctly).
Option B includes unnecessary UI actions like clicking buttons or field names, which are implementation- specific and violate the abstraction level expected of acceptance tests.
Option C uses appropriate structure but introduces incorrect balances in the THEN step (possibly a typo;
$4500 on X is wrong if funds were transferred from Y to X).
Option D uses improper syntax - WHEN is misused as another GIVEN, and THEN describes a computation rather than a system behavior.
Exact Reference - ISTQB CTFL Acceptance Testing Syllabus (Section 2.2.2):
"Acceptance criteria in BDD are best captured through Gherkin scenarios that are understandable by business stakeholders and focus on expected outcomes, not implementation details."


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

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

Answer: B

Explanation:
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


NEW QUESTION # 39
Which one of the following statements BEST explains how the quality of requirements / user stories and acceptance criteria affects acceptance testing?

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

Answer: D

Explanation:
Clear, complete, and testable requirements or user stories are critical for effective acceptance testing.
Ambiguities or vague statements lead to differing interpretations by stakeholders, developers, and testers. This often results in software that doesn't meet user expectations or in tests that fail to verify business needs correctly.
Option B is correct because it highlights the importance of precise requirements in both implementation and testing phases. Ambiguities can result in incorrect behavior, untestable features, or test cases that don't align with business goals.
Other options:
A is risky - while testers may explore assumptions during exploratory testing, relying on assumptions rather than clarification increases risk.
C is incorrect - the INVEST mnemonic helps write better user stories, but it doesn't replace review or validation processes.
D is false - Agile still values requirements engineering; it's more collaborative and incremental, with the product owner playing a key role, not diminishing its importance.
B). Vague or ambiguous requirements may lead to misunderstandings both during implementationand testing


NEW QUESTION # 40
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 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. 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 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.

Answer: C


NEW QUESTION # 41
Which of the following provides the BEST description of Beta testing?

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

Answer: B

Explanation:
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


NEW QUESTION # 42
Which one of the following test design techniques fits accepting testing purposes BEST?

  • A. defect-based test design
  • B. static code analysis
  • C. input validation
  • D. equivalence partitioning

Answer: D


NEW QUESTION # 43
As an acceptance tester you want to test the $100 withdrawal process described by the following BPMN model.

You would like to achieve decision coverage. Consider the following test cases: Test 1: balance = $100, receipt = YES Test 2: balance = $99 Test 3: balance = $120, receipt = NO Test 4: balance = $2500, receipt = YES Which of the following is the minimal set of test cases allowing to achieve full decision coverage?

  • A. Test 2, Test 3
  • B. Test 1, Test 2, Test 4
  • C. Test 1, Test 2, Test 3
  • D. Test 1, Test 2

Answer: C


NEW QUESTION # 44
Which of the following techniques is most likely applied to ensure the quality of acceptance testing activities?

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

Answer: C

Explanation:
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.


NEW QUESTION # 45
Which of the following statements corresponds BEST to a UX requirement analysis activity?

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

Answer: B


NEW QUESTION # 46
......


ISQI CTFL-AcT (ISTQB Foundation Level - Acceptance Testing) Certification Exam is a widely recognized certification exam in the field of software testing. CTFL-AcT exam is designed to test the knowledge and skills of individuals in the area of acceptance testing, which is a critical component of software development. ISTQB Foundation Level - Acceptance Testing certification is granted by the International Software Testing Qualifications Board (ISTQB), which is a global organization that promotes best practices in software testing.

 

Free CTFL-AcT braindumps download: https://torrentlabs.itexamsimulator.com/CTFL-AcT-brain-dumps.html