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

 

Question 161.

A business analyst is comparing two solution alternatives. One offers greater benefits but also introduces substantially greater operational risk. What should the analyst do?

1. Select the higher-benefit option automatically
   2. Present the benefits, risks, costs, constraints, and assumptions of both alternatives for informed decision-making
   3. Select the lower-risk option automatically
   4. Ignore operational risk because benefits are more important

Correct Answer: 2

Explanation:

Solution comparison should make important trade-offs visible rather than reducing the decision to a single factor. Greater expected benefits may justify additional risk in some circumstances, while in others the organization’s risk tolerance or regulatory obligations may favor a different alternative. The business analyst should evaluate relevant costs, benefits, risks, feasibility, assumptions, constraints, and strategic alignment using agreed criteria. Authorized stakeholders can then make an informed decision. The analyst’s role is to provide structured evidence rather than automatically choosing whichever option performs best on one dimension.

Question 162.

A business analyst wants to understand how the organization’s performance compares with similar organizations in the industry. Which technique is most appropriate?

1. Benchmarking
   2. Requirements versioning
   3. Interface testing
   4. Configuration management

Correct Answer: 1

Explanation:

Benchmarking compares organizational processes, capabilities, or performance measures with appropriate external or internal reference points. It can help identify performance gaps and opportunities for improvement. The analyst should ensure that comparisons use sufficiently similar definitions, populations, time periods, and operating contexts because misleading benchmarks can lead to poor conclusions. Benchmarking can inform objectives and improvement opportunities, but it does not automatically establish which solution should be implemented. Additional analysis is normally needed to understand why differences exist and what changes are feasible.

Question 163.

A requirement specifies that the application must remain available during a defined percentage of business hours. What type of requirement is this primarily?

1. Transition requirement
   2. Stakeholder communication requirement
   3. Nonfunctional requirement related to availability
   4. Project scheduling requirement

Correct Answer: 3

Explanation:

Availability describes a quality characteristic of a solution rather than a specific business function. It is therefore generally treated as a nonfunctional requirement. The requirement should define availability precisely enough to measure it, including relevant operating periods, exclusions, maintenance windows, and measurement methods when necessary. Other nonfunctional characteristics include performance, security, scalability, reliability, usability, and recoverability. These requirements can have major architectural and cost implications, so they should be identified and validated rather than treated as secondary concerns.

Question 164.

A business analyst discovers that a planned data migration includes thousands of duplicate customer records. What should the analyst do?

1. Migrate every record unchanged
   2. Delete duplicate records without business approval
   3. Ignore data quality because migration is a technical activity
   4. Define appropriate data-quality and cleansing requirements with relevant data owners before migration

Correct Answer: 4

Explanation:

Migrating poor-quality data can transfer existing problems directly into the new solution. The analyst should work with data owners and other stakeholders to define acceptable quality standards, duplicate-handling rules, validation requirements, ownership, and exception procedures. Technical teams can then implement appropriate cleansing and conversion mechanisms. Some apparent duplicates may represent legitimate separate records, so automatic deletion can also create risk. Data migration is often a transition requirement with significant business implications and should receive appropriate analysis and validation.

Question 165.

A stakeholder claims that a requirement is mandatory because “we have always done it this way.” What should the business analyst do?

1. Investigate the underlying rationale, rule, constraint, or business need before accepting the requirement as mandatory.
   2. Automatically classify it as mandatory.
   3. Remove it because historical practices have no value.
   4. Ask developers whether they prefer the requirement.

Correct Answer: 1

Explanation:

Historical practice can provide useful context, but it does not by itself demonstrate that a requirement remains mandatory. The analyst should determine whether the practice exists because of regulation, policy, contractual obligations, operational risk, customer needs, or simply habit. Understanding the rationale helps stakeholders decide whether the requirement should be retained, redesigned, or removed. Challenging assumptions about existing practices is particularly important during process improvement because unnecessary legacy activities can otherwise be reproduced in the future state without providing meaningful value.

