View Full PMI PMI-PBA Exam Dumps and Practice Test Dumps

 

Question 181.

A business analyst is reviewing a proposed solution and discovers that its expected benefits depend on customers changing their purchasing behavior. What should the analyst do?

1. Treat the behavioral change as guaranteed
   2. Document and validate the assumption and assess how different customer responses affect expected benefits
   3. Remove customer behavior from the business case
   4. Increase the benefit estimate to compensate for uncertainty

Correct Answer: 2

Explanation:

Expected benefits frequently depend on assumptions about stakeholder behavior, adoption, demand, or market conditions. When customer behavior is a significant driver of value, the assumption should be explicit and supported by available evidence. Research, historical data, pilots, experiments, or sensitivity analysis may help evaluate it. The analyst should also show how different levels of customer response would affect expected outcomes. Treating uncertain behavior as guaranteed can overstate the business case and prevent decision-makers from understanding the actual level of risk associated with the initiative.

Question 182.

A business analyst needs to identify the external systems that exchange information with a proposed solution. What should the analyst create or review?

1. A context or interface model
   2. A project vacation calendar
   3. A cost-benefit spreadsheet only
   4. A stakeholder training schedule

Correct Answer: 1

Explanation:

Context and interface models can identify external systems, organizations, users, and other actors that exchange information with the area being analyzed. They help establish solution boundaries and reveal integrations that require more detailed analysis. Once interfaces are identified, the analyst can investigate data content, direction, frequency, timing, security, protocols, ownership, and error handling as appropriate. Identifying external interactions early reduces the risk of discovering critical integration requirements late in implementation and also supports stakeholder and dependency analysis.

Question 183.

A business analyst finds that a requirement is technically feasible but would violate an organizational policy. What should the analyst do?

1. Implement it because technical feasibility is sufficient
   2. Ignore the policy if the requirement has high value
   3. Analyze the policy constraint and determine whether the requirement or policy can be appropriately changed through authorized governance
   4. Ask developers to decide whether the policy matters

Correct Answer: 3

Explanation:

Technical feasibility is only one consideration when evaluating requirements. Organizational policies can impose legitimate constraints on solution behavior and operating processes. The analyst should understand the policy’s purpose, authority, and applicability and determine whether it is mandatory or can be changed through an authorized process. Stakeholders can then evaluate alternatives. A technically possible solution may still be unacceptable from an operational, regulatory, legal, security, or governance perspective. Feasibility analysis should therefore consider all relevant constraints rather than technology alone.

Question 184.

A stakeholder requests a major requirement change after development has begun. What should the business analyst do first?

1. Reject the change because development has started
   2. Immediately instruct developers to implement it
   3. Replace the original requirement without documenting the change
   4. Analyze the change’s rationale and impact before supporting an approval decision

Correct Answer: 4

Explanation:

The timing of a change can influence its cost and impact, but it does not automatically determine whether the change should be accepted or rejected. The analyst should understand the business reason and assess effects on related requirements, design, testing, schedule, cost, risk, benefits, and dependencies. This information should be provided through the established change process so authorized stakeholders can make an informed decision. Transparent impact analysis helps organizations respond to legitimate changes without losing control of scope or downstream consequences.

Question 185.

Why should a business analyst identify the source of each significant requirement?

1. It supports clarification, traceability, accountability, and future impact analysis.
   2. It guarantees the requirement is correct.
   3. It prevents requirements from being modified.
   4. It eliminates the need for validation.

Correct Answer: 1

Explanation:

Knowing where a requirement originated provides valuable context throughout its lifecycle. If questions arise, the analyst can return to the relevant stakeholder, regulation, policy, business objective, or other source for clarification. Source information also supports traceability and can help identify affected requirements when an upstream source changes. A known source does not guarantee that a requirement is complete or valid, so verification and validation are still necessary. Source attributes are particularly valuable in large initiatives with many stakeholders and requirements.

