Question 120An application release meets every planned feature requirement, but a load test fails under anticipated seasonal traffic. Which governance control should be retained for future work? Define progress measurement and reporting rules before collecting earned-value metrics. Require rehearsal of test-environment failover but omit measurable production performance gates. Add capacity and stress thresholds to the project quality management plan. Define user-validation criteria separately from unit and integration test success. ExplanationCorrect Answer C:Add capacity and stress thresholds to the project quality management plan. The control prevents recurrence because functional completeness does not demonstrate performance requirements such as throughput and response latency. The immediate corrective step remains: Investigate performance testing failures before confirming the nonfunctional quality gate. Other Answers A:Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. A more direct preventive measure is to add capacity and stress thresholds to the project quality management plan. B:Require rehearsal of test-environment failover but omit measurable production performance gates. Failover procedures may be useful, but they do not prevent recurrence of insufficient application capacity under seasonal traffic. The controlling constraint in this case is: Functional completeness does not demonstrate performance requirements such as throughput and response latency. D:Technical component testing checks code behavior; validation asks whether the completed solution meets user needs. A more direct preventive measure is to add capacity and stress thresholds to the project quality management plan.
Question 121An API migration completes an agreed work package, but the team cannot tell whether it is ahead of schedule because it reports only spending. What action most directly resolves the specific project-management problem? Investigate performance testing failures before confirming the nonfunctional quality gate. Mark the work package complete and release the delivery specialists without calculating any planned or earned schedule value. Conduct user acceptance testing against signed business scenarios before declaring the deliverable accepted. Calculate and interpret schedule performance using earned value against planned value rather than cash consumed alone. ExplanationCorrect Answer D:Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. To confirm, reconcile the work-package percent complete with PV, EV, and the resulting schedule variance. Other Answers A:Functional completeness does not demonstrate performance requirements such as throughput and response latency. The corrective action for this requirement is to calculate and interpret schedule performance using earned value against planned value rather than cash consumed alone. B:Mark the work package complete and release the delivery specialists without calculating any planned or earned schedule value. Resource release does not measure project progress. The team needs earned value compared with planned value to assess schedule performance. The controlling constraint in this case is: Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. C:Technical component testing checks code behavior; validation asks whether the completed solution meets user needs. A more relevant action is to calculate and interpret schedule performance using earned value against planned value rather than cash consumed alone.
Question 122An API migration completes an agreed work package, but the team cannot tell whether it is ahead of schedule because it reports only spending. Why is the recommended action more appropriate for this situation? Technical component testing checks code behavior; validation asks whether the completed solution meets user needs. Functional completeness does not demonstrate performance requirements such as throughput and response latency. A project team being released after delivery is sufficient evidence that planned schedule value was earned. Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. ExplanationCorrect Answer D:Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. It supports this case-specific action: Calculate and interpret schedule performance using earned value against planned value rather than cash consumed alone. The relevant proof is: Reconcile the work-package percent complete with PV, EV, and the resulting schedule variance. Other Answers A:Technical component testing checks code behavior; validation asks whether the completed solution meets user needs. In the stated system, schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. B:Functional completeness does not demonstrate performance requirements such as throughput and response latency. In the stated system, schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. C:A project team being released after delivery is sufficient evidence that planned schedule value was earned. Staffing transition says nothing about whether the measured scope progressed relative to the approved schedule baseline. The controlling constraint in this case is: Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress.
Question 123An API migration completes an agreed work package, but the team cannot tell whether it is ahead of schedule because it reports only spending. Which check should be performed before the project lead accepts the correction? Repeat a representative load test and compare response times against approved service thresholds. Capture business-user test execution and explicit acceptance against the signed payroll scenarios. Reconcile the work-package percent complete with PV, EV, and the resulting schedule variance. Confirm the specialists have successor assignments, but do not calculate earned value or planned value for the work. ExplanationCorrect Answer C:Reconcile the work-package percent complete with PV, EV, and the resulting schedule variance. This checks the required decision: Calculate and interpret schedule performance using earned value against planned value rather than cash consumed alone. It matters because schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. Other Answers A:Functional completeness does not demonstrate performance requirements such as throughput and response latency. A more meaningful verification is to reconcile the work-package percent complete with PV, EV, and the resulting schedule variance. B:Technical component testing checks code behavior; validation asks whether the completed solution meets user needs. Proving this correction calls for a check to reconcile the work-package percent complete with PV, EV, and the resulting schedule variance. D:Confirm the specialists have successor assignments, but do not calculate earned value or planned value for the work. Handover evidence cannot validate schedule variance. The relevant comparison is completed work value versus scheduled work value. The controlling constraint in this case is: Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress.
Question 124An API migration completes an agreed work package, but the team cannot tell whether it is ahead of schedule because it reports only spending. Which governance control should be retained for future work? Complete team handover checklists without defining how earned value and planned value will be measured. Define progress measurement and reporting rules before collecting earned-value metrics. Add capacity and stress thresholds to the project quality management plan. Define user-validation criteria separately from unit and integration test success. ExplanationCorrect Answer B:Define progress measurement and reporting rules before collecting earned-value metrics. The control prevents recurrence because schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. The immediate corrective step remains: Calculate and interpret schedule performance using earned value against planned value rather than cash consumed alone. Other Answers A:Complete team handover checklists without defining how earned value and planned value will be measured. Resource closeout documentation cannot prevent distorted schedule reporting on future work packages. The controlling constraint in this case is: Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. C:Functional completeness does not demonstrate performance requirements such as throughput and response latency. A more direct preventive measure is to define progress measurement and reporting rules before collecting earned-value metrics. D:Technical component testing checks code behavior; validation asks whether the completed solution meets user needs. Reducing this risk requires a practice to define progress measurement and reporting rules before collecting earned-value metrics.
Question 125A sprint demonstration reveals a missing accessibility flow, yet the team schedules no opportunity to discuss process improvements. What action most directly resolves the specific project-management problem? Calculate and interpret schedule performance using earned value against planned value rather than cash consumed alone. Separate the product review of outcomes from a retrospective focused on how the team will improve delivery. Conduct user acceptance testing against signed business scenarios before declaring the deliverable accepted. Route newly requested features to backlog refinement and negotiate sprint-scope exceptions only with the team. ExplanationCorrect Answer B:A sprint review inspects the product increment; a retrospective inspects collaboration and process effectiveness. To confirm, find both documented product backlog changes and an actionable improvement from the team retrospective. Other Answers A:Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. This failure calls for a decision to separate the product review of outcomes from a retrospective focused on how the team will improve delivery. C:Technical component testing checks code behavior; validation asks whether the completed solution meets user needs. This failure calls for a decision to separate the product review of outcomes from a retrospective focused on how the team will improve delivery. D:A sprint goal supports focus; product backlog priority changes do not automatically invalidate an in-flight team commitment. A more relevant action is to separate the product review of outcomes from a retrospective focused on how the team will improve delivery.
Question 126A sprint demonstration reveals a missing accessibility flow, yet the team schedules no opportunity to discuss process improvements. Why is the recommended action more appropriate for this situation? A sprint goal supports focus; product backlog priority changes do not automatically invalidate an in-flight team commitment. A sprint review inspects the product increment; a retrospective inspects collaboration and process effectiveness. Technical component testing checks code behavior; validation asks whether the completed solution meets user needs. Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. ExplanationCorrect Answer B:A sprint review inspects the product increment; a retrospective inspects collaboration and process effectiveness. It supports this case-specific action: Separate the product review of outcomes from a retrospective focused on how the team will improve delivery. The relevant proof is: Find both documented product backlog changes and an actionable improvement from the team retrospective. Other Answers A:A sprint goal supports focus; product backlog priority changes do not automatically invalidate an in-flight team commitment. In the stated system, a sprint review inspects the product increment; a retrospective inspects collaboration and process effectiveness. C:Technical component testing checks code behavior; validation asks whether the completed solution meets user needs. By contrast, a sprint review inspects the product increment; a retrospective inspects collaboration and process effectiveness. D:Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. By contrast, a sprint review inspects the product increment; a retrospective inspects collaboration and process effectiveness.
Question 127A sprint demonstration reveals a missing accessibility flow, yet the team schedules no opportunity to discuss process improvements. Which check should be performed before the project lead accepts the correction? Check whether planned sprint work remains attainable and new requests enter the properly prioritized future backlog. Find both documented product backlog changes and an actionable improvement from the team retrospective. Reconcile the work-package percent complete with PV, EV, and the resulting schedule variance. Capture business-user test execution and explicit acceptance against the signed payroll scenarios. ExplanationCorrect Answer B:Find both documented product backlog changes and an actionable improvement from the team retrospective. This checks the required decision: Separate the product review of outcomes from a retrospective focused on how the team will improve delivery. It matters because a sprint review inspects the product increment; a retrospective inspects collaboration and process effectiveness. Other Answers A:A sprint goal supports focus; product backlog priority changes do not automatically invalidate an in-flight team commitment. A more meaningful verification is to find both documented product backlog changes and an actionable improvement from the team retrospective. C:Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. The failure is checked more directly by a test to find both documented product backlog changes and an actionable improvement from the team retrospective. D:Technical component testing checks code behavior; validation asks whether the completed solution meets user needs. The failure is checked more directly by a test to find both documented product backlog changes and an actionable improvement from the team retrospective.
Question 128A sprint demonstration reveals a missing accessibility flow, yet the team schedules no opportunity to discuss process improvements. Which governance control should be retained for future work? Explain sprint-goal protection and an explicit urgent-change agreement in the team working agreement. Reserve separate time for product acceptance and team learning in each iteration. Define user-validation criteria separately from unit and integration test success. Define progress measurement and reporting rules before collecting earned-value metrics. ExplanationCorrect Answer B:Reserve separate time for product acceptance and team learning in each iteration. The control prevents recurrence because a sprint review inspects the product increment; a retrospective inspects collaboration and process effectiveness. The immediate corrective step remains: Separate the product review of outcomes from a retrospective focused on how the team will improve delivery. Other Answers A:A sprint goal supports focus; product backlog priority changes do not automatically invalidate an in-flight team commitment. The lasting safeguard is to reserve separate time for product acceptance and team learning in each iteration. C:Technical component testing checks code behavior; validation asks whether the completed solution meets user needs. Reducing this risk requires a practice to reserve separate time for product acceptance and team learning in each iteration. D:Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. Reducing this risk requires a practice to reserve separate time for product acceptance and team learning in each iteration.
Question 129A global deployment team schedules live status calls at 3 a.m. for half the participants and begins losing decision-making attendance. What action most directly resolves the specific project-management problem? Provide a shared glossary and translated written acceptance steps, with confirmation from each vendor. Move incident communications to an approved restricted channel with defined recipients and archival rules. Publish decision minutes with owners, deadlines, distribution list, and a durable record of approvals. Use an agreed asynchronous status record plus rotating synchronous windows for decisions requiring discussion. ExplanationCorrect Answer D:Asynchronous records support different time zones; synchronous meetings remain useful for immediate joint decisions. To confirm, review response rates and documented approvals from each region after the revised communication cadence. Other Answers A:Language and cultural barriers can distort instructions even when the same message is broadcast to all parties. The corrective action for this requirement is to use an agreed asynchronous status record plus rotating synchronous windows for decisions requiring discussion. B:Information sensitivity determines communication channel access; convenience does not override confidentiality requirements. This failure calls for a decision to use an agreed asynchronous status record plus rotating synchronous windows for decisions requiring discussion. C:Communication integrity requires a traceable account of decisions, not just transmission of status summaries. The required change instead is to use an agreed asynchronous status record plus rotating synchronous windows for decisions requiring discussion.
Question 130A global deployment team schedules live status calls at 3 a.m. for half the participants and begins losing decision-making attendance. Why is the recommended action more appropriate for this situation? Language and cultural barriers can distort instructions even when the same message is broadcast to all parties. Asynchronous records support different time zones; synchronous meetings remain useful for immediate joint decisions. Information sensitivity determines communication channel access; convenience does not override confidentiality requirements. Communication integrity requires a traceable account of decisions, not just transmission of status summaries. ExplanationCorrect Answer B:Asynchronous records support different time zones; synchronous meetings remain useful for immediate joint decisions. It supports this case-specific action: Use an agreed asynchronous status record plus rotating synchronous windows for decisions requiring discussion. The relevant proof is: Review response rates and documented approvals from each region after the revised communication cadence. Other Answers A:Language and cultural barriers can distort instructions even when the same message is broadcast to all parties. By contrast, asynchronous records support different time zones; synchronous meetings remain useful for immediate joint decisions. C:Information sensitivity determines communication channel access; convenience does not override confidentiality requirements. In the stated system, asynchronous records support different time zones; synchronous meetings remain useful for immediate joint decisions. D:Communication integrity requires a traceable account of decisions, not just transmission of status summaries. In the stated system, asynchronous records support different time zones; synchronous meetings remain useful for immediate joint decisions.