I85PREP
⌘ K
ISTQB CTAL-TM study materials
ISTQB CTAL-TM study resources

ISTQB CTAL-TM practice questions

One question at a time. Build your ISTQB CTAL-TM understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Test Management in Context: Organizational Test Strategy and Test Approach

In ISTQB terms, what distinguishes an organizational test strategy from a test approach used on a single project?

  1. The organizational test strategy lists individual test cases, while the test approach lists only test environments
  2. The organizational test strategy describes generic testing requirements across the organization, while the test approach is the project-specific implementation of selected elements for a given project Correct answer.
  3. The organizational test strategy is written by the test manager for one release, while the test approach is a permanent corporate standard
  4. The organizational test strategy is optional documentation, while the test approach is mandatory for every test level

Explanation

The organizational test strategy is a generic, organization-wide document that provides the common frame for testing. A project then selects and tailors relevant parts into a project-specific test approach, adding project details such as levels, techniques and environments.

Question 2Test Management in Context: Organizational Test Strategy and Test Approach

Which content is most characteristic of an organizational test strategy rather than of a project test approach?

  1. The names of the testers assigned to the current release
  2. The entry and exit criteria for the current system test phase
  3. Organization-wide test process, generic test levels, and standard test tools and templates Correct answer.
  4. The estimation of effort for the next sprint's regression testing

Explanation

An organizational test strategy captures reusable, organization-wide elements such as the generic test process, standard test levels, and common tools and templates. Project-specific estimates, named resources and phase criteria belong to the project test approach.

Question 3Test Management in Context: Organizational Test Strategy and Test Approach

A test manager is deriving a project test approach from the organizational test strategy. Which activity best matches that derivation?

  1. Discarding the organizational test strategy because every project is unique
  2. Copying the organizational test strategy unchanged into the project test plan
  3. Selecting applicable elements of the organizational test strategy and adding project-specific details such as test levels, techniques and environments Correct answer.
  4. Rewriting the organizational test strategy so that it matches the project's schedule

Explanation

Deriving the test approach means tailoring: the project selects the relevant parts of the generic organizational strategy and supplements them with project-specific decisions. The organizational strategy itself remains organization-wide and is not rewritten per project.

Question 4Test Management in Context: Organizational Test Strategy and Test Approach

Which factor most strongly justifies tailoring the organizational test strategy for a project that is developing safety-critical embedded software?

  1. The product's risk profile and regulatory context demand more rigorous, documented and independent testing than the generic strategy assumes Correct answer.
  2. The organization has recently changed its holiday calendar
  3. The project uses a different word-processing template for its test plan
  4. The project manager prefers weekly rather than daily status meetings

Explanation

Tailoring is driven by project context, and risk and regulatory obligations are among the strongest context factors. Safety-critical embedded work typically needs more formal, independent and documented testing than a generic strategy describes.

Question 5Test Management in Context: Organizational Test Strategy and Test Approach

Which pair correctly matches a typical input to the organizational test strategy with a typical input to a project test approach?

  1. Organizational strategy: the current sprint backlog; project approach: the corporate quality policy
  2. Organizational strategy: the project's test environment inventory; project approach: enterprise architecture principles
  3. Organizational strategy: industry standards and organizational policies; project approach: product risk analysis and project scope Correct answer.
  4. Organizational strategy: the release schedule; project approach: the organization's generic test process

Explanation

The organizational strategy draws on durable, organization-wide inputs such as standards and policies. The project approach draws on project-specific inputs such as product risk analysis, scope and constraints.

Question 6Test Management in Context: Organizational Test Strategy and Test Approach

What is the primary business benefit of maintaining an organizational test strategy instead of letting every project invent its own testing approach?

  1. It guarantees that no defects will escape to production
  2. It removes the need for any project-level test planning
  3. It eliminates the need for test estimation on individual projects
  4. It provides consistency, reuse of proven practices and a common reference for compliance and improvement across projects Correct answer.

