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

 

Question 61.

A business analyst is asked to define success measures for a new customer self-service initiative. What should the analyst do first?

1. Identify measurable outcomes that are directly connected to the initiative’s business objectives.
   2. Select metrics that are easiest for the technical team to collect.
   3. Use the same measures as every previous project.
   4. Wait until the solution is implemented before defining success.

Correct Answer: 1

Explanation:

Success measures should demonstrate whether the initiative is producing the outcomes that justified the investment. The analyst should begin with the business objectives and identify measurable indicators that provide evidence of progress toward those objectives. For a self-service initiative, relevant measures might involve adoption, processing time, service cost, customer satisfaction, or reduction in assisted transactions. Metrics should not be selected merely because they are easy to collect. Defining measures early also establishes a baseline for later solution evaluation and benefits analysis.

Question 62.

A stakeholder states a requirement as, “The new solution must be easy to use.” What should the business analyst do?

1. Accept the statement because usability cannot be measured.
   2. Clarify the intended usability outcome and establish measurable criteria.
   3. Ask developers to decide what easy to use means.
   4. Remove usability from the requirements.

Correct Answer: 2

Explanation:

“Easy to use” is subjective and may mean different things to different stakeholders. The analyst should explore what users actually need and translate the expectation into measurable or observable criteria. Depending on the context, this could involve task completion time, error rates, number of steps, accessibility requirements, user satisfaction, or successful completion by representative users. Making the requirement measurable improves design guidance and provides an objective basis for validation and acceptance. Vague quality expectations can otherwise create disagreement late in the initiative.

Question 63.

A business analyst is reviewing a proposed requirement and discovers that satisfying it would negatively affect three previously approved requirements. What should the analyst do?

1. Implement the new requirement because it was requested most recently.
   2. Reject it automatically.
   3. Perform impact analysis and present the affected relationships and trade-offs to the appropriate decision-makers.
   4. Delete the existing requirements.

Correct Answer: 3

Explanation:

Requirements are often interconnected, so a proposed change can affect functionality, business processes, data, interfaces, testing, cost, schedule, or expected benefits. The analyst should use traceability and other relevant information to identify these consequences before a decision is made. Impact analysis does not automatically determine whether the change should be approved or rejected. Instead, it gives authorized stakeholders sufficient information to evaluate the trade-offs. This helps prevent changes from being considered in isolation and reduces unintended downstream effects.

Question 64.

A business analyst needs to obtain detailed information about how an experienced employee makes complex judgment-based decisions. Which approach would be most useful?

1. Review only the organizational chart.
   2. Send a generic survey to the entire organization.
   3. Review only the project budget.
   4. Use focused interviews and observation to explore the employee’s decision process.

Correct Answer: 4

Explanation:

Complex judgment-based work can contain tacit knowledge that employees may find difficult to describe through a questionnaire alone. Focused interviews allow the analyst to explore reasoning, exceptions, criteria, and examples, while observation can reveal how decisions are actually made in context. Combining techniques often produces richer information than relying on a single source. The analyst can then validate the resulting decision rules or models with the employee. Capturing this knowledge is especially important when a process is being redesigned or partially automated.

Question 65.

What is an important purpose of documenting the rationale for a requirement?

1. It explains why the requirement is needed and supports future prioritization, change analysis, and validation.
   2. It guarantees that the requirement will be implemented.
   3. It eliminates the need for traceability.
   4. It prevents stakeholders from challenging the requirement.

Correct Answer: 1

Explanation:

Requirement rationale records the reason a requirement exists. Understanding that reason helps stakeholders evaluate whether the requirement remains necessary when business conditions change. It also supports prioritization because decision-makers can compare the expected value or obligation behind different requirements. During change analysis, rationale helps determine whether a proposed modification still satisfies the original need. The rationale complements rather than replaces traceability. A requirement without a clear reason may warrant further investigation, particularly when implementation would require substantial cost or complexity.

Question 66.