Question 166.

A business analyst is defining requirements for a system expected to handle significant growth in transaction volume over the next three years. What should be addressed?

1. Only current transaction volume
   2. Measurable scalability and performance requirements based on expected future demand
   3. Only the visual design
   4. Only training requirements

Correct Answer: 2

Explanation:

A solution that satisfies current demand may fail quickly if expected growth is ignored. The analyst should work with stakeholders and technical experts to establish realistic assumptions about future transaction volumes and define measurable performance and scalability expectations. These requirements can influence architecture, infrastructure, cost, testing, and solution selection. Forecasts contain uncertainty, so important assumptions should be documented and reviewed. Defining future capacity needs early helps prevent a solution from meeting immediate requirements while becoming inadequate shortly after implementation.

Question 167.

A business analyst is facilitating a workshop in which participants disagree because they use the same term to mean different things. What should the analyst do?

1. Allow each participant to retain a different definition
   2. End the workshop
   3. Establish an agreed definition and record it in the appropriate glossary or business vocabulary
   4. Select the shortest definition without discussion

Correct Answer: 3

Explanation:

Terminology differences can create hidden disagreements and lead to inconsistent requirements. The analyst should identify the different meanings, determine which definition is appropriate for the initiative, and establish a shared vocabulary. A glossary or conceptual data model can help document important terms and their relationships. Agreement on terminology improves communication among business, technical, and testing stakeholders. When multiple legitimate meanings must coexist, the analyst should distinguish them explicitly rather than forcing ambiguous language into a single undefined term.

Question 168.

A proposed solution requires employees to adopt substantially different working practices. What should the business analyst analyze in addition to functional requirements?

1. Only software licensing
   2. Only hardware capacity
   3. Only project accounting
   4. Organizational readiness, training, process changes, communication, roles, and transition needs

Correct Answer: 4

Explanation:

A technically capable solution may fail to deliver benefits if the organization is not prepared to use it effectively. Significant changes in working practices can require training, revised roles, new procedures, communication, leadership support, and other transition activities. The analyst should identify these needs and assess organizational readiness so they can be incorporated into implementation planning. Some of these needs may become transition requirements. Considering organizational impacts early improves adoption and reduces the risk that the solution is delivered successfully from a technical perspective but underused operationally.

Question 169.

What is a major purpose of a context diagram during business analysis?

1. To show the solution or business area boundary and its interactions with external actors or systems
   2. To calculate project return on investment
   3. To define the detailed database schema
   4. To record project expenses

Correct Answer: 1

Explanation:

A context diagram provides a high-level view of the area being analyzed and the external people, organizations, or systems that interact with it. This makes scope boundaries and interfaces easier to understand. It can help identify missing stakeholders, external dependencies, and information exchanges before detailed requirements are developed. Because it is intentionally high-level, a context diagram does not normally describe detailed internal processing or database structures. It provides a useful foundation for deeper process, data, interface, and functional analysis.

Question 170.

A business analyst needs to determine whether a proposed solution can operate successfully within existing business operations. Which feasibility dimension is most relevant?

1. Graphic feasibility
   2. Operational feasibility
   3. Alphabetical feasibility
   4. Documentation feasibility

Correct Answer: 2

Explanation:

Operational feasibility examines whether the proposed solution can function effectively within the organization’s real operating environment. Factors may include processes, staffing, skills, organizational structure, procedures, user acceptance, support capability, and compatibility with existing operations. A solution can be technically possible but operationally impractical if the organization cannot support or adopt it. Feasibility analysis may also include technical, economic, schedule, legal, and other dimensions. Considering multiple dimensions gives decision-makers a more complete understanding of whether an alternative is realistic.

Question 171.

A business analyst discovers that several requirements cannot be objectively tested because they contain words such as “fast,” “flexible,” and “user-friendly.” What should the analyst do?

