PMI CAPM Practice Test 76
Question 750
For an original CAPM project delivery study scenario, consider: A finance dashboard requirement says 'easy to use' but stakeholders disagree whether that means one-click export or a simplified approval workflow. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Review prototype fidelity, tested user tasks, observed failures, accessibility evidence and changes recorded for product decisions.
- Check: Review contractual obligations, approved scope flexibility, refinement cadence, version records and how tests trace to requirements.
- Change: Classify requirements as Must, Should, Could or Won't for the current scope based on stakeholder value, obligations, feasibility and transparent decision rules.
- Change: Use a sufficiently realistic prototype with representative stakeholders to test interactions and translate ambiguous expectations into observable requirements.
- Release an untested clickable mockup as the finished product and dismiss all feedback because the colors were approved.
Explanation
Correct Answer
A:Prototypes support discovery and feedback; a visual demonstration does not by itself prove production security, performance or full implementation. Acceptance: Ambiguous experience needs become testable and user-informed without mistaking the prototype for a production-ready validated solution.
D:Prototypes support discovery and feedback; a visual demonstration does not by itself prove production security, performance or full implementation. Evidence: Review prototype fidelity, tested user tasks, observed failures, accessibility evidence and changes recorded for product decisions.
Incorrect Answers
B:Check: Review contractual obligations, approved scope flexibility, refinement cadence, version records and how tests trace to requirements. Prototypes support discovery and feedback; a visual demonstration does not by itself prove production security, performance or full implementation.
C:Change: Classify requirements as Must, Should, Could or Won't for the current scope based on stakeholder value, obligations, feasibility and transparent decision rules. A finance dashboard requirement says 'easy to use' but stakeholders disagree whether that means one-click export or a simplified approval workflow.
E:Prototypes support discovery and feedback; a visual demonstration does not by itself prove production security, performance or full implementation.
Question 751
A CAPM project team analyst is reviewing this delivery scenario: An appointment system can book a visit, but users complain that the response takes thirty seconds during peak hours despite a complete booking feature. An unsafe shortcut would be: Declare quality attributes optional because the buttons exist and an end-to-end user story passed once. What should the project team analyst recommend as the narrowly scoped correction? Select ONE best answer.
- Validate that captured requirements address the real need and separately verify that the delivered solution conforms to those approved requirements.
- Adapt business-analysis artifacts and approval cadence to the delivery approach while preserving traceability, stakeholder decision ownership and acceptance clarity.
- Declare quality attributes optional because the buttons exist and an end-to-end user story passed once.
- Separate required behaviors from measurable quality attributes such as latency, availability, usability and security, and define acceptance measures for both.
Explanation
Correct Answer
D:Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
Incorrect Answers
A:Validate that captured requirements address the real need and separately verify that the delivered solution conforms to those approved requirements. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
B:Adapt business-analysis artifacts and approval cadence to the delivery approach while preserving traceability, stakeholder decision ownership and acceptance clarity. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
C:Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
Question 752
A project delivery review finds: An appointment system can book a visit, but users complain that the response takes thirty seconds during peak hours despite a complete booking feature. The team proposes: Separate required behaviors from measurable quality attributes such as latency, availability, usability and security, and define acceptance measures for both. Which project management principle most strongly supports the proposed response? Select ONE best answer.
- Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
- Workshops accelerate shared understanding when dependencies and competing viewpoints need joint discussion with the appropriate decision makers.
- Technical tests establish implementation behavior, while user acceptance tests judge whether the solution meets real business requirements and usable workflows.
- Business analysis supports informed decisions, but domain accountability and product prioritization remain with their designated owners unless formally delegated.
Explanation
Correct Answer
A:Demonstrable success requires: Both business behaviors and applicable measurable quality requirements are demonstrated before acceptance.
Incorrect Answers
B:This option addresses a different CAPM project management topic (Facilitated requirements workshops) rather than the documented Functional versus nonfunctional requirements decision.
C:Technical tests establish implementation behavior, while user acceptance tests judge whether the solution meets real business requirements and usable workflows. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
D:This option addresses a different CAPM project management topic (Business analyst versus product owner versus process owner) rather than the documented Functional versus nonfunctional requirements decision.
Question 753
The project team has not approved a broad project-plan change. Available evidence indicates: An appointment system can book a visit, but users complain that the response takes thirty seconds during peak hours despite a complete booking feature. 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.
- Check strategic objectives, user outcomes, roadmap horizon confidence, dependencies and decision rights for proposed additions.
- Examine UAT cases, representative testers, outcomes, defect disposition, waivers and evidence of accountable owner approval.
- Review functional flows, response-time thresholds, security baselines, expected load and acceptance methods with owners.
Explanation
Correct Answer
D:This check evaluates the actual project, quality or delivery decision before a risky project-wide change.
Incorrect Answers
A:Review business actors, scenario variants, error conditions, acceptance needs and documentation burden against delivery context. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
B:This option addresses a different CAPM project management topic (Product roadmap outcome horizons) rather than the documented Functional versus nonfunctional requirements decision.
C:Examine UAT cases, representative testers, outcomes, defect disposition, waivers and evidence of accountable owner approval. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
Question 754
A candidate project response has been piloted and stakeholders require a post-change acceptance check. Original problem: An appointment system can book a visit, but users complain that the response takes thirty seconds during peak hours despite a complete booking feature. 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.
- Both business behaviors and applicable measurable quality requirements are demonstrated before acceptance.
- Ambiguous experience needs become testable and user-informed without mistaking the prototype for a production-ready validated solution.
- The product addresses the intended user problem and the released behaviors are supported by conformance evidence.
Explanation
Correct Answer
B:Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
Incorrect Answers
A:The requirements record includes appropriate affected representatives and explicitly resolves whose approval is necessary. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
C:Ambiguous experience needs become testable and user-informed without mistaking the prototype for a production-ready validated solution. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
D:The product addresses the intended user problem and the released behaviors are supported by conformance evidence. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
Question 755
An implementation sign-off request identifies the following problem: An appointment system can book a visit, but users complain that the response takes thirty seconds during peak hours despite a complete booking feature. Which paired project management action and verification should close the review? Select ONE best answer.
- 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: Use a sufficiently realistic prototype with representative stakeholders to test interactions and translate ambiguous expectations into observable requirements. Verify: Review prototype fidelity, tested user tasks, observed failures, accessibility evidence and changes recorded for product decisions.
- Change: Identify relevant internal and external stakeholders, their interests, influence, authority and information needs before agreeing requirement coverage. Verify: Compare organization and external ecosystem maps, affected workflows, accessibility populations and decision authorities.
- Change: Separate required behaviors from measurable quality attributes such as latency, availability, usability and security, and define acceptance measures for both. Verify: Review functional flows, response-time thresholds, security baselines, expected load and acceptance methods with owners.
Explanation
Correct Answer
D:The change is successful only when: Both business behaviors and applicable measurable quality requirements are demonstrated before acceptance.
Incorrect Answers
A:Change: Translate selected roadmap goals into a bounded release plan with candidate components, dependencies and acceptance conditions, while retaining higher-level strategy separately. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
B:Change: Use a sufficiently realistic prototype with representative stakeholders to test interactions and translate ambiguous expectations into observable requirements. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
C:Change: Identify relevant internal and external stakeholders, their interests, influence, authority and information needs before agreeing requirement coverage. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
Question 756
A CAPM project team analyst is reviewing this delivery scenario: An account portal meets the requested screens while storing sensitive identity records without encryption, contrary to the business's stated protection objective. An unsafe shortcut would be: Declare quality attributes optional because the buttons exist and an end-to-end user story passed once. What should the project team analyst recommend as the narrowly scoped correction? Select ONE best answer.
- Declare quality attributes optional because the buttons exist and an end-to-end user story passed once.
- Order backlog items with accountable stakeholder input using value, risk, urgency, dependency and delivery feasibility rather than submission date alone.
- Distinguish the business outcome, stakeholder capability needs and solution-specific functional or quality requirements before selecting implementation.
- Separate required behaviors from measurable quality attributes such as latency, availability, usability and security, and define acceptance measures for both.
Explanation
Correct Answer
D:Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
Incorrect Answers
A:Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
B:Order backlog items with accountable stakeholder input using value, risk, urgency, dependency and delivery feasibility rather than submission date alone. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
C:Distinguish the business outcome, stakeholder capability needs and solution-specific functional or quality requirements before selecting implementation. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
Question 757
A project delivery review finds: An account portal meets the requested screens while storing sensitive identity records without encryption, contrary to the business's stated protection objective. The team proposes: Separate required behaviors from measurable quality attributes such as latency, availability, usability and security, and define acceptance measures for both. Which project management principle most strongly supports the proposed response? Select ONE best answer.
- Acceptance criteria describe the boundaries of satisfactory behavior; vague adjectives and only positive demonstrations do not establish complete acceptance.
- Roadmap intent identifies direction; release planning commits a feasible, suitably evidenced subset of work to a delivery window.
- Artifacts should match behavioral complexity and risk; user stories and use cases serve complementary purposes rather than being universally interchangeable.
- Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
Explanation
Correct Answer
D:Demonstrable success requires: Both business behaviors and applicable measurable quality requirements are demonstrated before acceptance.
Incorrect Answers
A:This option addresses a different CAPM project management topic (Testable acceptance criteria and negative cases) rather than the documented Functional versus nonfunctional requirements decision.
B:Roadmap intent identifies direction; release planning commits a feasible, suitably evidenced subset of work to a delivery window. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
C:Artifacts should match behavioral complexity and risk; user stories and use cases serve complementary purposes rather than being universally interchangeable. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
Question 758
The project team has not approved a broad project-plan change. Available evidence indicates: An account portal meets the requested screens while storing sensitive identity records without encryption, contrary to the business's stated protection objective. Which evidence best tests the project diagnosis before approving a disruptive change? Select ONE best answer.
- Trace component dependencies, integration readiness, alternative sequencing, capacity and promised acceptance behavior across planned releases.
- Audit requirement IDs, source stakeholders, implementation links, test-case results and orphaned or uncovered items.
- Review functional flows, response-time thresholds, security baselines, expected load and acceptance methods with owners.
- Review contractual obligations, approved scope flexibility, refinement cadence, version records and how tests trace to requirements.
Explanation
Correct Answer
C:This check evaluates the actual project, quality or delivery decision before a risky project-wide change.
Incorrect Answers
A:This option addresses a different CAPM project management topic (Dependencies and release sequencing) rather than the documented Functional versus nonfunctional requirements decision.
B:Audit requirement IDs, source stakeholders, implementation links, test-case results and orphaned or uncovered items. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
D:Review contractual obligations, approved scope flexibility, refinement cadence, version records and how tests trace to requirements. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
Question 759
A candidate project response has been piloted and stakeholders require a post-change acceptance check. Original problem: An account portal meets the requested screens while storing sensitive identity records without encryption, contrary to the business's stated protection objective. 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.
- Each release contains coherent approved components and stakeholders understand which later ideas are not yet committed.
- Both business behaviors and applicable measurable quality requirements are demonstrated before acceptance.
- Delivery includes essential obligations and gives decision makers a visible credible set of deferrable enhancements.
- The approved requirement set resolves contradictions or transparently records open decisions without silently privileging one stakeholder.
Explanation
Correct Answer
B:Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
Incorrect Answers
A:Each release contains coherent approved components and stakeholders understand which later ideas are not yet committed. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
C:Delivery includes essential obligations and gives decision makers a visible credible set of deferrable enhancements. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
D:The approved requirement set resolves contradictions or transparently records open decisions without silently privileging one stakeholder. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
Question 760
For an original CAPM project delivery study scenario, consider: An account portal meets the requested screens while storing sensitive identity records without encryption, contrary to the business's stated protection objective. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Use concise user stories for value-focused backlog discussion and richer use cases or flow descriptions when interaction and alternate paths require precision.
- Change: Separate required behaviors from measurable quality attributes such as latency, availability, usability and security, and define acceptance measures for both.
- Declare quality attributes optional because the buttons exist and an end-to-end user story passed once.
- Check: Review functional flows, response-time thresholds, security baselines, expected load and acceptance methods with owners.
- Check: Compare conflicting statements, source authority, constraints, feasible alternatives, decision log and downstream design effects.
Explanation
Correct Answer
B:Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates. Evidence: Review functional flows, response-time thresholds, security baselines, expected load and acceptance methods with owners.
D:Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates. Required intervention: Separate required behaviors from measurable quality attributes such as latency, availability, usability and security, and define acceptance measures for both.
Incorrect Answers
A:Change: Use concise user stories for value-focused backlog discussion and richer use cases or flow descriptions when interaction and alternate paths require precision. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.
C:For this select two assessment, the shortcut changes or bypasses the necessary delivery, governance or operational boundary rather than correcting it.
E:Check: Compare conflicting statements, source authority, constraints, feasible alternatives, decision log and downstream design effects. Functional requirements describe what a solution does; nonfunctional requirements constrain how well or under what qualities it operates.