PMI-PBA Exam Practice Test Questions and Answers

Our PMI-PBA Exam Practice Test Questions and Answers are designed for candidates preparing for the PMI Professional in Business Analysis (PMI-PBA)® certification exam. The material focuses on scenario-based business analysis judgment, requirements, stakeholder needs, prioritization, traceability, solution evaluation, and the practical decisions a business analyst must make.

The questions are written as original exam-style practice material—not official PMI questions—and include answers with detailed reasoning to help you understand why one option is stronger than the others.

How This PMI-PBA Exam Practice Test Helps You Prepare

The strongest preparation comes from practicing how to analyze a situation and select the best business analysis action, rather than memorizing terminology.

• Practice realistic business analysis scenarios.
• Review correct answers and detailed explanations.
• Understand why alternative choices are less appropriate.
• Strengthen requirements analysis and stakeholder reasoning.
• Practice traceability, prioritization, validation, and evaluation concepts.
• Identify topics that need additional review.
• Build familiarity with the judgment-based style used in professional business analysis.

Use the questions in study mode first, then revisit difficult scenarios without looking at the answer until you can explain your reasoning.

What Is the PMI-PBA Exam?

The PMI Professional in Business Analysis certification recognizes practitioners who work with stakeholders to define business requirements, manage requirements, and help projects deliver intended business benefits. PMI currently lists the exam at 200 questions with 240 minutes of testing time.

The current PMI-PBA examination content is organized into five domains:

Analysis carries the largest share, so preparation should go beyond simple terminology review and give substantial attention to requirements, models, acceptance criteria, verification, validation, prioritization, risks, and solution alternatives.

PMI-PBA Exam Eligibility Requirements

PMI currently provides multiple eligibility pathways. Candidates should verify their circumstances against the latest PMI requirements before applying.

• Secondary degree: 60 months of business analysis experience earned within the last eight years plus 35 contact hours of business analysis education.
• Bachelor’s degree or higher: 36 months of business analysis experience earned within the last eight years plus 35 contact hours of business analysis education.
• GAC-accredited bachelor’s or postgraduate degree: PMI lists a pathway requiring 24 months of unique, nonoverlapping professional business analysis experience and 35 contact hours of formal education.

Experience and education should be documented accurately because PMI may select applications for an eligibility audit.

How to Register for the PMI-PBA Exam

Registration begins with checking eligibility and completing the PMI certification application. Candidates document relevant experience and education, submit the application, complete any applicable review or audit requirements, and then proceed with payment and exam scheduling after approval. PMI provides the current application and certification process through its official certification resources.

Always confirm current fees, scheduling options, identification requirements, and testing arrangements directly with PMI before booking your appointment.

How Is the PMI-PBA Exam Scored?

PMI does not publish a simple fixed percentage passing score for its certification exams. PMI explains that passing standards are established through psychometric analysis and that candidates are evaluated against criteria representing the proficiency expected for the role.

This is one reason practice scores should be used as a readiness indicator rather than treated as a guaranteed prediction of the real examination result.

What Topics Does This PMI-PBA Practice Material Cover?

The practice material reflects the major areas represented in the PMI-PBA examination blueprint, including:

• Business problems, opportunities, goals, and value.
• Stakeholder identification and stakeholder needs.
• Business analysis planning and communication.
• Requirements elicitation, analysis, and elaboration.
• Business, stakeholder, solution, transition, and quality requirements.
• Requirements models, business rules, acceptance criteria, and scenarios.
• Requirements verification and validation.
• Prioritization and evaluation of alternatives.
• Requirements traceability and dependencies.
• Requirements changes and monitoring.
• Solution performance and business outcomes.
• Benefits, risks, assumptions, and unintended consequences.

What Is Included in This Practice Test?

You receive a substantial collection of original PMI-PBA practice questions with answers and explanations, developed around practical business analysis situations. The material is intended for repeated study rather than one-time reading.

Each question provides:

• Four answer choices.
• A clearly identified correct answer.
• An explanation of the reasoning.
• Discussion of why the other choices are weaker.
• A short study guide to reinforce the underlying concept.

How We Create This PMI-PBA Practice Material

