BCS TM3 ISTQB Certified Tester Advanced Level - Test Management v3.0 Exam Practice Test

Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level – Test Manager v3.0 syllabus:

The syllabus requires that test objectives beSMART:Specific, Measurable, Achievable, Relevant, and Time-bound. OptionCis specific (“user issues”), measurable (“< 1 per week”), achievable (depending on context), relevant to system quality in production, and time-bound (“first 3 months after going live”).

Ais not measurable (“…without problems” is vague).

Bis partially SMART but uses ambiguous terms (“major defects”) and focuses on elapsed time rather than quality outcomes.

Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level – Test Manager v3.0 syllabus:

The syllabus distinguisheslightweightandheavyweightrisk-based approaches. Lightweight approaches typically usequalitativeassessments withordinalscales for likelihood and impact (e.g., Low/Medium/High). Heavyweight approaches aremore formal and quantitative, may involvemathematical models,detailed documentation, anddefined processes, and can still involve a broad stakeholder set (e.g., via structured workshops), but theydo not rely on simple ordinal scalesas their main analysis device. Therefore, usingordinal scales(B) is characteristic oflightweight, not heavyweight.

Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level – Test Manager v3.0 syllabus:

WithinTest Planning(Chapter:Test Planning, Monitoring, and Control), the syllabus describes that the test manager defines the test approach fornon-functional quality characteristics(e.g., performance, load, scalability, reliability). For these, the test manager oftensets or references benchmarks/baselines and success criteria(e.g., response-time thresholds, throughput targets) to evaluate system behavior under specified conditions. Establishing and usingbenchmarksis a hallmark ofnon-functional testing, particularlyperformance testing.

(Reference: CTAL-TM v3.0 Syllabus — Chapter “Test Planning, Monitoring, and Control”, subsections on defining the test approach for non-functional testing and specifying success criteria/benchmarks.)

Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level – Test Manager v3.0 syllabus:

In the CTAL-TM v3.0 syllabus (Chapter on Risk-Based Testing), checklists are described as a reusable aid for identifying risks based on prior knowledge and experience. They help ensure important areas are not overlooked and are frequently used in contexts where compliance with standards is required. These characteristics match the question’s bullets exactly (re-use/experience, prompting memory of commonly missed areas, and standards alignment).

Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level – Test Manager v3.0 syllabus:

The syllabus describesratio-based estimation(e.g., estimating test effort as a proportion of known or estimated development effort) as appropriate when reliable development-effort data or estimates and clear scope are available. Here, detailed specifications exist, overall development effort is estimated, and increments are defined—conditions well-suited to ratio-based estimation.

Extrapolationrequires comparable historical test data for this context.

Wide-band Delphiis useful when data is scarce and expert consensus is needed.

Planning pokeris typically used by Agile development teams to size user stories, not for contracting UAT with a third party.

===========

Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level – Test Manager v3.0 syllabus:

The syllabus lists multiple competence development approaches (training/education, coaching/mentoring, on-the-job learning, peer learning, andself-study) and explicitly characterizesself-studyas learning through materials such as books and recorded content. This aligns directly with the scenario of “reading books and watching recorded videos,” which isself-study(CTAL-TM v3.0, People Skills – competence development options).

Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level – Test Manager v3.0 syllabus:

The syllabus differentiatescost of qualityinto:

Prevention(to avoid defects),

Appraisal(to evaluate products, e.g., reviews, testing),

Internal failure(defectsfound before release, including the cost to fix during testing), and

External failure(defects foundafter release).“Fixing a defect found during testing” is aninternal failure cost, because the failure is detected and corrected prior to delivery (CTAL-TM v3.0, Organizational Test Management – economics of testing and cost of quality categories).

Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level – Test Manager v3.0 syllabus:

Using thecost of qualityperspective in the syllabus, compute the savings from moving defects fromexternal failuretointernal discovery(prevention + appraisal + internal failure).

Internal discovery cost per defect:€200 + €400 + €150 = €750.

External failure cost per defect:€2,500.

Net saving per defect moved inside:€2,500 − €750 = €1,750.

For50defects:€1,750 × 50 = €87,500→Answer: €87,500.The syllabus directs test managers to articulate testing’s value by quantifyingavoided external failure costsagainstprevention, detection, and internal failure costs, supporting investment decisions and demonstrating ROI for testing initiatives (Chapter: Test Management in the Organization – economics/cost of quality; business case and benefit evaluation).

The syllabus explicitly states thatexit criteriamust be met before considering completion of a test level:

“Exit criteria are the conditions that must be achieved to declare completion of a given test level… including coverage criteria and status of required tests (e.g., passed).”

— ISTQB CTAL-TM v3.0 Syllabus, Chapter 5Test Monitoring and Test Control

And test control must act when exit criteria are not met:

“If the exit criteria are not satisfied, appropriate actions must be taken to address the situation.”