Explanation

An organizational test strategy gives consistency and reuse of proven practices, and supplies a common reference against which projects can be assessed and improved. It does not remove the need for project planning or guarantee defect-free delivery.

Question 7Test Management in Context: Organizational Test Strategy and Test Approach

A test manager must decide how much of the organizational test strategy to apply to a small, low-risk internal tool. Which approach best reflects sound test management judgment?

  1. Apply a proportionately reduced set of the organizational elements, documenting the rationale for the reduction based on risk Correct answer.
  2. Apply the full organizational test strategy without change because consistency always outweighs risk
  3. Defer the decision until after the tool has been released to users
  4. Abandon all organizational practices because the tool is small

Explanation

Tailoring should be proportionate to risk and context, and the reasoning for what was reduced should be recorded. This keeps the benefits of organizational consistency while avoiding disproportionate effort on a low-risk item.

Question 8Test Management in Context: Organizational Test Strategy and Test Approach

Which statement best describes how an organizational test strategy relates to test levels?

  1. It forbids projects from defining any test levels of their own
  2. It may describe generic test levels and their typical objectives, which projects then refine for their own life cycle Correct answer.
  3. It specifies the exact number of test cases to be executed at each level
  4. It defines only the acceptance test level because that is the business-facing level

Explanation

The organizational test strategy commonly describes generic test levels and their objectives as a reusable frame. Projects then refine, combine or rename levels to fit their life cycle and context.

Question 9Test Management in Context: Organizational Test Strategy and Test Approach

An organization operates in a regulated domain and also runs several fast-moving digital projects. How should the organizational test strategy accommodate both?

  1. Mandate the most rigorous documented process for every project regardless of domain
  2. Provide a common core of mandatory practices plus optional tailorable elements that projects select according to risk and context Correct answer.
  3. Restrict the strategy to tool selection so that process decisions stay entirely local
  4. Require every project to define its own strategy from scratch with no organizational input

Explanation

A strategy serving diverse contexts works best as a common mandatory core plus optional elements that projects tailor. This preserves compliance where required while allowing lighter practice where risk is lower.

Question 10Test Management in Context: Organizational Test Strategy and Test Approach

Which item is a test approach decision rather than an organizational test strategy statement?

  1. The organization's standard test documentation templates
  2. The choice of risk-based technique weighting and the test environment sequence for this particular product release Correct answer.
  3. The organization's policy on independence of testing
  4. The organization's standard defect classification scheme

Explanation

Choosing technique weighting and environment sequencing for a specific release is a project-level test approach decision. Standard schemes, policies and templates are organization-wide assets that belong to the organizational test strategy.

Question 11Test Management in Context: Organizational Test Strategy and Test Approach

What does 'test policy' typically mean in relation to the organizational test strategy?

  1. The set of automated test scripts maintained by the team
  2. A list of the individual testers authorized to execute test cases
  3. A high-level statement of the organization's testing principles and objectives that the test strategy elaborates Correct answer.
  4. The schedule of test execution for a single project

Explanation

A test policy expresses the organization's high-level testing principles and objectives. The organizational test strategy then elaborates how those principles are realized in practice.

Question 12Test Management in Context: Organizational Test Strategy and Test Approach

A project's context differs from the assumptions in the organizational test strategy: it uses an iterative life cycle with continuous delivery. What is the most appropriate response when deriving the test approach?

  1. Keep the strategy's sequential phase gates unchanged because the organizational strategy is binding in all details
  2. Wait for the organization to rewrite its strategy before planning any testing
  3. Skip testing entirely until a final release phase because iterative delivery makes testing impractical
  4. Adapt the generic elements, for example by distributing test activities across iterations and emphasizing automation and regression, and record the deviations Correct answer.

Explanation

Deriving the approach includes adapting generic organizational elements to the project's life cycle and recording where and why the project departs from them. Iterative delivery calls for distributing activities and strengthening automation and regression.

