Courseiva

CCNA Managing the Test Activities Questions

36 questions · Managing the Test Activities · All types, answers revealed

Practice these questionsDomain overviewAll questions
1
MCQeasy

Which of the following is a primary objective of the test manager during the test closure phase?

A.Writing the initial test strategy for a future project.
B.Archiving results, documents, and capturing lessons learned.
C.Assigning new tasks to developers for the next sprint.
D.Conducting the final performance review of the IT director.
AnswerB

Archiving and capturing lessons learned are essential for knowledge management and process improvement. They provide a historical record of the testing performed, which is critical for future audits and helps the team avoid repeating past mistakes, thereby increasing the efficiency and quality of subsequent testing projects in the organization.

Why this answer

Test closure is the final step where the manager collects metrics, archives documents, and records lessons learned. This ensures that the organization benefits from the experience gained during the project. By formalizing this phase, the manager prevents the loss of knowledge, improves future test processes, and ensures that the final state of the project is accurately recorded for future reference or audit requirements.

Exam trap

Candidates often confuse 'test closure' with 'test execution' or 'monitoring', incorrectly assuming it involves fixing bugs or continuing to run remaining test cases.

Practice this question →
2
MCQmedium

A test manager is implementing a risk-based testing strategy. What is the logical sequence of activities for this strategy?

A.Test execution, risk analysis, test design, risk identification.
B.Risk identification, risk analysis, prioritize testing, test execution.
C.Test design, risk identification, risk analysis, test execution.
D.Prioritize testing, risk analysis, risk identification, test execution.
AnswerB

This is the correct logical flow. First, identify potential risks, then analyze their probability and impact. Next, prioritize testing activities based on these findings, and finally execute the tests. This structured process ensures that the most critical components are verified first, maximizing the return on investment for the testing effort.

Why this answer

Risk-based testing follows a structured approach where risks are identified, analyzed, and then used to drive the testing strategy. By prioritizing testing based on these risks, the test manager ensures that the most critical areas receive the most attention. This systematic approach is a core competency in ISTQB testing management, ensuring that resources are allocated efficiently to reduce the most significant project risks.

Exam trap

Candidates often place 'prioritize testing' before 'risk analysis.' You cannot prioritize effectively without first analyzing the severity and likelihood identified during the analysis phase of the risk assessment.

Practice this question →
3
MCQmedium

An automotive software project experiences a critical delay due to supply chain issues with the hardware components. As the test manager, you must revise the test plan to reflect changed conditions. Which action represents the most appropriate test planning adjustment according to ISTQB guidelines?

A.Reduce the planned test coverage by half without consulting stakeholders to compensate for the lost project time.
B.Proceed with test execution exactly as originally scheduled, ignoring the hardware delay to maintain the baseline.
C.Update the test plan and schedule to align with the revised hardware delivery dates and re-evaluate associated risks.
D.Permanently dismiss all manual testing resources and transition entirely to automated exploratory testing immediately.
AnswerC

Updating the test plan and schedule in response to external constraints ensures that testing activities remain feasible and targeted. Re-evaluating risks helps identify new vulnerabilities introduced by compressed timelines and allows for proactive mitigation strategies.

Why this answer

Revising the test plan to align with changed project conditions is a fundamental responsibility of test monitoring and control. Updating schedules, resource allocations, and dependencies ensures the testing process remains synchronized with overall project realities and stakeholder expectations, preventing wasted effort on unavailable features.

Exam trap

Candidates tend to choose options that halt all testing or continue testing despite unavailable hardware, ignoring the need for proactive plan revision.

Practice this question →
4
MCQmedium

What is the primary objective of 'Test Control' within the ISTQB framework?

A.To create new test cases based on changing requirements.
B.To guide and adjust the testing effort based on monitored progress.
C.To write the initial Test Policy for the company.
D.To report the final test results to the CEO.
AnswerB

Test Control is specifically defined as taking action to guide the testing process when actual progress deviates from the plan. It involves analyzing reports, identifying bottlenecks, and adjusting resources or schedules to bring the project back on track. This is the essence of management and project stewardship in testing.

Why this answer

Test Control is the activity of comparing actual progress against the plan and taking corrective action when necessary. It is the 'feedback loop' of test management. By continuously monitoring the project, the test manager ensures that the testing effort remains aligned with business objectives, budget, and time, which is essential for successful project delivery in any software organization.

Exam trap

Candidates often confuse 'Test Control' with 'Test Monitoring'. They assume it is just about gathering data, forgetting that control requires taking active, corrective action.

Practice this question →
5
Multi-Selecthard

A test manager is reviewing the project risk assessment. Which TWO of the following factors should be considered when determining the test approach and effort?

