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

 

Question 381.

A business analyst discovers that a proposed solution depends on customers changing a long-established behavior. What should the analyst do?

1. Assume customers will change once the solution is launched
   2. Analyze the behavioral assumption, obtain supporting evidence, and consider adoption risks and enabling actions
   3. Remove customer behavior from the business case
   4. Guarantee the expected adoption rate

Correct Answer: 2

Explanation:

Expected benefits may fail to materialize when they depend on behavioral changes that have not been validated. The analyst should make the assumption explicit and seek evidence through research, prototypes, pilots, experiments, interviews, or relevant historical data. Barriers to adoption should also be identified. The solution may require communication, incentives, process changes, training, or usability improvements to encourage the desired behavior. By evaluating the assumption before relying heavily on it, stakeholders gain a more realistic understanding of expected value and benefit-realization risk.

Question 382.

A business analyst wants to identify the root cause of repeated operational failures by progressively asking why each condition occurs. Which technique is most appropriate?

1. Five Whys
   2. RACI matrix
   3. Context diagram
   4. Kano analysis

Correct Answer: 1

Explanation:

The Five Whys technique explores cause-and-effect relationships by repeatedly asking why a problem or contributing condition exists. The number five is not mandatory; the analyst continues until a sufficiently actionable underlying cause is identified. The technique is simple and useful for many operational problems, although complex issues may have multiple interacting causes and require additional evidence or techniques. Analysts should avoid forcing a single causal chain when the data suggests several causes. The objective is to move beyond symptoms and identify factors that can meaningfully be addressed.

Question 383.

A business analyst finds that a requirement is based on data from a report whose calculation method recently changed. What should the analyst do?

1. Continue using the old figures without investigation
   2. Remove all quantitative requirements
   3. Determine how the calculation change affects the evidence, assumptions, baseline, and requirement
   4. Select whichever calculation produces the preferred result

Correct Answer: 3

Explanation:

Changes in measurement methodology can make historical and current figures difficult to compare. The analyst should understand what changed in the calculation, whether previous values can be restated, and how the change affects baselines, targets, assumptions, and requirements. Stakeholders should know when apparent performance differences result from measurement changes rather than actual business improvement or deterioration. Reliable requirements and business cases depend on trustworthy evidence. Measurement definitions should therefore be documented and maintained consistently whenever quantitative information supports important decisions.

Question 384.

A new system must recover critical business operations within two hours after a major disruption. What should the business analyst clarify?

1. Only the backup software brand
   2. Only the number of servers
   3. Only the disaster-recovery team’s location
   4. Business continuity priorities, recovery objectives, critical capabilities, data-loss tolerance, dependencies, and acceptance measures

Correct Answer: 4

Explanation:

A two-hour recovery requirement should be connected to the organization’s actual continuity needs. The analyst should identify which capabilities are critical, what recovery time is required, how much data loss is tolerable, and which dependencies must also be restored. Different business services may require different recovery objectives. Technical specialists can design the recovery architecture, but business stakeholders should define the required outcomes based on operational impact and risk tolerance. Clear continuity requirements also provide a basis for recovery testing and acceptance.

Question 385.

Why should a business analyst record decisions made during requirements analysis?

1. A decision record preserves what was decided, relevant rationale, authority, and context for future understanding and change analysis.
   2. Decision records prevent all future changes.
   3. Only rejected decisions should be documented.
   4. Decision records replace requirements.

Correct Answer: 1

Explanation:

Requirements often reflect decisions about scope, priorities, business rules, alternatives, assumptions, and trade-offs. Without a decision record, future stakeholders may understand what was selected but not why. Recording important decisions, rationale, authority, date, and relevant alternatives can improve transparency and reduce repeated debate. Decision information is also useful when conditions change because analysts can determine whether the original rationale remains valid. Decision records complement requirements, traceability, and change management rather than replacing them.

Question 386.

