I85PREP
⌘ K
CPIT BA study materials
CPIT BA study resources

CPIT BA practice questions

One question at a time. Build your CPIT BA understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Business Analysis Planning and Monitoring

Which business analysis planning artifact defines how requirements will be elicited, analyzed, and managed throughout the initiative?

  1. The stakeholder engagement plan
  2. The requirements traceability matrix
  3. The business analysis approach Correct answer.
  4. The solution scope statement

Explanation

The business analysis approach describes the overall method the analyst will use: the activities, deliverables, techniques, and governance for requirements work. It is a core output of Business Analysis Planning and Monitoring. Scope, stakeholder engagement, and traceability are separate planning outputs or artifacts.

Question 2Business Analysis Planning and Monitoring

A business analyst is identifying the people who may affect or be affected by a proposed process change. Which planning activity is being performed?

  1. Requirements prioritization
  2. Risk mitigation planning
  3. Stakeholder identification Correct answer.
  4. Solution assessment

Explanation

Stakeholder identification is the planning task of determining who has an interest in or influence over the change and recording their characteristics. It is performed early so engagement and communication can be planned. Prioritization, solution assessment, and risk mitigation are different concerns.

Question 3Business Analysis Planning and Monitoring

Which technique is most appropriate for deciding how requirements will be prioritized when stakeholders disagree about relative importance?

  1. A process model of the current-state workflow
  2. A glossary validation of business terms
  3. A data dictionary review of field definitions
  4. A facilitated prioritization session using a defined scheme such as MoSCoW Correct answer.

Explanation

Prioritization requires a defined scheme and a structured forum so stakeholders can agree on relative value. A facilitated session applying a scheme such as MoSCoW or weighted scoring produces a defensible ranking. Data dictionaries, process models, and glossaries support other analysis tasks.

Question 4Business Analysis Planning and Monitoring

What is the primary purpose of a requirements traceability approach?

  1. To estimate the cost of implementing each requirement
  2. To record the chronological order in which requirements were elicited
  3. To link requirements to their sources, related requirements, and downstream work products Correct answer.
  4. To assign each requirement to a single stakeholder for approval

Explanation

Traceability connects requirements backward to their sources and forward to design, build, and test artifacts. This supports impact analysis, coverage verification, and change control. It is not about chronology, cost estimation, or single-owner assignment.

Question 5Business Analysis Planning and Monitoring

An analyst must plan how changes to approved requirements will be requested, assessed, and approved. Which plan element is being defined?

  1. The requirements change control process Correct answer.
  2. The communication plan
  3. The solution acceptance criteria
  4. The elicitation schedule

Explanation

Change control defines how requirement changes are submitted, evaluated for impact, and approved or rejected. It protects the integrity of the approved baseline. Communication plans, elicitation schedules, and acceptance criteria address different planning needs.

Question 6Business Analysis Planning and Monitoring

Which factor most directly influences how much formality a business analysis approach should have?

  1. The length of the analyst's prior experience
  2. The regulatory environment and organizational standards governing the initiative Correct answer.
  3. The availability of diagramming software
  4. The number of techniques the analyst personally prefers

Explanation

Organizational standards, regulatory constraints, and contractual obligations drive the required degree of documentation and formality. Personal preference, experience, and tooling are secondary and should not determine governance rigor. The approach must fit the context and risk of the initiative.

Question 7Business Analysis Planning and Monitoring

When planning business analysis activities, what does the term 'business analysis performance metrics' refer to?

  1. Measures used to evaluate the quality and effectiveness of the analysis work itself Correct answer.
  2. Counts of defects found in the final software release
  3. Ratings of individual stakeholder satisfaction with the product
  4. Financial return measures for the delivered solution

Explanation

Performance metrics assess how well the business analysis effort is executed, for example completeness of requirements or timeliness of deliverables. They are distinct from solution benefits, product defect counts, and product satisfaction. Metrics inform continuous improvement of the analysis process.

Question 8Business Analysis Planning and Monitoring

Which element belongs in a stakeholder engagement plan?

  1. The level of involvement and communication needs for each stakeholder group Correct answer.
  2. The vendor licensing costs
  3. The database schema for the new system
  4. The unit test coverage targets

Explanation