Select 2 answers
A.The total budget allocated for marketing and advertising.
B.The likelihood of a component failure occurring.
C.The impact of a failure on the end-user or business.
D.The number of coffee breaks permitted for the testing team.
E.The color scheme chosen for the user interface documentation.
AnswersB, C

Likelihood is a primary component of risk assessment. Components with a higher probability of failure require more rigorous testing, such as white-box or structural testing techniques. Understanding the likelihood helps the test manager distribute resources where they are most needed to prevent defects from reaching the end users.

Why this answer

ISTQB standards emphasize that test effort and approach must be tailored to the specific risks identified for the project. By evaluating the likelihood of failure and the impact of those failures, the test manager ensures that testing activities provide maximum value. These two factors directly influence the rigor of the testing process and the depth of test design required to mitigate potential business risks effectively.

Exam trap

Candidates often select generic project management metrics like budget or team size instead of core risk dimensions like the likelihood and impact of a component failure.

Practice this question →
6
MCQmedium

Which of the following actions is a typical 'corrective action' taken by a test manager during Test Control?

A.Permanently deleting the original test plan to start over.
B.Reallocating team members from low-priority tasks to address critical delays.
C.Increasing the number of meetings to discuss project history.
D.Ignoring the defects until the end of the project.
AnswerB

Reallocating resources is a standard corrective action. By shifting staff from less urgent areas to address bottlenecks, the test manager optimizes the use of available capacity to meet the most pressing project needs. This keeps the project moving toward completion while managing the most critical risks effectively.

Why this answer

Corrective actions aim to bring the project back in line with the test plan. If a test phase is delayed, the manager must act decisively. Reallocating resources, extending the schedule, or narrowing the test scope are all standard management responses.

These actions ensure that the team focuses on high-value tasks, maintaining project control even when unforeseen challenges threaten the original delivery plan.

Exam trap

Candidates often choose 're-running all tests' or 'reporting the status to the client.' While these are activities, they are not 'corrective actions' designed to fix a specific project delay.

Practice this question →
7
MCQmedium

A test manager observes that a project is behind schedule due to high defect density in a core module. Which test management action is most appropriate to address this bottleneck?

A.Increase the number of test cases for all modules to ensure coverage.
B.Delegate all testing tasks to external contractors to accelerate execution.
C.Prioritize testing of high-risk functional areas and negotiate scope reduction for non-critical features.
D.Skip remaining unit tests to focus entirely on system integration testing.
AnswerC

Risk-based testing allows the team to allocate limited resources effectively by focusing on features with the highest business impact. Negotiating scope reduction for low-priority features provides the necessary buffer to address high defect density in core modules, ensuring that the most critical system components remain stable for release.

Why this answer

Prioritizing testing activities based on risk is a fundamental task for a test manager. By refocusing resources on high-risk areas while potentially postponing low-risk test execution, the manager balances quality objectives with schedule constraints. This approach ensures critical defects are identified early, minimizing the cost of repair and preventing catastrophic failures, which aligns with the ISTQB objective of optimizing testing within project constraints.

Exam trap

Candidates often suggest 'adding more testers' or 'working overtime.' These are resource-heavy reactions that don't address the core issue of prioritizing quality in high-risk areas during a schedule constraint.

Practice this question →
8
MCQhard

Refer to the exhibit. As a Test Manager, how should you handle this pattern of recurring errors in the test environment?

A.Log these as critical bugs for the development team to fix immediately.
B.Coordinate with the infrastructure team to investigate and stabilize the environment.
C.Instruct testers to ignore these errors and continue testing other modules.
D.Update the test plan to exclude Module-A from the current test cycle.
AnswerB

Since the error is consistent and related to database connectivity, the environment is the likely culprit. The Test Manager must engage the relevant technical team responsible for the infrastructure to diagnose and resolve the connection issues, ensuring the environment is stable enough for valid functional test results.

Why this answer

The recurring error suggests an environmental instability, not a functional bug in Module-A. The manager's role is to ensure the test environment is fit for purpose. By escalating this to infrastructure or DevOps teams, the manager removes a significant blocker, allowing functional testers to resume their work.

Effective test management relies on identifying root causes of impediments to keep the project on its planned schedule.

Exam trap

Candidates often choose 'log a bug for the module.' This is incorrect because the issue is environmental, not a defect in the code, and logging a bug will not fix the infrastructure problem.

Practice this question →
9
MCQmedium

Why should a test manager perform a 'test summary report' at the end of a testing project?

A.To prove that the testing team worked harder than the development team.
B.To provide a record of test results and communicate the software's readiness.
C.To delete all defect records to save storage space.
D.To blame the developers for all the defects found during testing.
AnswerB

The test summary report is the final communication artifact. It consolidates test data, confirms whether the exit criteria were met, and provides a clear statement on the software's readiness for release. This transparency is crucial for stakeholders to make an informed decision on whether to deploy the software into production.

Why this answer