The questions are developed around the PMI-PBA examination domains and business analysis concepts, with emphasis on realistic workplace situations rather than isolated definition-based questions. Scenarios are varied across industries and organizational settings so candidates practice applying principles to unfamiliar situations.

The goal is to help you recognize the best next action, strongest analysis approach, appropriate requirement treatment, or most defensible decision when several answers initially appear reasonable.

Study Tips for the PMI-PBA Exam

Start by understanding the five examination domains, then spend additional time on Analysis because it represents the largest portion of the exam. For every missed question, identify what made the correct option better—not simply what made your selected option wrong.

• Keep an error log for recurring weaknesses.
• Review requirements concepts instead of memorizing answer wording.
• Practice scenario questions under time limits.
• Revisit questions involving “best,” “first,” “next,” or “most appropriate.”
• Study why distractors are wrong.
• Mix domains once you become comfortable with individual topics.
• Use timed practice sessions before the actual examination.

PMI-PBA Exam Day Tips

The exam provides 240 minutes for 200 questions, so pacing matters. Read the scenario carefully, identify the business-analysis problem being tested, eliminate clearly inappropriate choices, and avoid spending excessive time on one difficult question.

Check PMI’s current exam policies before test day because identification, testing-center, online-proctored, and personal-item procedures can change.

Common PMI-PBA Preparation Mistakes to Avoid

Avoid memorizing practice answers without understanding the reasoning behind them. The PMI-PBA exam is designed around professional business analysis judgment, so recognizing the situation and applying the appropriate principle is more useful than remembering a particular question.

Other common problems include ignoring the higher-weighted Analysis domain, confusing verification with validation, choosing a solution before understanding the problem, overlooking stakeholder value, and treating every requirement change as automatically beneficial or harmful.

How to Pass the PMI-PBA Exam

Build your preparation around understanding, application, and repeated practice. Work through questions systematically, review every mistake, strengthen weak domains, and gradually increase the difficulty and time pressure of your practice sessions.

No practice product can guarantee a passing result. Your outcome depends on your experience, preparation, understanding of the examination content, and performance on exam day.

PMI-PBA Exam Sample Questions and Answers

Question 1. A financial-services organization is experiencing a 28% increase in customer complaints about loan-processing delays. Senior management initially asks the project team to replace the existing loan-processing application. During interviews, the business analyst discovers that most delays occur because applications are repeatedly returned to branch staff for missing information and manual compliance checks. What should the business analyst do FIRST?

A. Document replacement of the application as the confirmed solution scope.
B. Perform root cause analysis to understand the underlying causes of the delays.
C. Develop detailed functional requirements for the new application.
D. Create a stakeholder register for the application replacement project.

Correct Answer: B

Answer Explanation: Option B is correct because the business analyst should understand the actual business problem before accepting the initially proposed solution. The stated need is faster loan processing, while application replacement is only a proposed solution. Root cause analysis can determine whether delays result from inadequate information, inefficient processes, unnecessary approvals, system limitations, or a combination of factors. This prevents the organization from investing in technology that may not address the real source of poor performance. Once the current-state problem and contributing causes are understood, the BA can help define the future state, assess viable options, and establish an appropriate solution scope. PMI’s Needs Assessment domain specifically emphasizes defining or reviewing business problems and opportunities before developing the solution scope or contributing to the business case.

Why the other options are incorrect:

Option A assumes the proposed technology is already the correct solution without validating the underlying business problem.

Option C moves prematurely into detailed requirements before the business need and solution direction are sufficiently understood.

Option D may eventually be necessary, but identifying stakeholders does not address the immediate need to determine why the performance problem exists.

Study Guide:
Focus on the distinction between a business problem and a proposed solution.
Before defining detailed requirements, establish the current state, identify root causes, and determine what outcome the organization actually needs.

Question 2. A company is considering three options to reduce customer-support costs: expanding its internal support team, outsourcing support, or implementing an AI-assisted support platform. The CFO wants the BA to recommend the option with the lowest initial cost. However, the BA determines that the AI platform has a higher initial investment but substantially lower operating costs and faster response times over three years. What should the BA do?

A. Recommend the AI platform because it has the lowest operating cost.
B. Recommend outsourcing because it requires less internal staffing.
C. Present a comparative value analysis that considers relevant costs, benefits, risks, and organizational objectives.
D. Select the option requested by the CFO because the CFO owns the budget.

