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

 

Question 121.

A business analyst learns that two departments calculate the same key performance indicator differently. What should the analyst do?

1. Facilitate agreement on a consistent definition, calculation method, data source, and ownership for the indicator.
   2. Allow both definitions to remain without clarification.
   3. Select the calculation that produces the better result.
   4. Stop using performance indicators.

Correct Answer: 1

Explanation:

A performance indicator provides useful information only when stakeholders understand and apply it consistently. Different calculation methods can produce conflicting reports and undermine solution evaluation. The business analyst should identify the purpose of the indicator, clarify required data, establish an agreed calculation, and determine the authoritative source and owner. Historical data may also need to be interpreted carefully if previous calculations used different definitions. Consistent measurement allows stakeholders to compare results reliably and determine whether business objectives and expected benefits are actually being achieved.

Question 122.

A business analyst is assessing a business problem and finds several possible causes. Which action should be taken before recommending a solution?

1. Select the cause mentioned by the most senior stakeholder.
   2. Analyze available evidence to determine the underlying root cause or causes.
   3. Implement separate solutions for every possible cause.
   4. Assume technology is responsible.

Correct Answer: 2

Explanation:

A visible business problem may have several contributing factors, and stakeholders’ initial explanations may describe symptoms rather than root causes. The analyst should examine relevant data, processes, policies, systems, and stakeholder observations to understand what is actually producing the problem. Root cause techniques can help organize and test possible explanations. Recommending a solution before understanding the causes can result in investment that addresses symptoms while leaving the underlying problem unchanged. Evidence-based analysis provides a stronger foundation for defining requirements and evaluating solution alternatives.

Question 123.

During requirements planning, the business analyst identifies a stakeholder who has high influence but limited interest in detailed project activities. How should the analyst generally approach engagement?

1. Send every detailed requirement to the stakeholder daily.
   2. Exclude the stakeholder because interest is low.
   3. Provide appropriately focused information and engage the stakeholder when significant decisions or issues require attention.
   4. Delegate the stakeholder’s authority to the development team.

Correct Answer: 3

Explanation:

Stakeholder engagement should reflect both influence and information needs. A highly influential stakeholder may be important to major decisions even when that person does not need detailed involvement in routine analysis. The business analyst should provide concise, relevant information and ensure the stakeholder is engaged when decisions, risks, or changes warrant attention. Excessive detail can reduce engagement, while complete exclusion can create governance problems. Stakeholder strategies should also be reviewed over time because influence, interest, and decision needs can change during an initiative.

Question 124.

A stakeholder asks for a requirement to be implemented, but the analyst cannot determine what business need it supports. What should the analyst do?

1. Add it because every stakeholder request is automatically a requirement.
   2. Assign it to the next release without analysis.
   3. Ask developers to invent a justification.
   4. Investigate the rationale and establish traceability to a legitimate need before recommending implementation.

Correct Answer: 4

Explanation:

A requested feature should have a legitimate reason for consuming project resources. The analyst should determine whether it supports a business objective, stakeholder need, regulatory obligation, risk response, or another justified outcome. If no rationale can be established, the request should be challenged through the appropriate prioritization or governance process. This does not mean the analyst independently rejects stakeholder requests. Instead, the analyst makes the absence of justification visible so authorized stakeholders can make an informed scope decision based on value and necessity.

Question 125.

What is an important purpose of requirements attributes such as priority, status, source, and owner?

1. They provide management information that supports analysis, tracking, governance, and requirements lifecycle activities.
   2. They replace the actual requirement statements.
   3. They eliminate the need for stakeholder communication.
   4. They guarantee that requirements cannot change.

Correct Answer: 1

Explanation:

Requirements attributes provide useful information about requirements beyond their descriptive text. Priority supports sequencing and trade-offs, status indicates lifecycle position, source supports clarification and traceability, and ownership can identify responsibility for decisions or maintenance. Other attributes may include risk, complexity, release, rationale, or acceptance status. The specific attributes should be tailored to the initiative rather than collected unnecessarily. Well-managed attributes make a large requirement set easier to organize, analyze, communicate, and govern throughout its lifecycle.