The test summary report provides closure to the testing phase and valuable feedback for future improvement. It documents what was tested, the outcomes, and lessons learned. This is a critical management activity because it allows the organization to refine its testing processes, improve estimation accuracy, and provide transparency to stakeholders about the final state of the software quality before the transition to production.

Exam trap

Candidates often assume the report is primarily for the test team’s internal use. However, the primary purpose is stakeholder communication regarding software readiness and the final quality status of the system.

Practice this question →
10
MCQmedium

Which TWO of the following tasks are primary responsibilities of a test manager in a formal testing organization?

A.Writing low-level unit test cases for developer code review.
B.Defining the test strategy and scope for the project.
C.Executing manual regression tests during the final release phase.
D.Monitoring and controlling the test project against the test plan.
E.Configuring the continuous integration build server hardware.
AnswerB, D

Defining the test strategy and scope is a core duty of the test manager. This ensures that the testing effort is focused on the most critical areas, providing a clear roadmap for the test team and ensuring that stakeholders understand what will be tested and what remains out of scope.

Why this answer

Test managers focus on high-level orchestration, including planning, monitoring, and controlling the testing effort. They bridge the gap between technical execution and management expectations by ensuring resources are allocated correctly and that metrics are accurately tracked against project objectives. These activities are essential for maintaining visibility into the testing progress and ensuring the testing process remains aligned with the overall software development lifecycle and quality requirements.

Exam trap

Candidates often confuse the high-level management tasks of a test manager (like defining strategy and monitoring) with the hands-on execution tasks performed by testers, such as writing and running individual test cases.

Practice this question →
11
Multi-Selectmedium

Which THREE of the following are essential components that a test manager should monitor during test execution to ensure the project remains on track?

Select 3 answers
A.The number of test cases passed, failed, and blocked.
B.The current status of defect resolution and re-testing.
C.The number of hours spent by developers on their personal emails.
D.Remaining effort and resource availability.
E.The average salary of the software engineering team.
AnswersA, B, D

Tracking pass/fail/blocked status is essential to understand the current progress of testing. Blocked tests indicate dependencies that need resolution, while high failure rates suggest instability. This data enables the manager to report actual progress versus planned progress and identify bottlenecks that could delay the project delivery date.

Why this answer

Monitoring test execution requires constant vigilance over progress and quality. Tracking these three areas—execution status, defect status, and resource usage—gives the test manager the data needed to perform project control. If any of these metrics deviate from the plan, the manager can take corrective action, such as reallocating tasks or adjusting the schedule to maintain alignment with project goals.

Exam trap

Candidates frequently include 'total number of test cases' as a monitorable component. Total count is a static planning metric, not a dynamic execution status metric needed to ensure the project stays on track.

Practice this question →
12
MCQhard

You are the Test Manager for an agile team delivering a mobile insurance claims app. The team tracks progress using a burn-down chart of test execution tasks and a defect report grouped by severity. At the sprint review, the Product Owner asks for a single indicator showing whether the remaining open defects are likely to block the sprint goal. Which test management artifact is MOST appropriate to present?

A.A defect status report showing open defects by severity and their resolution status.
B.A test summary report listing all test cases executed and their pass/fail status.
C.A defect density report showing defects per module of the claims app.
D.A test progress burn-down chart showing the number of open test cases per day.
AnswerA

A defect status report groups open defects by severity and resolution state, which directly reveals whether high-severity defects remain unresolved and could block the sprint goal. This gives the Product Owner a focused view of outstanding risk rather than general execution progress.

Why this answer

The Product Owner needs an indicator of whether remaining defects threaten the sprint goal. A defect status report showing open defects by severity and resolution status directly exposes unresolved high-severity items that could block delivery, making it the most relevant artifact. Execution charts, density metrics, and full summary reports describe activity or aggregate quality but do not isolate the blocking risk.

Exam trap

The trap here is assuming that any defect-related chart satisfies a request about defect risk, when only a severity- and status-grouped view exposes unresolved blocking defects.

Practice this question →
13
Multi-Selectmedium

Which TWO of the following are primary responsibilities of a Test Manager during the Test Monitoring and Control activity?

Select 2 answers
A.Writing detailed test scripts for automated regression testing.
B.Comparing current test progress against the planned test schedule.
C.Taking corrective actions when test execution deviates from the plan.
D.Executing the test cases on the production environment.
E.Establishing the coding standards for the development team.
AnswersB, C

This is a core monitoring activity. By tracking metrics like test execution rates and defect arrival patterns, the manager identifies if the project is meeting its milestones. This objective data is necessary to determine if the testing effort is on track or if adjustments are required.

Why this answer

A Test Manager must balance tracking progress against the plan with taking corrective actions when deviations occur. These two activities are cyclical and essential for keeping the project within budget, schedule, and quality constraints. By monitoring metrics and controlling resources, the manager ensures that the testing process provides maximum value to stakeholders and remains transparent throughout the software development lifecycle.