Question 186.

An organization is considering a new solution, but employees currently lack the skills required to operate it. What should the business analyst identify?

1. Only additional functional requirements
   2. Capability gaps and appropriate transition needs such as training, staffing, or process changes
   3. Only software defects
   4. Only customer requirements

Correct Answer: 2

Explanation:

A gap between current employee capabilities and those required by the future state can prevent successful adoption even when the solution itself performs correctly. The analyst should identify the gap and determine how it can be addressed. Possible responses include training, revised roles, recruitment, external support, process redesign, or changes to the proposed solution. These may become transition requirements or influence solution selection. Capability analysis helps ensure that future-state planning addresses people and organizational needs rather than focusing exclusively on technology.

Question 187.

A business analyst is reviewing a user story that does not explain why the requested capability is valuable. What should the analyst do?

1. Estimate the story without further discussion
   2. Remove the story automatically
   3. Clarify the user’s goal and expected value before prioritizing or refining the requirement
   4. Assign the story the highest priority

Correct Answer: 3

Explanation:

Understanding the purpose behind a user story helps stakeholders determine whether it supports a legitimate need and how important it is relative to other work. The analyst should clarify the user or stakeholder objective, expected outcome, and relevant acceptance expectations. This information supports prioritization, refinement, validation, and solution design. A story can be concise while still communicating meaningful value. Without understanding the intended outcome, teams may implement functionality correctly but fail to deliver the benefit the stakeholder actually needed.

Question 188.

A proposed solution will require temporary operation of both the old and new systems. What should the business analyst analyze?

1. Only the final-state requirements
   2. Only the new system’s interface colors
   3. Only the project’s procurement process
   4. Parallel-operation requirements, data synchronization, responsibilities, controls, duration, and exit criteria

Correct Answer: 4

Explanation:

Parallel operation can reduce transition risk but creates additional requirements and complexity. The analyst should determine how data will remain consistent, which system is authoritative, who performs duplicated activities, how discrepancies are handled, and when the old system can be retired. Operational controls and clear exit criteria are particularly important because temporary arrangements can otherwise continue longer than intended. These are transition concerns that may not exist in the final future state but are essential for moving safely from the existing environment to the new solution.

Question 189.

What is an important purpose of backlog refinement in an adaptive delivery environment?

1. To progressively clarify, split, estimate, prioritize, and prepare upcoming work for delivery
   2. To permanently freeze all requirements
   3. To eliminate stakeholder feedback
   4. To move every backlog item into the next iteration

Correct Answer: 1

Explanation:

Backlog refinement keeps upcoming requirements sufficiently understood and appropriately ordered for future delivery. Activities may include clarifying needs, adding acceptance criteria, decomposing large items, reviewing dependencies, estimating effort, and reconsidering priorities. Not every backlog item must be fully detailed far in advance because adaptive approaches intentionally allow learning to influence later work. Refinement supports readiness without permanently freezing scope. Business analysts can contribute by maintaining alignment between backlog items, stakeholder needs, business objectives, and evolving information.

Question 190.

A business analyst must determine whether a proposed process improvement actually removes a bottleneck. What should the analyst compare?

1. Only the number of process steps
   2. Relevant baseline and future performance measures such as queue time, throughput, cycle time, or capacity
   3. Only the number of employees
   4. Only stakeholder meeting attendance

Correct Answer: 2

Explanation:

A process can have fewer steps without actually improving its limiting constraint. The analyst should identify appropriate measures that demonstrate whether the bottleneck has been reduced. Depending on the process, these might include waiting time, throughput, cycle time, work-in-progress, capacity utilization, or error rates. Baseline measurements establish current performance and enable meaningful comparison after improvement. Quantitative evidence can be combined with stakeholder observations to determine whether the future process produces the intended operational benefit rather than merely appearing simpler.

Question 191.

A business analyst discovers that a requirement conflicts with another requirement owned by a different business unit. What should the analyst do?

