[Jan 16, 2026] Get Up-To-Date Real Exam Questions for TM3 with New Materials
Updated TM3 Certification Exam Sample Questions
NEW QUESTION # 31
Factors that are important to take into account when performing test estimation include:
i. The quality of the test basis
ii. The availability of test automation
iii. The amount of rework required
iv. The distribution of testing across several locations
The various factors can be grouped by characteristic. Examples of characteristics include:
- A. Development processWhich factor is related to which characteristic?
- B. A = i, B = ii, C = iii, D = iv
- C. A = ii, B = iii, C = iv, D = i
- D. A = iv, B = iii, C = ii, D = i
- E. Product
- F. A = iv, B = iii, C = i, D = ii
- G. Test results
- H. Test context
Answer: G
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
Product characteristic # quality of the test basis (C = i):The syllabus lists the quality and stability of the requirements/specifications (test basis) as a product-related estimation driver.
Test results characteristic # amount of rework (B = iii):Expected rework/defect-fix cycles and their impact on retesting and confirmation testing are identified through past results/defect patterns and directly affect estimates.
Test context characteristic # distribution across locations (A = iv):Organizational and logistical context (multiple sites, time zones, communication overhead) influences test effort.
Development process characteristic # availability of test automation (D = ii):Process/tooling capability (e.g., presence of automation frameworks) is treated as a development/process factor affecting test efficiency and thus estimation.The syllabus groups estimation drivers into characteristics such as product, development process, test results/history, and test/organizational context, and recommends mapping specific factors to these groups to structure estimation.
NEW QUESTION # 32
Which of the following statements about test management activities for an iterative development model is false?
- A. Roles are integrated; facilitator or coach typically replace the traditional test manager.
- B. Reporting is done at project milestones.
- C. With testware the focus is on acceptance criteria and definition of done. The level of documentation is minimal.
- D. The test approach is embedded within iterations, with a focus on adaptability and feedback.
Answer: B
Explanation:
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.)
NEW QUESTION # 33
Management is sceptical regarding the budget request (€25,000) for the next testing project. You are asked for a cost-benefit calculation. Based on historical data from several projects, you have come up with the following numbers:
Average prevention cost per defect: €200
Average cost of detection per defect: €400
Average cost of internal failure: €150
Average cost of external failure: €2,500
Expected number of defects to be found in this project during testing: 50 What is the result for the expected cost-benefit calculation for the upcoming project?
- A. €87,500
- B. €72,500
- C. €92,500
- D. €62,500
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
Per the syllabus, when building abusiness caseusing thecost of qualitymodel, compare theavoided external failure costswith thesum of relevant pre-release costs(prevention, detection/appraisal, and internal failure). For
50 expected defects found in testing:
Avoided external failure cost= 50 × €2,500 =€125,000
Pre-release costsper defect = €200 (prevention) + €400 (detection) + €150 (internal failure) =€750 Total pre-release costs= 50 × €750 =€37,500 Net benefit (cost-benefit)= €125,000 # €37,500 =€87,500 This computation follows the syllabus' guidance to quantify bothcosts(prevention, detection, internal failure) andbenefits(external failures avoided) to demonstrate the economic value of testing.
NEW QUESTION # 34
Study the following characteristics:
Avoid re-inventing the wheel
Pool on experiences from earlier projects
They prompt thought in areas that are sometimes forgotten
Often used when compliance to specific standards is relevant
To which risk identification technique do these characteristics relate?
- A. Retrospectives
- B. Brainstorming
- C. Risk Workshops
- D. Checklists
Answer: D
Explanation:
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).
Reference: ISTQB CTAL-TM v3.0 Syllabus, Chapter 4 (Risk-Based Testing) - section describingrisk identification techniquesincludingchecklists(purpose, reuse of prior experience, prompting thorough coverage, applicability for standards/compliance).
NEW QUESTION # 35
In an Agile context, defects are often fixed without writing a formal defect report. However, there are some conditions where it is good practice to write a defect report, even in an Agile context.
When is a defect report typically not written in an Agile context?
- A. A defect that must be resolved by or in co-operation with other teams
- B. A defect that is blocking other iteration activities and cannot be immediately solved
- C. A defect that cannot be solved in the same iteration
- D. A defect that is found for a high-priority user story
Answer: D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
Same rationale as Q35. In Agile,no formal defect reportis typically created when the team canfix the issue immediatelyand maintain flow (e.g., defect on a high-priority user story that is quickly addressed). Formal reports are encouraged whenblocking,spanning iterations, orrequiring cross-teamwork for visibility
/traceability. Refer to CTAL-TM v3.0, Chapter 5 on defect management and Agile reporting considerations.
NEW QUESTION # 36
The diagram below shows an incomplete defect management process, where three states (states X, Y and Z) have yet to be named appropriately.
Which of the following labels would correctly complete the process?
- A. X: In Progress, Y: Verified, Z: Terminated.
- B. X: Accepted, Y: Tested, Z: Deferred.
- C. X: Accepted, Y: Reviewed, Z: Duplicate.
- D. X: Approved, Y: Reviewed, Z: Deferred.
Answer: B
Explanation:
According to theISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus (Chapter 2: Test Management in the Organization), thedefect management processdefines how defects are handled from discovery to closure, ensuring traceability and communication between testing and development.
"The defect management process defines the states a defect may have during its lifetime, including identification, evaluation, correction, re-testing (confirmation testing), and closure." (ISTQB CTAL-TM v3.0 Syllabus, Chapter 2 - Defect Management Process) In the standard ISTQB defect workflow:
Afterevaluation, a defect can either be:
Rejected(e.g., not a defect, duplicate, or out of scope), or
Accepted(X) - meaning it is confirmed as a valid defect and will be corrected.
Once accepted, the defect isplannedfor correction andfixedby development.
After being fixed, it must betested (Y)- also referred to asconfirmation testingorretesting.
Some evaluated defects may bedeferred (Z)- postponed for future releases.
Thus, the correct states are:
X = Accepted(defect confirmed as valid and correction planned)
Y = Tested(confirmation testing after the fix)
Z = Deferred(postponed correction)
This sequence aligns directly with the ISTQB-defineddefect management lifecycle, which includes transitions betweenopen,evaluated,accepted (planned/fixed/tested), andclosed, as well as possiblerejectedordeferredbranches.
References (from ISTQB Certified Tester Advanced Level - Test Manager v3.0 Syllabus):
Chapter 2: Test Management in the Organization
Section:Defect Management Process
Describes thedefect states, includingopen, evaluated, accepted, planned, fixed, tested (retested), closed, and alternate states such asrejectedordeferred.
NEW QUESTION # 37
Which of the following characteristics of risk-based techniques is not appropriate to a more heavyweight risk- based technique?
- A. Defined processes and detailed documentation
- B. Risk likelihood and risk impact on an ordinal scale
- C. Mathematical formulas
- D. Broad group of stakeholders
Answer: B
Explanation:
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.
Reference: ISTQB CTAL-TM v3.0 Syllabus, Chapter 4 (Risk-Based Testing) - subsection contrastinglightweight vs. heavyweightrisk-based techniques (qualitative/ordinal vs. quantitative/formal attributes).
NEW QUESTION # 38
Which one of the following metrics is primarily used to measure the achievement of a test objective and reported in a test completion report?
- A. Number of automated test cases versus planned automated test cases
- B. Accumulated number of resolved defects versus accumulated number of defects
- C. Actual versus planned estimation (in hours) for testing activities
- D. Code coverage
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
The syllabus explains thattest objectivesare agreed during planning andachievement against these objectivesis assessed and reported intest completion. A common objective is toautomate a defined proportion of tests; the metric "number of automated test cases versus planned automated test cases" directly measures the degree to which thatobjectivewas achieved and is reported in completion.
A (code coverage)andC (defect trends)are valuable but are not inherently tied to a specificstated objectiveunless such a target was set (e.g., 80% branch coverage).
Bis amonitoringmetric (variance to plan) rather than a direct measure ofobjective achievement.(Reference:
CTAL-TM v3.0 -Test Planning, Monitoring, and ControlandTesting Process (Test Completion): defining measurable test objectives; reporting objective achievement in the test summary/completion report.)
NEW QUESTION # 39
You are a process improver and have decided to use the data from the defect management system to identify and drive improvement actions... Which of the following options could have been identified as missing from the defect reports to be used for process improvement?
- A. The status of the defect
- B. Steps to reproduce the failure, along with the actual and expected results
- C. The priority to fix the problem
- D. The software lifecycle phase in which the defect was detected
Answer: D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
Forprocess improvement and root-cause analysis, the syllabus highlights the value ofdefect origin and detection phase datato evaluatewhere defects are injected and where they are detected, calculate removal effectiveness, and focus improvements (e.g., earlier-phase prevention or reviews). Thelifecycle phase detectedenables meaningful analysis ofphase containment, trends, and improvement targets; the other fields are useful operationally but less pivotal fororganizational/process improvement analytics(Chapter 2: Test Management in the Organization - improvement approaches using defect data; Chapter 5: Reporting and analysis of defect trends).
NEW QUESTION # 40
Which of the following test stakeholders are most likely not involved in defining requirements?
- A. Development Leads
- B. Users
- C. Operations Team
- D. Product Owners
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
The syllabus (Chapter:People Skills - Team Composition) discusses stakeholder roles and collaboration.
Product OwnersandUsersare primary sources forrequirements and acceptance criteria.Development Leadstypically collaborate on clarifying requirements and translating them into technical solutions and testability. By contrast, theOperations Teamis primarily focused ondeployment, support, and operational concerns(e.g., environments, monitoring, reliability in production). While operations may influencenon- functional constraintsor service levels, they arenot typically the primary participants in defining functional requirements, makingOperations Teamthe most likely answer here.
(Reference: CTAL-TM v3.0 Syllabus - Chapter "People Skills - Team Composition", stakeholder roles and collaboration; contrasts in responsibilities across PO/Users/Dev vs. Operations.)
NEW QUESTION # 41
In multi-team environments with hybrid software development approaches, there are various challenges in the context of defect management, such as:
i. Alignment of defect attributes to be used
ii. Prioritisation of defects
iii. Alignment of the approach for defect fixes
Solutions to the above-mentioned challenges include:
- A. Synchronisation between the defect management tools
- B. A = i, B = iii, C = ii
- C. A = i, B = ii, C = iii
- D. The product owner should be involved in the defect management meetings
- E. Transparency of plans by sharing them between teams via dashboardsWhich solution is related to which challenge?
- F. A = i, B = ii, C = i
- G. A = ii, B = i, C = iii
Answer: E
Explanation:
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).
NEW QUESTION # 42
Analytical test improvement approaches identify problems based on data from the project or team.
Appropriate improvements can be derived from an analysis of the identified set of problems.
Which of the following is not an example of an analytical-based test process improvement approach?
- A. Root cause analysis
- B. Quantitative TPI NEXT assessment
- C. Analysis using measures, metrics and indicators
- D. The Goal Question Metric (GQM) approach
Answer: B
NEW QUESTION # 43
You are involved in the selection of a test management tool and have decided to calculate the ROI for the two potential tools: TestMaker and ImproveIT.
TestMaker is priced at €15,000 with yearly maintenance costs of €1,500. Its traceability to requirements feature is strong and the defect management process can easily be customised to meet the needs of the organisation. Effort for test management activities is expected to decrease by 20%.
ImproveIT is priced at €20,000 with yearly maintenance costs of €2,500. Its traceability feature is also strong and has a high level of usability. It also has interesting options for adding extensions to its features in the future. Effort for test management activities is expected to decrease by 30%.
Based on the calculated ROI, which tool would you suggest?
- A. None of the tools, since they do not provide a positive ROI
- B. TestMaker
- C. There is too little information to accurately calculate the ROIs
- D. ImproveIT
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
InTest Tool and Automation, the syllabus states that determining thebusiness case/ROIfor a tool requires identifying and quantifyingall relevant costs(acquisition, maintenance,training,pilot/rollout,integration, customization) andbenefits(e.g.,effort reductionacross activities, quality and cycle-time gains), then comparing them over a defined period within the organization's context. A % effort reduction alone is insufficient without knowing thebaseline effort/cost, number of users, training/transition costs, and implementation scope. Therefore, ROI cannot be accurately computed with the given data.
(Reference: CTAL-TM v3.0 -Test Tool and Automation: tool selection and introduction; establishing a business case/ROI by quantifying costs and benefits; considering acquisition, maintenance, training, pilot, integration, process changes, and productivity gains.)
NEW QUESTION # 44
Which of the following activities in the test process is considered to deliver a document which can be used as a major input for test process improvement?
- A. Test Execution
- B. Test Planning
- C. Test Completion
- D. Test Monitoring
Answer: C
Explanation:
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.)
NEW QUESTION # 45
You have recently been employed as a test manager for a software company producing Human Resource (HR) systems... You have been asked to write a test strategy for the project and have chosen to implement a flexible and change-relatedreactive test strategy.
Which of the following would be an essential part of your test approach?
- A. Using defect-based attacks and exploratory testing
- B. Using decision table testing, equivalence partitioning and boundary value analysis
- C. Implementing ISO/IEC 29119 as a testing framework
- D. Performing a detailed product risk analysis
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
In areactive(change-driven) test strategy-appropriate when requirements are evolving and flexibility is essential-the syllabus highlightsexploratory testinganddefect/experience-based techniques (defect-based attacks)as key elements because they adapt rapidly to change and emerging information.
A(product risk analysis) is central torisk-based/analyticalstrategies.
B(standard-compliant framework) aligns withstandard/process-compliantstrategies.
References: ISTQB CTAL-TM v3.0 Syllabus-Chapter 4 (Approaches for test prioritization and effort allocation: strategy/approach types including reactive strategies; emphasis on exploratory and defect-based approaches under change-driven contexts).
NEW QUESTION # 46
You are a test manager managing a test team and working at a government agency. The test team is responsible for performing the system test. Senior management has been provided with the following test objective for a new project:
"The system should be of high quality."
Using the SMART goal methodology, which of the following statements would be appropriate as a revision to the defined test objective by management?
- A. During component testing a statement coverage of 90% shall be achieved
- B. The number of user issues reported in the first 3 months after going live shall be less than an average of
1 per week - C. At least three weeks of system testing shall be performed and no major defects will be outstanding before going live
- D. All defined requirements shall be implemented and function without problems
Answer: B
Explanation:
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.
References: ISTQB CTAL-TM v3.0 Syllabus-Chapter 3 (Test Planning: defining measurable test objectives and SMART criteria; aligning objectives to levels and stakeholders).
NEW QUESTION # 47
Management is sceptical regarding the budget request (€25,000) for the next testing project. You are asked for a cost-benefit calculation. Based on historical data from several projects, you have the following numbers:
Average prevention cost per defect: €200
Average cost of detection per defect: €400
Average cost of internal failure: €150
Average cost of external failure: €2,500
Expected number of defects to be found in this project during testing: 50 What is the result for the expected cost-benefit calculation for the upcoming project?
- A. €87,500
- B. €72,500
- C. €92,500
- D. €62,500
Answer: A
Explanation:
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).
NEW QUESTION # 48
Three exit criteria have been defined for a project:
- A. Number of outstanding defects is less than 5
- B. Number of defects per test case is less than 0.5 The first week of the testing has shown the following results (Mon-Fri):Defects Found = 21 (3+4+2+5+7)Defects Fixed = 8 (0+2+2+3+1)Tests Run = 43 (10+3+20+5+5)Tests Passed = 24 (5+3+15+0+1)
- C. Criteria A = OK, criteria B = NOT OK, criteria C = NOT OK
- D. Criteria A = NOT OK, criteria B = NOT OK, criteria C = NOT OK
- E. Test cases passed is more than 70%
- F. Criteria A = OK, criteria B = OK, criteria C = OK
- G. Criteria A = NOT OK, criteria B = NOT OK, criteria C = OK
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
Pass rate = 24/43 = 55.8% #less than 70%#A =NOT OK.
Outstanding defects = 21 # 8 =13#not less than 5#B =NOT OK.
Defects per test case = 21/43 #0.49#less than 0.5#C =OK.The syllabus (Test Monitoring and Reporting) specifies using quantitative measures such as pass/fail rates, defect status (open vs. fixed), and defect detection metrics against exit criteria to evaluate test completion and readiness for release. These measures are used to decide whether exit criteria are met and to trigger control actions where they are not.
NEW QUESTION # 49
Assume you are a test manager of a project that develops software in the medical domain. You are responsible for analysing the organisational test strategy and the project context to choose the appropriate test approach.
You consider the following factors:
Detailed requirements of high quality are available
Parts of the software to be developed are expected to be safety critical Internal audits and an external audit by a government agency are expected to take place, as such traceability and evidence are important elements for the test approach A release date has been defined, and a marketing campaign has already been scheduled The project works according to the sequential V-model lifecycle The independent test team has a lot of domain knowledge but has also been trained and has experience in using test design techniques Which of the following test approaches would be most appropriate for this project?
- A. Experience-based testing, e.g., exploratory testing, to make maximum use of the domain knowledge of the testers
- B. Define acceptance criteria for each of the requirements and implement definition-of-done criteria to drive testing
- C. Use Acceptance Test-Driven Development (ATDD) as a way to implement shift-left, and use test automation in addition to enhance product quality
- D. Risk-based testing to identify the most critical features and use a methodical approach to testing, e.g., more formal test design techniques to drive testing and ensure traceability
Answer: D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
In regulated, safety-critical domains with audits and strong traceability requirements, the syllabus emphasizes defining amethodical, documented test approachwithin test planning, includingselection of formal test design techniquesandrisk-based testingto focus effort on the most critical features. These elements are explicitly tied toV-modelcontexts, where traceability from requirements through test conditions and cases is expected, and evidence is essential for internal and external audits (CTAL-TM v3.0 Syllabus - Chapter 3, Test Planning; and Chapter 4, Risk-Based Testing and effort allocation).
Option B aligns with these needs: applyingrisk-based testingto prioritize safety-critical functions and usingformal techniquesto producetraceable, auditabletest assets.
Options A and D are practices typically associated with agile/ATDD and "definition of done," which do not best fit asequential V-modelcontext. Option C (experience-based) may complement but isinsufficientas the primary approach wheretraceability and auditabilityare key.
(References: CTAL-TM v3.0 Syllabus - Chapter 3 "Test Planning, Monitoring, and Control" - defining the test approach and selecting test design techniques; Chapter 4 "Risk-Based Testing and Other Approaches for Test Prioritization and Effort Allocation" - prioritizing safety-critical areas; material on traceability/audit expectations in regulated contexts.)
NEW QUESTION # 50
A company that sells an established capture-replay execution tool is adding a test management tool. Same team, same technology, incremental development (V-model per increment), known first-year features; later features driven by customer demand.
Which two of the following factors are most likely to influence the estimation technique that would be selected in this scenario?
- A. Expert availability
- B. Time constraints
- C. Knowledge in modelling
- D. Data availability
- E. Estimation error
Answer: A,D
Explanation:
According to theISTQB Certified Tester Advanced Level - Test Manager v3.0 Syllabus (Chapter 3: Test Planning, Monitoring, and Control), the choice oftest estimation techniquedepends on several influencing factors, including data availability, expert availability, and knowledge of historical information or models.
"The selection of a suitable estimation approach (metrics-based or expert-based) depends on factors such as the availability of relevant historical data, the availability of experts with appropriate experience, the time available to perform estimation, and the knowledge of applicable models." (ISTQB CTAL-TM v3.0 Syllabus, Chapter 3 - Test Planning, Section: Test Estimation) Analysis for this scenario:
* The organization isadding a test management toolto anexisting productusing thesame team and technology- implyingavailability of previous project datafrom similar development work.#Data availability(B) is a significant factor, enabling the use ofmetrics-based estimation.
* Thesame experienced teamis working on the project, meaningdomain and technical expertsare available.#Expert availability(C) also influences estimation and may support anexpert-based estimationapproach for new, customer-driven increments.
Therefore, the combination ofdata availability (B)andexpert availability (C)most strongly influences the estimation technique to be applied in this scenario.
Why the Other Options Are Incorrect:
* A. Estimation error- This is a result of estimation, not a factor influencing the choice of estimation technique.
* D. Knowledge in modelling- While useful, modelling is not central to this specific context because data and experts are readily available.
* E. Time constraints- Not highlighted as a limiting factor in this scenario; estimation can be planned adequately given the context.
References (from ISTQB Certified Tester Advanced Level - Test Manager v3.0 Syllabus):
* Chapter 3: Test Planning, Monitoring, and Control
* Section:Test Estimation
* Lists influencing factors for selecting estimation techniques:availability of historical data, expert knowledge, applicable models, and time available for estimation.
NEW QUESTION # 51
Which status would typically be assigned to a false-positive defect report during defect management?
- A. Resolved
- B. Accepted
- C. Deferred
- D. Rejected
Answer: D
Explanation:
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).
NEW QUESTION # 52
......
TM3 Study Guide Cover to Cover as Literally: https://www.actual4cert.com/TM3-real-questions.html
Get Unlimited Access to TM3 Certification Exam Cert Guide: https://drive.google.com/open?id=180ReoUNm_uaH_NFQoICZRiyhTvUYouTH