Exam trap

Test-takers frequently mix up monitoring tasks (which involve observation and measurement) with control tasks (which involve taking corrective interventions).

Practice this question →
14
MCQeasy

Which document is primarily used by a test manager to outline the scope, objectives, and test schedule for a project?

A.Test Summary Report.
B.Test Plan.
C.Test Case Specification.
D.Defect Report.
AnswerB

The Test Plan is the foundational document that defines the scope, approach, resources, and schedule for the intended test activities. It acts as the primary communication tool for the test manager to coordinate the testing effort and align the expectations of various project stakeholders regarding the quality assurance process.

Why this answer

The Test Plan is the central document in ISTQB methodology for managing test activities. It serves as the master guide, defining what will be tested, how it will be tested, the schedule for execution, and the resources required. This ensures all stakeholders have a shared understanding of the testing strategy, allowing for better coordination between the development and QA departments throughout the project life cycle.

Exam trap

Candidates confuse the Test Plan with the Test Strategy or Test Summary Report, missing that the Plan is the specific document for project-level scheduling and resource management.

Practice this question →
15
MCQeasy

Which of the following is an example of a 'test control' activity?

A.Recording the number of defects found in a spreadsheet.
B.Re-prioritizing the test schedule due to a resource shortage.
C.Writing the initial test plan for the project.
D.Training a new employee on the testing tools.
AnswerB

Re-prioritizing is a classic test control activity. It is a direct management response to a change in project constraints, like a resource shortage. By modifying the schedule, the test manager ensures the team remains productive and focuses on the most critical tasks despite the current limitations in staff or time.

Why this answer

Test control involves taking action based on monitoring data. When a project deviates from its plan, the manager must adjust the strategy to bring it back into alignment. This active management ensures that the testing effort is responsive to real-world challenges, such as resource changes or schedule delays, rather than blindly following an outdated plan that no longer fits the project's current reality.

Exam trap

Candidates often confuse test monitoring (observing and collecting metrics) with test control (taking active corrective actions to fix deviations).

Practice this question →
16
MCQmedium

During a banking application project, the test manager notices that defect density in the payment module is twice as high as expected. How should the test manager apply risk-based testing to adjust the test plan?

A.Immediately halt all testing across other modules and reallocate all resources exclusively to writing manual regression test scripts for the payment module.
B.Analyze the high defect density to update risk assessments, prioritize additional testing on identified high-risk payment features, and inform stakeholders.
C.Delegate all defect root cause analysis entirely to the software development team while continuing test execution strictly according to the initial schedule.
D.Reduce the entry criteria for the payment module to allow faster sign-off and recover lost project schedule time without altering test coverage.
AnswerB

Risk-based testing uses observed defect density as an input to reassess likelihood. Updating risk assessments, re-prioritising testing toward the high-risk payment features, and informing stakeholders turns the metric into adjusted test effort, which is the prescribed response.

Why this answer

Risk-based testing involves prioritizing test execution based on product risks. When defect density spikes in a critical module, the test manager must re-evaluate product risks and redirect testing effort to find remaining failures. This ensures quality focus remains aligned with business exposure.

Exam trap

Candidates often choose 'stop testing' or 'immediately fix all defects.' These are not risk-based strategies; they ignore the need to re-evaluate priorities based on the new data about defect density.

Practice this question →
17
MCQhard

Refer to the exhibit. Given the current test progress report, which action should the test manager take to ensure the project remains on track for the final release deadline?

A.Immediately increase the test execution velocity by adding more manual testers to the project.
B.Investigate the blocked test cases to resolve dependencies and continue execution progress.
C.Ignore the failed test cases for now and focus entirely on executing the remaining untested cases.
D.Update the test plan to reflect a lower number of total test cases for the final release.
AnswerB

Blocked tests indicate environmental, data, or requirement issues that prevent the team from verifying functionality. Resolving these is the highest priority because they impact the critical path. Addressing them allows the team to resume testing, reducing the risk of a late delivery due to undiscovered software defects.

Why this answer

The report shows 20 blocked tests and 50 failed tests, with 150 cases remaining. The test manager must address the blocked items immediately, as these prevent full verification of the system. This demonstrates effective test management by prioritizing blockers, which are often external dependencies, to ensure the remaining 150 tests can be executed without further delays before the deadline.

Exam trap

Candidates often suggest re-running failed tests immediately, ignoring that 'blocked' tests prevent the system from being fully exercised and represent a fundamental dependency issue.

Practice this question →
18
MCQmedium

A test manager observes that a project is behind schedule due to high defect density in a core module. The manager decides to reallocate resources from the documentation phase to the execution phase. Which risk-based testing activity is being performed?

