CTFL-AcT Exam Dumps : ISTQB Certified Tester - Acceptance Testing (CT-AcT)

Security requirements specify how a system should handle access control, data protection, confidentiality, integrity, and authentication. In acceptance testing, validating that users cannot access data or functions they are not authorized for is a critical test objective when dealing with security.

Option D is correct because it directly relates to access control — a fundamental aspect of security. Ensuring that “normal users shall have restricted access to private data” reflects both a security requirement and a condition that must be tested for compliance.

Other options:

A relates to performance (response time).

B refers to architecture or platform (web-based system).

C is about UI design and usability (style compliance).

Only D addresses security specifically.

Answer: D. Normal users shall have restricted access to private data.

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.

Answer: B. Development of acceptance criteria for user stories

Beta testing is a type of external user acceptance testing performed by potential or existing customers in a real-world environment. It typically occurs after internal validation and acceptance tests have been passed. The purpose is to validate the product in realistic contexts, identify usability issues, uncover defects that may have been missed in lab settings, and gather feedback for improvements.

Option C is correct because it best describes the intent and value of beta testing — to observe how the product performs in real-life configurations, which may include varying hardware, usage patterns, or business workflows.

Option A is incorrect — while some people use the terms loosely, beta testing is not a strict synonym for acceptance testing. Acceptance testing usually refers to more formal, criteria-driven testing (e.g., alpha or internal acceptance testing), while beta testing emphasizes broad, usage-based validation.

Option B is misleading — beta testers may follow scenarios, but beta testing is not typically based on predefined acceptance criteria alone. It emphasizes exploration in realistic use cases.

Option D is false — beta testing is not primarily about measuring test coverage. It is qualitative and feedback-driven rather than systematically structured.

Exact Reference – ISTQB CTFL Acceptance Testing Syllabus (Section 3.2):

“Beta testing is performed by users in their own environment and supports validation of the system in realistic operational conditions.”