Question 13Test Management in Context: Organizational Test Strategy and Test Approach

Which statement about the level of detail in an organizational test strategy is most accurate?

  1. It should contain every project's detailed test cases so that nothing is left to projects
  2. It should be so abstract that no concrete guidance can be derived from it
  3. It should be detailed enough to guide projects while remaining generic enough to apply across the organization Correct answer.
  4. It should be rewritten by each project to reflect that project's specifics

Explanation

The organizational strategy must be concrete enough to guide projects yet generic enough to be reused across them. Excessive detail turns it into a project plan, while excessive abstraction makes it useless.

Question 14Test Management in Context: Organizational Test Strategy and Test Approach

Which element of a test approach is most directly influenced by the product's identified risks?

  1. The depth, technique selection and prioritization of testing for the product Correct answer.
  2. The choice of office location for the test team
  3. The version control system used for source code
  4. The organization's corporate logo on test reports

Explanation

Risk analysis drives how deeply and with which techniques a product is tested, and in what order. The test approach should reflect that risk-based prioritization explicitly.

Question 15Test Management in Context: Organizational Test Strategy and Test Approach

A test manager is reviewing whether the project test approach is complete. Which question best tests alignment with the organizational test strategy?

  1. Does the approach avoid mentioning the organizational test strategy at all?
  2. Does the approach reuse the applicable organizational elements and clearly justify any deviations from them? Correct answer.
  3. Does the approach name every employee in the testing department?
  4. Does the approach contain more pages than the organizational test strategy?

Explanation

Alignment is shown by reusing applicable organizational elements and explaining any deliberate deviations. Document length or omitting the organizational reference are not indicators of alignment.

Question 16Test Management in Context: Organizational Test Strategy and Test Approach

Which of the following best illustrates an organization-wide test process element that a project would adopt rather than invent?

  1. The floor plan of the test laboratory
  2. The personal calendar of the test lead
  3. The agreed workflow for reporting, triaging and tracking defects across the organization Correct answer.
  4. The specific defect counts observed in last month's release

Explanation

A defect management workflow is a reusable process asset defined organization-wide and adopted by projects. Observed defect counts, personal calendars and floor plans are not process elements.

Question 17Test Management in Context: Organizational Test Strategy and Test Approach

An organization's test strategy mandates a specific commercial test management tool, but a project's context makes a different tool far more suitable. What is the most professional course of action?

  1. Use the mandated tool regardless and accept the inefficiency without comment
  2. Secretly use the preferred tool and report using the mandated one
  3. Analyze and document the context-based justification for a deviation, and raise it for approval through the appropriate governance channel Correct answer.
  4. Cancel the project until the organizational strategy is changed

Explanation

Tailoring includes justified, documented and approved deviations from organizational standards. This preserves governance while allowing the project to respond to its context.

Question 18Test Management in Context: Organizational Test Strategy and Test Approach

Which statement correctly describes the relationship between the organizational test strategy and test metrics?

  1. The strategy must contain the exact metric values expected from each project
  2. Metrics are entirely unrelated to the organizational test strategy
  3. The strategy may define standard metrics and reporting conventions that projects then apply and interpret in their own context Correct answer.
  4. Projects may never define any metric beyond those in the organizational strategy

Explanation

Organizational strategies commonly define standard metrics and reporting conventions to enable comparability. Projects apply these and may add context-specific measures where needed.

Question 19Test Management in Context: Organizational Test Strategy and Test Approach

A test manager is choosing the test approach for a product with a mature, stable architecture and a history of few defects. Which approach is most consistent with sound tailoring?

  1. Apply the most exhaustive technique set available regardless of risk
  2. Copy the approach used by an unrelated high-risk project without modification
  3. Eliminate regression testing because the architecture is stable
  4. Proportionally reduce test depth in low-risk areas while retaining targeted regression and monitoring for change Correct answer.

Explanation