A stakeholder engagement plan records who the stakeholders are, their influence and interest, and how and when they will be engaged. Technical schemas, test targets, and licensing costs belong to solution or project planning. The plan focuses on collaboration and communication.

Question 9Business Analysis Planning and Monitoring

A project has a fixed regulatory deadline and a large, geographically dispersed stakeholder group. Which planning decision is most appropriate?

  1. Plan structured, documented communication and early elicitation to manage distance and time pressure Correct answer.
  2. Reduce traceability to save time regardless of regulatory needs
  3. Defer all stakeholder engagement until the solution is designed
  4. Rely solely on informal hallway conversations to reduce documentation overhead

Explanation

Dispersed stakeholders and a hard deadline increase the risk of miscommunication, so the plan should emphasize structured communication and early elicitation. Regulatory context also raises documentation needs. Informal channels and deferral increase risk rather than control it.

Question 10Business Analysis Planning and Monitoring

What is the main purpose of conducting a business analysis planning session at the start of an initiative?

  1. To finalize the technical architecture of the solution
  2. To agree on the activities, deliverables, and governance for the analysis work Correct answer.
  3. To sign off on the project budget
  4. To assign software developers to coding tasks

Explanation

Planning sessions align the team on how analysis will be performed, what will be produced, and how decisions will be governed. They establish the business analysis approach before work begins. Architecture, budget approval, and coding assignments are outside this scope.

Question 11Business Analysis Planning and Monitoring

Which of the following best describes the relationship between the business analysis plan and the project management plan?

  1. The analysis plan replaces the project plan for agile initiatives
  2. The analysis plan details analysis work and should align with the broader project plan Correct answer.
  3. The project plan is created only after the analysis plan is closed
  4. They are identical documents with different titles

Explanation

The business analysis plan covers analysis-specific activities, deliverables, and resources, and it must be consistent with the overall project plan's schedule and governance. The two are complementary, not identical or substitutable. Alignment prevents conflicts in timing and dependencies.

Question 12Business Analysis Planning and Monitoring

An analyst needs to decide which elicitation techniques to schedule. Which input is most relevant to that decision?

  1. The availability and location of stakeholders plus the nature of the information needed Correct answer.
  2. The programming language chosen for implementation
  3. The color scheme of the final user interface
  4. The marketing budget for the product launch

Explanation

Technique selection depends on who the stakeholders are, where they are, how available they are, and what type of information is sought. These factors determine whether workshops, interviews, observation, or surveys fit. Interface styling, implementation language, and marketing budget do not drive elicitation planning.

Question 13Business Analysis Planning and Monitoring

What does establishing a requirements baseline enable in business analysis planning and monitoring?

  1. It allows requirements to change freely without review
  2. It eliminates the need for stakeholder communication
  3. It guarantees the solution will meet all user needs
  4. It provides an agreed reference point against which changes are evaluated Correct answer.

Explanation

A baseline is an approved snapshot of requirements that serves as the reference for change control and impact analysis. Changes are then assessed against it rather than made arbitrarily. A baseline does not remove the need for communication or guarantee solution success.

Question 14Business Analysis Planning and Monitoring

Which situation best indicates that the business analysis approach should be revised during the initiative?

  1. The analyst has selected a preferred diagramming tool
  2. Stakeholders consistently fail to attend planned workshops, delaying elicitation Correct answer.
  3. The project sponsor has approved the charter
  4. The team has finished documenting the glossary

Explanation

Recurring stakeholder absence signals that the planned elicitation approach is not working and should be adapted, for example by changing timing or methods. Monitoring performance and adjusting the plan is central to this domain. Completing a glossary, charter approval, or tool selection does not by itself require revision.

Question 15Business Analysis Planning and Monitoring

What is the role of a requirements management tool in business analysis planning?

  1. It replaces the need for stakeholder engagement
  2. It automatically writes the business analysis approach
  3. It guarantees requirements are complete and correct
  4. It supports storing, tracing, and controlling requirements throughout the lifecycle Correct answer.

Explanation

Requirements management tools help capture, link, version, and control requirements, supporting traceability and change control. They are enablers, not substitutes for engagement or judgment. No tool can guarantee that requirements are complete or correct.

Question 16Business Analysis Planning and Monitoring

An analyst is estimating the effort required for requirements activities. Which approach is most defensible?

  1. Guessing based on a single stakeholder's opinion
  2. Adopting the largest estimate available to avoid overruns
  3. Using historical data from comparable initiatives combined with expert judgment Correct answer.
  4. Assuming zero effort because requirements are already known