1. Approve the requirements because stakeholders understand them
   2. Remove all quality requirements
   3. Replace subjective terms with measurable or otherwise objectively assessable criteria
   4. Allow testers to define the criteria after implementation

Correct Answer: 3

Explanation:

Subjective terms can create inconsistent expectations because different stakeholders may interpret them differently. The analyst should determine what characteristics actually matter and express them using measurable or observable criteria whenever practical. For example, “fast” might become a response-time target under specified conditions, while usability could be evaluated using task completion or error measures. Making quality expectations testable improves requirements verification and solution acceptance. The analyst should preserve the stakeholder’s underlying need while replacing ambiguous wording with clearer criteria.

Question 172.

An approved change increases expected business value but also delays the planned release. What should the business analyst do?

1. Conceal the schedule impact
   2. Reverse the approval personally
   3. Ignore the additional value
   4. Communicate the value and schedule trade-off and update affected requirements information and plans through appropriate governance

Correct Answer: 4

Explanation:

Approved changes can alter multiple aspects of an initiative, including scope, value, cost, schedule, risk, and dependencies. These impacts should remain visible so stakeholders understand the consequences of their decisions. The analyst should ensure affected requirements, traceability, priorities, release information, and related artifacts are updated as appropriate. The analyst should not conceal an unfavorable schedule consequence or independently reverse an authorized decision. Maintaining alignment among requirements and planning information supports effective governance after changes are approved.

Question 173.

Why might a business analyst recommend a proof of concept before committing to a solution approach?

1. To test an important feasibility assumption or technical concept with limited investment before full implementation
   2. To replace all requirements elicitation
   3. To guarantee the final solution will succeed
   4. To eliminate stakeholder involvement

Correct Answer: 1

Explanation:

A proof of concept can reduce uncertainty when a solution depends on an important assumption about technology, integration, performance, or another feasibility concern. Rather than committing substantial resources immediately, the organization can test whether the concept is viable within a limited scope. Results can inform solution selection, estimates, risk analysis, and requirements. A proof of concept does not guarantee production success because the final environment may involve additional complexity. It should therefore address specific uncertainties and have clear evaluation criteria.

Question 174.

A business analyst receives 1,000 survey responses, but nearly all responses came from one customer segment. What should the analyst consider?

1. The survey must be representative because the sample is large.
   2. The results may contain sampling bias and may not represent the broader stakeholder population.
   3. Customer segmentation is irrelevant.
   4. Every response should be treated as a separate mandatory requirement.

Correct Answer: 2

Explanation:

A large number of responses does not automatically make a survey representative. If one segment is heavily overrepresented, the results may reflect that group’s needs more strongly than those of the overall population. The analyst should understand the target population, response distribution, sampling approach, and potential nonresponse or selection bias before drawing conclusions. Additional research may be necessary for underrepresented groups. Survey findings should be interpreted as evidence with known limitations rather than automatically converted into requirements based solely on response volume.

Question 175.

A business analyst is reviewing a requirement that combines five unrelated capabilities in one statement. What should the analyst do?

1. Keep it unchanged because longer requirements are more complete.
   2. Add additional capabilities to the same requirement.
   3. Decompose it into appropriately atomic requirements while maintaining relationships and context.
   4. Remove the entire requirement.

Correct Answer: 3

Explanation:

Requirements are generally easier to understand, prioritize, trace, implement, and test when each represents a coherent need rather than several unrelated capabilities. The analyst should decompose an overly compound statement into appropriate atomic requirements while preserving relevant relationships and the broader business context. Decomposition should not be taken so far that meaning is lost or unnecessary administrative complexity is created. The objective is to make each requirement sufficiently focused to support clear analysis, lifecycle management, and acceptance.

Question 176.

A business analyst discovers that a proposed solution will require customer information to be shared with a new external provider. What should be analyzed?