A business analyst needs to collect ideas from a group while preventing senior participants from influencing others during initial idea generation. Which technique could help?

1. Open debate led by the most senior stakeholder
   2. Nominal group technique with independent idea generation followed by structured sharing and prioritization
   3. Unstructured interviewing
   4. Observation

Correct Answer: 2

Explanation:

The nominal group technique can reduce dominance effects by allowing participants to generate ideas independently before structured sharing and evaluation. This gives quieter participants an opportunity to contribute without immediately adapting their ideas to the views of senior or vocal stakeholders. The group can then clarify and prioritize the collected ideas using an agreed method. The technique is useful when balanced participation matters and a group must produce or rank alternatives. Effective facilitation remains important to ensure that the resulting priorities reflect informed judgment.

Question 387.

A business analyst discovers that a solution requires information that is maintained differently by several business units. What should the analyst do?

1. Select one unit’s data without analysis
   2. Require all units to change immediately
   3. Analyze definitions, ownership, quality, sources, transformation needs, and legitimate business differences
   4. Duplicate all conflicting information permanently

Correct Answer: 3

Explanation:

Differences in data across business units may result from inconsistent definitions, local business requirements, quality problems, or legitimate regional or operational variations. The analyst should understand these causes before recommending standardization. Relevant data owners and business stakeholders can determine which information should be authoritative and which variations must remain. Integration or transformation rules may also be required. Treating one source as correct without analysis can introduce errors, while preserving unnecessary inconsistencies can create reporting and operational problems.

Question 388.

A business analyst is evaluating a proposed automated decision that could materially affect customers. What should the analyst ensure is addressed?

1. Only processing speed
   2. Only implementation cost
   3. Only the algorithm’s name
   4. Decision rules, required data, exceptions, controls, transparency needs, review paths, and relevant legal or policy obligations

Correct Answer: 4

Explanation:

High-impact automated decisions require careful analysis beyond functional automation. The analyst should understand the decision rules, input data, quality requirements, exceptions, and business controls. Depending on the context, customers or employees may require explanations, correction mechanisms, or human review. Legal, regulatory, privacy, fairness, and organizational policy requirements may also apply. The analyst should work with appropriate specialists and business authorities rather than assuming technical automation automatically makes a decision acceptable. Clear requirements support accountable and consistent business outcomes.

Question 389.

What is an important purpose of analyzing requirement volatility?

1. It can reveal areas of uncertainty or frequent change that may affect planning, risk, analysis effort, and solution decisions.
   2. It proves frequently changing requirements have no value.
   3. It prevents all future requirement changes.
   4. It automatically determines project cost.

Correct Answer: 1

Explanation:

Requirement volatility describes the extent to which requirements change over time. High volatility may indicate evolving stakeholder understanding, changing market conditions, unresolved decisions, unstable regulations, or poorly understood needs. Tracking meaningful change trends can help the analyst and project stakeholders identify areas requiring additional analysis, flexible solution approaches, or risk attention. Volatility is not inherently negative, particularly in iterative environments where learning is expected. The key is understanding why change occurs and ensuring that the initiative can respond appropriately.

Question 390.

A business analyst needs to understand which business entities are created, read, updated, or deleted by different process activities. Which technique can help?

1. PESTLE analysis
   2. CRUD matrix
   3. Kano analysis
   4. Force-field analysis

Correct Answer: 2

Explanation:

A CRUD matrix maps business entities or data objects against activities, processes, roles, or system functions and indicates where information is Created, Read, Updated, or Deleted. It can reveal missing responsibilities, duplicated maintenance, unexpected data dependencies, and inconsistencies between process and data requirements. The technique is useful when analysts need to understand how business activities interact with information. A CRUD matrix does not replace detailed data models or process models, but it provides a valuable cross-check between these perspectives.

Question 391.

A business analyst finds that stakeholders have different opinions about a proposed change because they are using different assumptions about future transaction growth. What should the analyst do?