Explanation

Effort estimates are most credible when grounded in historical data and refined with expert judgment. This balances realism with context. Single opinions, assumptions of no effort, and inflated padding are unreliable and undermine planning credibility.

Question 17Business Analysis Planning and Monitoring

Which of the following is a valid reason to tailor the level of detail in requirements documentation?

  1. To ensure every requirement is exactly one sentence long
  2. To match the risk, complexity, and audience needs of the initiative Correct answer.
  3. To reduce documentation to zero in every initiative
  4. To avoid involving stakeholders in reviews

Explanation

Documentation detail should reflect the risk of the change, the complexity of the domain, and what the audience needs to act. High-risk, regulated work may need more rigor, while low-risk work may need less. Reducing to zero, imposing sentence limits, and excluding reviewers are not sound tailoring rationales.

Question 18Business Analysis Planning and Monitoring

What is the primary output of the stakeholder identification and analysis activity?

  1. A list of stakeholders with their characteristics, influence, and needs Correct answer.
  2. A cost-benefit analysis of the solution
  3. A signed contract with the vendor
  4. A finalized project schedule

Explanation

Stakeholder analysis produces a profile of who the stakeholders are, their influence, interest, attitudes, and communication needs. This informs engagement planning. Schedules, cost-benefit analyses, and contracts are separate project outputs.

Question 19Business Analysis Planning and Monitoring

A business analyst is defining how requirement conflicts between two departments will be resolved. Which plan element addresses this?

  1. The data migration strategy
  2. The user interface style guide
  3. The decision-making and escalation approach Correct answer.
  4. The test data management plan

Explanation

The analysis approach should specify how conflicts are resolved and how unresolved issues escalate to the right authority. This prevents requirements work from stalling. Migration, style guides, and test data are solution or delivery concerns.

Question 20Business Analysis Planning and Monitoring

Which of the following best describes the concept of 'requirements governance' in this domain?

  1. The set of roles, decision rights, and processes that control requirements throughout the lifecycle Correct answer.
  2. The schedule for releasing software versions
  3. The process of writing code to meet requirements
  4. The method for selecting a cloud provider

Explanation

Governance defines who can approve, change, and validate requirements and through what processes. It establishes accountability and consistency for requirements work. Coding, release scheduling, and vendor selection are delivery or procurement activities.

Question 21Business Analysis Planning and Monitoring

An initiative is highly uncertain, with evolving needs and frequent feedback. Which planning posture is most appropriate?

  1. No plan at all, relying on ad hoc decisions
  2. A plan that excludes stakeholder feedback by design
  3. A lightweight, iterative approach with frequent re-planning of analysis activities Correct answer.
  4. A rigid, fully detailed plan fixed at the outset

Explanation

High uncertainty favors iterative planning that adapts as understanding grows, with short cycles and frequent feedback. A rigid upfront plan tends to become obsolete. Abandoning planning or excluding feedback increases risk rather than managing it.

Question 22Business Analysis Planning and Monitoring

What does the term 'requirements lifecycle' describe in planning and monitoring?

  1. The stages requirements pass through from elicitation to retirement Correct answer.
  2. The sequence of project budget approvals
  3. The warranty period of the purchased software
  4. The tenure of the project manager

Explanation

The requirements lifecycle covers how requirements are elicited, analyzed, documented, approved, maintained, and eventually retired. Planning and monitoring ensure each stage is governed appropriately. Warranty periods, budget approvals, and staff tenure are unrelated.

Question 23Business Analysis Planning and Monitoring

A business analyst wants to verify that the analysis plan is realistic before execution. Which action best supports this?

  1. Publish the plan without informing the team
  2. Review the plan with key stakeholders and validate assumptions about availability and resources Correct answer.
  3. Delete the plan to avoid accountability
  4. Lock the plan immediately and prohibit any review

Explanation

Validating the plan with stakeholders tests assumptions about stakeholder availability, resources, and timing before work begins. This reduces the chance of unrealistic commitments. Locking it without review, deleting it, or hiding it from the team undermines planning.

Question 24Business Analysis Planning and Monitoring