Tailoring should be proportionate to risk, so low-risk stable areas can receive less depth while targeted regression and monitoring guard against change. This balances economy with adequate coverage.

Question 20Test Management in Context: Organizational Test Strategy and Test Approach

Which statement about who owns the organizational test strategy is most accurate?

  1. It is owned by the customer and cannot be changed once approved
  2. It is owned by the development team and excludes test specialists
  3. It is typically owned at organizational or programme level by test management and is maintained as a living reference Correct answer.
  4. It is owned by a single tester on one project and applies only to that project

Explanation

The organizational test strategy is an organization-level asset maintained by test management and kept current. It is a living reference rather than a one-project or immutable document.

Question 21Test Management in Context: Organizational Test Strategy and Test Approach

An organization wants its test strategy to support continuous improvement. Which characteristic is most important?

  1. Removing all references to past project experience
  2. Including a defined mechanism for reviewing lessons learned and updating the strategy periodically Correct answer.
  3. Freezing the strategy permanently so that it never changes
  4. Restricting strategy review to a single person with no project input

Explanation

Continuous improvement requires a defined review cycle that feeds lessons learned from projects back into the strategy. A permanently frozen or single-owner document cannot adapt to new evidence.

Question 22Test Management in Context: Organizational Test Strategy and Test Approach

Which situation most clearly indicates that a project has failed to derive a proper test approach from the organizational test strategy?

  1. The project copied the organizational strategy verbatim and performed no analysis of its own risks, levels or environments Correct answer.
  2. The project documented which organizational elements it adopted and which it tailored
  3. The project consulted the organizational strategy and adapted its test levels to an iterative life cycle
  4. The project used organizational templates and added project-specific risk analysis

Explanation

A verbatim copy with no project-specific analysis is not a derived test approach; it omits tailoring to the project's risks, levels and environments. Documented adoption and adaptation indicate proper derivation.

Question 23Test Management in Context: Organizational Test Strategy and Test Approach

Which factor is least relevant when deciding how closely a project should follow the organizational test strategy?

  1. The color scheme used in the organization's presentation slides Correct answer.
  2. Contractual or regulatory obligations applicable to the product
  3. The life cycle model and delivery cadence of the project
  4. The risk level and criticality of the product

Explanation

Tailoring decisions rest on substantive factors such as risk, obligations and life cycle. Presentation styling has no bearing on how testing should be conducted.

Question 24Test Management in Context: Organizational Test Strategy and Test Approach

A programme comprises several projects sharing a common platform. What is the most effective way to use the organizational test strategy across them?

  1. Establish a common programme-level approach derived from the organizational strategy, then let each project tailor it further for its own scope Correct answer.
  2. Let each project choose randomly from the organizational elements
  3. Apply only the organizational strategy and forbid any project-level tailoring
  4. Have each project define completely independent strategies with no shared elements

Explanation

A programme-level approach derived from the organizational strategy gives shared consistency across related projects, while each project still tailors for its own scope. This layers tailoring rather than duplicating or ignoring it.

Question 25Test Management in Context: Organizational Test Strategy and Test Approach

Which statement best captures why the organizational test strategy should be independent of any single project's schedule?

  1. Because it is intended to remain a durable reference that outlives individual projects and guides many of them Correct answer.
  2. Because schedules are never relevant to testing
  3. Because the strategy is written only after all projects have finished
  4. Because projects are not allowed to have schedules

Explanation

The organizational strategy is a durable, reusable reference that should outlast individual projects. Tying it to one project's schedule would make it project-specific and reduce its long-term value.

Question 26Test Management in Context: Organizational Test Strategy and Test Approach

An organizational test strategy describes reusable test process assets, while a project test approach describes how testing will be performed on one product. Which pair best matches the two levels?

  1. The strategy records this project's incident log; the approach defines the organization's long-term quality goals.
  2. The strategy defines organization-wide conventions such as defect classification rules; the approach selects which test levels and techniques this project will use. Correct answer.
  3. The strategy defines the project's release date; the approach defines the organization's annual budget.
  4. The strategy lists the individual testers assigned to each sprint; the approach records their daily progress.