1. Implement both and allow the system to resolve the conflict
   2. Give priority automatically to the older requirement
   3. Facilitate resolution among appropriate stakeholders using business objectives, rules, constraints, and decision authority
   4. Delete both requirements

Correct Answer: 3

Explanation:

Conflicting requirements should be resolved before they create inconsistent solution behavior. The analyst should understand the rationale and constraints behind each requirement and identify the stakeholders with appropriate decision authority. Business objectives, policies, regulatory obligations, value, and operational impacts can provide useful decision criteria. The analyst facilitates the discussion and documents the outcome rather than arbitrarily selecting one requirement. Traceability and decision records should then be updated so affected teams understand which requirement or revised approach is authoritative.

Question 192.

A business analyst learns that users are bypassing a newly implemented workflow because it requires excessive manual data entry. What should the analyst do?

1. Assume users are simply resistant to change
   2. Disable alternative workflows without investigation
   3. Declare the solution successful because it was deployed
   4. Investigate the behavior, underlying usability or process issues, and resulting impact on expected benefits

Correct Answer: 4

Explanation:

User workarounds can provide evidence that the implemented solution does not fit operational needs effectively. The analyst should investigate why users bypass the workflow rather than immediately attributing the behavior to resistance. Excessive data entry, duplicated information, poor usability, performance issues, or misaligned processes may be contributing factors. Usage data, observation, and stakeholder feedback can help identify the cause. Corrective action may involve solution changes, process redesign, training, or other measures. Adoption is an important component of benefits realization.

Question 193.

Why is requirements decomposition useful?

1. It breaks complex needs into manageable components that can be analyzed, understood, prioritized, and validated more effectively.
   2. It guarantees that every requirement becomes independent.
   3. It eliminates relationships among requirements.
   4. It prevents requirements from being grouped into higher-level capabilities.

Correct Answer: 1

Explanation:

Complex requirements or capabilities can be difficult to understand and implement as single large statements. Decomposition breaks them into smaller components that can be examined in greater detail. This can improve clarity, estimation, prioritization, traceability, and acceptance. However, decomposition should preserve relationships and the higher-level context so teams understand how individual requirements contribute to broader outcomes. The analyst should avoid excessive fragmentation that makes requirements difficult to manage or causes stakeholders to lose sight of the overall business capability being delivered.

Question 194.

A business analyst is evaluating whether a requirement can realistically be delivered before a legally mandated deadline. Which feasibility aspect is especially important?

1. Visual feasibility
   2. Schedule feasibility
   3. Terminology feasibility
   4. Stakeholder popularity

Correct Answer: 2

Explanation:

Schedule feasibility considers whether required capabilities can be delivered within necessary time constraints. A legally mandated deadline may make timing particularly important because missing it could create compliance or operational consequences. The analyst should consider dependencies, resource availability, procurement lead times, implementation complexity, testing, approvals, and transition activities. If the deadline appears infeasible, stakeholders may need to reduce scope, change the solution approach, add resources, or pursue another authorized response. Schedule feasibility should be evaluated alongside other feasibility dimensions.

Question 195.

A requirement specifies that customer records must be recoverable after a major system failure. What should the business analyst clarify?

1. Only the screen used to view customer records
   2. Only who originally requested the requirement
   3. Recovery objectives, acceptable data loss, restoration expectations, business criticality, and applicable constraints
   4. Only the database product

Correct Answer: 3

Explanation:

A general requirement for recoverability is insufficient unless stakeholders define what acceptable recovery means. The analyst should clarify how quickly service or information must be restored, how much data loss is tolerable, which capabilities are most critical, and whether regulatory or contractual constraints apply. These expectations can have significant architectural, operational, and cost implications. Technical specialists can help determine implementation approaches, but the business should establish the required level of resilience based on operational impact and risk tolerance.

Question 196.