Which pair correctly distinguishes 'planning' from 'monitoring' in this domain?

  1. Planning and monitoring are identical activities with different names
  2. Planning sets the approach and activities; monitoring tracks performance against the plan and adjusts it Correct answer.
  3. Planning applies only to agile; monitoring applies only to waterfall
  4. Planning tracks results; monitoring creates the initial approach

Explanation

Planning establishes how analysis will be done, while monitoring compares actual performance to the plan and triggers adjustments. The two are complementary phases of the same knowledge area. They are not identical, reversed, or tied to a single methodology.

Question 25Business Analysis Planning and Monitoring

An analyst discovers that the approved analysis plan omitted a critical stakeholder group. What is the most appropriate response?

  1. Ignore the omission to preserve the original plan
  2. Cancel the initiative immediately
  3. Proceed without engaging the group to save time
  4. Update stakeholder analysis and engagement planning, then revise the plan accordingly Correct answer.

Explanation

Monitoring should detect gaps and prompt plan updates, including revised stakeholder analysis and engagement activities. Adjusting the plan is the intended response to new information. Ignoring the gap or proceeding without engagement risks missed requirements and resistance.

Question 26Business Analysis Planning and Monitoring

In business analysis planning and monitoring, what distinguishes a 'plan-driven' business analysis approach from a 'change-driven' one?

  1. A plan-driven approach eliminates stakeholder involvement, while a change-driven approach involves stakeholders continuously.
  2. A plan-driven approach requires a dedicated requirements tool, while a change-driven approach relies on verbal agreements only.
  3. A plan-driven approach defines most requirements up front, while a change-driven approach accepts that requirements will emerge through short, iterative cycles. Correct answer.
  4. A plan-driven approach is used only for regulatory initiatives, while a change-driven approach is used only for internal ones.

Explanation

The core distinction is timing and certainty of requirements: plan-driven work front-loads definition and formal approval, whereas change-driven work assumes evolving needs and refines requirements in iterations. This choice shapes documentation depth, review cadence, and how baselines are managed.

Question 27Business Analysis Planning and Monitoring

An analyst is deciding how requirements changes will be requested, assessed, approved, and communicated after the baseline is set. Which business analysis planning element is being defined?

  1. The requirements traceability matrix structure
  2. The stakeholder communication cadence
  3. The elicitation activity schedule
  4. The requirements change control process Correct answer.

Explanation

Change control covers the formal path a requirement takes after baselining: who may request a change, how impact is assessed, who approves, and how the decision is communicated. Traceability supports this but is only the linkage mechanism, not the decision process itself.

Question 28Business Analysis Planning and Monitoring

A business analyst is estimating effort for requirements work on a similar past initiative that had comparable scope, stakeholders, and regulatory constraints. Which estimating technique is being applied?

  1. Bottom-up estimation from a decomposed work breakdown
  2. Three-point estimation using optimistic, pessimistic, and most likely values
  3. Delphi estimation with anonymous expert rounds
  4. Analogous estimation based on historical comparison Correct answer.

Explanation

Analogous estimation uses actual effort from a comparable prior initiative as the basis for the current forecast. It is fast and defensible when genuine similarity exists, though it should be adjusted for known differences.

Question 29Business Analysis Planning and Monitoring

Midway through an initiative, an analyst notices that a key stakeholder group is not responding to review requests, causing requirements approvals to stall. Which monitoring response is most appropriate?

  1. Assess the engagement plan for that group, adjust the approach, and track the effect on approval timeliness Correct answer.
  2. Remove the group from the stakeholder list so the approval metrics reflect only responsive stakeholders
  3. Re-baseline all approved requirements so pending approvals are no longer outstanding
  4. Escalate to the sponsor immediately and suspend all analysis work until the group responds

Explanation

Monitoring exists to detect deviations and trigger corrective action against the plan. The disciplined response is to diagnose why the engagement approach is failing, adapt it, and keep measuring whether approvals recover.

Question 30Business Analysis Planning and Monitoring

An organization wants assurance that business analysis work products meet agreed quality standards before they are used downstream. Which planning decision most directly provides this assurance?

  1. Increasing the frequency of status reporting to the project board
  2. Adopting a requirements management tool with role-based access control
  3. Defining verification and validation activities, including review types and entry and exit criteria Correct answer.
  4. Scheduling more elicitation sessions with a wider set of stakeholders

Explanation