Correct Answer: C

Answer Explanation: Option C is correct because business analysis should evaluate the value proposition of an initiative rather than selecting an alternative based solely on one financial measure. A meaningful comparison should consider investment and operating costs, expected benefits, risks, strategic alignment, operational implications, and the time horizon relevant to the organization. In this case, the AI-assisted platform may have a higher upfront cost but produce greater long-term value. The BA’s responsibility is to provide decision-makers with credible analysis so they can make an informed choice. The recommendation should therefore be based on transparent evaluation criteria tied to organizational objectives rather than the preference of one stakeholder or a single cost category.

Why the other options are incorrect:

Option A considers only operating cost and ignores initial investment, risk, strategic fit, and other value factors.

Option B focuses on staffing implications without establishing whether outsourcing delivers the best overall value.

Option D gives one stakeholder’s preference inappropriate priority instead of providing objective analysis for the decision.

Study Guide:
Know how cost-benefit analysis, value analysis, SWOT, force-field analysis, and value-stream thinking can support solution selection.
A BA should help decision-makers compare alternatives against agreed business objectives and value criteria.

Question 3. A healthcare organization plans to introduce an online appointment platform. During stakeholder identification, the BA identifies patients, physicians, reception staff, IT support, compliance personnel, executives, and an external accessibility advocacy group. A project manager suggests excluding the advocacy group because it will not use the platform directly. What should the BA do?

A. Include the group because its interests may affect solution requirements and acceptance.
B. Exclude the group because only direct users should be stakeholders.
C. Ask the project sponsor to decide whether the group matters.
D. Include the group only if it has authority to approve project funding.

Correct Answer: A

Answer Explanation: Option A is correct because stakeholder identification should consider people or groups that can affect, be affected by, or have an interest in the product or its outcomes. The accessibility advocacy group may not directly operate the appointment system, but it can provide important perspectives concerning accessibility requirements, regulatory expectations, usability, and equitable access. Excluding such a stakeholder could result in requirements gaps that are discovered late, potentially requiring expensive changes or creating barriers for users. The BA should identify relevant stakeholders based on their relationship to the business need, requirements, product, and expected outcomes rather than limiting the stakeholder population to people who directly interact with the solution.

Why the other options are incorrect:

Option B uses an unnecessarily narrow definition of stakeholder involvement and can overlook important requirements sources.

Option C unnecessarily delays analysis that the BA is responsible for performing.

Option D incorrectly assumes that financial authority is required for stakeholder relevance.

Study Guide:
Stakeholder analysis is broader than identifying end users.
Consider influence, interest, impact, expertise, regulatory involvement, and potential effects on requirements and outcomes when identifying stakeholders.

Question 4. A project is using a hybrid life cycle. The organization requires formal approval for major business requirements, while development teams deliver functionality incrementally. The sponsor asks the BA to explain how business analysis activities should be planned. Which approach is MOST appropriate?

A. Use only a predictive requirements process because formal approval is required.
B. Use only an agile requirements process because development is incremental.
C. Allow each development team to establish its own requirements process.
D. Define a business analysis approach that accommodates both formal governance and iterative elaboration.

Correct Answer: D

Answer Explanation: Option D is correct because a hybrid life cycle requires the business analysis approach to reflect the characteristics of both governance and delivery environments. Formal approval of major requirements can coexist with iterative elaboration, refinement, prioritization, and feedback during development. The BA should establish how requirements will be elicited, analyzed, documented, prioritized, approved, communicated, traced, and changed while recognizing that the level of detail may evolve as understanding improves. The approach should provide enough governance to satisfy organizational controls without creating unnecessary barriers to incremental delivery. PMI’s business analysis framework is intended to apply across predictive, agile, iterative, and hybrid approaches, with practices adapted to the project’s environment.

Why the other options are incorrect:

Option A ignores the iterative characteristics of the delivery environment.

Option B ignores the organization’s need for formal governance and approval.

Option C creates inconsistent practices and weakens coordinated requirements management.

Study Guide:
PMI-PBA questions may test how BA practices adapt to predictive, agile, iterative, and hybrid environments.
Do not assume that one life-cycle approach requires one rigid requirements-management method.

