The correct answer is C . CTAL-TA v4.0 describes a session-based exploratory test charter as a focused mission, commonly structured as Explore [target] With [resources] To discover [information] . The charter should focus the tester's limited exploratory effort on the highest-value area, using suitable resources and a clear discovery objective. The syllabus includes test charters supporting session-based testing under test analysis and design.
Here, the relevant new functionality is Requirement 3 , especially the entry of complex forecasting parameters through a browser-based front end. The Merchandising Manager's explicit concern is usability , not functional correctness of the existing actual sales reports and not performance. The scenario also states that entry of forecasting parameters and report requests will be low volume , which weakens performance as the initial exploratory objective.
Option A targets report request entry, but the problem statement says the complexity and concern are around forecasting parameters , not the act of requesting a report. Option B targets Requirement 2, the existing actual sales report production, rather than the new Requirement 3 functionality. Option D uses the right target but the wrong objective: performance is not the main stated risk for this initial exploratory session. Reference:
CTAL-TA v4.0, Section 3.4.1 Test Charters Supporting Session-Based Testing and Section 4.2 Usability Testing .

The correct answer is B . In CTAL-TA v4.0 decision table testing, the checksum procedure is used to detect structural problems in a minimized decision table. A rule without any "-" condition represents one full-table combination. Each "-" multiplies that rule's checksum by the number of possible values for that condition. If the minimized-table checksum is higher than the original-table checksum, some rules overlap or additional rules exist; if it is lower, the table is incomplete; if equal, the minimization may be structurally correct.
The original full table has 3 loyalty tiers × 2 luxury-room values × 2 breakfast values = 12 feasible combinations . The minimized rules score as follows: Rule 1 G/Y/- = 2 , Rule 2 G/N/- = 2 , Rule 3 S/Y/- = 2
, Rule 4 S/-/- = 4 , Rule 5 B/-/Y = 2 , Rule 6 B/-/N = 2 . Total checksum = 2 + 2 + 2 + 4 + 2 + 2 = 14 . Since
14 > 12 , the minimized table cannot be structurally clean. The overlap is visible: Rule 3 covers Silver + Luxury + either breakfast value , while Rule 4 covers Silver + any room type + any breakfast value , so the Silver/Luxury combinations are covered twice. Option C is wrong because all condition values are represented. Option D alone is weaker than B , because the actual symptom here is overlap. Reference: CTAL- TA v4.0, Section 3.3.1 Decision Table Testing .

The correct answer is B , but the question is slightly under-specified as written. CTAL-TA v4.0 defines a metamorphic relation as a property that describes how a change in test input is reflected in the expected result.
It is used to create follow-up test cases from a source test case and then evaluate the source and follow-up results jointly.
For the trapezium formula, if b changes while a and h remain unchanged, the area must change, not the height. Therefore, options C and D are structurally wrong because changing an input side length does not imply a change in h . Option A is also weak because it mixes an absolute increase in b with a fixed percentage increase in area, without considering the original values of a , b , and h . Option B is the only option that correctly expresses the expected-result relationship: a percentage increase in b causes a predictable percentage increase in area . Strictly, the exact percentage depends on the contribution of b to a + b ; the shown 2/3 relation is valid when b / (a + b) = 2/3 . Reference: CTAL-TA v4.0, Section 3.3.2 Metamorphic Testing .

The correct answer is D . The diagram contains an internal inconsistency that can be identified directly from the model, without waiting for test design or execution. The activity diagram shows Receive details , then splits into parallel activities: Confirm receipt and Validate details . The validation path then branches into
[Valid] Accept details and [Invalid] Reject details . However, after either acceptance or rejection, the flow rejoins and continues to Confirm acceptance of details . That means the model allows rejected details to proceed into an activity that confirms acceptance, which is logically inconsistent.
CTAL-TA v4.0 states that scenario-based testing uses workflow models such as activity diagrams, use cases, flowcharts, BPMN diagrams, sequence diagrams, and collaboration diagrams to derive scenarios through the test item. The syllabus also emphasizes that modeling and test analysis can reveal defects in the test basis, including workflow-related defects, before dynamic test execution begins.
Option A is wrong because the inconsistency is visible statically; test execution is not needed to confirm it.
Option B is also wrong because formal test cases are not required before recognizing the contradiction.
Option C is dangerous and incorrect: stakeholder approval does not prove technical or logical correctness.
The issue is a structural workflow defect in the model itself. Reference: CTAL-TA v4.0, Scenario-Based Testing and Test Analysis of the Test Basis .
For the first process, when 'Something is needed', which option contains the MOST appropriate keywords for action and verification?
Required Goods / Check PR
Enter Required Goods I Check PR Created
Enter Details of Required Goods / Is PR Created?
Required Goods Entry I PR Creation Check

The correct answer is D . Once test cases have been written during test design, the Test Analyst should ensure their quality before considering the design activity complete. CTAL-TA v4.0 states that test design is typically performed using test cases, and during test design the TA designs test cases according to defined quality criteria. It also emphasizes that test cases have a communicative role and should be understandable to relevant stakeholders, including other testers, developers, and auditors.
A stakeholder review is the best next step because it checks whether the test cases are correct, feasible, necessary, understandable, traceable, precise, complete, and concise. CTAL-TA specifically says test cases may be reviewed, modified, and executed by people other than the author, and that the TA should write them in a format understandable to all involved stakeholders.
Option A belongs mainly to test implementation , where test procedures are organized and execution-order dependencies are identified. Option B should have been decided earlier during test design, before or while writing the cases. Option C is also implementation-oriented because suggesting test cases for automation is listed under test implementation. Reference: CTAL-TA v4.0, Sections 1.2.2 Test Design , 1.2.3 Test Implementation , and 1.3.2 Quality Criteria for Test Cases .