Quality assurance for analysis work products comes from planned verification (are we building the requirement right) and validation (are we building the right requirement), each with defined review methods and criteria for completion. These criteria make quality checkable rather than assumed.

Question 31Elicitation and Collaboration

In business analysis, which activity is the primary purpose of elicitation rather than mere gathering of requirements?

  1. Drawing out information from stakeholders through deliberate techniques so that needs, constraints and context become explicit Correct answer.
  2. Confirming the budget baseline before scope is defined
  3. Recording the project manager's instructions for the delivery team
  4. Collecting all documents that stakeholders have already written about the solution

Explanation

Elicitation is an active, planned process of drawing out information that stakeholders may not have articulated, using interviews, workshops, observation and similar techniques. It differs from passively collecting existing documents because the analyst must probe, clarify and validate. The output feeds collaboration and later analysis, not budget control.

Question 32Elicitation and Collaboration

A business analyst schedules a facilitated workshop with eight stakeholders from competing departments. Which preparation step most directly improves the quality of the elicited information?

  1. Allowing the discussion to roam freely so that unexpected ideas can emerge
  2. Recording the session without telling participants to avoid influencing their answers
  3. Inviting additional observers so the room reflects the widest possible attendance
  4. Sending a clear purpose, agenda and pre-reading so participants arrive prepared to discuss specific topics Correct answer.

Explanation

Effective elicitation preparation includes defining objectives, selecting participants, distributing an agenda and materials, and setting ground rules. Pre-reading and a focused agenda let participants contribute substantively instead of spending the session orienting themselves. Preparation also reduces the risk of the workshop drifting or being dominated by one group.

Question 33Elicitation and Collaboration

Which elicitation technique is most appropriate when a business analyst needs to understand how a task is actually performed rather than how stakeholders describe it?

  1. Document analysis of the procedure manual
  2. Job shadowing and observation Correct answer.
  3. A focus group
  4. A survey questionnaire

Explanation

Observation, including job shadowing, captures real behaviour and workarounds that people may not report or even notice. Descriptions and manuals often reflect the intended process rather than the executed one. Observation is therefore the technique that reveals the gap between stated and actual practice.

Question 34Elicitation and Collaboration

During an interview a stakeholder keeps giving vague answers about approval rules. Which technique best helps the analyst move from general statements to specific, verifiable detail?

  1. Switching immediately to a closed questionnaire to force short answers
  2. Summarising the stakeholder's opinion back to them and moving on
  3. Ending the interview and requesting a written statement instead
  4. Asking open questions first, then probing with who, what, when and how-examples Correct answer.

Explanation

Effective interviewing moves from open questions that encourage elaboration to probing questions that clarify specifics such as actors, triggers, timing and exceptions. This progression surfaces detail without prematurely constraining the stakeholder. Closed formats or ending the session too early lose the opportunity to resolve ambiguity.

Question 35Elicitation and Collaboration

A business analyst is eliciting requirements for a system used by hundreds of customers across regions. Which approach best supports broad, comparable input at reasonable cost?

  1. Reading only the existing marketing materials
  2. Relying on the sponsor's personal view of customer needs
  3. A structured survey with a pilot test, followed by targeted interviews for outliers Correct answer.
  4. A single workshop with whoever is available that week

Explanation

Surveys reach large, dispersed populations efficiently and produce comparable data when questions are well designed and piloted. Following up with interviews for unusual or unclear responses captures depth where it matters. This combines breadth with targeted depth rather than relying on a narrow sample.

Question 36Elicitation and Collaboration

What distinguishes a focus group from a facilitated requirements workshop in elicitation practice?

  1. A focus group always produces signed-off requirements, while a workshop only collects opinions
  2. A workshop must be led by the sponsor, while a focus group is led by any participant
  3. A focus group explores perceptions and attitudes among similar participants, while a workshop aims to produce agreed work products toward a defined objective Correct answer.
  4. A focus group requires no preparation, while a workshop requires a full agenda

Explanation

Focus groups are used to explore attitudes, perceptions and reactions within a homogeneous group, typically for market or user insight. Workshops are structured working sessions with defined deliverables such as agreed requirements or models. Both require preparation, but their objectives and outputs differ.

Question 37Elicitation and Collaboration