A project has stakeholders in several countries who cannot attend the same live workshop. How should the business analyst approach elicitation?

1. Obtain requirements only from the project sponsor.
   2. Use an appropriate combination of asynchronous and synchronous techniques based on stakeholder availability and information needs.
   3. Exclude stakeholders who cannot attend live sessions.
   4. Wait until all stakeholders can travel to one location.

Correct Answer: 2

Explanation:

Distributed stakeholders may require a flexible elicitation strategy. The analyst can combine virtual interviews, surveys, document reviews, collaborative tools, recorded demonstrations, and smaller workshops across suitable time zones. The choice should reflect the complexity of the information, stakeholder availability, language or cultural considerations, and the need for interaction. Important findings should be validated across relevant groups. Effective elicitation does not depend on placing every stakeholder in one meeting; it depends on obtaining and reconciling the necessary perspectives using suitable techniques.

Question 67.

During requirements analysis, the business analyst identifies a requirement that provides little business value but consumes substantial implementation effort. What should happen?

1. It should automatically be implemented because it was elicited.
   2. Its estimated effort should be hidden from stakeholders.
   3. Its priority and justification should be reconsidered using the agreed decision criteria.
   4. All high-effort requirements should be rejected.

Correct Answer: 3

Explanation:

Elicitation does not mean that every identified requirement must be implemented. Requirements should be evaluated and prioritized based on factors such as business value, cost, effort, risk, urgency, dependencies, and mandatory obligations. A low-value, high-effort requirement may be deferred or removed unless another factor provides sufficient justification. The analyst should make the trade-off visible rather than deciding unilaterally. This helps stakeholders allocate limited resources toward capabilities that provide stronger value or satisfy essential business constraints.

Question 68.

A stakeholder requests access to sensitive customer data that is not necessary for the stakeholder’s business role. What should the business analyst do?

1. Add the access because the stakeholder requested it.
   2. Give all users the same access for consistency.
   3. Ignore security and privacy requirements during business analysis.
   4. Analyze the legitimate business need and applicable access, privacy, security, and compliance constraints before defining the requirement.

Correct Answer: 4

Explanation:

Access requirements should be based on legitimate business responsibilities and applicable security, privacy, regulatory, and organizational rules. The analyst should determine why the stakeholder believes the data is necessary and whether the requested access is proportionate to the business need. Alternatives such as limited views or masked information may satisfy the underlying requirement with less exposure. Business analysis should incorporate security and privacy considerations early because inappropriate access requirements can create significant organizational risk even when the requested functionality is technically feasible.

Question 69.

Why is baseline information important when evaluating the benefits of an implemented solution?

1. It provides a reference point for comparing performance before and after the change.
   2. It guarantees that performance will improve.
   3. It eliminates the need for success criteria.
   4. It determines the project’s final budget.

Correct Answer: 1

Explanation:

A baseline establishes the relevant level of performance before a change is implemented. Without it, stakeholders may have difficulty determining whether measured outcomes actually represent improvement. For example, if an initiative aims to reduce average processing time, the organization should understand the previous processing time so the new result can be compared meaningfully. Baseline information should use appropriate definitions and measurement methods so before-and-after comparisons remain valid. Baselines support benefits evaluation but do not guarantee that the expected improvement will occur.

Question 70.

A business analyst receives contradictory information from two subject matter experts about an existing policy. What should the analyst do?

1. Use the opinion of the person interviewed first.
   2. Investigate the authoritative source of the policy and reconcile the conflicting interpretations.
   3. Document both versions as simultaneously correct.
   4. Ignore the policy.

Correct Answer: 2

Explanation:

Conflicting stakeholder statements should be investigated rather than resolved arbitrarily. The analyst should identify the authoritative policy, rule, document, or decision owner and determine whether the disagreement results from outdated information, different interpretations, exceptions, or inconsistent practice. The correct interpretation should then be documented and communicated to relevant stakeholders. This is particularly important when policy influences requirements or acceptance criteria. Resolving such conflicts early prevents different teams from implementing inconsistent business behavior based on contradictory assumptions.