1. Select the highest forecast automatically
   2. Select the lowest forecast automatically
   3. Make the assumptions explicit and compare solution implications under reasonable growth scenarios
   4. Remove growth from the analysis

Correct Answer: 3

Explanation:

Disagreement may arise not from different objectives but from different underlying assumptions. The analyst should identify those assumptions explicitly and evaluate how alternative growth scenarios affect capacity, cost, benefits, performance, and solution feasibility. Scenario or sensitivity analysis can show whether the preferred approach remains appropriate under a range of plausible conditions. This allows stakeholders to discuss the actual source of disagreement rather than debating conclusions based on hidden assumptions. Important assumptions should also be monitored as better information becomes available.

Question 392.

A business analyst is reviewing a proposed solution that depends on a single specialized employee for a critical operational activity. What should the analyst investigate?

1. Only the employee’s salary
   2. Whether the employee likes the proposed solution
   3. Only the employee’s job title
   4. Key-person dependency, knowledge transfer, backup capability, process resilience, and operational risk

Correct Answer: 4

Explanation:

Critical dependence on one individual can create significant operational risk. The analyst should determine what knowledge or authority is concentrated in that role, what happens when the employee is unavailable, and whether responsibilities can be documented, transferred, cross-trained, or supported through other controls. The solution may require changes to roles, procedures, access, training, or automation. Organizational feasibility includes the ability to sustain operations after implementation, not simply whether the initial solution can be delivered while a particular individual remains available.

Question 393.

Why should requirements be traceable to relevant business rules?

1. Traceability helps explain required behavior and supports impact analysis when the underlying business rule changes.
   2. Business rules can never change.
   3. Traceability eliminates the need to document requirements.
   4. Every requirement must originate from exactly one business rule.

Correct Answer: 1

Explanation:

Requirements often implement or support business rules concerning eligibility, calculations, approvals, limits, or other organizational behavior. Linking requirements to relevant rules helps stakeholders understand why the behavior exists and identify affected solution components when a rule changes. One rule may affect multiple requirements, and a requirement may be influenced by several sources, so traceability need not be one-to-one. Maintaining meaningful relationships supports change analysis, consistency, auditability, and long-term maintenance, particularly in environments where policies or regulations change frequently.

Question 394.

A business analyst is preparing a workshop involving participants who rarely speak during group discussions. What should the analyst do?

1. Assume silence means agreement
   2. Use facilitation approaches such as silent idea generation, direct invitations, structured rounds, or smaller groups to encourage participation
   3. Allow only vocal stakeholders to contribute
   4. Remove quiet participants from the workshop

Correct Answer: 2

Explanation:

Silence does not necessarily indicate agreement or lack of useful knowledge. Some participants may hesitate because of hierarchy, personality, language, meeting dynamics, or uncertainty. The analyst should use facilitation techniques that provide multiple ways to contribute. Silent brainstorming, structured rounds, smaller groups, anonymous input, or direct but respectful questions can help surface additional perspectives. Balanced participation improves requirements quality because important operational knowledge may reside with people who are less comfortable competing for speaking time in a large group.

Question 395.

A business analyst discovers that a proposed requirement would create a large amount of additional data but there is no defined business need for retaining it. What should the analyst do?

1. Retain all data indefinitely because storage is inexpensive
   2. Collect the data first and decide later
   3. Clarify the purpose, necessity, retention, access, privacy, security, and lifecycle requirements before collecting it
   4. Make all collected data publicly accessible

Correct Answer: 3

Explanation:

Collecting data without a defined purpose can create unnecessary cost, privacy exposure, security risk, and governance obligations. The analyst should determine why the information is needed, who requires access, how long it should be retained, and what legal, regulatory, contractual, or organizational rules apply. Data should support legitimate business needs rather than being collected merely because the technology permits it. Clear lifecycle requirements also address archival, deletion, and appropriate use, helping the organization manage information responsibly throughout its existence.