Explanation

The organizational test strategy establishes durable, reusable assets and conventions that many projects draw on, such as defect classification schemes or standard test processes. A project test approach is the tailored instance: it selects levels, techniques, environments and exit criteria for one product's context. Mixing staffing or scheduling detail into the strategy would make it project-specific and short-lived.

Question 27Test Management in Context: Organizational Test Strategy and Test Approach

Which characteristic of an organizational test strategy most directly enables projects to tailor it without losing organizational consistency?

  1. It fixes a single test approach for every product regardless of context.
  2. It is kept confidential from project managers.
  3. It is written exclusively by external consultants.
  4. It states mandatory rules together with guidance on where documented tailoring is permitted. Correct answer.

Explanation

A usable strategy separates what must be followed organization-wide from what may be adapted, and it describes how deviations are agreed and recorded. That gives projects room to respond to context while keeping alignment auditable. A single fixed approach or hidden rules removes that flexibility.

Question 28Test Management in Context: Organizational Test Strategy and Test Approach

An organization's test policy states that all safety-critical products must undergo independent verification. Which statement correctly places this rule within the strategy hierarchy?

  1. It is a project test approach decision because it affects one product.
  2. It is a defect management metric used to compare suppliers.
  3. It is a test execution schedule entry owned by the test analyst.
  4. It is an organizational test strategy constraint derived from test policy, which projects then implement in their test approaches. Correct answer.

Explanation

Test policy expresses high-level organizational intent, and the organizational test strategy translates that intent into directives such as mandatory independent verification for safety-critical work. Individual projects then reflect the directive concretely in their own test approach. Treating it as a schedule entry or metric confuses the levels.

Question 29Test Management in Context: Organizational Test Strategy and Test Approach

A test manager is documenting the test approach for a new product. Which content belongs in the test approach rather than in the organizational test strategy?

  1. The decision to use exploratory sessions at system level because requirements are still emerging. Correct answer.
  2. The organization's standard definition of severity levels.
  3. The organization's standard template for a test plan.
  4. The organization-wide requirement that all testware be peer reviewed.

Explanation

Selecting exploratory sessions at a specific level is a context-driven decision about how this product will be tested, so it belongs in the project test approach. Severity definitions, review mandates and templates are reusable organizational assets that projects adopt. The approach should explain why the choice suits the product's situation.

Question 30Test Management in Context: Organizational Test Strategy and Test Approach

Two projects share the same organizational test strategy, yet one plans four test levels and the other plans two. Which explanation is most consistent with sound test management?

  1. Each project's test approach legitimately adapts level selection to its life cycle, risk and size within the strategy's constraints. Correct answer.
  2. The project with two levels is non-compliant by definition.
  3. The strategy is defective because it should force identical level counts.
  4. Test levels are always dictated by the number of available testers.

Explanation

The organizational test strategy sets constraints and conventions, while level selection is a test approach decision that depends on life cycle, risk profile and scale. Two projects can therefore differ legitimately without breaching the strategy. Uniform level counts would ignore context and are not a sign of compliance.

Question 31Test Management in Context: Organizational Test Strategy and Test Approach

Which organizational factor most strongly shapes the content of an organizational test strategy for a company entering a heavily regulated market?

  1. The applicable regulatory standards and the evidence they require. Correct answer.
  2. The average age of the development team.
  3. The preferred colour scheme of test reports.
  4. The number of coffee machines per test floor.

Explanation

Regulatory standards impose mandatory practices and evidence, such as traceability and independent review, which the strategy must encode so projects comply consistently. The other items are irrelevant to testing obligations. This is why context analysis precedes strategy definition.

Question 32Test Management in Context: Organizational Test Strategy and Test Approach