Question 126.

A business analyst wants to understand which organizational strengths and weaknesses may influence a proposed change. Which technique could help?

1. Source-code review
   2. SWOT analysis
   3. Automated regression testing
   4. Contract invoicing

Correct Answer: 2

Explanation:

SWOT analysis examines strengths, weaknesses, opportunities, and threats relevant to a business situation or proposed initiative. Strengths and weaknesses generally address internal factors, while opportunities and threats often relate to the external environment. The technique can help stakeholders consider organizational capabilities and environmental conditions when evaluating change. SWOT analysis is typically one input among several rather than a complete solution-selection method. Findings should be supported by appropriate evidence and connected to objectives, risks, constraints, and other business analysis information.

Question 127.

A proposed requirement is expected to increase revenue but may significantly reduce customer retention. What should the business analyst do?

1. Recommend it based only on the revenue increase.
   2. Reject it immediately because customer retention may decline.
   3. Analyze the combined benefits, costs, risks, assumptions, and longer-term business impacts.
   4. Exclude customer impact from the business case.

Correct Answer: 3

Explanation:

Business value should be considered holistically. An initiative that produces short-term revenue but damages customer retention could create unfavorable longer-term consequences. The analyst should quantify or otherwise evaluate both effects where possible and make important assumptions explicit. Sensitivity analysis may help when future customer behavior is uncertain. The appropriate decision belongs to authorized stakeholders, but they need visibility into the full trade-off. Evaluating only one favorable measure can result in a recommendation that does not reflect the organization’s broader objectives.

Question 128.

During elicitation, stakeholders frequently move into discussions that are outside the agreed initiative scope. What should the business analyst do?

1. Allow unlimited discussion of every topic.
   2. Delete every out-of-scope idea immediately.
   3. Expand project scope during the meeting.
   4. Refocus the session while appropriately capturing potentially valuable out-of-scope items for separate consideration.

Correct Answer: 4

Explanation:

Effective facilitation keeps elicitation aligned with its objectives while ensuring useful ideas are not unnecessarily lost. When discussion moves outside scope, the analyst can record the item in a parking lot, issue list, future-opportunity log, or another appropriate location and return participants to the current topic. The item can later be evaluated through the appropriate governance process. This approach respects stakeholder contributions while protecting limited workshop time and preventing informal scope expansion without analysis or authorization.

Question 129.

A business analyst is reviewing a business case. Why is sensitivity analysis useful?

1. It helps show how changes in important assumptions can affect expected costs, benefits, or outcomes.
   2. It guarantees that forecasts are accurate.
   3. It removes uncertainty from the initiative.
   4. It replaces stakeholder decision-making.

Correct Answer: 1

Explanation:

Business cases often depend on assumptions about volumes, adoption, costs, savings, revenue, implementation time, or other uncertain variables. Sensitivity analysis changes important assumptions to determine how strongly they affect expected results. This helps decision-makers understand which assumptions matter most and how robust the business case is under different conditions. It does not eliminate uncertainty or predict the future with certainty. Instead, it makes uncertainty more visible and supports more informed investment, risk, and contingency decisions.

Question 130.

A business analyst needs to identify the responsibilities of several roles participating in a complex business process. Which technique is useful?

1. Product pricing analysis
   2. Responsibility assignment or role-responsibility analysis
   3. Source-code debugging
   4. Financial auditing only

Correct Answer: 2

Explanation:

Role-responsibility analysis can clarify who performs activities, provides input, makes decisions, approves outputs, or owns results within a business process. This is useful when unclear accountability contributes to delays, duplicated effort, or missed work. A responsibility matrix can make these relationships easier to discuss with stakeholders. The analyst should ensure that the representation reflects actual organizational authority rather than simply documenting assumed responsibilities. Clear roles also help define future-state processes and identify organizational changes required to implement a solution successfully.