A.Test monitoring
B.Test control
C.Test estimation
D.Test implementation
AnswerB

Test control involves taking necessary actions to align test execution with the project plan when deviations occur. Reallocating resources to address high defect density is a classic example of corrective action taken to manage schedule risks, ensuring that project objectives remain achievable despite the identified quality issues.

Why this answer

This activity involves active risk management through monitoring and control. By reallocating resources, the test manager is adjusting the test approach based on current status to mitigate the risk of schedule slippage. This practice is essential in ISTQB test management because it ensures that testing priorities align with project constraints and quality goals, maintaining control over the testing lifecycle despite unexpected technical challenges during development.

Exam trap

Candidates mistake this for 'Test Monitoring' or 'Risk Analysis.' The act of actively reallocating resources to address a specific issue is a 'Test Control' action.

Practice this question →
19
MCQmedium

Why is it important for a test manager to implement a test-monitoring process throughout the software lifecycle?

A.To ensure that all testers are working at the same speed.
B.To identify deviations from the plan and take corrective action.
C.To justify the need for higher salaries for the team.
D.To fulfill requirements for legal compliance audits.
AnswerB

The core purpose of monitoring is to detect discrepancies between planned and actual progress. Once identified, the test manager can take corrective actions—such as reallocating resources or adjusting the test scope—to keep the project on track and minimize the impact of unforeseen issues on the final release schedule.

Why this answer

Test monitoring provides the feedback loop necessary for proactive management. By continuously comparing actual progress against the plan, a manager can identify risks early, allocate resources where they are needed most, and make informed decisions about whether the project is on track. This visibility is essential for maintaining the quality and speed requirements of modern software development, preventing minor issues from becoming critical project failures.

Exam trap

Students frequently select options about finding bugs or executing scripts, confusing test monitoring with the actual hands-on test execution phase.

Practice this question →
20
MCQmedium

A Test Manager is concerned that the current defect arrival rate is too high to complete testing on time. What is the most appropriate management response?

A.Extend the test schedule without informing stakeholders.
B.Analyze the impact, communicate with stakeholders, and adjust the plan if necessary.
C.Stop all testing activities to force developers to fix the existing defects immediately.
D.Reduce the number of test cases to be executed to meet the deadline.
AnswerB

This is the correct management approach. It involves assessing the situation, keeping stakeholders informed of risks, and proactively adjusting the plan to manage expectations. This demonstrates accountability and ensures that decisions are made based on accurate project status rather than assumptions or attempts to force an unrealistic deadline.

Why this answer

When defect rates are high, it indicates instability. The manager must assess the impact and communicate with stakeholders. Simply ignoring the issue or pushing harder is counterproductive.

By evaluating the impact on the schedule and potential scope, the manager provides the team with a realistic path forward, which is a fundamental aspect of effective test control and stakeholder transparency in the ISTQB framework.

Exam trap

Candidates often pick reactive, aggressive options like forcing testers to work overtime or simply ignoring the arrival rate to meet the original deadline.

Practice this question →
21
MCQmedium

Which of the following metrics is the most effective for a test manager to report the current status of defect discovery and resolution during the monitoring phase?

A.Total number of test cases executed against the total number of planned test cases.
B.Defect arrival and resolution rate trends over time.
C.The number of hours spent by developers on debugging.
D.The total number of requirements identified in the SRS document.
AnswerB

This trend analysis is critical for assessing the stability of the software. A high defect arrival rate combined with a slow resolution rate indicates significant stability issues. Tracking these metrics over time helps the test manager determine if the system is approaching a state where it is ready for release.

Why this answer

Defect arrival and resolution rates provide a clear picture of the testing trajectory and software stability. Monitoring these metrics allows the test manager to identify trends, such as whether defect discovery is plateauing or if resolution is lagging behind discovery, enabling informed decisions regarding exit criteria and release readiness as per ISTQB standards for project control.

Exam trap

Candidates select static metrics like 'total defects found,' which do not account for the progress or velocity of the testing effort relative to the project timeline.

Practice this question →
22
MCQmedium

Which of the following metrics would be most useful for a Test Manager to report the effectiveness of the testing process to stakeholders?

A.Number of test cases written per week.
B.Defect detection percentage.
C.Total number of test cases executed.
D.Average number of hours per test case.
AnswerB

Defect detection percentage (DDP) compares bugs found in testing to total bugs found (including those in production). A high DDP indicates that the testing process is highly effective at uncovering issues before release, which is the primary goal of testing and a key indicator for stakeholders.

Why this answer

Measuring test effectiveness requires evaluating the quality of the tests themselves, not just the quantity of work. Defect detection percentage, or defect removal efficiency, provides a direct view of how many bugs were found during testing versus those found by end-users. This metric is critical for demonstrating the value of testing activities to business stakeholders who are concerned about software reliability and risk.

Exam trap