1. Only the provider’s logo
   2. Only implementation schedule
   3. Only the number of customer records
   4. Business need, privacy, security, consent, contractual, regulatory, data-handling, and interface requirements

Correct Answer: 4

Explanation:

Sharing customer information with an external organization can create important privacy, security, regulatory, contractual, and operational implications. The analyst should first understand why the sharing is necessary and then identify applicable constraints and controls. Requirements may address permitted data, purpose limitations, authorization, transmission, storage, retention, deletion, auditability, and responsibilities between organizations. Appropriate legal, security, privacy, and business stakeholders may need to participate. Addressing these considerations early reduces the risk of designing a solution that cannot be approved or safely operated.

Question 177.

What is the main purpose of defining a minimum viable product in an iterative initiative?

1. To identify a sufficiently valuable and usable set of capabilities that can support learning or early value with limited scope
   2. To include every known requirement in the first release
   3. To eliminate future enhancements
   4. To deliver the lowest-quality solution possible

Correct Answer: 1

Explanation:

A minimum viable product focuses on a limited set of capabilities sufficient to provide meaningful value and, often, generate learning from actual use. It does not mean delivering an intentionally poor-quality product or ignoring essential security, compliance, and operational requirements. The business analyst can help stakeholders identify which capabilities are necessary to achieve the release objective and which can be deferred. Feedback from early delivery can then inform subsequent requirements and priorities, reducing the risk of investing heavily in features that provide limited value.

Question 178.

A business analyst must select between interviews and a focus group for customer research. What should primarily guide the choice?

1. Which technique has the shorter name
   2. The type of information needed, sensitivity of the subject, desired interaction, participant characteristics, and practical constraints
   3. Which technique was used on the previous project
   4. The analyst’s personal preference

Correct Answer: 2

Explanation:

Interviews and focus groups serve different elicitation purposes. Interviews can provide deeper individual perspectives and may be more appropriate for sensitive topics. Focus groups can reveal reactions, shared experiences, and differences through participant interaction. The analyst should consider the research objective, confidentiality needs, stakeholder characteristics, available time, and potential group dynamics when choosing a technique. Sometimes both techniques can be used together. Elicitation methods should be selected deliberately based on the information required rather than habit or personal preference.

Question 179.

A business analyst discovers that a solution’s reported success depends on excluding failed transactions from the performance metric. What should the analyst do?

1. Accept the metric because it produces favorable results
   2. Remove failed transactions permanently from all reporting
   3. Review the metric definition and ensure performance is measured transparently against the intended business outcome
   4. Stop evaluating the solution

Correct Answer: 3

Explanation:

Performance measures should accurately represent the outcome they are intended to assess. Excluding failed transactions may materially distort the result if those failures affect customers or business performance. The analyst should examine the metric’s definition, calculation, exclusions, and original success criteria and make any limitations transparent. Different measures may legitimately use different populations, but those choices should have a sound business rationale. Reliable solution evaluation depends on consistent and meaningful measurement rather than selecting calculations that merely make performance appear favorable.

Question 180.

A business analyst is reviewing lessons learned and notices that many defects resulted from requirements being misunderstood across teams. What should be recommended for future initiatives?

1. Reduce stakeholder involvement
   2. Stop documenting requirements
   3. Eliminate requirements reviews
   4. Improve requirements clarity, collaborative reviews, models, examples, confirmation practices, and communication across affected teams

Correct Answer: 4

Explanation:

Repeated misunderstanding indicates an opportunity to improve requirements communication and quality practices. Depending on the causes, improvements might include clearer language, better acceptance criteria, visual models, examples, collaborative reviews, shared terminology, confirmation of elicitation results, and more effective communication between business and delivery teams. The objective is not necessarily to create more documentation but to provide information in forms that stakeholders can understand consistently. Lessons learned should lead to practical changes that reduce avoidable rework and defects on future initiatives.