Question 5. A product owner tells the BA, “Customers need a faster checkout.” During elicitation, different stakeholders interpret “faster” differently. Some mean fewer screens, others mean shorter payment-processing time, and others mean less information entry. What should the BA do NEXT?

A. Select the interpretation most frequently mentioned by stakeholders.
B. Ask stakeholders to clarify the desired outcome and define measurable acceptance criteria.
C. Convert “faster checkout” directly into a functional requirement.
D. Ask the development team to determine which interpretation is technically feasible.

Correct Answer: B

Answer Explanation: Option B is correct because the phrase “faster checkout” is ambiguous and represents an outcome that requires clarification before it can become a useful requirement. The BA should facilitate further elicitation to determine what improvement customers actually need and how that improvement will be measured. For example, stakeholders might establish a target checkout duration, reduced number of required interactions, or improved completion rate. Measurable acceptance criteria can then be developed so that stakeholders and the delivery team share the same understanding of success. The BA should resolve ambiguity rather than arbitrarily selecting an interpretation or transferring the responsibility to developers.

Why the other options are incorrect:

Option A treats frequency of comments as proof of meaning and does not resolve the ambiguity.

Option C converts an unclear statement into an equally unclear requirement.

Option D places business interpretation on technical staff who may not understand the intended business outcome.

Study Guide:
Strong requirements are clear, testable, feasible, and aligned with the intended outcome.
When stakeholder language is ambiguous, use elicitation and measurable acceptance criteria to establish shared understanding.

Question 6. During requirements analysis for an insurance claims platform, stakeholders provide 42 requested capabilities. The development team can deliver only 18 in the first release. Several executives argue that their requests should automatically receive the highest priority. What should the BA recommend?

A. Prioritize requirements according to stakeholder seniority.
B. Allow developers to select the requirements that are easiest to implement.
C. Apply agreed prioritization criteria such as business value, risk, regulatory importance, dependencies, and implementation considerations.
D. Divide the requirements equally among stakeholder groups.

Correct Answer: C

Answer Explanation: Option C is correct because requirements should be prioritized using transparent criteria that reflect the organization’s objectives and the product’s expected value. Business value is important, but other considerations can materially affect priority, including regulatory obligations, risk reduction, dependencies, urgency, customer impact, cost, and feasibility. Techniques such as MoSCoW, weighted criteria, and multi-voting can help stakeholders reach a structured decision. Seniority alone should not determine priority, because an executive request may have lower business value or higher implementation consequences than another requirement. The BA should facilitate an objective prioritization process and make the decision criteria visible to stakeholders.

Why the other options are incorrect:

Option A substitutes organizational hierarchy for business value and agreed prioritization criteria.

Option B prioritizes technical convenience rather than the organization’s needs and expected outcomes.

Option D treats all requirements as equally valuable despite differences in urgency, value, risk, and dependencies.

Study Guide:
Know common requirements prioritization techniques, especially MoSCoW, weighted criteria, and multi-voting.
Priority should reflect agreed business and delivery considerations rather than stakeholder rank alone.

Question 7. A BA is analyzing a new warehouse-management process. A stakeholder describes the desired process verbally, but several activities involve decisions, alternate paths, and system-generated events. The project team needs a common representation of how work will flow from receiving an order through shipment. Which technique is MOST appropriate?

A. Process model or workflow diagram
B. Stakeholder register
C. Product roadmap
D. Communication management plan

Correct Answer: A

Answer Explanation: Option A is correct because a process model or workflow representation can show activities, decisions, alternate paths, events, and dependencies across the warehouse process. Visualizing the process helps stakeholders identify unnecessary steps, bottlenecks, missing controls, handoffs, and opportunities for improvement. It also provides a common basis for discussing the current and future states with business and technical stakeholders. A stakeholder register identifies interested parties but does not model process behavior. A product roadmap communicates planned product evolution, while a communication plan addresses how information will be exchanged. Because the immediate need is to understand and analyze workflow behavior, process modeling is the most suitable technique.

Why the other options are incorrect:

Option B identifies stakeholders but does not represent how the warehouse process operates.

Option C describes product direction and timing rather than detailed process behavior.