— ISTQB CTAL-TM v3.0 Syllabus, Chapter 5

Sincetest condition 2 still has critical tests not yet executed, thedefined exit criteria are not fulfilled, and therefore a release decision should not be approved.

Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level – Test Manager v3.0 syllabus:

In the ISTQB CTAL-TM v3.0 syllabus (Chapter:Testing Process, section onTest Completion), the Test Completion activity includes producing thetest summary report, capturinglessons learned, and finalizing/archiving testware. Thetest summary report and lessons learned are specifically identified as key inputs to test process improvement, enabling organizations to refine their approach, improve efficiency, and address gaps revealed during the test effort. This makesTest Completionthe activity that delivers the document(s) most directly used for ongoingtest process improvement.

(Reference: CTAL-TM v3.0 Syllabus — Chapter “Testing Process”, subsection “Test Completion”: responsibilities include creating the test summary report, collecting lessons learned, and providing input to process improvement.)

Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level – Test Manager v3.0 syllabus:

ii. Prioritisation of defects → A. Product owner involvement: The PO (or equivalent business authority) ensuresbusiness-value/risk-based prioritizationis consistent across teams.

i. Alignment of defect attributes → B. Tool synchronization: Toalign fields/attributes/statuses, teams synchronize or harmonize defect management tools and schemas.

iii. Alignment of approach for fixes → C. Transparent shared dashboards:Shared plans/dashboardssupport coordination onhow/whenfixes are implemented across teams, improving consistency and visibility.This mapping reflects the syllabus coverage oforganization-level test management, multi-team governance, tool alignment, and cross-team transparency practices in hybrid/Agile environments (CTAL-TM v3.0, Chapter 2: Test Management in the Organization; Chapter 5: defect management coordination and reporting).

Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level – Test Manager v3.0 syllabus:

The syllabus highlightscontinuous improvementpractices, includingretrospectivesin Agile lifecycles, encouragingcollaborative techniquessuch asbrainstormingto generateconcrete improvement ideas, often followingroot cause analysisof issues.

Effective retrospectives should involve thewhole team and relevant stakeholders, generatespecific actions(anaction plan), and recognize that some actions may requiresupport beyond the team.

Therefore,Cis a good practice.Ais incorrect (retrospectives should be cross-functional),Bis too narrow (some actions require organizational support), andDis incorrect (capturing concrete actions is recommended even in Agile contexts).

(References: CTAL-TM v3.0 Syllabus — Chapter 1 “Testing Process” – lessons learned and process improvement; Agile lifecycle considerations for retrospectives and collaborative improvement techniques; emphasis on actionable outcomes.)

Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level – Test Manager v3.0 syllabus:

Afalse-positivedefect is one where the reported behavior isnot actually a defect(e.g., intended behavior, misuse, environment/setup issue). In defect management, the appropriate disposition for “not a defect” is torejectthe report rather than accept, resolve, or defer it.

Rejected: used when the item is not a defect (e.g., “as designed,” duplicate, or cannot be reproduced).

Accepted/Resolved: used when confirmed and fixed.

Deferred: used when confirmed, but the fix is postponed to a later release.This aligns with the syllabus content ondefect lifecycle states and dispositionswithin defect management governance and reporting (CTAL-TM v3.0, Chapter 5: Test Monitoring, Test Control, and Test Reporting — defect management process, defect states, and reporting).

===========

Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level – Test Manager v3.0 syllabus:

The syllabus advises thatrisk mitigationincludes allocatingstronger capability and more efforttohigh-riskareas (e.g., by assigningmore experienced testersand more intensive testing to those features). In alow-maturity (TMMi level 1)context withnovice testers not yet trained, immediately deployingexperienced testersto high-risk items is the most practical and effective step to achievedeeper, more reliable testing.

Option B would be beneficial, but without formal training yet, immediate effectiveness is uncertain.

Option C is a longer-term improvement initiative, not a direct immediate mitigation for the current project risks.

Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level – Test Manager v3.0 syllabus:

In iterative/Agile contexts (Chapter:Test Management in the Organization), the syllabus emphasizes:

A: Testware tends to be lean; focus is onacceptance criteriaand theDefinition of Done; documentation is oftenminimalbut sufficient.

B: Thetest approach is integrated within iterations, emphasizingadaptability,continuous feedback, and close collaboration.

D: Traditional, centralized “test manager” roles are oftenevolved or distributed; responsibilities may be shared across the team, with afacilitator/coach (e.g., Scrum Master/Agile coach)supporting quality practices.

Cisfalsebecause in iterative modelsreporting is continuous and occurs every iteration (e.g., sprint reviews, daily information radiators), not only at traditionalproject milestonestypical of sequential models.(Reference: CTAL-TM v3.0 Syllabus — Chapter “Test Management in the Organization”, sections on Agile/iterative test management, roles, minimal documentation, and iterative reporting.)