ISTQB ISTQB-AL-TA Free Practice Questions — Page 2

Correct Answer: B. Creating a test execution schedule, including resource allocation.

Creating a test execution schedule including resource allocation is a Test Manager responsibility, not the Test Analyst's. This activity belongs to Test Planning, which is managed at a managerial level. The Test Analyst's implementation responsibilities include: updating traceability between the test basis and testware (A), creating or identifying tests for automation (C), and reporting defects based on observed failures (D). Option D may seem like an execution activity, but defect reporting is also part of implementation when failures are found during test script preparation or dry runs. The key distinction is that scheduling and resource allocation require management authority and project-level visibility that sit outside the Test Analyst's role.

Correct Answer: C. R03.

To determine which risk to address first, we must evaluate two factors: the Risk Level (calculated by Impact and Likelihood) and the Scope of the current iterations (Iterations 1 and 2). Risk Analysis Breakdown R03 (The Winner): This risk has a High Impact and Medium Likelihood. More importantly, it is directly relevant to the current scope. Iteration 1 focuses on iOS and Iteration 2 focuses on Android. Since R03 specifically addresses installation issues on these devices, it is the highest priority risk that falls within the Test Analyst's responsibility for the specified timeframe. R02: While this has the highest overall risk rating (High Impact / High Likelihood), it is associated with "daily budget usage based on seasonal historic data." According to the project plan, this feature isn't delivered until Iteration 3. Therefore, it is out of scope for the current task. R01: This risk (Accessibility) has a Medium Impact and Low Likelihood, giving it a lower overall risk priority compared to R03. R04: This is a Project Risk (related to time and resources), not a Product Risk (related to the software's quality or function). Test Analysts primarily design test conditions for product risks; managing testing time is typically a Test Management concern.

Correct Answer: C. Test generation, test definition, test execution, test adaptation

The generic Test Automation Architecture (gTAA) defines four horizontal layers, each with a distinct responsibility: Test Generation — creates test cases (manually or automatically) from the test basis or models. Test Definition — specifies test data, expected results, and test scripts in a structured form. Test Execution — runs the automated tests and captures results. Test Adaptation — provides the interface between the automation framework and the System Under Test (SUT), handling protocol/technology differences. Option A is incorrect — "test APIs" is a vertical concern, not a layer. Option B replaces "test generation" with "test APIs," which is wrong. Option D replaces "test generation" with "test reporting," which is also not a gTAA horizontal layer. Reporting is a support function, not a defined layer.

Correct Answer: A. £748, £749, £750, £751.

According to ISTQB standards, 2-point Boundary Value Analysis (BVA) requires testing the boundary value itself and its closest neighbor in the adjacent partition. In this scenario, the commission bandings are determined by specific price points: the change introduces a new boundary between £749 and £750 (transitioning from 5.5% to 4.5%) and preserves or clarifies the existing boundaries at £499/£500 (6% to 5.5%) and £999/£1000 (4.5% to 3.5%). Option C is correct because it identifies the two values for every transition point affected by the change: the values just below and exactly at/above the limit (499/500, 749/750, and 999/1000).

Correct Answer: A. All layers are used, but the test generation layer will be automated based on the defined model.

In model-based testing (MBT), test cases are automatically generated from a model (e.g., finite state machine, decision table). This automates the test generation layer, but all other gTAA layers remain necessary. The test definition layer still structures the generated tests. The test execution layer still runs them against the SUT. The test adaptation layer still bridges the framework to the SUT's interfaces. Option B is wrong — the execution layer is always needed; without it, tests cannot run. Option C is wrong — adaptation is driven by SUT technology, not by the model. Option D is wrong — API test design is part of the adaptation layer and is still required regardless of the modeling approach.