A test manager inherits a strategy that mandates a heavyweight, document-driven approach. The new product is a mobile app released weekly. What is the most appropriate action?

  1. Propose a documented tailoring that keeps the strategy's mandatory controls while replacing document-heavy steps with lightweight, automated evidence. Correct answer.
  2. Delay the product until the organizational strategy is rewritten.
  3. Abandon the organizational strategy entirely for this product.
  4. Apply the heavyweight approach unchanged to preserve consistency.

Explanation

Sound tailoring preserves mandatory organizational controls, such as traceability or review of critical testware, while adapting the means of achieving them to the project's cadence. Documented tailoring keeps the deviation transparent and reviewable. Neither blind compliance nor wholesale abandonment respects both consistency and context.

Question 33Test Management in Context: Organizational Test Strategy and Test Approach

Which statement best explains why an organizational test strategy should be reviewed periodically rather than treated as fixed?

  1. Projects are required to change their approaches whenever a document ages.
  2. Reviewing documents is a mandatory ritual in every quality standard.
  3. Frequent revision guarantees fewer defects in released products.
  4. Organizational context, technology and risk profiles change, so the strategy must stay relevant to the projects it serves. Correct answer.

Explanation

A strategy is only useful if it reflects the organization's current technology, risk exposure and business context. Periodic review keeps it aligned with those changes and prevents projects from inheriting obsolete constraints. Revision alone does not guarantee quality outcomes; it maintains relevance.

Question 34Test Management in Context: Organizational Test Strategy and Test Approach

An organization wants its test strategy to support measurement and comparison across projects. Which strategy content contributes most directly to that goal?

  1. A list of preferred office locations for test teams.
  2. A rule that metrics are collected only when a defect escapes.
  3. A common set of test metrics with agreed definitions and collection points. Correct answer.
  4. A statement that each project may invent its own metric definitions.

Explanation

Comparability across projects requires shared metric definitions, consistent units and defined collection points, which the organizational strategy can standardize. Without agreed definitions, numbers from different projects cannot be aggregated or compared meaningfully. Project-invented definitions defeat the purpose.

Question 35Test Management in Context: Organizational Test Strategy and Test Approach

A test manager must justify why a project's test approach departs from the organizational test strategy in one area. Which justification is strongest?

  1. The project team prefers working in a different way.
  2. The product's architecture and risk profile make the prescribed technique ineffective, and an alternative provides equivalent or better coverage. Correct answer.
  3. The departure reduces the number of test cases executed.
  4. The departure shortens the test manager's reporting effort.

Explanation

A defensible deviation rests on evidence about the product's context and on an alternative that preserves or improves coverage and control. Personal preference, case counts or reporting convenience do not demonstrate that assurance is maintained. Documenting the rationale makes the deviation auditable.

Question 36Test Management in Context: Organizational Test Strategy and Test Approach

Which activity best demonstrates that a project has genuinely aligned its test approach with the organizational test strategy?

  1. Sending the strategy to all stakeholders by email.
  2. Mapping each strategy directive to a concrete project decision and recording any approved deviations. Correct answer.
  3. Copying the strategy document into the project repository without change.
  4. Mentioning the strategy in the project's kick-off slides.

Explanation

Alignment is demonstrated by traceable mapping from organizational directives to project decisions, including documented and approved deviations. Copying, mentioning or distributing the document shows awareness but not that the approach actually reflects it. The mapping also supports later audits and improvement.

Question 37Test Management in Context: Organizational Test Strategy and Test Approach

An organization operates both long-lived legacy systems and short-cycle innovation projects. Which organizational test strategy structure is most appropriate?

  1. No organizational strategy, leaving every project to decide alone.
  2. A strategy written only for the legacy systems, since they carry most risk.
  3. A core of mandatory organization-wide elements plus defined profiles for different project types. Correct answer.
  4. A single prescriptive process with no exceptions.

Explanation