Question 71.

A business analyst needs to understand how information moves among external organizations, internal departments, and a proposed system. Which technique would be most helpful?

1. A meeting calendar
   2. A stakeholder attendance sheet
   3. A data flow or interface model
   4. A cost invoice

Correct Answer: 3

Explanation:

A data flow or interface model can show where information originates, where it goes, how it is transformed, and which external or internal parties exchange it. This helps the analyst identify interface requirements, missing information, duplicate data entry, dependencies, and potential ownership questions. Such models are particularly useful when multiple systems and organizations participate in a business process. The analyst should validate the model with relevant stakeholders so that important exchanges, triggers, and data requirements are accurately represented.

Question 72.

A requested requirement would improve one department’s efficiency but substantially increase workload for another department. What should the business analyst do?

1. Approve it because one department benefits.
   2. Ignore the second department because it did not request the change.
   3. Calculate only implementation cost.
   4. Analyze the end-to-end organizational impact and present the trade-off to the appropriate stakeholders.

Correct Answer: 4

Explanation:

Local optimization can create poor overall organizational outcomes. The analyst should evaluate the requirement across the complete process and identify impacts on all affected stakeholders. The analysis can consider workload, cost, cycle time, quality, risk, customer experience, and other relevant measures. Decision-makers can then determine whether the overall benefit justifies the redistribution of effort or whether another approach would provide better value. Business analysis should help stakeholders understand cross-functional consequences rather than evaluating requirements only from the requesting group’s perspective.

Question 73.

What should a business analyst do when a requirement no longer supports the initiative’s objectives because business conditions have changed?

1. Reassess its value and disposition through the established requirements-management process.
   2. Implement it because it was originally approved.
   3. Hide the changed business condition.
   4. Prevent stakeholders from reviewing it.

Correct Answer: 1

Explanation:

Requirements should remain aligned with current business needs throughout an initiative. If market conditions, regulations, strategy, assumptions, or other circumstances change, a previously valuable requirement may no longer justify its cost or complexity. The analyst should reassess the requirement and provide relevant information to authorized stakeholders so they can retain, modify, defer, or remove it. Approval is not a reason to deliver obsolete value. Requirements management should maintain control while allowing the initiative to respond appropriately to legitimate business changes.

Question 74.

A business analyst is preparing a requirements package for different stakeholder groups. What should guide how the information is presented?

1. Use exactly the same detail and format for every audience.
   2. Tailor the level of detail, format, terminology, and emphasis to stakeholder information needs while preserving consistency of meaning.
   3. Present only technical models to executives.
   4. Remove requirement identifiers from all documentation.

Correct Answer: 2

Explanation:

Different stakeholders use requirements information for different purposes. Executives may need objectives, scope, value, and major decisions, while developers and testers may require greater functional detail, rules, models, and acceptance criteria. Tailoring communication improves understanding without changing the underlying approved meaning. The analyst should select appropriate formats and terminology for each audience while maintaining traceability and consistency. Effective requirements communication is not simply distributing the same document to everyone; it involves ensuring that each stakeholder receives usable information.

Question 75.

A solution option has the lowest implementation cost but the highest ongoing operating cost. What should the business analyst do?

1. Select it because implementation cost is lowest.
   2. Ignore operating cost because it occurs after the project.
   3. Compare total costs, expected benefits, risks, and lifecycle implications across the alternatives.
   4. Reject every option with recurring costs.

Correct Answer: 3

Explanation:

Solution evaluation should consider more than initial implementation expense. A lower upfront cost can be outweighed by higher maintenance, licensing, staffing, support, or operating expenses over the solution’s useful life. The analyst should help stakeholders compare relevant lifecycle costs together with expected benefits, risks, feasibility, and strategic considerations. The appropriate time horizon depends on the business case and organizational context. A structured comparison prevents decision-makers from selecting an apparently inexpensive solution that produces a higher overall cost of ownership.

