Question 110A sponsor wants the approved project end date moved after a two-day variance, but no scope or authorized commitment changed. Why is the recommended action more appropriate for this situation? The critical path is the longest dependency sequence; delay on it changes the projected finish absent recovery. Story points express relative effort or complexity; actual team throughput informs capacity forecasts over iterations. A forecast records expected performance; rebaselining changes the approved reference and requires change authorization. Mandatory task dependencies constrain the schedule; a successor cannot safely start before its required predecessor output exists. ExplanationCorrect Answer C:A forecast records expected performance; rebaselining changes the approved reference and requires change authorization. It supports this case-specific action: Update the current forecast and variance commentary without automatically rebaselining the approved schedule. The relevant proof is: Compare original baseline, current forecast, and variance log to confirm historical performance remains visible. Other Answers A:The critical path is the longest dependency sequence; delay on it changes the projected finish absent recovery. By contrast, a forecast records expected performance; rebaselining changes the approved reference and requires change authorization. B:Story points express relative effort or complexity; actual team throughput informs capacity forecasts over iterations. By contrast, a forecast records expected performance; rebaselining changes the approved reference and requires change authorization. D:Mandatory task dependencies constrain the schedule; a successor cannot safely start before its required predecessor output exists. By contrast, a forecast records expected performance; rebaselining changes the approved reference and requires change authorization.
Question 111A sponsor wants the approved project end date moved after a two-day variance, but no scope or authorized commitment changed. Which check should be performed before the project lead accepts the correction? Compare original baseline, current forecast, and variance log to confirm historical performance remains visible. Compare planned story points, completed velocity, and release forecast over several sprints. Inspect the network diagram and check that conversion begins only after source approval evidence. Recalculate early and late dates after the delay and verify the launch-date sensitivity. ExplanationCorrect Answer A:Compare original baseline, current forecast, and variance log to confirm historical performance remains visible. This checks the required decision: Update the current forecast and variance commentary without automatically rebaselining the approved schedule. It matters because a forecast records expected performance; rebaselining changes the approved reference and requires change authorization. Other Answers B:Story points express relative effort or complexity; actual team throughput informs capacity forecasts over iterations. The relevant acceptance check is to compare original baseline, current forecast, and variance log to confirm historical performance remains visible. C:Mandatory task dependencies constrain the schedule; a successor cannot safely start before its required predecessor output exists. The relevant acceptance check is to compare original baseline, current forecast, and variance log to confirm historical performance remains visible. D:The critical path is the longest dependency sequence; delay on it changes the projected finish absent recovery. The relevant acceptance check is to compare original baseline, current forecast, and variance log to confirm historical performance remains visible.
Question 112A sponsor wants the approved project end date moved after a two-day variance, but no scope or authorized commitment changed. Which governance control should be retained for future work? Recalibrate estimates from completed work instead of treating point values as universal hours. Define thresholds distinguishing forecast updates from approved baseline changes. Review predecessor relationships during planning whenever tasks consume other teams' deliverables. Refresh critical-path analysis after dependency, duration, or resource changes. ExplanationCorrect Answer B:Define thresholds distinguishing forecast updates from approved baseline changes. The control prevents recurrence because a forecast records expected performance; rebaselining changes the approved reference and requires change authorization. The immediate corrective step remains: Update the current forecast and variance commentary without automatically rebaselining the approved schedule. Other Answers A:Story points express relative effort or complexity; actual team throughput informs capacity forecasts over iterations. Reducing this risk requires a practice to define thresholds distinguishing forecast updates from approved baseline changes. C:Mandatory task dependencies constrain the schedule; a successor cannot safely start before its required predecessor output exists. Reducing this risk requires a practice to define thresholds distinguishing forecast updates from approved baseline changes. D:The critical path is the longest dependency sequence; delay on it changes the projected finish absent recovery. Reducing this risk requires a practice to define thresholds distinguishing forecast updates from approved baseline changes.
Question 113A delivery team completes automated unit tests but has not shown business users that payroll workflows satisfy acceptance needs. What action most directly resolves the specific project-management problem? Investigate performance testing failures before confirming the nonfunctional quality gate. 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. Separate the product review of outcomes from a retrospective focused on how the team will improve delivery. ExplanationCorrect Answer B:Technical component testing checks code behavior; validation asks whether the completed solution meets user needs. To confirm, capture business-user test execution and explicit acceptance against the signed payroll scenarios. Other Answers A:Functional completeness does not demonstrate performance requirements such as throughput and response latency. The required change instead is to conduct user acceptance testing against signed business scenarios before declaring the deliverable accepted. C:Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. This failure calls for a decision to conduct user acceptance testing against signed business scenarios before declaring the deliverable accepted. D:A sprint review inspects the product increment; a retrospective inspects collaboration and process effectiveness. This failure calls for a decision to conduct user acceptance testing against signed business scenarios before declaring the deliverable accepted.
Question 114A delivery team completes automated unit tests but has not shown business users that payroll workflows satisfy acceptance needs. Why is the recommended action more appropriate for this situation? A sprint review inspects the product increment; a retrospective inspects collaboration and process effectiveness. Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. 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. ExplanationCorrect Answer C:Technical component testing checks code behavior; validation asks whether the completed solution meets user needs. It supports this case-specific action: Conduct user acceptance testing against signed business scenarios before declaring the deliverable accepted. The relevant proof is: Capture business-user test execution and explicit acceptance against the signed payroll scenarios. Other Answers A:A sprint review inspects the product increment; a retrospective inspects collaboration and process effectiveness. By contrast, technical component testing checks code behavior; validation asks whether the completed solution meets user needs. B:Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. By contrast, technical component testing checks code behavior; validation asks whether the completed solution meets user needs. D:Functional completeness does not demonstrate performance requirements such as throughput and response latency. In the stated system, technical component testing checks code behavior; validation asks whether the completed solution meets user needs.
Question 115A delivery team completes automated unit tests but has not shown business users that payroll workflows satisfy acceptance needs. 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. Find both documented product backlog changes and an actionable improvement from the team retrospective. ExplanationCorrect Answer B:Capture business-user test execution and explicit acceptance against the signed payroll scenarios. This checks the required decision: Conduct user acceptance testing against signed business scenarios before declaring the deliverable accepted. It matters because technical component testing checks code behavior; validation asks whether the completed solution meets user needs. Other Answers A:Functional completeness does not demonstrate performance requirements such as throughput and response latency. Proving this correction calls for a check to capture business-user test execution and explicit acceptance against the signed payroll scenarios. 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 capture business-user test execution and explicit acceptance against the signed payroll scenarios. D:A sprint review inspects the product increment; a retrospective inspects collaboration and process effectiveness. The failure is checked more directly by a test to capture business-user test execution and explicit acceptance against the signed payroll scenarios.
Question 116A delivery team completes automated unit tests but has not shown business users that payroll workflows satisfy acceptance needs. Which governance control should be retained for future work? Define progress measurement and reporting rules before collecting earned-value metrics. Define user-validation criteria separately from unit and integration test success. Add capacity and stress thresholds to the project quality management plan. Reserve separate time for product acceptance and team learning in each iteration. ExplanationCorrect Answer B:Define user-validation criteria separately from unit and integration test success. The control prevents recurrence because technical component testing checks code behavior; validation asks whether the completed solution meets user needs. The immediate corrective step remains: Conduct user acceptance testing against signed business scenarios before declaring the deliverable accepted. Other Answers A:Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. Reducing this risk requires a practice to define user-validation criteria separately from unit and integration test success. C:Functional completeness does not demonstrate performance requirements such as throughput and response latency. A more direct preventive measure is to define user-validation criteria separately from unit and integration test success. D:A sprint review inspects the product increment; a retrospective inspects collaboration and process effectiveness. Reducing this risk requires a practice to define user-validation criteria separately from unit and integration test success.
Question 117An application release meets every planned feature requirement, but a load test fails under anticipated seasonal traffic. 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. Investigate performance testing failures before confirming the nonfunctional quality gate. Conduct user acceptance testing against signed business scenarios before declaring the deliverable accepted. Activate a spare test environment and declare the performance requirement met without rerunning representative load tests. ExplanationCorrect Answer B:Functional completeness does not demonstrate performance requirements such as throughput and response latency. To confirm, repeat a representative load test and compare response times against approved service thresholds. 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 investigate performance testing failures before confirming the nonfunctional quality gate. C:Technical component testing checks code behavior; validation asks whether the completed solution meets user needs. This failure calls for a decision to investigate performance testing failures before confirming the nonfunctional quality gate. D:Activate a spare test environment and declare the performance requirement met without rerunning representative load tests. The failure is unacceptable throughput under seasonal demand, not environment availability; a spare test environment does not prove capacity. The controlling constraint in this case is: Functional completeness does not demonstrate performance requirements such as throughput and response latency.
Question 118An application release meets every planned feature requirement, but a load test fails under anticipated seasonal traffic. Why is the recommended action more appropriate for this situation? Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. Availability of a backup testing environment proves that the application will meet seasonal traffic loads. 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. ExplanationCorrect Answer D:Functional completeness does not demonstrate performance requirements such as throughput and response latency. It supports this case-specific action: Investigate performance testing failures before confirming the nonfunctional quality gate. The relevant proof is: Repeat a representative load test and compare response times against approved service thresholds. Other Answers A:Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. In the stated system, functional completeness does not demonstrate performance requirements such as throughput and response latency. B:Availability of a backup testing environment proves that the application will meet seasonal traffic loads. Environment redundancy is not equivalent to measured response time and throughput under the required load profile. The controlling constraint in this case is: Functional completeness does not demonstrate performance requirements such as throughput and response latency. C:Technical component testing checks code behavior; validation asks whether the completed solution meets user needs. In the stated system, functional completeness does not demonstrate performance requirements such as throughput and response latency.
Question 119An application release meets every planned feature requirement, but a load test fails under anticipated seasonal traffic. Which check should be performed before the project lead accepts the correction? Capture business-user test execution and explicit acceptance against the signed payroll scenarios. Record that the fallback test environment started, without collecting any response-time or throughput observations. Repeat a representative load test and compare response times against approved service thresholds. Reconcile the work-package percent complete with PV, EV, and the resulting schedule variance. ExplanationCorrect Answer C:Repeat a representative load test and compare response times against approved service thresholds. This checks the required decision: Investigate performance testing failures before confirming the nonfunctional quality gate. It matters because functional completeness does not demonstrate performance requirements such as throughput and response latency. Other Answers A:Technical component testing checks code behavior; validation asks whether the completed solution meets user needs. Proving this correction calls for a check to repeat a representative load test and compare response times against approved service thresholds. B:Record that the fallback test environment started, without collecting any response-time or throughput observations. A startup check cannot establish whether peak traffic meets the approved nonfunctional service thresholds. The controlling constraint in this case is: Functional completeness does not demonstrate performance requirements such as throughput and response latency. D:Schedule variance compares earned value to planned value; actual costs alone cannot establish schedule progress. Proving this correction calls for a check to repeat a representative load test and compare response times against approved service thresholds.
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.