Question 396.

A business analyst finds that a planned release delivers several technical components but no capability that users can meaningfully use until a later release. What should the analyst do?

1. Measure success only by the number of components delivered
   2. Ignore business value until the final project release
   3. Split every technical component into smaller technical components
   4. Explore whether requirements can be sliced or sequenced to deliver usable incremental business value earlier

Correct Answer: 4

Explanation:

Incremental delivery is most valuable when increments provide meaningful capabilities or useful learning rather than merely completing disconnected technical components. The analyst can work with stakeholders and delivery teams to examine whether requirements can be sliced vertically across necessary process, data, interface, and rule elements. Dependencies may prevent some capabilities from being delivered earlier, but those constraints should be understood explicitly. Earlier usable increments can accelerate feedback, validate assumptions, reduce risk, and begin realizing business value before the entire initiative is complete.

Question 397.

What is an important purpose of conducting a retrospective or lessons-learned activity during iterative delivery?

1. To identify improvements to collaboration, analysis, delivery practices, and future iterations based on recent experience
   2. To assign blame for every problem
   3. To prevent requirements from changing
   4. To replace solution evaluation

Correct Answer: 1

Explanation:

Retrospectives create a structured opportunity to examine what worked, what did not, and what the team can improve in subsequent iterations. Business analysis practices may benefit through better elicitation timing, stakeholder engagement, requirement refinement, communication, or validation. The purpose is continuous improvement rather than blame. Actions should be specific enough to influence future work and can be reviewed in later retrospectives. Retrospectives focus primarily on how work is performed, while solution evaluation addresses whether the resulting solution produces expected business value.

Question 398.

A business analyst needs to understand factors supporting and resisting a proposed organizational change. Which technique could be useful?

1. Entity relationship diagram
   2. Force-field analysis
   3. CRUD matrix
   4. Decision table

Correct Answer: 2

Explanation:

Force-field analysis examines forces that support a desired change and forces that resist it. Supporting forces might include executive sponsorship, customer demand, or expected cost savings, while restraining forces could include skill gaps, cultural resistance, workload, or competing priorities. Understanding both sides can help stakeholders develop more realistic transition and adoption strategies. The technique does not determine whether the change should automatically proceed, but it provides a structured way to consider organizational conditions that may enable or hinder successful implementation.

Question 399.

A business analyst discovers that a solution’s reported adoption rate includes users who logged in once but never completed a meaningful business task. What should the analyst do?

1. Continue using login count because it produces a higher adoption rate
   2. Stop measuring adoption
   3. Define adoption using meaningful business behavior and establish an appropriate measurement method
   4. Count every employee as an active user

Correct Answer: 3

Explanation:

A metric should represent the business concept it claims to measure. A single login may demonstrate awareness or access but may not indicate meaningful adoption. The analyst should clarify what successful adoption means in the context of expected benefits, such as completing important transactions, using key capabilities repeatedly, or replacing an old process. The measurement population, frequency, and thresholds should also be defined. Meaningful adoption measures provide better evidence about whether users are changing behavior sufficiently to support expected business outcomes.

Question 400.

A business analyst completes a solution evaluation and identifies several opportunities to increase realized value. What should happen next?

1. Ignore the opportunities because implementation is complete
   2. Implement every improvement without authorization
   3. Reopen the original project automatically
   4. Communicate the findings and recommendations so authorized stakeholders can evaluate potential corrective actions or future changes

Correct Answer: 4

Explanation:

Solution evaluation can identify opportunities to improve benefits, reduce costs, address limitations, increase adoption, or respond to changing business conditions. The analyst should communicate evidence, impacts, assumptions, and potential recommendations to the stakeholders responsible for investment or operational decisions. Some improvements may justify immediate corrective action, while others may become future initiatives or be rejected because their cost exceeds expected value. Evaluation supports informed decisions; it does not automatically authorize implementation of every identified opportunity.