Question 76.

During a requirements workshop, one participant dominates the discussion and quieter stakeholders are not contributing. What should the business analyst do?

1. End the workshop immediately.
   2. Accept the dominant participant’s views as group consensus.
   3. Remove quieter participants from future sessions.
   4. Use facilitation techniques that encourage balanced participation and capture different perspectives.

Correct Answer: 4

Explanation:

Effective facilitation helps ensure that important perspectives are not lost because of group dynamics. The analyst can use structured turn-taking, targeted questions, breakout discussions, silent brainstorming, voting, or other techniques appropriate to the situation. Dominant participants may have valuable expertise, but their views should not automatically be treated as consensus. Balanced participation is especially important when different stakeholder groups experience different impacts from the initiative. The facilitator should create an environment where relevant disagreements and concerns can be expressed constructively.

Question 77.

What is the primary purpose of a requirements management plan or agreed requirements-management approach?

1. To define how requirements will be documented, traced, prioritized, approved, changed, communicated, and maintained
   2. To guarantee that requirements never change
   3. To replace the project management plan
   4. To define only software coding standards

Correct Answer: 1

Explanation:

A requirements-management approach establishes how requirements will be handled throughout the initiative. It can define attributes, repositories, traceability expectations, prioritization methods, approval authority, change procedures, version control, and communication practices. Establishing these expectations early improves consistency and reduces confusion when requirements evolve. The approach should be tailored to the initiative’s size, complexity, lifecycle, governance, and regulatory environment. It supports project management but does not replace the broader project management framework or technical development standards.

Question 78.

A business analyst discovers that a requirement depends on data that the organization does not currently capture. What should the analyst do?

1. Assume the data will become available automatically.
   2. Analyze the data requirement, source, ownership, collection feasibility, quality needs, and impacts.
   3. Remove all data-related requirements.
   4. Wait until user acceptance testing to investigate the issue.

Correct Answer: 2

Explanation:

A requirement dependent on unavailable data may require additional capabilities, process changes, integrations, data acquisition, or manual collection. The analyst should determine what data is needed, where it could originate, who owns it, how reliable it must be, and what effort or constraints are associated with obtaining it. This analysis can materially affect solution feasibility and cost. Discovering the dependency early gives stakeholders time to evaluate alternatives. Assuming unavailable data will somehow appear later creates significant implementation and solution-performance risk.

Question 79.

An implemented solution meets performance targets, but only 30% of intended users have adopted it. What should the business analyst investigate?

1. Only the technical response time
   2. Whether the original requirements document was long enough
   3. Adoption barriers such as usability, training, communication, process alignment, incentives, and stakeholder readiness
   4. Only the project’s original budget

Correct Answer: 3

Explanation:

Technical performance alone does not ensure business value if intended users do not adopt the solution. The analyst should investigate why adoption is low and determine whether the cause relates to usability, training, awareness, workflow disruption, organizational incentives, resistance, missing capabilities, or other factors. Usage data and stakeholder feedback can help distinguish among these possibilities. The findings may lead to solution enhancements, process changes, training, communication, or change-management actions. Benefits realization depends on both solution capability and effective organizational use.

Question 80.

A business analyst is closing an initiative and wants to improve business analysis practices on future projects. What should the analyst do?

1. Delete working documents after acceptance.
   2. Record only successful activities.
   3. Avoid reviewing stakeholder feedback.
   4. Capture lessons, performance observations, effective techniques, problems encountered, and recommended improvements for organizational reuse.

Correct Answer: 4

Explanation:

Business analysis practices improve when teams preserve useful knowledge from completed initiatives. The analyst should identify which elicitation, modeling, communication, prioritization, traceability, and requirements-management practices worked well and which created problems or rework. Stakeholder feedback and performance measures can provide useful evidence. Lessons should be documented in an accessible organizational repository or process so future teams can apply them. Both successful and unsuccessful experiences are valuable because they help improve methods, planning assumptions, and decision-making on subsequent initiatives.