Question 131.

A requirement has been implemented, but testing shows that it satisfies the written specification while failing to meet the stakeholder’s actual business need. What does this most strongly indicate?

1. The requirement must be technically correct because testing passed.
   2. The stakeholder should change the business need.
   3. There may have been a requirements validation problem despite successful verification against the specification.
   4. Traceability is no longer necessary.

Correct Answer: 3

Explanation:

A solution can conform precisely to a written requirement and still fail to solve the intended business problem. This distinction highlights the importance of requirements validation. Verification asks whether the requirement or solution conforms to specified expectations, while validation considers whether the right requirement was defined to satisfy the underlying need. The analyst should examine how the requirement was derived, what assumptions were made, and whether stakeholder intent was correctly understood. The resulting correction should follow appropriate change and governance procedures.

Question 132.

A stakeholder requests a requirement change that appears minor but affects a shared data field used by many systems. What should the business analyst do?

1. Approve it immediately because the wording change is small.
   2. Modify only the user interface.
   3. Ignore downstream systems.
   4. Perform impact analysis using data, interface, requirement, and solution traceability before a decision is made.

Correct Answer: 4

Explanation:

The apparent size of a request does not necessarily reflect its actual impact. A change to a shared data element can affect integrations, reports, business rules, downstream systems, migration logic, testing, and operational procedures. The analyst should use available traceability and models to identify these relationships and communicate the consequences to decision-makers. This enables the change to be evaluated based on its real cost, risk, and value. Impact analysis is particularly important in highly integrated environments where small data changes can propagate widely.

Question 133.

Why should a business analyst define the scope of analysis before detailed requirements elicitation?

1. It establishes boundaries that help focus analysis on the business problem, affected capabilities, and relevant stakeholders.
   2. It prevents any future scope changes.
   3. It eliminates the need to identify stakeholders.
   4. It defines every detailed requirement in advance.

Correct Answer: 1

Explanation:

Defining analysis scope provides boundaries for what the initiative is intended to address and helps determine which processes, capabilities, systems, and stakeholders require attention. Without sufficient scope clarity, elicitation can expand into unrelated areas or overlook important interfaces. Scope can evolve through controlled decisions as new information emerges, so it should not be viewed as permanently fixed. Establishing boundaries early improves elicitation planning, stakeholder identification, estimation, communication, and the evaluation of proposed changes against the initiative’s intended purpose.

Question 134.

A business analyst needs to understand how customer satisfaction varies across different customer groups. What should the analyst do?

1. Use only the overall average satisfaction score.
   2. Segment relevant data and analyze patterns across meaningful customer groups.
   3. Interview only the most satisfied customer.
   4. Assume all customers have identical needs.

Correct Answer: 2

Explanation:

Aggregate measures can hide important differences among stakeholder or customer groups. Segmentation allows the analyst to examine whether satisfaction varies by characteristics relevant to the business, such as customer type, channel, geography, product, or service level. These patterns may reveal different needs or problems that should influence requirements. Segmentation should be purposeful and use appropriate, reliable data. The analyst should also avoid drawing conclusions from very small or unrepresentative groups without considering the limitations of the available evidence.

Question 135.

A business analyst is evaluating a proposed automation that will eliminate several manual control steps. What should the analyst do?

1. Remove the controls because automation always reduces risk.
   2. Preserve every manual step exactly as it exists.
   3. Determine the purpose of the controls and ensure the future solution provides appropriate control effectiveness.
   4. Ignore controls until after implementation.

Correct Answer: 3

Explanation:

Manual activities may exist partly to provide authorization, validation, segregation of duties, auditability, or other controls. When automating a process, the analyst should understand why those controls exist rather than simply eliminating or reproducing them. Some controls may become unnecessary, while others may need automated equivalents or redesigned procedures. Relevant compliance, risk, and operational stakeholders should be involved. The objective is to create an efficient future process while preserving the necessary level of control and ensuring requirements reflect the intended risk-management outcomes.