Candidates frequently confuse test effectiveness metrics with productivity metrics like total tests executed or test velocity, overlooking quality and defect leakage aspects.

Practice this question →
23
MCQeasy

When selecting test tools, what is the most important factor for a Test Manager to consider?

A.The lowest cost of the software license.
B.The tool's compatibility with the current testing process and environment.
C.The availability of the tool's source code for modification.
D.The fame and popularity of the vendor in the market.
AnswerB

The most important factor is the tool's fit for the specific project context. If a tool cannot integrate with existing test management platforms, CI/CD pipelines, or the team's technical skills, it will create friction rather than efficiency. Success is measured by how well the tool supports objectives.

Why this answer

The primary goal of any tool is to support the testing process in the specific context of the project. A tool that is powerful but does not integrate with existing workflows, or is too complex for the team, will fail to provide value. Compatibility with the current development environment and the team's skillset is paramount to ensure successful adoption and long-term utility.

Exam trap

Candidates often assume the cheapest tool or the tool with the most advanced features is automatically the best choice for selection.

Practice this question →
24
MCQmedium

Which TWO of the following are examples of test-monitoring metrics that a test manager should track?

A.Percentage of test cases executed.
B.Number of coffee breaks taken by the team.
C.Number of defects found vs. number of defects resolved.
D.The favorite programming language of each tester.
E.The total cost of office supplies for the year.
AnswerA, C

Tracking the percentage of test execution gives a clear view of how much of the planned work has been accomplished. This is a critical metric for understanding the schedule status and identifying if the team is behind, on track, or ahead of the projected timeline for the testing phase.

Why this answer

Monitoring metrics provide objective evidence of project status. By tracking test execution progress and defect density, a manager can identify whether the testing effort is sufficient and if the software quality is improving. These metrics are fundamental for reporting to stakeholders, justifying decisions, and identifying the need for corrective action to keep the project on track and within the defined quality boundaries.

Exam trap

Candidates often select 'number of test cases written' or 'total defects found' as metrics. These are static counts that do not show progress or quality trends, unlike execution percentage and defect resolution ratios.

Practice this question →
25
MCQeasy

What is the primary role of a 'Test Basis' in the context of managing test activities?

A.It provides the budget for the testing project.
B.It is used as the source of information to derive test cases.
C.It lists the names of all testers assigned to the project.
D.It serves as the final report for the project's stakeholders.
AnswerB

The test basis, such as requirements, user stories, or design specifications, is the source material for creating test cases. It defines the 'expected behavior' of the system, which allows the test team to create scenarios that verify whether the system is functioning correctly as per the stated goals.

Why this answer

The test basis serves as the foundation for the entire testing process. It represents the source of information used to derive test cases. Without a clear and stable test basis, it is impossible to know what needs to be tested or to measure test coverage accurately.

Managing the test basis is critical for ensuring that the testing effort is aligned with the project's requirements and business objectives.

Exam trap

Candidates commonly confuse the test basis with the test plan or defect log, forgetting its fundamental role as the origin point for deriving test cases.

Practice this question →
26
MCQhard

When managing test activities across a distributed team, which factor is most critical for ensuring consistent test execution?

A.Ensuring all testers are in the same physical office.
B.Standardizing test environments and documentation processes.
C.Assigning only the most senior testers to the distributed team.
D.Limiting communication to one email per week.
AnswerB

Standardization is the key to distributed success. If all team members use the same environment configurations and documentation formats, the results are comparable and reliable. This reduces variance and ensures that every tester is following the same rigorous process, which is vital for maintaining high quality across different locations.

Why this answer

In distributed teams, synchronization and communication are the primary challenges. Standardizing the test environment, documentation, and reporting tools ensures that all team members, regardless of their location, are working toward the same goals. According to ISTQB standards, clear process definition and effective communication channels are essential to mitigate the risks of misunderstanding and fragmentation, leading to a cohesive and successful testing outcome.

Exam trap

Candidates often prioritize 'frequent video meetings' or 'centralized defect tracking.' While helpful, these do not ensure consistent test execution; standardizing the environment and process is the fundamental requirement.

Practice this question →
27
MCQeasy

During a project, a Test Manager decides to prioritize testing of the payment processing module due to its critical impact on revenue. Which test management activity does this illustrate?

A.Test estimation
B.Test planning
C.Test execution
D.Test closure
AnswerB

Risk-based prioritization is a key component of test planning. The manager determines the test approach, scope, and schedule by identifying which parts of the system are most critical. Setting these priorities early ensures that the most important areas receive adequate focus and testing depth during execution.

Why this answer

Prioritizing testing based on the business impact of a module is a fundamental part of risk-based test planning. By focusing limited resources on high-risk areas, the manager maximizes the probability of finding critical defects early. This aligns with ISTQB principles that emphasize risk-based approaches to optimize test effectiveness and project success in environments where resources are constrained.

