Question 300An Agile team promises a three-month release but its backlog contains only epics without smaller estimable work items. Which governance control should be retained for future work? Review scope completeness with operations before baselining the project plan. Require measurable acceptance gates before adding a release milestone to the baseline. Reserve scarce operational specialists as soon as approved work packages are scheduled. Hold backlog refinement before sprint planning to control uncertainty. ExplanationCorrect Answer D:Hold backlog refinement before sprint planning to control uncertainty. The control prevents recurrence because estimating a release requires sufficiently sliced work and known acceptance conditions, not broad unbounded epics. The immediate corrective step remains: Refine epics into actionable backlog items with acceptance criteria before commitment-based sprint forecasting. Other Answers A:A detailed scope baseline decomposes authorized outcomes into verifiable work and exposes omissions. A more direct preventive measure is to hold backlog refinement before sprint planning to control uncertainty. B:Quality planning defines what success must be proven before transition, rather than relying on a deployment date alone. The lasting safeguard is to hold backlog refinement before sprint planning to control uncertainty. C:Resource planning aligns actual capacity to the schedule before work is committed. A more direct preventive measure is to hold backlog refinement before sprint planning to control uncertainty.
Question 301A data-center relocation schedule lists tasks but no baseline milestone dates or dependencies approved by the sponsor. What action most directly resolves the specific project-management problem? Develop an integrated schedule with task sequencing, key milestones, and an approved baseline. Assess resource availability and assign named or role-based people to each clinic milestone. Develop a detailed scope statement and WBS with explicit included deliverables and acceptance boundaries. Prepare a cost baseline covering vendor, transition, contingency, and support activities associated with approved scope. ExplanationCorrect Answer A:Schedule baselines provide a controlled performance reference and expose critical dependency timing. To confirm, compare the approved milestone table with the network diagram and allocated resources. Other Answers B:Resource planning aligns actual capacity to the schedule before work is committed. A more relevant action is to develop an integrated schedule with task sequencing, key milestones, and an approved baseline. C:A detailed scope baseline decomposes authorized outcomes into verifiable work and exposes omissions. A more relevant action is to develop an integrated schedule with task sequencing, key milestones, and an approved baseline. D:A credible project budget includes planned lifecycle work, not just initial software development. A more relevant action is to develop an integrated schedule with task sequencing, key milestones, and an approved baseline.
Question 302A data-center relocation schedule lists tasks but no baseline milestone dates or dependencies approved by the sponsor. Why is the recommended action more appropriate for this situation? A detailed scope baseline decomposes authorized outcomes into verifiable work and exposes omissions. Schedule baselines provide a controlled performance reference and expose critical dependency timing. A credible project budget includes planned lifecycle work, not just initial software development. Resource planning aligns actual capacity to the schedule before work is committed. ExplanationCorrect Answer B:Schedule baselines provide a controlled performance reference and expose critical dependency timing. It supports this case-specific action: Develop an integrated schedule with task sequencing, key milestones, and an approved baseline. The relevant proof is: Compare the approved milestone table with the network diagram and allocated resources. Other Answers A:A detailed scope baseline decomposes authorized outcomes into verifiable work and exposes omissions. In the stated system, schedule baselines provide a controlled performance reference and expose critical dependency timing. C:A credible project budget includes planned lifecycle work, not just initial software development. In the stated system, schedule baselines provide a controlled performance reference and expose critical dependency timing. D:Resource planning aligns actual capacity to the schedule before work is committed. In the stated system, schedule baselines provide a controlled performance reference and expose critical dependency timing.
Question 303A data-center relocation schedule lists tasks but no baseline milestone dates or dependencies approved by the sponsor. Which check should be performed before the project lead accepts the correction? Inspect technician allocations and confirm no overlapping clinic assignments exceed availability. Trace manuals and training to approved WBS packages or recorded exclusions. Reconcile each cost element to a WBS package and forecast remaining expenditure. Compare the approved milestone table with the network diagram and allocated resources. ExplanationCorrect Answer D:Compare the approved milestone table with the network diagram and allocated resources. This checks the required decision: Develop an integrated schedule with task sequencing, key milestones, and an approved baseline. It matters because schedule baselines provide a controlled performance reference and expose critical dependency timing. Other Answers A:Resource planning aligns actual capacity to the schedule before work is committed. Proving this correction calls for a check to compare the approved milestone table with the network diagram and allocated resources. B:A detailed scope baseline decomposes authorized outcomes into verifiable work and exposes omissions. Proving this correction calls for a check to compare the approved milestone table with the network diagram and allocated resources. C:A credible project budget includes planned lifecycle work, not just initial software development. Proving this correction calls for a check to compare the approved milestone table with the network diagram and allocated resources.
Question 304A data-center relocation schedule lists tasks but no baseline milestone dates or dependencies approved by the sponsor. Which governance control should be retained for future work? Reserve scarce operational specialists as soon as approved work packages are scheduled. Require change control for baseline commitments while allowing transparent forecast revisions. Require cost signoff from both implementation and receiving operations teams. Review scope completeness with operations before baselining the project plan. ExplanationCorrect Answer B:Require change control for baseline commitments while allowing transparent forecast revisions. The control prevents recurrence because schedule baselines provide a controlled performance reference and expose critical dependency timing. The immediate corrective step remains: Develop an integrated schedule with task sequencing, key milestones, and an approved baseline. Other Answers A:Resource planning aligns actual capacity to the schedule before work is committed. The stronger recurring control is to require change control for baseline commitments while allowing transparent forecast revisions. C:A credible project budget includes planned lifecycle work, not just initial software development. The stronger recurring control is to require change control for baseline commitments while allowing transparent forecast revisions. D:A detailed scope baseline decomposes authorized outcomes into verifiable work and exposes omissions. The stronger recurring control is to require change control for baseline commitments while allowing transparent forecast revisions.
Question 305An insurance upgrade project ignores vendor API unreliability until a failed test blocks integration, although the risk was predictable. What action most directly resolves the specific project-management problem? Prepare a cost baseline covering vendor, transition, contingency, and support activities associated with approved scope. Perform an initial risk assessment with probability, impact, owner, triggers, and responses. Build a QA plan with test cycles, thresholds, roles, and evidence for technical and user acceptance. Develop a transition plan covering training, operational handoff, cutover checks, rollback authority, and stabilization. ExplanationCorrect Answer B:Early planning turns foreseeable uncertainty into managed exposure before it becomes an expensive issue. To confirm, find API failure recorded with an evaluated response and verify a resilience test was planned. Other Answers A:A credible project budget includes planned lifecycle work, not just initial software development. The corrective action for this requirement is to perform an initial risk assessment with probability, impact, owner, triggers, and responses. C:Quality planning defines what success must be proven before transition, rather than relying on a deployment date alone. This failure calls for a decision to perform an initial risk assessment with probability, impact, owner, triggers, and responses. D:Release planning connects delivered technology to ongoing support and user adoption, beyond technical installation. The corrective action for this requirement is to perform an initial risk assessment with probability, impact, owner, triggers, and responses.
Question 306An insurance upgrade project ignores vendor API unreliability until a failed test blocks integration, although the risk was predictable. Why is the recommended action more appropriate for this situation? A credible project budget includes planned lifecycle work, not just initial software development. Quality planning defines what success must be proven before transition, rather than relying on a deployment date alone. Release planning connects delivered technology to ongoing support and user adoption, beyond technical installation. Early planning turns foreseeable uncertainty into managed exposure before it becomes an expensive issue. ExplanationCorrect Answer D:Early planning turns foreseeable uncertainty into managed exposure before it becomes an expensive issue. It supports this case-specific action: Perform an initial risk assessment with probability, impact, owner, triggers, and responses. The relevant proof is: Find API failure recorded with an evaluated response and verify a resilience test was planned. Other Answers A:A credible project budget includes planned lifecycle work, not just initial software development. By contrast, early planning turns foreseeable uncertainty into managed exposure before it becomes an expensive issue. B:Quality planning defines what success must be proven before transition, rather than relying on a deployment date alone. In the stated system, early planning turns foreseeable uncertainty into managed exposure before it becomes an expensive issue. C:Release planning connects delivered technology to ongoing support and user adoption, beyond technical installation. By contrast, early planning turns foreseeable uncertainty into managed exposure before it becomes an expensive issue.
Question 307An insurance upgrade project ignores vendor API unreliability until a failed test blocks integration, although the risk was predictable. Which check should be performed before the project lead accepts the correction? Find API failure recorded with an evaluated response and verify a resilience test was planned. Reconcile each cost element to a WBS package and forecast remaining expenditure. Run a transition rehearsal with support staff and confirm decision authority if cutover fails. Verify test cases cover peak load, reconciliation, and approval by the payment business owner. ExplanationCorrect Answer A:Find API failure recorded with an evaluated response and verify a resilience test was planned. This checks the required decision: Perform an initial risk assessment with probability, impact, owner, triggers, and responses. It matters because early planning turns foreseeable uncertainty into managed exposure before it becomes an expensive issue. Other Answers B:A credible project budget includes planned lifecycle work, not just initial software development. A more meaningful verification is to find API failure recorded with an evaluated response and verify a resilience test was planned. C:Release planning connects delivered technology to ongoing support and user adoption, beyond technical installation. A more meaningful verification is to find API failure recorded with an evaluated response and verify a resilience test was planned. D:Quality planning defines what success must be proven before transition, rather than relying on a deployment date alone. The relevant acceptance check is to find API failure recorded with an evaluated response and verify a resilience test was planned.
Question 308An insurance upgrade project ignores vendor API unreliability until a failed test blocks integration, although the risk was predictable. Which governance control should be retained for future work? Gate production handoff on operational readiness and knowledge transfer records. Reassess high-exposure dependencies at every phase transition. Require cost signoff from both implementation and receiving operations teams. Require measurable acceptance gates before adding a release milestone to the baseline. ExplanationCorrect Answer B:Reassess high-exposure dependencies at every phase transition. The control prevents recurrence because early planning turns foreseeable uncertainty into managed exposure before it becomes an expensive issue. The immediate corrective step remains: Perform an initial risk assessment with probability, impact, owner, triggers, and responses. Other Answers A:Release planning connects delivered technology to ongoing support and user adoption, beyond technical installation. The stronger recurring control is to reassess high-exposure dependencies at every phase transition. C:A credible project budget includes planned lifecycle work, not just initial software development. The stronger recurring control is to reassess high-exposure dependencies at every phase transition. D:Quality planning defines what success must be proven before transition, rather than relying on a deployment date alone. Reducing this risk requires a practice to reassess high-exposure dependencies at every phase transition.
Question 309A field deployment team signs off completed hardware tasks before installing the approved security configuration required by the project plan. What action most directly resolves the specific project-management problem? Track accepted outcomes and rework accurately rather than counting physical installation as completed delivery. Execute and verify the complete defined work packages before reporting them finished. Update the integrated execution plan and coordinate dependent workstreams with the newly approved sequence. Report the material issue and project-wide delivery impact promptly through the planned escalation channel. ExplanationCorrect Answer B:Execution must produce the planned accepted deliverable, not just a visible portion of installation. To confirm, inspect security configuration tests and task acceptance evidence for each deployed site. Other Answers A:Execution progress must reflect deliverable acceptance and quality gaps, not activity alone. The corrective action for this requirement is to execute and verify the complete defined work packages before reporting them finished. C:Controlled execution requires teams to follow the current approved schedule rather than obsolete baselines or undocumented assumptions. The required change instead is to execute and verify the complete defined work packages before reporting them finished. D:Execution tracking must surface risks and issues that affect decisions, not only percent-complete statistics. The corrective action for this requirement is to execute and verify the complete defined work packages before reporting them finished.
Question 310A field deployment team signs off completed hardware tasks before installing the approved security configuration required by the project plan. Why is the recommended action more appropriate for this situation? Execution must produce the planned accepted deliverable, not just a visible portion of installation. Execution tracking must surface risks and issues that affect decisions, not only percent-complete statistics. Execution progress must reflect deliverable acceptance and quality gaps, not activity alone. Controlled execution requires teams to follow the current approved schedule rather than obsolete baselines or undocumented assumptions. ExplanationCorrect Answer A:Execution must produce the planned accepted deliverable, not just a visible portion of installation. It supports this case-specific action: Execute and verify the complete defined work packages before reporting them finished. The relevant proof is: Inspect security configuration tests and task acceptance evidence for each deployed site. Other Answers B:Execution tracking must surface risks and issues that affect decisions, not only percent-complete statistics. In the stated system, execution must produce the planned accepted deliverable, not just a visible portion of installation. C:Execution progress must reflect deliverable acceptance and quality gaps, not activity alone. In the stated system, execution must produce the planned accepted deliverable, not just a visible portion of installation. D:Controlled execution requires teams to follow the current approved schedule rather than obsolete baselines or undocumented assumptions. By contrast, execution must produce the planned accepted deliverable, not just a visible portion of installation.