Option D defines communication practices rather than operational workflow.

Study Guide:
Review process models, use cases, user stories, data-flow diagrams, dependency graphs, and event-based analysis.
Choose the model based on what needs to be understood: workflow, user interaction, data movement, or dependencies.

Question 8. A mobile banking project has completed requirements elicitation. During analysis, the BA discovers that a security requirement conflicts with a previously approved usability requirement. The security team requires multifactor authentication for every login, while customer research shows that this creates significant abandonment. What should the BA do?

A. Remove the usability requirement because security always has priority.
B. Remove the security requirement because customers dislike the additional step.
C. Ask developers to implement both requirements without further analysis.
D. Facilitate stakeholder analysis of the conflict, constraints, risks, and trade-offs before agreeing on a resolution.

Correct Answer: D

Answer Explanation: Option D is correct because conflicting requirements should be analyzed collaboratively rather than resolved through an unsupported assumption about which stakeholder is more important. The BA should clarify the underlying business objectives, applicable security obligations, customer impact, risk exposure, and possible alternatives. For example, the organization might consider risk-based authentication, trusted-device mechanisms, transaction-based authentication, or other approaches that preserve an appropriate level of security while reducing unnecessary friction. The resolution should be consistent with organizational policies, regulatory requirements, and agreed product objectives. Facilitating this trade-off allows stakeholders to make an informed decision and ensures the resulting requirements represent an intentional balance rather than an accidental compromise.

Why the other options are incorrect:

Option A assumes security automatically overrides all other concerns without considering feasible alternatives or business context.

Option B dismisses security risk based solely on user preference.

Option C avoids resolving the conflict and may create an infeasible or internally inconsistent solution.

Study Guide:
When requirements conflict, analyze business objectives, constraints, risks, dependencies, and trade-offs.
The BA facilitates informed resolution rather than deciding based on stakeholder authority alone.

Question 9. A requirements baseline contains a requirement stating, “The system shall provide a secure and user-friendly payment process.” During verification, the BA determines that the statement cannot be objectively tested. What is the BEST action?

A. Approve it because stakeholders understand what “secure and user-friendly” means.
B. Rewrite the requirement into measurable, testable criteria and obtain appropriate stakeholder agreement.
C. Ask testers to interpret the requirement during system testing.
D. Remove the requirement because quality requirements should not be documented.

Correct Answer: B

Answer Explanation: Option B is correct because the requirement contains subjective and insufficiently measurable language. Terms such as “secure” and “user-friendly” may represent legitimate business needs, but they must be elaborated into criteria that can be verified. Security might be expressed through applicable security controls or measurable performance conditions, while usability could include task completion rates, response times, error rates, or other agreed usability measures. The BA should work with appropriate stakeholders and subject-matter experts to refine the requirement without losing the underlying business intent. Requirements should be sufficiently clear and testable to support verification and validation activities and to establish an objective basis for determining whether the delivered solution satisfies expectations.

Why the other options are incorrect:

Option A accepts ambiguity that can produce inconsistent interpretations during development and testing.

Option C transfers requirements interpretation to testers and creates avoidable uncertainty.

Option D incorrectly assumes quality requirements should be omitted rather than made measurable.

Study Guide:
Watch for vague terms such as fast, easy, flexible, secure, efficient, user-friendly, and adequate.
Convert them into measurable conditions that can be objectively verified and validated.

Question 10. Midway through development, a regulatory authority introduces a new reporting requirement. The requirement affects several existing business requirements, a database component, two user stories, and planned acceptance tests. What should the BA do FIRST?

A. Update the affected requirements and traceability relationships so the impact can be assessed systematically.
B. Tell developers to implement the regulatory requirement immediately.
C. Delete the requirements that conflict with the new regulation.
D. Wait until testing to determine whether the new requirement affects the solution.

Correct Answer: A

Answer Explanation: Option A is correct because the new regulatory requirement can create impacts across multiple related requirements and solution components. Traceability provides a structured way to identify those relationships and determine what must change. The BA should assess the impact on existing requirements, design elements, development work, test cases, approvals, and potentially business processes before implementation decisions are finalized. This approach helps prevent incomplete changes, contradictory requirements, and missed validation activities. Immediate implementation without impact analysis may cause downstream defects, while waiting until testing is unnecessarily late. Traceability is particularly valuable when requirements change because it allows the team to understand the consequences of a change and maintain alignment between business needs, requirements, solution components, and verification activities.