Exam trap

Candidates often mistake risk-based prioritization occurring mid-project for 'test control', overlooking that setting initial priorities falls under overall test planning.

Practice this question →
28
MCQhard

Refer to the exhibit. As a Test Manager, you find that the project has 96% coverage and a 99% pass rate, with one open severity-1 defect. Based on the policy, what is the correct status of the project?

A.The project meets the requirements for release.
B.The project is on the verge of success and can be released after a quick review.
C.The project does not meet the exit criteria and cannot be released.
D.The coverage metric overrides the other two failure points.
AnswerC

The project fails the exit criteria on two counts: it contains a severity-1 defect and the pass rate is less than 100%. Therefore, it is ineligible for release according to the provided policy. The Test Manager must communicate this status clearly to the project team and stakeholders.

Why this answer

The project fails the exit criteria. The presence of a severity-1 defect violates the 'Max_Allowed_Severity_1_Defects: 0' policy, and the 99% pass rate is below the '100%' requirement. As a Test Manager, you must report that the project does not meet the criteria for release.

This is crucial for maintaining quality standards and managing stakeholder expectations regarding the software's readiness for production deployment.

Exam trap

Candidates focus solely on high numerical coverage and pass percentages while ignoring strict zero-tolerance criteria for open severity-1 defects.

Practice this question →
29
MCQmedium

Which THREE factors should a test manager consider when estimating the effort required for a new testing project?

A.The complexity of the system under test.
B.The test team's experience and skill level.
C.The salary of the individual test team members.
D.Availability of test environments and tools.
E.The branding colors and company logo requirements.
AnswerA, B, D

System complexity directly impacts the effort needed to design and execute effective test cases. More complex systems require more time for test analysis, test design, and debugging, making it a primary factor in any realistic estimation process for a professional test management strategy.

Why this answer

Accurate estimation is critical for successful project management. A manager must consider the complexity of the software, the capabilities of the team, and the availability of the required tools and environments. By assessing these factors, the manager creates a realistic schedule that avoids burnout and ensures that the testing effort is sufficient to uncover significant risks before the product is released to the end user.

Exam trap

Test-takers frequently select factors related to actual test execution results or bug fixes, forgetting that estimation happens before testing begins and relies on project constraints and resources.

Practice this question →
30
MCQmedium

Which of the following is an example of a 'test exit criterion' defined in a test plan?

A.All developers must be present for the final system demo.
B.100% of all critical and high-priority test cases must have passed.
C.The budget for the test team should be increased by 10%.
D.Testing should stop because the team is tired.
AnswerB

This is a measurable, objective exit criterion. It ensures that the most important parts of the system have been verified and passed. This standard provides a clear signal to stakeholders that the product has reached a level of quality that is suitable for moving to the next stage.

Why this answer

Exit criteria define the conditions under which testing can be considered complete. According to ISTQB, these criteria must be measurable and objective. Common criteria include achieving 100% test coverage, passing all high-severity tests, and meeting predefined quality thresholds.

Without clear exit criteria, it is impossible to determine when to stop testing, leading to either premature release or infinite testing cycles.

Exam trap

Test-takers often confuse exit criteria with test inputs or tasks, such as selecting 'writing 50 test cases' instead of focusing on measurable completion conditions like pass rates.

Practice this question →
31
MCQmedium

When should a test manager decide to stop the testing process?

A.When all test cases have been executed and passed.
B.When the project budget is completely exhausted.
C.When the defined exit criteria are satisfied.
D.When the developers tell the test team to stop.
AnswerC

Exit criteria serve as the objective benchmark for project readiness. When these criteria are met, it indicates that the risk has been reduced to an acceptable level as agreed upon by stakeholders. This provides a clear, professional basis for concluding the testing phase and moving to the next project step.

Why this answer

Testing should stop when the exit criteria defined in the test plan are met or when the project can no longer justify the cost of further testing. This balance is crucial; testing until every single bug is found is impossible and economically unfeasible. By using defined criteria, the manager provides a clear, defensible decision for when to release the product while acknowledging that some residual risk will always exist.

Exam trap

Students often fall for the trap of answering 'when all bugs are fixed' or 'when time runs out', ignoring that testing stops based on predefined, objective exit criteria.

Practice this question →
32
MCQmedium

Which of the following describes the 'Monitoring' aspect of test management?

A.Taking corrective actions when progress is slower than planned.
B.Gathering data on test execution progress and comparing it to the plan.
C.Writing the final test summary report for the project.
D.Designing the test cases based on the system requirements.
AnswerB

Monitoring is precisely about collecting metrics like test cases passed, failed, or blocked, and comparing those results against the planned milestones. This provides the objective data required to understand if the project is moving according to the original plan or if it is drifting off course.

Why this answer