A stakeholder proposes using a specific technology before the business requirements have been sufficiently analyzed. What should the business analyst do?

1. Adopt the technology immediately
   2. Reject the technology because stakeholders should not suggest solutions
   3. Stop elicitation and begin procurement
   4. Understand the underlying need and evaluate the proposed technology alongside appropriate alternatives

Correct Answer: 4

Explanation:

Stakeholders can provide valuable solution ideas, but a proposed technology should not automatically become the requirement. The analyst should separate the underlying business need from the suggested implementation and determine what capabilities and outcomes are actually required. The technology can then be evaluated against those needs, constraints, costs, risks, and other alternatives. It may ultimately be the most appropriate choice, but the decision should be supported by analysis. This reduces the risk of forcing business needs to fit a prematurely selected solution.

Question 197.

What should a business analyst do when a requirement’s priority changes because a new regulatory deadline has been announced?

1. Reassess the priority and related release or dependency implications using the new information.
   2. Preserve the old priority because priorities should never change.
   3. Remove the regulatory requirement.
   4. Change priorities without informing stakeholders.

Correct Answer: 1

Explanation:

Prioritization should respond to legitimate changes in the business environment. A new regulatory deadline can significantly increase urgency and may require adjustments to release planning, dependencies, resource allocation, and other requirements. The analyst should evaluate these consequences and ensure the revised priority follows appropriate governance. Changes should be communicated to affected stakeholders so teams understand why sequencing has changed. Maintaining outdated priorities despite material new information can prevent the initiative from satisfying mandatory obligations at the required time.

Question 198.

A business analyst wants to identify how external political, economic, social, technological, legal, and environmental factors may affect an initiative. Which technique is appropriate?

1. Decision table
   2. PESTLE analysis
   3. Data normalization
   4. Requirements versioning

Correct Answer: 2

Explanation:

PESTLE analysis provides a structured way to examine external political, economic, social, technological, legal, and environmental factors that can influence an organization or initiative. It can reveal opportunities, threats, constraints, and assumptions that might otherwise be overlooked. The technique is particularly useful during strategic and needs analysis when understanding the broader environment is important. Findings should be connected to business objectives, risks, requirements, or solution decisions rather than treated as an isolated exercise. External factors should also be revisited when conditions change.

Question 199.

A business analyst finds that a solution meets every documented functional requirement but users still cannot efficiently complete a critical business task. What should the analyst investigate?

1. Only whether every requirement has an identifier
   2. Only whether development finished on schedule
   3. Usability, workflow, nonfunctional requirements, missing needs, and whether the documented requirements adequately represented the business outcome
   4. Only the original project budget

Correct Answer: 3

Explanation:

Functional compliance does not necessarily mean the solution enables users to achieve business outcomes effectively. Poor usability, inefficient workflow, performance problems, missing scenarios, or incomplete requirements can prevent users from completing tasks despite individual functions working as specified. The analyst should evaluate the solution from the stakeholder and business-outcome perspective and determine where the gap originates. This illustrates why solution validation and evaluation extend beyond checking whether each documented function was technically implemented according to specification.

Question 200.

After reviewing solution performance, the business analyst identifies an opportunity that could generate additional value beyond the original initiative objectives. What should the analyst do?

1. Implement the opportunity without authorization
   2. Ignore it because the original project is complete
   3. Add it retroactively to the original requirements baseline
   4. Document and communicate the opportunity so appropriate stakeholders can evaluate it as potential future work

Correct Answer: 4

Explanation:

Solution evaluation can reveal new opportunities as well as performance problems. If an opportunity falls outside the original objectives or authorized scope, the analyst should document its potential value, supporting evidence, assumptions, and relevant impacts and communicate it to appropriate stakeholders. It can then be considered through normal portfolio, product, enhancement, or project decision processes. The analyst should not implement unauthorized scope simply because the opportunity appears valuable. Preserving the finding enables the organization to consider it deliberately as part of future investment decisions.