Why the other options are incorrect:

Option B skips impact analysis and can result in incomplete or conflicting implementation.

Option C removes requirements without determining whether they are actually incompatible with the new regulation.

Option D delays analysis until a stage where correcting missed impacts can be substantially more expensive.

Study Guide:
Traceability is not merely documentation. It supports impact analysis, change management, completeness, and verification.
When a requirement changes, examine all related requirements, solution elements, and validation activities.

Question 11. A project team has completed development of a customer self-service portal. The BA reviews the requirements traceability matrix and finds that several approved requirements have no corresponding test cases. What should the BA do?

A. Mark the requirements as complete because development has finished.
B. Remove the requirements from the traceability matrix.
C. Determine why the requirements lack validation coverage and address the gaps before concluding that the requirements have been satisfied.
D. Ask the project manager to accept the missing test coverage as a project risk.

Correct Answer: C

Answer Explanation: Option C is correct because the absence of corresponding test coverage creates a validation gap. A requirement cannot simply be considered satisfied because development work has ended. The BA should determine whether the missing relationship resulted from incomplete test planning, an undocumented requirement, an incorrect traceability link, or another issue. Appropriate validation activities should then be established so that stakeholders can determine whether the implemented solution satisfies the approved requirement. Traceability provides evidence of coverage between requirements and validation activities, making it useful for identifying gaps before acceptance. The objective is not merely to complete the matrix but to ensure that requirements can be demonstrated as fulfilled.

Why the other options are incorrect:

Option A confuses completion of development work with confirmation that requirements have been satisfied.

Option B hides the traceability gap instead of correcting it.

Option D may record the issue but does not address the missing evidence that the requirements have been validated.

Study Guide:
Use traceability to check requirement-to-test coverage and requirement completeness.
A missing relationship can indicate a genuine gap in testing, documentation, implementation, or requirements management.

Question 12. Six months after implementing a new inventory solution, management reports that stockout frequency has not improved despite the project meeting all documented functional requirements. The BA investigates and discovers that employees are bypassing the new replenishment workflow because it takes longer than the previous manual process. What should the BA recommend?

A. Declare the solution successful because all requirements were delivered.
B. Replace the entire solution immediately.
C. Add more functional requirements without investigating user behavior.
D. Evaluate actual solution performance against intended business outcomes and identify improvement opportunities.

Correct Answer: D

Answer Explanation: Option D is correct because successful delivery of requirements does not automatically mean the solution is producing the intended business value. The organization expected reduced stockouts, but actual behavior indicates that users are bypassing the workflow because of process friction. The BA should evaluate the solution against the intended outcomes, analyze the performance gap, identify the causes, and determine appropriate improvements. Potential actions could include workflow redesign, training, usability improvements, policy changes, or targeted solution modifications. Solution evaluation focuses on whether the delivered solution is achieving the expected value and identifying gaps between expected and actual performance. This scenario demonstrates why evaluation must extend beyond confirming that documented requirements were implemented.

Why the other options are incorrect:

Option A measures delivery against requirements but ignores whether the business outcome was achieved.

Option B is premature because the actual cause of the performance problem has not been fully evaluated.

Option C adds requirements without first determining why users are bypassing the process.

Study Guide:
Remember the distinction between requirements satisfaction and business-value realization.
A solution can meet documented requirements and still fail to produce the intended business outcome.

Question 13. A retailer launches a new loyalty application. Before launch, stakeholders predicted a 15% increase in repeat purchases. Three months later, repeat purchases have increased only 2%. The BA discovers that adoption is high among existing loyal customers but very low among occasional customers, who were a major target group. What should the BA do NEXT?

A. Conclude that the application has failed because the original target was not achieved.
B. Compare actual results with the expected benefits, investigate the performance gap, and identify corrective or improvement options.
C. Rewrite the original business case so the 2% increase appears acceptable.
D. Remove occasional customers from the target stakeholder group.

Correct Answer: B

