PMI CAPM Practice Test 78
Question 770
For an original CAPM project delivery study scenario, consider: A retail program specifies a barcode scanner model as its business requirement even though the actual goal is reliable inventory accuracy across locations. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Treat a preferred vendor product name as the entire business objective and reject analysis of alternative solutions.
- Change: Distinguish the business outcome, stakeholder capability needs and solution-specific functional or quality requirements before selecting implementation.
- Check: Trace each proposed feature to business objectives, stakeholder impacts, assumptions and alternative solution options.
- Change: Adapt business-analysis artifacts and approval cadence to the delivery approach while preserving traceability, stakeholder decision ownership and acceptance clarity.
- Check: Compare requirement intent, test inputs, expected outputs, error cases, objective thresholds and stakeholder sign-off needs.
Explanation
Correct Answer
B:High-level business requirements explain why change matters; solution requirements detail what must be provided to satisfy those needs. Acceptance: The chosen design has defensible requirement lineage and can be changed without losing the underlying business problem.
C:High-level business requirements explain why change matters; solution requirements detail what must be provided to satisfy those needs. Required intervention: Distinguish the business outcome, stakeholder capability needs and solution-specific functional or quality requirements before selecting implementation.
Incorrect Answers
A:High-level business requirements explain why change matters; solution requirements detail what must be provided to satisfy those needs.
D:Change: Adapt business-analysis artifacts and approval cadence to the delivery approach while preserving traceability, stakeholder decision ownership and acceptance clarity. A retail program specifies a barcode scanner model as its business requirement even though the actual goal is reliable inventory accuracy across locations.
E:Check: Compare requirement intent, test inputs, expected outputs, error cases, objective thresholds and stakeholder sign-off needs. High-level business requirements explain why change matters; solution requirements detail what must be provided to satisfy those needs.
Question 771
A CAPM project team analyst is reviewing this delivery scenario: A relief-data portal has a mandatory legal accessibility requirement and optional decorative charts, but its team calls both Must Have while the release date is fixed. An unsafe shortcut would be: Label every requested feature Must Have to avoid difficult tradeoffs and assume the release date remains attainable. What should the project team analyst recommend as the narrowly scoped correction? Select ONE best answer.
- Classify requirements as Must, Should, Could or Won't for the current scope based on stakeholder value, obligations, feasibility and transparent decision rules.
- Identify relevant internal and external stakeholders, their interests, influence, authority and information needs before agreeing requirement coverage.
- Confirm candidate release scope against approved requirements or backlog, acceptance evidence, unresolved defects, traceability and appropriate owner decisions.
- Label every requested feature Must Have to avoid difficult tradeoffs and assume the release date remains attainable.
Explanation
Correct Answer
A:MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
Incorrect Answers
B:Identify relevant internal and external stakeholders, their interests, influence, authority and information needs before agreeing requirement coverage. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
C:Confirm candidate release scope against approved requirements or backlog, acceptance evidence, unresolved defects, traceability and appropriate owner decisions. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
D:MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
Question 772
A project delivery review finds: A relief-data portal has a mandatory legal accessibility requirement and optional decorative charts, but its team calls both Must Have while the release date is fixed. The team proposes: Classify requirements as Must, Should, Could or Won't for the current scope based on stakeholder value, obligations, feasibility and transparent decision rules. Which project management principle most strongly supports the proposed response? Select ONE best answer.
- Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
- Interviews discover detailed individual context but are vulnerable to bias, missing perspectives and unverified interpretation.
- MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
- Stakeholder maps help reveal conflicting value expectations and overlooked affected groups whose participation is needed for valid requirements.
Explanation
Correct Answer
C:Demonstrable success requires: Delivery includes essential obligations and gives decision makers a visible credible set of deferrable enhancements. This principle explains the proposed project response, which is: Classify requirements as Must, Should, Could or Won't for the current scope based on stakeholder value, obligations, feasibility and transparent decision rules.
Incorrect Answers
A:Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
B:Interviews discover detailed individual context but are vulnerable to bias, missing perspectives and unverified interpretation. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
D:Stakeholder maps help reveal conflicting value expectations and overlooked affected groups whose participation is needed for valid requirements. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
Question 773
The project team has not approved a broad project-plan change. Available evidence indicates: A relief-data portal has a mandatory legal accessibility requirement and optional decorative charts, but its team calls both Must Have while the release date is fixed. Which evidence best tests the project diagnosis before approving a disruptive change? Select ONE best answer.
- Check strategic objectives, user outcomes, roadmap horizon confidence, dependencies and decision rights for proposed additions.
- Compare requirement intent, test inputs, expected outputs, error cases, objective thresholds and stakeholder sign-off needs.
- Compare business criticality, statutory constraints, dependency links, effort, sponsor agreement and explicit exclusions for the planned release.
- Review participant roles, mapped disagreements, facilitator agenda, decision evidence and action ownership after the session.
Explanation
Correct Answer
C:MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
Incorrect Answers
A:Check strategic objectives, user outcomes, roadmap horizon confidence, dependencies and decision rights for proposed additions. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
B:Compare requirement intent, test inputs, expected outputs, error cases, objective thresholds and stakeholder sign-off needs. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
D:This option addresses a different CAPM project management topic (Facilitated requirements workshops) rather than the documented MoSCoW prioritization with fixed deadlines decision.
Question 774
A candidate project response has been piloted and stakeholders require a post-change acceptance check. Original problem: A relief-data portal has a mandatory legal accessibility requirement and optional decorative charts, but its team calls both Must Have while the release date is fixed. The accountable project owner requires evidence that outcomes are met without disrupting planned work. Which acceptance result demonstrates that the project response meets the intended outcome? Select ONE best answer.
- Process changes and product priorities have accountable owners while analysts supply clear evidence and avoid unauthorized sign-off.
- Delivery includes essential obligations and gives decision makers a visible credible set of deferrable enhancements.
- Every required capability has traceable verification and unexpected functionality can be justified through an approved change.
- Delivery and acceptance use one approved requirement version and all dependent artifacts reflect authorized decisions.
Explanation
Correct Answer
B:MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory. The approved implementation step was: Classify requirements as Must, Should, Could or Won't for the current scope based on stakeholder value, obligations, feasibility and transparent decision rules.
Incorrect Answers
A:Process changes and product priorities have accountable owners while analysts supply clear evidence and avoid unauthorized sign-off. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
C:Every required capability has traceable verification and unexpected functionality can be justified through an approved change. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
D:Delivery and acceptance use one approved requirement version and all dependent artifacts reflect authorized decisions. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
Question 775
An implementation sign-off request identifies the following problem: A relief-data portal has a mandatory legal accessibility requirement and optional decorative charts, but its team calls both Must Have while the release date is fixed. Which paired project management action and verification should close the review? Select ONE best answer.
- Change: Convert expectations into observable acceptance criteria with measurable thresholds, normal cases, failure behavior and appropriate authorized stakeholder approval. Verify: Compare requirement intent, test inputs, expected outputs, error cases, objective thresholds and stakeholder sign-off needs.
- Change: Surface conflicting needs, assess regulatory and business constraints, facilitate tradeoffs and document a decision by the appropriate accountable owner. Verify: Compare conflicting statements, source authority, constraints, feasible alternatives, decision log and downstream design effects.
- Change: Observe real users in context and record actual tasks, exceptions and workarounds, then validate observations with responsible participants. Verify: Compare observed work sequence, timings, exceptional conditions, privacy permissions and stakeholder confirmation of what was recorded.
- Change: Classify requirements as Must, Should, Could or Won't for the current scope based on stakeholder value, obligations, feasibility and transparent decision rules. Verify: Compare business criticality, statutory constraints, dependency links, effort, sponsor agreement and explicit exclusions for the planned release.
Explanation
Correct Answer
D:MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
Incorrect Answers
A:Change: Convert expectations into observable acceptance criteria with measurable thresholds, normal cases, failure behavior and appropriate authorized stakeholder approval. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
B:Change: Surface conflicting needs, assess regulatory and business constraints, facilitate tradeoffs and document a decision by the appropriate accountable owner. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
C:Change: Observe real users in context and record actual tasks, exceptions and workarounds, then validate observations with responsible participants.
Question 776
A CAPM project team analyst is reviewing this delivery scenario: A library modernization requests many integrations but lacks agreement on which features are essential for basic loan processing on launch day. An unsafe shortcut would be: Label every requested feature Must Have to avoid difficult tradeoffs and assume the release date remains attainable. What should the project team analyst recommend as the narrowly scoped correction? Select ONE best answer.
- Classify requirements as Must, Should, Could or Won't for the current scope based on stakeholder value, obligations, feasibility and transparent decision rules.
- Choose surveys for broad standardized input and focus groups for facilitated qualitative interaction, using careful sampling and bias controls.
- Conduct planned open and probing interviews with representative role holders, capture exceptions and confirm findings against source processes.
- Label every requested feature Must Have to avoid difficult tradeoffs and assume the release date remains attainable.
Explanation
Correct Answer
A:MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
Incorrect Answers
B:Choose surveys for broad standardized input and focus groups for facilitated qualitative interaction, using careful sampling and bias controls. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
C:Conduct planned open and probing interviews with representative role holders, capture exceptions and confirm findings against source processes. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
D:MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory. Use this instead: Classify requirements as Must, Should, Could or Won't for the current scope based on stakeholder value, obligations, feasibility and transparent decision rules.
Question 777
A project delivery review finds: A library modernization requests many integrations but lacks agreement on which features are essential for basic loan processing on launch day. The team proposes: Classify requirements as Must, Should, Could or Won't for the current scope based on stakeholder value, obligations, feasibility and transparent decision rules. Which project management principle most strongly supports the proposed response? Select ONE best answer.
- MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
- Stakeholder maps help reveal conflicting value expectations and overlooked affected groups whose participation is needed for valid requirements.
- Elicitation finds claims, not automatically compatible requirements; reconciliation needs source context and governing priorities.
- Direct observation reveals tacit steps and operational constraints that interview memory or stated policy may omit.
Explanation
Correct Answer
A:Demonstrable success requires: Delivery includes essential obligations and gives decision makers a visible credible set of deferrable enhancements.
Incorrect Answers
B:Stakeholder maps help reveal conflicting value expectations and overlooked affected groups whose participation is needed for valid requirements. A library modernization requests many integrations but lacks agreement on which features are essential for basic loan processing on launch day.
C:Elicitation finds claims, not automatically compatible requirements; reconciliation needs source context and governing priorities. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
D:Direct observation reveals tacit steps and operational constraints that interview memory or stated policy may omit. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
Question 778
The project team has not approved a broad project-plan change. Available evidence indicates: A library modernization requests many integrations but lacks agreement on which features are essential for basic loan processing on launch day. Which evidence best tests the project diagnosis before approving a disruptive change? Select ONE best answer.
- Review business actors, scenario variants, error conditions, acceptance needs and documentation burden against delivery context.
- Compare business criticality, statutory constraints, dependency links, effort, sponsor agreement and explicit exclusions for the planned release.
- Check audience sampling, response rate, question neutrality, moderation, demographic coverage and consistency with behavioral evidence.
- Examine UAT cases, representative testers, outcomes, defect disposition, waivers and evidence of accountable owner approval.
Explanation
Correct Answer
B:MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
Incorrect Answers
A:Review business actors, scenario variants, error conditions, acceptance needs and documentation burden against delivery context. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
C:Check audience sampling, response rate, question neutrality, moderation, demographic coverage and consistency with behavioral evidence. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
D:Examine UAT cases, representative testers, outcomes, defect disposition, waivers and evidence of accountable owner approval. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
Question 779
A candidate project response has been piloted and stakeholders require a post-change acceptance check. Original problem: A library modernization requests many integrations but lacks agreement on which features are essential for basic loan processing on launch day. The accountable project owner requires evidence that outcomes are met without disrupting planned work. Which acceptance result demonstrates that the project response meets the intended outcome? Select ONE best answer.
- The approved requirement set resolves contradictions or transparently records open decisions without silently privileging one stakeholder.
- Every required capability has traceable verification and unexpected functionality can be justified through an approved change.
- Delivery includes essential obligations and gives decision makers a visible credible set of deferrable enhancements.
- The team documents concrete needs and exceptions with traceable sources and no unsupported assumption that one role speaks for everyone.
Explanation
Correct Answer
C:MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
Incorrect Answers
A:The approved requirement set resolves contradictions or transparently records open decisions without silently privileging one stakeholder. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
B:Every required capability has traceable verification and unexpected functionality can be justified through an approved change. A library modernization requests many integrations but lacks agreement on which features are essential for basic loan processing on launch day.
D:The team documents concrete needs and exceptions with traceable sources and no unsupported assumption that one role speaks for everyone. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
Question 780
For an original CAPM project delivery study scenario, consider: A library modernization requests many integrations but lacks agreement on which features are essential for basic loan processing on launch day. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Compare business criticality, statutory constraints, dependency links, effort, sponsor agreement and explicit exclusions for the planned release.
- Check: Check strategic objectives, user outcomes, roadmap horizon confidence, dependencies and decision rights for proposed additions.
- Change: Identify relevant internal and external stakeholders, their interests, influence, authority and information needs before agreeing requirement coverage.
- Label every requested feature Must Have to avoid difficult tradeoffs and assume the release date remains attainable.
- Change: Classify requirements as Must, Should, Could or Won't for the current scope based on stakeholder value, obligations, feasibility and transparent decision rules.
Explanation
Correct Answer
A:MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory. Required intervention: Classify requirements as Must, Should, Could or Won't for the current scope based on stakeholder value, obligations, feasibility and transparent decision rules.
E:MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory. Evidence: Compare business criticality, statutory constraints, dependency links, effort, sponsor agreement and explicit exclusions for the planned release.
Incorrect Answers
B:Check: Check strategic objectives, user outcomes, roadmap horizon confidence, dependencies and decision rights for proposed additions. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
C:Change: Identify relevant internal and external stakeholders, their interests, influence, authority and information needs before agreeing requirement coverage. MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
D:MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.