When is document analysis the most efficient elicitation technique for a business analyst?

  1. When the goal is to build consensus among conflicting departments
  2. When the analyst needs to observe real-time user behaviour under load
  3. When stakeholders are unwilling to speak and no other source exists
  4. When existing policies, contracts or system documentation already contain rules and data definitions that must be understood Correct answer.

Explanation

Document analysis is efficient when authoritative written sources already hold the rules, definitions or constraints the analyst needs. It lets the analyst prepare informed questions and avoid asking stakeholders for information already documented. It is not a substitute for observing behaviour or building consensus.

Question 38Elicitation and Collaboration

A business analyst uses a prototype during elicitation. What is the main elicitation value of this technique?

  1. It removes the need to interview end users
  2. It guarantees the final solution will match the prototype exactly
  3. It gives stakeholders something concrete to react to, surfacing needs that abstract discussion would miss Correct answer.
  4. It replaces the need for any further requirements validation

Explanation

Prototypes act as tangible stimuli that help stakeholders recognise and articulate needs, especially for user interfaces and workflows. Reactions to a prototype reveal expectations and gaps that abstract descriptions often hide. The prototype is a communication device, not a validated final design.

Question 39Elicitation and Collaboration

Which behaviour by a business analyst best demonstrates active listening during an elicitation session?

  1. Writing notes silently and avoiding eye contact to stay neutral
  2. Planning the next question while the stakeholder is still speaking
  3. Repeating the stakeholder's exact words back without interpretation
  4. Paraphrasing what the stakeholder said and asking whether the understanding is accurate Correct answer.

Explanation

Active listening involves attending fully, then reflecting and paraphrasing to confirm understanding and invite correction. It signals engagement and reduces the risk of misinterpretation. Silent note-taking, rehearsing the next question, or mechanical repetition do not confirm shared meaning.

Question 40Elicitation and Collaboration

A stakeholder is hostile and challenges the analyst's competence in front of the group. Which response best preserves the elicitation objective?

  1. Respond with equal force so the group sees the analyst is not weak
  2. Acknowledge the concern briefly, refocus on the shared goal, and offer to discuss the specific issue separately Correct answer.
  3. Ignore the stakeholder for the rest of the session
  4. Cancel the session and escalate immediately to the sponsor

Explanation

Managing difficult stakeholder behaviour requires de-escalation, acknowledgement and redirection toward the shared objective. Offering a separate conversation removes the audience dynamic that fuels confrontation. Retaliation, exclusion or abrupt cancellation damages trust and loses information.

Question 41Elicitation and Collaboration

During elicitation, a stakeholder describes a desired feature but cannot explain the underlying problem it solves. What should the analyst do next?

  1. Escalate the stakeholder to the sponsor for non-cooperation
  2. Reject the request because it lacks a stated problem
  3. Accept the feature request as a requirement and record it verbatim
  4. Probe for the underlying business problem and the outcome the stakeholder is trying to achieve Correct answer.

Explanation

Requirements should trace to a business need, so the analyst must uncover the problem the requested feature is meant to solve. Understanding the underlying outcome allows better solution options and prevents premature solutioneering. Recording the feature verbatim or rejecting it both bypass the elicitation work.

Question 42Elicitation and Collaboration

What is the main purpose of confirming elicitation results with stakeholders?

  1. To obtain budget approval for the project
  2. To replace the need for any written documentation
  3. To assign blame if requirements later change
  4. To validate that the recorded information accurately reflects stakeholder intent before it is used for further analysis Correct answer.

Explanation

Confirmation ensures that what the analyst captured matches what stakeholders meant, reducing rework caused by misunderstanding. It is a validation step in the elicitation and collaboration process. It is distinct from funding decisions and does not remove the need for documentation.

Question 43Elicitation and Collaboration

A business analyst has elicited information from several departments and now needs to ensure a shared, consistent understanding. Which action best supports this?

  1. File each department's notes separately without reconciliation
  2. Communicate the consolidated results back to participants and resolve discrepancies with them Correct answer.
  3. Send the results only to the sponsor for silent approval
  4. Wait until the solution is built so stakeholders can see it working

Explanation

Communicating consolidated results back to stakeholders lets them confirm accuracy and resolve conflicts while change is still inexpensive. Reconciliation is essential when multiple sources contribute overlapping or contradictory information. Silent approval by one party or deferring to build time leaves misunderstandings unresolved.