Answer Explanation: Option B is correct because solution evaluation should compare actual performance with expected outcomes and determine why the expected value has not been fully realized. The gap between a predicted 15% increase and the actual 2% increase is meaningful, but it does not automatically prove that the solution itself is unsuccessful. The BA should examine adoption patterns, customer behavior, communication, incentives, usability, competitive factors, and other relevant causes. The analysis may identify opportunities such as targeted engagement, changes to loyalty incentives, improved onboarding, or adjustments to the product experience. Evaluation should produce evidence that supports informed improvement decisions rather than manipulating the original expectations or prematurely declaring the initiative a failure.

Why the other options are incorrect:

Option A reaches a conclusion without investigating the reasons for the performance gap.

Option C changes the benchmark instead of evaluating actual performance against the approved business expectation.

Option D removes an important stakeholder group to avoid addressing the underlying adoption problem.

Study Guide:
Solution evaluation involves measuring actual outcomes, comparing them with expected benefits, analyzing gaps, and recommending improvements.
Do not confuse benefit shortfalls with automatic solution failure.

Question 14. During a requirements workshop for a national logistics platform, regional managers strongly disagree about whether delivery-time optimization or cost reduction should receive higher priority. The disagreement is becoming personal, and participants are defending their regions rather than the enterprise objective. What should the BA do?

A. Allow the project sponsor to select whichever requirement is most important.
B. Prioritize the requirements according to the region with the largest budget.
C. Facilitate the group in establishing shared evaluation criteria tied to organizational objectives and use those criteria to compare the alternatives.
D. Ask each regional manager to submit a separate requirements list and select the most common request.

Correct Answer: C

Answer Explanation: Option C is correct because the conflict should be redirected from personal or regional preferences toward transparent criteria based on the organization’s objectives. The BA can facilitate agreement on factors such as customer impact, strategic value, operational cost, regulatory obligations, service-level commitments, revenue impact, risk, and implementation dependencies. The alternatives can then be evaluated consistently against those criteria. This approach makes the decision more objective and helps stakeholders understand why one requirement may receive greater priority than another. Business analysis requires effective stakeholder engagement and the ability to manage conflicting interests while keeping the discussion focused on the business need and expected value rather than organizational politics.

Why the other options are incorrect:

Option A removes the opportunity to facilitate an evidence-based stakeholder decision.

Option B uses budget size as a proxy for value without demonstrating that it reflects enterprise priorities.

Option D treats frequency as importance and does not resolve competing business objectives.

Study Guide:
When stakeholders disagree, establish shared decision criteria before debating individual requirements.
Effective BA facilitation turns competing opinions into a structured comparison based on business value, risk, constraints, and strategic objectives.

Question 15. A software company is replacing an internal order-management system. During user acceptance testing, users report that the new system performs the documented functions correctly, but order-entry staff take 40% longer to complete common transactions. The original requirements did not specify transaction completion time. What should the BA do?

A. Investigate the gap between the delivered functionality and the operational outcome, then determine whether additional requirements or solution changes are needed.
B. Reject the users’ feedback because the system satisfies the approved requirements.
C. Close the project because performance was never included in the requirements.
D. Ask users to work faster until the measured transaction time reaches the desired level.

Correct Answer: A

Answer Explanation: Option A is correct because the situation reveals a gap between functional requirement satisfaction and the intended operational effectiveness of the solution. The BA should investigate why transaction completion is slower, determine whether performance, usability, workflow, training, or process requirements were insufficiently understood, and assess the impact on the business outcome. The absence of an explicit timing requirement does not automatically make the operational problem irrelevant. Evaluation and stakeholder feedback can reveal unmet needs or quality expectations that should be addressed through appropriate analysis and change processes. The BA should use evidence from actual usage to determine whether additional requirements, configuration changes, process improvements, or other actions are necessary.

Why the other options are incorrect:

Option B focuses narrowly on documented functionality and ignores evidence that the solution may not support the intended business outcome.

Option C treats incomplete requirements as proof that no improvement is possible.

Option D shifts responsibility to users without investigating whether the solution itself creates unnecessary operational effort.

Study Guide:
PMI-PBA scenarios often distinguish functional requirements from quality, usability, performance, and business-outcome expectations.
Evaluate how the solution works in the real operating environment, not just whether individual functions were delivered.