A core-plus-profiles structure keeps essential controls universal while giving distinct project types a pre-agreed, consistent way to adapt. This avoids both rigid uniformity and fragmentation into unrelated local practices. Profiles are documented so tailoring remains transparent.

Question 38Test Management in Context: Organizational Test Strategy and Test Approach

Which statement about the relationship between an organizational test strategy and test estimation is most accurate?

  1. The strategy supplies standard estimation assumptions and historical data that projects use as a starting point. Correct answer.
  2. Only the finance department may use strategy data for estimation.
  3. Estimation is unrelated to the organizational strategy.
  4. The strategy fixes the exact effort for every project.

Explanation

Organizational strategy content such as standard assumptions, productivity data and historical metrics gives projects a defensible baseline for estimation. Projects then adjust for their own context. Fixing exact effort centrally would ignore project differences, and claiming no relationship discards valuable data.

Question 39Test Management in Context: Organizational Test Strategy and Test Approach

A test manager finds that the organizational test strategy contains detailed test case designs for one legacy product. What is the most likely consequence for the strategy's effectiveness?

  1. It has no effect on projects using other technologies.
  2. It automatically satisfies regulatory requirements for all products.
  3. It makes the strategy harder to apply broadly and risks becoming obsolete as that product changes. Correct answer.
  4. It strengthens the strategy because more detail is always better.

Explanation

Embedding product-specific designs turns a reusable organizational asset into a snapshot tied to one system, reducing its applicability elsewhere and dating it quickly. Strategy content should stay at a level that remains valid across projects. Product-specific designs belong in project testware.

Question 40Test Management in Context: Organizational Test Strategy and Test Approach

Which element of an organizational test strategy most directly supports consistent tool adoption across projects?

  1. A statement that tools are chosen informally by each tester.
  2. A list of past project managers.
  3. A defined tooling policy covering approved tools, evaluation criteria and support responsibilities. Correct answer.
  4. A description of the organization's brand guidelines.

Explanation

A tooling policy sets approved tools, criteria for evaluating new ones and who supports them, which yields consistent adoption and reduces duplicated evaluation effort. Informal per-tester choices produce fragmentation and support gaps. Brand guidelines and personnel lists do not govern tool selection.

Question 41Building the Test Team and Testing Competencies

In the ISTQB test manager role, which activity is the primary responsibility of the test manager rather than the individual test analyst?

  1. Selecting the test approach and estimating overall test effort for the project Correct answer.
  2. Reporting individual defects found during test execution
  3. Executing exploratory sessions on a single feature
  4. Designing detailed test cases from a given specification

Explanation

The test manager owns planning-level decisions such as test approach selection, effort estimation, and resource allocation across the project. Analysts typically handle detailed test design, while execution and defect reporting sit with testers.

Question 42Building the Test Team and Testing Competencies

A test manager needs a team member who can independently decide which test techniques to apply and coach others on test design. Which skill set best matches this need?

  1. Network administration skills combined with hardware procurement
  2. Project budgeting skills combined with contract negotiation
  3. Advanced test analysis skills combined with mentoring ability Correct answer.
  4. Basic defect logging skills combined with tool administration

Explanation

Choosing techniques independently and coaching others reflects advanced analytical competence plus the ability to develop colleagues. This is a higher-level test competency than routine execution or administrative support.

Question 43Building the Test Team and Testing Competencies

Which statement best describes the purpose of a test team skills matrix maintained by the test manager?

  1. It documents the tool licences allocated to each tester
  2. It tracks the defect density of each module under test
  3. It records each member's proficiency per skill to guide assignment and training Correct answer.
  4. It lists the test cases each member has executed in the current cycle

Explanation

A skills matrix maps individuals against required competencies and proficiency levels, supporting task assignment and targeted development. It is a people-focused planning instrument, not a record of execution or defect metrics.

Question 44Building the Test Team and Testing Competencies