Question 136.

During requirements review, a stakeholder identifies a missing scenario that could cause substantial financial loss. What should the business analyst do?

1. Ignore it because the requirements were already drafted.
   2. Wait until production to determine whether it occurs.
   3. Remove related scenarios to maintain consistency.
   4. Analyze the scenario, determine required behavior, and update affected requirements and related artifacts appropriately.

Correct Answer: 4

Explanation:

Requirements reviews are intended to identify omissions and problems before they become expensive implementation defects. A missing scenario with potentially significant financial consequences deserves careful analysis even if it is uncommon. The analyst should understand its trigger, expected business response, rules, data needs, and relationships to existing requirements. Models, acceptance criteria, and tests may also require updates. The change should follow applicable governance. Discovering such a scenario during review is valuable because it provides an opportunity to address the risk before deployment.

Question 137.

What is an important reason to maintain a decision log during business analysis?

1. It preserves significant decisions, rationale, responsible parties, and relevant context for later reference.
   2. It eliminates the need for requirements documentation.
   3. It ensures decisions can never be reconsidered.
   4. It replaces formal approvals in every situation.

Correct Answer: 1

Explanation:

Business analysis frequently involves decisions about scope, priorities, requirements, assumptions, rules, and solution alternatives. A decision log provides a record of what was decided, why, by whom, and sometimes when or under what assumptions. This information is useful when stakeholders later question a requirement or when conditions change. It supports continuity when team members change and reduces repeated discussion of previously resolved issues. A decision log complements other governance artifacts and does not automatically replace whatever formal approval mechanisms the initiative requires.

Question 138.

A business analyst discovers that different reports contain conflicting values for the same business metric. What should the analyst investigate first?

1. Which report has the most attractive design
   2. Data sources, definitions, transformation rules, timing, and calculation methods
   3. Which stakeholder has the highest title
   4. Whether all reports can be deleted

Correct Answer: 2

Explanation:

Conflicting metric values often result from differences in definitions, source systems, reporting periods, transformations, filters, or calculation rules. The analyst should determine how each report produces the value and identify the authoritative business definition. This analysis can expose broader data-quality or governance issues that need to be addressed in requirements. Selecting a value based on appearance or stakeholder seniority would not resolve the underlying inconsistency. Reliable reporting depends on common definitions and trustworthy data lineage.

Question 139.

An organization wants to measure whether a newly implemented process has reduced operational risk. What should the business analyst do?

1. Count only the number of requirements delivered.
   2. Assume risk decreased because the process changed.
   3. Compare relevant risk indicators and outcomes against established baseline and target measures.
   4. Evaluate only implementation cost.

Correct Answer: 3

Explanation:

Risk reduction should be evaluated using measures related to the risk itself rather than simply confirming that a process was implemented. Depending on the context, measures could include incident frequency, error rates, control failures, financial exposure, audit findings, or other indicators. Baseline information provides a reference point, while target measures define the expected improvement. The analyst should also consider whether external factors influenced results. Measuring outcomes helps determine whether the new process actually delivered the intended risk-reduction benefit.

Question 140.

A solution is ready for release, but an important stakeholder group has not participated in validation. What should the business analyst do?

1. Assume other stakeholders adequately represent the missing group.
   2. Release the solution automatically because development is complete.
   3. Remove the stakeholder group from project records.
   4. Assess the validation gap and obtain appropriate representation or input before acceptance when their needs materially affect solution suitability.

Correct Answer: 4

Explanation:

Validation should provide reasonable confidence that the solution satisfies the needs of relevant stakeholders and supports intended business outcomes. If an important affected group has not participated, the analyst should determine whether their perspective is sufficiently represented elsewhere or whether additional validation is necessary. This may involve representative users, targeted reviews, demonstrations, or other suitable techniques. Releasing without considering a materially affected stakeholder group can result in missed requirements, poor adoption, or operational problems that become much more expensive to correct after deployment.