PMI CAPM Practice Test 90
Question 890
For an original CAPM project delivery study scenario, consider: Two regional teams demand different date formats and data retention durations, but the requirements log records one global rule without source attribution. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Compare conflicting statements, source authority, constraints, feasible alternatives, decision log and downstream design effects.
- Change: Record the proposed requirement change, assess affected design, tests and stakeholder commitments, and maintain a controlled approved version before implementation.
- Insert contradictory instructions into the same acceptance test and expect the implementation to satisfy both automatically.
- Check: Review prototype fidelity, tested user tasks, observed failures, accessibility evidence and changes recorded for product decisions.
- Change: Surface conflicting needs, assess regulatory and business constraints, facilitate tradeoffs and document a decision by the appropriate accountable owner.
Explanation
Correct Answer
A:Required intervention: Surface conflicting needs, assess regulatory and business constraints, facilitate tradeoffs and document a decision by the appropriate accountable owner.
E:Acceptance: The approved requirement set resolves contradictions or transparently records open decisions without silently privileging one stakeholder.
Incorrect Answers
B:Change: Record the proposed requirement change, assess affected design, tests and stakeholder commitments, and maintain a controlled approved version before implementation. Elicitation finds claims, not automatically compatible requirements; reconciliation needs source context and governing priorities.
C:Elicitation finds claims, not automatically compatible requirements; reconciliation needs source context and governing priorities.
D:Check: Review prototype fidelity, tested user tasks, observed failures, accessibility evidence and changes recorded for product decisions. Elicitation finds claims, not automatically compatible requirements; reconciliation needs source context and governing priorities.
Question 891
A CAPM project team analyst is reviewing this delivery scenario: A product owner marks a release ready because all stories are moved to Done, but two mandatory contract requirements have no linked verification evidence. An unsafe shortcut would be: Declare readiness based only on the percentage of tickets closed without checking mandatory coverage or current requirement versions. What should the project team analyst recommend as the narrowly scoped correction? Select ONE best answer.
- Declare readiness based only on the percentage of tickets closed without checking mandatory coverage or current requirement versions.
- Model the current flow, bottlenecks, roles and decision points, then design a validated future flow that addresses the business need and required controls.
- Observe real users in context and record actual tasks, exceptions and workarounds, then validate observations with responsible participants.
- Confirm candidate release scope against approved requirements or backlog, acceptance evidence, unresolved defects, traceability and appropriate owner decisions.
Explanation
Correct Answer
D:Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
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.
B:This option addresses a different CAPM project management topic (Current-state and future-state process mapping) rather than the documented Delivery readiness through traceability and backlog evidence decision.
C:Observe real users in context and record actual tasks, exceptions and workarounds, then validate observations with responsible participants. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
Question 892
A project delivery review finds: A product owner marks a release ready because all stories are moved to Done, but two mandatory contract requirements have no linked verification evidence. The team proposes: Confirm candidate release scope against approved requirements or backlog, acceptance evidence, unresolved defects, traceability and appropriate owner decisions. 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.
- High-level business requirements explain why change matters; solution requirements detail what must be provided to satisfy those needs.
- MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory.
- Interviews discover detailed individual context but are vulnerable to bias, missing perspectives and unverified interpretation.
Explanation
Correct Answer
A:Demonstrable success requires: Each mandatory current requirement has verified evidence and any deferred condition is explicitly accepted by the authorized party.
Incorrect Answers
B:This option addresses a different CAPM project management topic (Business needs versus stakeholder and solution requirements) rather than the documented Delivery readiness through traceability and backlog evidence decision.
C:MoSCoW helps negotiate scope; priorities are contextual to the release and should not make every desirable feature mandatory. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
D:Interviews discover detailed individual context but are vulnerable to bias, missing perspectives and unverified interpretation. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
Question 893
The project team has not approved a broad project-plan change. Available evidence indicates: A product owner marks a release ready because all stories are moved to Done, but two mandatory contract requirements have no linked verification evidence. Which evidence best tests the project diagnosis before approving a disruptive change? Select ONE best answer.
- Compare requirement intent, test inputs, expected outputs, error cases, objective thresholds and stakeholder sign-off needs.
- Compare conflicting statements, source authority, constraints, feasible alternatives, decision log and downstream design effects.
- Review prototype fidelity, tested user tasks, observed failures, accessibility evidence and changes recorded for product decisions.
- Cross-check latest requirement versions, backlog items, test results, critical issues and stakeholder sign-off for the exact release build.
Explanation
Correct Answer
D:Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
Incorrect Answers
A:Compare requirement intent, test inputs, expected outputs, error cases, objective thresholds and stakeholder sign-off needs. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
B:Compare conflicting statements, source authority, constraints, feasible alternatives, decision log and downstream design effects. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
C:This option addresses a different CAPM project management topic (Prototypes and iterative requirements discovery) rather than the documented Delivery readiness through traceability and backlog evidence decision.
Question 894
A candidate project response has been piloted and stakeholders require a post-change acceptance check. Original problem: A product owner marks a release ready because all stories are moved to Done, but two mandatory contract requirements have no linked verification evidence. 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 requirements record includes appropriate affected representatives and explicitly resolves whose approval is necessary.
- Each mandatory current requirement has verified evidence and any deferred condition is explicitly accepted by the authorized party.
- The product addresses the intended user problem and the released behaviors are supported by conformance evidence.
- Process changes and product priorities have accountable owners while analysts supply clear evidence and avoid unauthorized sign-off.
Explanation
Correct Answer
B:Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
Incorrect Answers
A:The requirements record includes appropriate affected representatives and explicitly resolves whose approval is necessary. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
C:The product addresses the intended user problem and the released behaviors are supported by conformance evidence. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
D:Process changes and product priorities have accountable owners while analysts supply clear evidence and avoid unauthorized sign-off. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
Question 895
An implementation sign-off request identifies the following problem: A product owner marks a release ready because all stories are moved to Done, but two mandatory contract requirements have no linked verification evidence. Which paired project management action and verification should close the review? Select ONE best answer.
- Change: Confirm candidate release scope against approved requirements or backlog, acceptance evidence, unresolved defects, traceability and appropriate owner decisions. Verify: Cross-check latest requirement versions, backlog items, test results, critical issues and stakeholder sign-off for the exact release build.
- Change: Clarify who owns process outcomes, product value and backlog decisions, and who elicits, analyzes and communicates requirements in the chosen delivery approach. Verify: Inspect responsibility assignments, decision rights, backlog ownership, stakeholder approvals and actual requirements-analysis participation.
- Change: Translate selected roadmap goals into a bounded release plan with candidate components, dependencies and acceptance conditions, while retaining higher-level strategy separately. Verify: Compare roadmap themes, release candidate list, dependency constraints, capacity and explicit approval of release acceptance criteria.
- 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.
Explanation
Correct Answer
A:Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
Incorrect Answers
B:Change: Clarify who owns process outcomes, product value and backlog decisions, and who elicits, analyzes and communicates requirements in the chosen delivery approach. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
C:This option addresses a different CAPM project management topic (Roadmap versus release plan distinction) rather than the documented Delivery readiness through traceability and backlog evidence decision.
D:Change: Convert expectations into observable acceptance criteria with measurable thresholds, normal cases, failure behavior and appropriate authorized stakeholder approval. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
Question 896
A CAPM project team analyst is reviewing this delivery scenario: A safety-critical service has complete test reports for old specifications, while recently approved changes remain outside the tested release candidate. An unsafe shortcut would be: Declare readiness based only on the percentage of tickets closed without checking mandatory coverage or current requirement versions. What should the project team analyst recommend as the narrowly scoped correction? Select ONE best answer.
- Declare readiness based only on the percentage of tickets closed without checking mandatory coverage or current requirement versions.
- Identify relevant internal and external stakeholders, their interests, influence, authority and information needs before agreeing requirement coverage.
- Classify requirements as Must, Should, Could or Won't for the current scope based on stakeholder value, obligations, feasibility and transparent decision rules.
- Confirm candidate release scope against approved requirements or backlog, acceptance evidence, unresolved defects, traceability and appropriate owner decisions.
Explanation
Correct Answer
D:Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
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.
B:Identify relevant internal and external stakeholders, their interests, influence, authority and information needs before agreeing requirement coverage. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
C:Classify requirements as Must, Should, Could or Won't for the current scope based on stakeholder value, obligations, feasibility and transparent decision rules. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
Question 897
A project delivery review finds: A safety-critical service has complete test reports for old specifications, while recently approved changes remain outside the tested release candidate. The team proposes: Confirm candidate release scope against approved requirements or backlog, acceptance evidence, unresolved defects, traceability and appropriate owner decisions. Which project management principle most strongly supports the proposed response? Select ONE best answer.
- Artifacts should match behavioral complexity and risk; user stories and use cases serve complementary purposes rather than being universally interchangeable.
- Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
- Backlog ordering is a dynamic decision; relative value and constraints affect the sequence in which requirements should be delivered.
- Business analysis supports informed decisions, but domain accountability and product prioritization remain with their designated owners unless formally delegated.
Explanation
Correct Answer
B:Demonstrable success requires: Each mandatory current requirement has verified evidence and any deferred condition is explicitly accepted by the authorized party.
Incorrect Answers
A:This option addresses a different CAPM project management topic (User stories versus detailed use cases) rather than the documented Delivery readiness through traceability and backlog evidence decision.
C:Backlog ordering is a dynamic decision; relative value and constraints affect the sequence in which requirements should be delivered. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
D:Business analysis supports informed decisions, but domain accountability and product prioritization remain with their designated owners unless formally delegated. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
Question 898
The project team has not approved a broad project-plan change. Available evidence indicates: A safety-critical service has complete test reports for old specifications, while recently approved changes remain outside the tested release candidate. Which evidence best tests the project diagnosis before approving a disruptive change? Select ONE best answer.
- Audit requirement IDs, source stakeholders, implementation links, test-case results and orphaned or uncovered items.
- Examine question design, participant coverage, interview notes, exception scenarios and playback confirmation with respondents.
- Cross-check latest requirement versions, backlog items, test results, critical issues and stakeholder sign-off for the exact release build.
- Check audience sampling, response rate, question neutrality, moderation, demographic coverage and consistency with behavioral evidence.
Explanation
Correct Answer
C:Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count. This check evaluates the actual project, quality or delivery decision before a risky project-wide change.
Incorrect Answers
A:Audit requirement IDs, source stakeholders, implementation links, test-case results and orphaned or uncovered items. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
B:Examine question design, participant coverage, interview notes, exception scenarios and playback confirmation with respondents. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
D:Check audience sampling, response rate, question neutrality, moderation, demographic coverage and consistency with behavioral evidence. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
Question 899
A candidate project response has been piloted and stakeholders require a post-change acceptance check. Original problem: A safety-critical service has complete test reports for old specifications, while recently approved changes remain outside the tested release candidate. 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.
- Release contents provide complete usable capabilities with dependencies satisfied and intentional deferrals communicated.
- High-impact feasible outcomes appear at the right time and stakeholders can explain why lower-value requests were deferred.
- Delivery includes essential obligations and gives decision makers a visible credible set of deferrable enhancements.
- Each mandatory current requirement has verified evidence and any deferred condition is explicitly accepted by the authorized party.
Explanation
Correct Answer
D:Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count. The approved implementation step was: Confirm candidate release scope against approved requirements or backlog, acceptance evidence, unresolved defects, traceability and appropriate owner decisions.
Incorrect Answers
A:Release contents provide complete usable capabilities with dependencies satisfied and intentional deferrals communicated. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
B:High-impact feasible outcomes appear at the right time and stakeholders can explain why lower-value requests were deferred. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
C:Delivery includes essential obligations and gives decision makers a visible credible set of deferrable enhancements. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
Question 900
For an original CAPM project delivery study scenario, consider: A safety-critical service has complete test reports for old specifications, while recently approved changes remain outside the tested release candidate. Select THREE compatible elements: a proper correction, a targeted diagnostic and an acceptance result.
- Result: High-impact feasible outcomes appear at the right time and stakeholders can explain why lower-value requests were deferred.
- Check: Compare observed work sequence, timings, exceptional conditions, privacy permissions and stakeholder confirmation of what was recorded.
- Change: Clarify who owns process outcomes, product value and backlog decisions, and who elicits, analyzes and communicates requirements in the chosen delivery approach.
- Change: Confirm candidate release scope against approved requirements or backlog, acceptance evidence, unresolved defects, traceability and appropriate owner decisions.
- Result: Each mandatory current requirement has verified evidence and any deferred condition is explicitly accepted by the authorized party.
- Check: Cross-check latest requirement versions, backlog items, test results, critical issues and stakeholder sign-off for the exact release build.
Explanation
Correct Answer
D:Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count. Evidence: Cross-check latest requirement versions, backlog items, test results, critical issues and stakeholder sign-off for the exact release build.
E:Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count. Required intervention: Confirm candidate release scope against approved requirements or backlog, acceptance evidence, unresolved defects, traceability and appropriate owner decisions.
F:Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count. Acceptance: Each mandatory current requirement has verified evidence and any deferred condition is explicitly accepted by the authorized party.
Incorrect Answers
A:Result: High-impact feasible outcomes appear at the right time and stakeholders can explain why lower-value requests were deferred. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
B:Check: Compare observed work sequence, timings, exceptional conditions, privacy permissions and stakeholder confirmation of what was recorded. Delivery readiness depends on coverage of current requirements and acceptable residual risk, not a status-board color or a raw completed-item count.
C:Change: Clarify who owns process outcomes, product value and backlog decisions, and who elicits, analyzes and communicates requirements in the chosen delivery approach. A safety-critical service has complete test reports for old specifications, while recently approved changes remain outside the tested release candidate.