Monitoring is the process of continuously tracking the current status of the project against the initial plan. It involves gathering metrics and comparing them to expected progress. This allows the manager to identify deviations early and provide transparency to stakeholders, ensuring that everyone has an accurate understanding of the testing progress and any potential risks to the project's schedule or quality.

Exam trap

Candidates confuse monitoring with controlling, picking actions that take corrective measures rather than simply gathering and comparing progress data.

Practice this question →
33
MCQmedium

During project monitoring, the test manager realizes the team is falling behind the schedule due to an unexpectedly high number of defects. What is the most effective management response?

A.Demand the team work unpaid overtime to complete the original plan.
B.Reduce the scope of testing by focusing only on high-risk areas.
C.Ignore the defects and continue with the original testing sequence.
D.Replace the test team with more experienced external consultants.
AnswerB

Reducing scope through risk-based prioritization is a standard management technique when schedules are compressed. By focusing on critical functionality, the test manager ensures that the most impactful risks are mitigated, maximizing the value of the remaining testing time and ensuring the project delivers a stable product to the customer.

Why this answer

A proactive response involves re-assessing risks and adjusting priorities. By shifting focus to high-risk areas, the test manager ensures that even if the schedule is tight, the most critical features are verified. This approach aligns with the ISTQB focus on risk-based testing, where resources are allocated based on potential impact rather than simply trying to execute every test case without consideration of project value.

Exam trap

Candidates suggest 'testing everything faster' or 'working overtime,' which are not effective management responses to schedule slippage in a risk-based testing framework.

Practice this question →
34
MCQeasy

Which document is primarily used by the test manager to define the scope, approach, resources, and schedule of the testing activities?

A.Test Case Specification.
B.Test Plan.
C.Defect Report.
D.Requirement Traceability Matrix.
AnswerB

The Test Plan is the primary artifact for coordinating and controlling testing. It covers the strategy, objectives, risk assessment, resource planning, and schedule. It provides the necessary framework for the test manager to lead the testing activities, track progress, and communicate with stakeholders throughout the software development life cycle.

Why this answer

The Test Plan is the central document for test management. It outlines the 'what', 'how', 'when', and 'who' of the testing process. According to ISTQB, the test plan acts as the roadmap for the entire testing effort, ensuring that all stakeholders are aligned on the testing strategy, resource availability, and the timeline for completion of all planned testing activities.

Exam trap

Candidates mistakenly choose documents like the Test Summary Report or Test Strategy, confusing the overarching operational roadmap with retrospective summaries or high-level organizational guidelines.

Practice this question →
35
MCQmedium

A project manager is analyzing test progress during a sprint. The team has completed 60% of planned test cases, but 40% of those executed failed due to a critical environment issue. Which test management action is most appropriate?

A.Increase the number of testers to execute remaining cases faster.
B.Prioritize and resolve the environment issue before resuming test execution.
C.Report the 60% completion rate to stakeholders to indicate success.
D.Stop testing immediately and declare the sprint a failure.
AnswerB

Addressing the environmental bottleneck is critical because high failure rates due to infrastructure prevent the team from verifying actual product functionality. By stabilizing the environment first, the test manager ensures that subsequent test executions yield valid, reliable results, preventing further waste of time and resources on false-positive defect reports.

Why this answer

The primary focus must be mitigating the blocker rather than continuing execution. By prioritizing environment resolution, the test manager ensures the remaining test cases can be executed in a stable system. This aligns with ISTQB principles of managing test activities by monitoring progress and reacting to deviations that impede the testing process, ensuring the team remains productive and goals are eventually achieved.

Exam trap

Candidates mistakenly choose to continue executing remaining test cases despite critical environmental failures, ignoring that blocked environments invalidate further execution results.

Practice this question →
36
MCQmedium

What is the primary purpose of a 'Defect Triage' meeting in the context of managing test activities?

A.To discipline developers for writing poor quality code.
B.To decide which defects will be fixed and their priority levels.
C.To rewrite the test cases for the defects that were found.
D.To automatically trigger the redeployment of the test environment.
AnswerB

The core goal of triage is to review reported defects, confirm their validity, determine their priority based on business risk, and assign them to the appropriate developers. This ensures that the team is working on the most important issues to improve the product before the release deadline arrives.

Why this answer

Defect triage is a collaborative effort to prioritize bugs. It ensures that developers and testers agree on which defects must be fixed immediately versus which can be deferred. This prevents resource wastage on low-priority items and ensures that the most critical issues, which represent the highest risk to the software, are addressed by the development team first during the limited release window.

Exam trap

Candidates think triage is about fixing bugs, whereas it is actually a management meeting to decide the priority and status of bugs in the release cycle.

Practice this question →

Ready to test yourself?

Try a timed practice session using only Managing the Test Activities questions.

Start 20-question session