Question 44Elicitation and Collaboration

In the elicitation and collaboration knowledge area, what does collaboration primarily add beyond elicitation itself?

  1. A substitute for stakeholder analysis
  2. Ongoing engagement with stakeholders so information is shared, verified and jointly refined throughout the change Correct answer.
  3. A method for approving project funding
  4. A one-time event that ends once requirements are written

Explanation

Collaboration is continuous and reciprocal: stakeholders and analysts work together to share, verify and refine information as understanding evolves. It is not a single event and does not replace stakeholder analysis, which identifies who should be engaged. Funding approval is outside this knowledge area.

Question 45Elicitation and Collaboration

A business analyst is planning elicitation for a project with stakeholders in three time zones. Which scheduling approach best maintains engagement?

  1. Require all stakeholders to attend every session regardless of relevance
  2. Always schedule at the headquarters' convenience
  3. Rotate meeting times and use asynchronous options so no single group always bears an inconvenient slot Correct answer.
  4. Hold separate sessions and never share outputs between groups

Explanation

Distributed stakeholders require fair scheduling and a blend of synchronous and asynchronous channels to sustain participation. Rotating times avoids systematically disadvantaging one group. Sharing outputs between groups keeps understanding aligned, and relevance should determine who attends.

Question 46Elicitation and Collaboration

Which question type is most useful for uncovering unanticipated information during elicitation?

  1. Binary yes-or-no questions
  2. Leading questions that suggest the desired answer
  3. Open-ended questions that invite the stakeholder to explain and elaborate Correct answer.
  4. Rhetorical questions that require no answer

Explanation

Open-ended questions encourage stakeholders to describe context, rationale and exceptions, which is how unanticipated information emerges. Leading questions bias responses, binary questions restrict scope, and rhetorical questions gather nothing. The analyst can follow up with closed questions to confirm detail.

Question 47Elicitation and Collaboration

A business analyst notices that a senior manager dominates a workshop and junior staff stay silent. Which facilitation action best improves the quality of elicited input?

  1. Ask the senior manager to leave the room permanently
  2. Allow the senior manager to continue because rank implies authority
  3. Use round-robin or written idea capture so quieter participants contribute before group discussion Correct answer.
  4. Remove junior staff from future sessions

Explanation

Facilitation techniques such as round-robin, silent brainstorming or written capture give all participants an equal chance to contribute before dominant voices shape the discussion. This preserves psychological safety and improves information quality. Excluding participants or deferring to rank loses valuable operational knowledge.

Question 48Elicitation and Collaboration

Why should a business analyst record the source and date of elicited information?

  1. To determine which stakeholder should be blamed for errors
  2. To satisfy formatting rules of the documentation template
  3. To avoid the need to confirm results with stakeholders
  4. To support traceability and later re-confirmation when circumstances or stakeholders change Correct answer.

Explanation

Recording source and date creates traceability, allowing the analyst to revisit information when conditions change and to confirm it remains valid. It supports accountability and quality rather than blame. It does not remove the need for confirmation.

Question 49Elicitation and Collaboration

A business analyst must elicit information from a stakeholder group that distrusts the project. Which opening approach is most likely to build enough trust for productive elicitation?

  1. Present the final solution design and ask for objections
  2. Explain how their input will be used and what has happened to earlier input, then listen to their concerns Correct answer.
  3. State that decisions are already made and their input is informational only
  4. Begin with a detailed technical questionnaire

Explanation

Trust grows when stakeholders see that their input matters and that earlier contributions had visible consequences. Acknowledging concerns before asking for information demonstrates respect and reciprocity. Announcing predetermined outcomes or starting with a heavy questionnaire reinforces distrust.

Question 50Elicitation and Collaboration

During a workshop, two departments give directly contradictory rules for the same process. What is the most appropriate immediate action for the business analyst?

  1. Silently choose the rule from the more senior department
  2. Record both rules and leave the conflict for implementation
  3. Average the two rules into a single compromise
  4. Make the conflict explicit, capture both positions with their rationale, and facilitate agreement on how it will be resolved Correct answer.

Explanation

Conflicts should be surfaced and documented with rationale so they can be resolved deliberately rather than buried. Facilitating agreement on a resolution path keeps stakeholders accountable. Silent selection, deferral or arbitrary averaging leaves a defect that resurfaces later.