A test manager is forming a new team and wants to balance technical testing skills with domain knowledge. What is the most appropriate first step?

  1. Hire the cheapest available testers to stay within budget
  2. Delay competency planning until the first test cycle begins
  3. Assign all testing to developers to reduce headcount
  4. Identify the required competencies from the test strategy and product risks Correct answer.

Explanation

Team composition should be driven by the competencies the strategy and product risks demand, so the manager first derives required skills. Only then can gaps be filled through recruitment, training, or reassignment.

Question 45Building the Test Team and Testing Competencies

Which pairing best reflects the distinction between testing skills and testing knowledge in a competency framework?

  1. Knowledge is certification; skill is years of experience
  2. Knowledge is defect count; skill is test case count
  3. Knowledge is tool usage; skill is reading specifications
  4. Knowledge is what a tester understands; skill is the ability to apply it effectively Correct answer.

Explanation

In competency models, knowledge refers to understanding concepts and standards, while skill is the demonstrated ability to apply that understanding to real tasks. Certification and experience are evidence, not the definitions themselves.

Question 46Building the Test Team and Testing Competencies

During a project, the test manager notices that team members avoid raising risks early. Which action most directly develops the team's testing competency in this area?

  1. Provide training and coaching on risk identification and encourage open escalation Correct answer.
  2. Reassign risk analysis to the project manager permanently
  3. Increase the number of test cases each tester must execute daily
  4. Add a penalty for any risk raised after the test cycle starts

Explanation

Building competency in risk awareness requires developing the skill through training and coaching plus an environment that rewards early escalation. Penalising late risk reports or shifting ownership away from the team suppresses the behaviour.

Question 47Building the Test Team and Testing Competencies

A test manager must assign testers to a safety-critical payment module. Which assignment approach best reflects competency-based staffing?

  1. Rotate testers randomly to spread experience evenly
  2. Assign the newest testers so they gain experience quickly
  3. Assign based on who has the most free calendar time
  4. Assign testers with proven domain and analytical skills for critical risk areas Correct answer.

Explanation

Competency-based staffing matches the risk level and complexity of the work to demonstrated skills, placing stronger analytical and domain competence on critical areas. Random or availability-driven assignment ignores the risk profile.

Question 48Building the Test Team and Testing Competencies

Which situation is the clearest indicator that a test team needs additional training in test design techniques?

  1. Testers document their test environment setup accurately
  2. Testers repeatedly produce similar test cases and miss boundary conditions Correct answer.
  3. Testers complete assigned test execution on schedule
  4. Testers submit defect reports with clear reproduction steps

Explanation

Repetitive tests that miss boundary conditions signal weak application of design techniques such as equivalence partitioning and boundary value analysis. Clear defect reports, on-time execution, and accurate documentation indicate adequate competence.

Question 49Building the Test Team and Testing Competencies

A test manager introduces pair testing so experienced testers work alongside newcomers. What is the main competency benefit of this approach?

  1. It guarantees that defect counts will increase in the short term
  2. It removes the need for any formal test documentation
  3. It allows the manager to reduce the team size immediately
  4. It transfers tacit testing skills through observation and immediate feedback Correct answer.

Explanation

Pair testing is a knowledge-transfer mechanism where newcomers acquire tacit skills by observing and getting feedback from experienced colleagues. It is a development technique, not a guarantee of metric improvement or a reason to drop documentation.

Question 50Building the Test Team and Testing Competencies

According to the TMMi or general test process improvement thinking, why should competency development be aligned with the test process maturity level?

  1. Competency development is irrelevant once processes are documented
  2. Higher maturity processes demand more analytical and technical skills from the team Correct answer.
  3. Maturity assessment replaces the need for a skills matrix
  4. Maturity levels only concern tooling and never affect people skills

Explanation

As test processes mature toward risk-based, analytically rigorous practices, the team needs stronger analysis and technical skills to perform those practices. Tooling and documentation alone cannot raise maturity without matching competence.