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
A business analyst is deciding how formal the requirements approval process should be for a small internal reporting tool. Which factor most directly justifies a lightweight approval approach?
- The organization has a large PMO with standardized templates
- The project sponsor prefers weekly status meetings
- The solution will be built using a new technology stack
- The solution affects a single department with low regulatory exposure Correct answer.
Explanation
Stakeholder risk, regulatory exposure, and organizational reach drive how much ceremony a plan needs. A small, low-risk, single-department solution warrants lighter governance, whereas broad reach or high compliance exposure demands more formality.
Question 2Business Analysis Planning and Monitoring
Which artifact in business analysis planning and monitoring defines how changes to approved requirements will be received, assessed, and decided upon?
- The solution scope statement
- The requirements change control process Correct answer.
- The requirements traceability repository
- The stakeholder engagement matrix
Explanation
Change control describes the workflow for submitting, evaluating, and approving or rejecting requirement changes, including who holds decision authority. Traceability and engagement artifacts support it but do not define the decision path.
Question 3Business Analysis Planning and Monitoring
A BA is identifying stakeholders for a project and finds a regulator who will not participate in workshops but whose published rules constrain the solution. How should this stakeholder best be classified and handled?
- Defer consideration of the regulator until solution validation begins
- Omit the regulator because they will not attend elicitation sessions
- Classify as an indirect stakeholder and analyze the published rules as a constraint Correct answer.
- Treat the regulator as a team member to ensure compliance sign-off
Explanation
Stakeholders who do not participate directly but influence the solution are indirect stakeholders. Their influence is captured by analyzing their rules and constraints rather than by scheduling elicitation with them.
Question 4Business Analysis Planning and Monitoring
During planning, a BA maps which stakeholders must be consulted on requirements versus merely informed of progress. Which planning artifact is being developed?
- Business analysis communication plan Correct answer.
- Solution design baseline
- Requirements architecture
- Risk register
Explanation
The business analysis communication plan defines who receives what information, in what form, and at what frequency, including consultation versus notification. It is a core output of stakeholder engagement planning.
Question 5Business Analysis Planning and Monitoring
A BA plans elicitation for a project with geographically dispersed experts and tight schedules. Which planning consideration is most relevant to selecting elicitation techniques?
- The availability and location of participants plus the depth of information needed Correct answer.
- The number of test cases planned for system testing
- The programming language used by the development team
- The color scheme of the final user interface
Explanation
Elicitation planning weighs participant availability, location, and the kind and depth of information required when choosing techniques such as workshops, interviews, or surveys. Technical implementation and testing details are outside elicitation planning.
Question 6Business Analysis Planning and Monitoring
A BA is defining performance measures for the business analysis work itself. Which measure best evaluates the quality of elicited requirements?
- Number of meetings held per month
- Elapsed time from project kickoff to first draft
- Percentage of requirements that pass peer review without rework Correct answer.
- Count of stakeholders invited to workshops
Explanation
Business analysis performance metrics should reflect the quality and usefulness of the work products, such as defect or rework rates on requirements. Activity counts and elapsed time measure effort rather than requirement quality.
Question 7Business Analysis Planning and Monitoring
Which statement best describes the purpose of the business analysis approach as a planning output?
- It records the approved solution architecture and technology choices
- It documents the selected methodology, deliverables, and level of detail for business analysis work Correct answer.
- It lists all identified project risks and their mitigation strategies
- It captures the final accepted requirements for sign-off
Explanation
The business analysis approach describes how business analysis will be performed, including methodology, deliverables, timing, and level of detail. It is a planning artifact, not a design, risk, or requirements baseline document.
Question 8Business Analysis Planning and Monitoring
A BA is determining how requirements will be traced from business need through to testing. Which planning decision does this represent?
- Selecting the requirements elicitation technique
- Determining the solution deployment schedule
- Establishing the communication frequency
- Defining the requirements traceability approach Correct answer.
Explanation
Traceability planning defines the levels and relationships to be tracked, such as linking business objectives to requirements and test cases. It is separate from technique selection, communication cadence, and deployment timing.
Question 9Business Analysis Planning and Monitoring
An organization is using an adaptive approach on a product with rapidly changing priorities. How should the BA plan requirements prioritization?
- Freeze priorities at project start and prohibit changes
- Prioritize only once at the end of the project
- Prioritize continuously in short cycles with active stakeholder involvement Correct answer.
- Delegate all prioritization decisions to the development team alone
Explanation
Adaptive approaches assume changing priorities, so prioritization is repeated frequently with stakeholder collaboration. Freezing priorities or deferring them contradicts the iterative nature of such approaches.
Question 10Business Analysis Planning and Monitoring
Which of the following is a valid reason to tailor the level of formality in business analysis documentation?
- To shorten the project timeline regardless of risk
- To match organizational culture and the risk of the initiative Correct answer.
- To reduce the number of stakeholders involved
- To avoid documenting requirements altogether
Explanation
Tailoring formality is legitimate when it aligns with organizational culture, contractual obligations, and risk. Reducing stakeholders or skipping documentation are not valid tailoring goals because they undermine analysis quality.
Question 11Business Analysis Planning and Monitoring
A BA needs to track the status of each requirement through its lifecycle. Which planning element supports this?
- A stakeholder satisfaction survey
- A requirements management tool configured with lifecycle states Correct answer.
- A project budget forecast
- A solution usability test plan
Explanation
Requirement lifecycle tracking requires a repository or tool configured with defined states such as proposed, approved, and implemented. Surveys, budgets, and usability plans do not track requirement status.
Question 12Business Analysis Planning and Monitoring
A BA is planning how to manage conflicts that arise among stakeholders over competing requirements. Which approach is most consistent with sound planning?
- Allow the most senior stakeholder to always decide unilaterally
- Ignore conflicts until they resolve themselves
- Escalate every disagreement immediately to the sponsor
- Define a decision-making and escalation process in advance Correct answer.
Explanation
Planning should establish how conflicts and decisions will be resolved, including escalation paths and decision authority. Predefined processes reduce ad hoc escalation and unilateral dominance.
Question 13Business Analysis Planning and Monitoring
Which planning activity ensures that business analysis work aligns with organizational governance such as audit and compliance requirements?
- Drafting the solution deployment runbook
- Estimating development effort in story points
- Reviewing organizational process assets and constraints during approach planning Correct answer.
- Running a usability test on a prototype
Explanation
Approach planning considers organizational process assets, policies, and constraints, including audit and compliance obligations. Testing, estimation, and deployment activities occur later and do not establish governance alignment.
Question 14Business Analysis Planning and Monitoring
A BA is estimating the effort required to elicit and document requirements for a large, unfamiliar domain. Which factor most increases that estimate?
- High familiarity of the BA with the domain
- Reuse of existing approved requirement templates
- Limited availability of subject matter experts Correct answer.
- A stable and well-documented business process
Explanation
Scarce subject matter expertise increases elicitation effort because scheduling and knowledge capture become harder. Domain familiarity, templates, and stable processes tend to reduce effort.
Question 15Business Analysis Planning and Monitoring
Which statement best distinguishes business analysis planning from business analysis monitoring?
- Monitoring defines the approach and planning measures its results
- Planning occurs only at project initiation while monitoring occurs only at closure
- Planning and monitoring are identical activities with different names
- Planning sets the approach and monitoring tracks performance against that approach Correct answer.
Explanation
Planning establishes how business analysis will be conducted, while monitoring compares actual performance and quality against those plans and triggers adjustments. They are complementary and both occur throughout the initiative.
Question 16Business Analysis Planning and Monitoring
A BA notices that requirement reviews are consistently missing defects that surface during testing. What is the most appropriate monitoring response?
- Conclude that testing is unnecessary and stop it
- Reduce the number of reviewers to speed up reviews
- Accept the defects as an unavoidable cost of the project
- Adjust the review process and quality criteria to improve defect detection Correct answer.
Explanation
Monitoring reveals a gap between planned quality and actual outcomes, which should trigger corrective action such as revising review criteria or techniques. Abandoning testing or reducing rigor worsens the problem.
Question 17Business Analysis Planning and Monitoring
When planning stakeholder engagement, a BA identifies a stakeholder who has high influence but low interest in the project. Which engagement strategy is most appropriate?
- Ignore them because their interest is low
- Engage intensively through frequent collaborative workshops
- Provide them with full technical documentation on a daily basis
- Keep them satisfied with concise, targeted updates and monitor their concerns Correct answer.
Explanation
High-influence, low-interest stakeholders should be kept satisfied with efficient, targeted communication so their support is maintained without overburdening them. Intensive workshops or full documentation would be disproportionate.
Question 18Business Analysis Planning and Monitoring
Which output of business analysis planning and monitoring identifies the specific business analysis tasks, their sequence, and their timing?
- The business analysis plan or work breakdown Correct answer.
- The solution requirements specification
- The test strategy document
- The organizational chart
Explanation
The business analysis plan lays out the tasks, sequencing, and schedule for the analysis work. Requirements specifications, organizational charts, and test strategies serve different purposes.
Question 19Business Analysis Planning and Monitoring
A BA is selecting techniques to elicit requirements from a large group of users across multiple locations. Which technique is best suited to gathering broad input efficiently?
- A single deep-dive observation session
- One-on-one interviews with every user
- A focused review of source code
- A structured survey or questionnaire Correct answer.
Explanation
Surveys and questionnaires efficiently collect input from large, dispersed groups. Interviews and observation are resource-intensive and suited to depth, while code review does not elicit user needs.
Question 20Business Analysis Planning and Monitoring
Which consideration most influences how frequently a BA should re-plan business analysis activities?
- The color palette chosen for reports
- The number of developers on the team
- The frequency of changes to scope, priorities, or stakeholder composition Correct answer.
- The choice of database vendor
Explanation
Monitoring triggers re-planning when scope, priorities, or stakeholders change significantly. Technical choices like report colors, team size, or database vendors do not by themselves signal a need to revisit the analysis plan.
Question 21Business Analysis Planning and Monitoring
A BA is planning how to validate that requirements remain aligned with business goals throughout the project. Which planning element is most relevant?
- Selecting the code repository branching strategy
- Scheduling the team holiday calendar
- Choosing the office seating arrangement
- Defining traceability from business goals to requirements Correct answer.
Explanation
Tracing business goals to requirements enables ongoing verification that requirements still support the intended outcomes. The other options are administrative or technical logistics unrelated to goal alignment.
Question 22Business Analysis Planning and Monitoring
A BA discovers that a planned elicitation workshop cannot proceed because key participants are unavailable for several weeks. What is the most appropriate planning response?
- Reassess the elicitation plan and consider alternative techniques or sequencing Correct answer.
- Proceed without the key participants and finalize requirements
- Document the delay and take no further action
- Cancel the project entirely
Explanation
Monitoring deviations from the plan should prompt reassessment of techniques, sequencing, or scheduling so analysis continues productively. Proceeding without critical input or doing nothing risks poor requirements.
Question 23Business Analysis Planning and Monitoring
Which of the following best describes a stakeholder map used in business analysis planning?
- A diagram of the solution's database schema
- A list of approved software licenses
- A schedule of project milestones and deliverables
- A visual representation of stakeholders and their relationships, influence, and interest Correct answer.
Explanation
A stakeholder map depicts stakeholders along with their relationships, influence, and interest to guide engagement planning. Schema diagrams, milestone schedules, and license lists serve unrelated purposes.
Question 24Business Analysis Planning and Monitoring
A BA is defining how business analysis deliverables will be reviewed and approved. Which planning decision is being made?
- The development team's coding standards
- The requirements approval and sign-off process Correct answer.
- The solution's user interface layout
- The production server configuration
Explanation
Planning must specify who reviews and approves business analysis deliverables and how sign-off occurs. Interface layout, coding standards, and server configuration are technical or design concerns.
Question 25Business Analysis Planning and Monitoring
A BA is evaluating whether the business analysis approach should be predictive or adaptive for a regulated financial system with stable, well-understood requirements. Which choice is most defensible?
- An adaptive approach with no documentation
- A predictive approach with formal baselines and controlled change Correct answer.
- An adaptive approach that skips stakeholder engagement
- A predictive approach that forbids any change requests
Explanation
Stable, well-understood requirements in a regulated context favor a predictive approach with formal baselines and controlled change to satisfy audit needs. Forbidding all change or skipping documentation and engagement is never defensible.
Question 26Business Analysis Planning and Monitoring
Which business analysis planning output defines the activities, tasks, deliverables, and timing for the requirements work on an initiative?
- The business analysis plan Correct answer.
- The solution scope statement
- The stakeholder engagement matrix
- The requirements traceability matrix
Explanation
The business analysis plan is the planning output that describes how the work will be performed, including tasks, deliverables, schedule, and techniques. Other artifacts record stakeholder information, requirement relationships, or solution boundaries rather than the work plan itself.
Question 27Business Analysis Planning and Monitoring
A BA must decide how formally to document requirements for a small internal tool used by one department. Which factor most directly supports choosing a lighter level of formality?
- The number of integration points with external systems
- The anticipated lifespan of the resulting solution
- The organization's regulatory audit obligations
- The size and co-location of the stakeholder group Correct answer.
Explanation
Level of formality should be tailored to factors such as stakeholder size, distribution, and organizational culture. A small, co-located stakeholder group reduces the coordination burden that heavy documentation addresses. Regulatory obligations, integrations, and lifespan typically push toward more rigor.
Question 28Business Analysis Planning and Monitoring
Which element of business analysis planning and monitoring establishes how changes to approved requirements will be requested, assessed, and decided?
- The requirements management plan Correct answer.
- The elicitation activity schedule
- The communication plan for stakeholders
- The solution acceptance criteria
Explanation
The requirements management plan defines how requirements will be managed over their lifecycle, including change control, baselining, and approval authority. Scheduling elicitation, communicating, and defining acceptance criteria are separate concerns.
Question 29Business Analysis Planning and Monitoring
A BA is planning how to measure whether the business analysis effort is progressing as planned. Which set of measures best fits business analysis performance monitoring?
- Number of requirements approved, open change requests, and stakeholder review turnaround Correct answer.
- Server availability and average transaction response time
- Defect density in delivered code and mean time to resolve production incidents
- Return on investment and payback period of the proposed solution
Explanation
Business analysis performance monitoring tracks the analysis work itself, such as requirement throughput, change volume, and review cycle time. Code defects, solution financials, and system performance measure the solution or operations rather than the analysis effort.
Question 30Business Analysis Planning and Monitoring
Midway through an initiative, a BA learns that a new compliance rule will require additional stakeholder approvals for every requirement. What is the most appropriate monitoring response?
- Ask stakeholders to approve requirements verbally until the rule is clarified
- Continue the current plan and note the rule in the final lessons-learned report
- Escalate to the project sponsor to have the compliance rule waived for the initiative
- Update the business analysis plan to reflect the new approval steps and re-baseline affected activities Correct answer.
Explanation
Monitoring compares actual conditions against the plan and triggers re-planning when assumptions change. A new approval requirement alters the analysis process, so the plan must be updated and affected activities re-baselined. Deferring, waiving, or bypassing the rule leaves the work misaligned with governance.
Question 31Business Analysis Planning and Monitoring
A BA is planning which stakeholders must be consulted during elicitation versus merely informed of outcomes. Which planning artifact most directly supports this decision?
- The business analysis communication plan
- The solution design document
- The requirements architecture
- The stakeholder engagement approach Correct answer.
Explanation
The stakeholder engagement approach defines how stakeholders will be involved, including their roles, influence, and required level of participation. Communication planning addresses information distribution, while the other artifacts concern solution structure or design.
Question 32Business Analysis Planning and Monitoring
A BA is estimating the effort to complete requirements work on an initiative with a well-understood domain but a very large stakeholder base spread across regions. Which factor most increases estimation uncertainty?
- The number and geographic distribution of stakeholders Correct answer.
- The availability of a documented current-state process
- The familiarity of the business domain
- The experience level of the assigned BA
Explanation
Estimation uncertainty rises with coordination complexity, and a large, dispersed stakeholder base increases scheduling, elicitation, and review effort. A familiar domain, documented processes, and experienced staff reduce rather than increase uncertainty.
Question 33Business Analysis Planning and Monitoring
An organization wants the business analysis approach to support frequent, low-cost course corrections as understanding of customer needs evolves. Which planning choice is most consistent with that goal?
- Plan short iterations with lightweight documentation and continuous stakeholder feedback Correct answer.
- Require formal sign-off of a complete requirements specification before each review
- Baseline all requirements before any design work begins and route changes through a change board
- Defer all stakeholder engagement until the requirements are fully documented
Explanation
Adaptive planning favors short cycles, minimal documentation overhead, and ongoing stakeholder feedback so that direction can be corrected cheaply. Heavy upfront baselining and deferred engagement are characteristics of predictive planning.
Question 34Business Analysis Planning and Monitoring
A BA notices that the planned elicitation approach relies on a single workshop with senior managers, while frontline staff who perform the work are excluded. Which planning gap does this most directly represent?
- An inadequate change control process
- An incorrect technique selection for capturing quantitative data
- A missing requirements traceability structure
- An incomplete stakeholder analysis that misjudges who holds relevant information Correct answer.
Explanation
Stakeholder analysis identifies who has relevant knowledge and how they should be engaged; excluding the people who do the work signals that this analysis is incomplete. The issue is about participant coverage rather than data type, traceability, or change control.
Question 35Elicitation and Collaboration
According to the elicitation and collaboration knowledge area, which task comes first in the sequence of activities?
- Confirm elicitation results
- Prepare for elicitation Correct answer.
- Conduct elicitation activity
- Manage stakeholder collaboration
Explanation
The knowledge area organizes work so that practitioners prepare for elicitation before running an activity, then confirm results with stakeholders afterward. Collaboration management runs alongside and across all of these tasks rather than preceding them.
Question 36Elicitation and Collaboration
A business analyst is deciding which elicitation technique to use for a sensitive topic where participants may be reluctant to speak openly in a group. Which preparation consideration most directly drives this choice?
- The physical location of the meeting room
- The project's change control process
- The number of slides in the presentation deck
- The characteristics of the stakeholder audience and the sensitivity of the information Correct answer.
Explanation
Technique selection during preparation is driven by who the stakeholders are, what information is needed, and how sensitive or contested the topic is. Audience characteristics and topic sensitivity point toward individual or anonymous techniques rather than large group sessions.
Question 37Elicitation and Collaboration
During preparation, a business analyst identifies that key decision makers are unavailable for the planned workshop. What is the most appropriate action?
- Proceed with the workshop and approve decisions on their behalf
- Replace the workshop with a written survey sent only to the unavailable stakeholders
- Cancel the entire initiative until everyone is available
- Reschedule or restructure the session and secure alternate representation or follow-up input Correct answer.
Explanation
Preparation includes confirming participant availability and ensuring the right stakeholders can contribute or authorize outcomes. Adjusting timing or representation preserves decision quality without stalling the whole effort.
Question 38Elicitation and Collaboration
Which output is produced by the 'Prepare for Elicitation' task?
- Stakeholder engagement assessment matrix
- Verified requirements baseline
- Elicitation activity plan Correct answer.
- Requirements architecture
Explanation
The preparation task yields an elicitation activity plan covering scope, techniques, logistics, and supporting materials. The other listed artifacts belong to planning, requirements analysis, or stakeholder analysis work outside this task.
Question 39Elicitation and Collaboration
A business analyst wants to uncover underlying assumptions and surface disagreements among stakeholders early. Which elicitation technique is best suited to this goal?
- Observation
- Interface analysis
- Brainstorming Correct answer.
- Document analysis
Explanation
Brainstorming brings stakeholders together to generate and challenge ideas, which surfaces differing assumptions and conflicts quickly. Document and interface analysis examine existing artifacts and system boundaries rather than group assumptions.
Question 40Elicitation and Collaboration
Which technique is specifically designed to help a group of stakeholders reach agreement on requirements priorities?
- Surveys
- Data mining
- Facilitated workshops Correct answer.
- Focus groups
Explanation
Facilitated workshops assemble cross-functional stakeholders with a facilitator to collaborate, resolve conflicts, and reach agreement on requirements. The other techniques gather information but are not structured for negotiated consensus.
Question 41Elicitation and Collaboration
A business analyst completes a series of interviews and now needs to ensure the captured information is accurate and agreed upon. Which action best fulfills the 'Confirm Elicitation Results' task?
- Convert the notes into a project schedule
- Immediately submit the notes for formal sign-off as final requirements
- Compare the elicited information against other sources and validate it with the participants Correct answer.
- Archive the interview notes without review
Explanation
Confirming results involves checking elicited information for consistency with other sources and validating it with stakeholders to ensure shared understanding. This step precedes treating the information as an approved requirement.
Question 42Elicitation and Collaboration
Two stakeholders provide conflicting descriptions of the same business process during elicitation. What is the most appropriate next step?
- Discard both descriptions and restart the project
- Average the two descriptions into a single narrative
- Investigate the discrepancy with additional elicitation and reconcile the accounts Correct answer.
- Choose the description from the more senior stakeholder
Explanation
Conflicting information must be investigated and reconciled, often through further elicitation or corroborating sources, before results can be confirmed. Deferring to seniority or merging narratives risks embedding errors.
Question 43Elicitation and Collaboration
What is the primary purpose of the 'Communicate Business Analysis Information' task?
- To select the project management methodology
- To assign work to development team members
- To ensure stakeholders receive and understand the information they need Correct answer.
- To formally approve the project budget
Explanation
This task ensures that business analysis information is packaged and delivered so stakeholders understand it and can act on it. Budget approval, work assignment, and methodology selection belong to other disciplines.
Question 44Elicitation and Collaboration
A business analyst must present complex requirements to an executive audience with limited time. Which communication approach is most appropriate?
- A raw export of the requirements repository
- A detailed technical specification with all supporting data
- A series of lengthy working sessions with the executives
- A concise summary emphasizing key decisions and impacts Correct answer.
Explanation
Communication should be tailored to the audience's needs, level of detail, and available time. Executives typically need concise, decision-focused summaries rather than exhaustive technical detail.
Question 45Elicitation and Collaboration
Which of the following best describes the 'Manage Stakeholder Collaboration' task?
- Encouraging stakeholders to work together toward shared business analysis goals and addressing collaboration issues Correct answer.
- Controlling stakeholder access to the requirements repository
- Documenting stakeholder job titles and reporting lines
- Negotiating contracts with external vendors
Explanation
Managing stakeholder collaboration involves fostering productive working relationships, keeping stakeholders engaged, and resolving issues that impede collaboration. It is broader than access control, org charting, or procurement.
Question 46Elicitation and Collaboration
A stakeholder who was initially enthusiastic becomes disengaged and stops responding to requests. As part of managing stakeholder collaboration, what should the business analyst do first?
- Remove the stakeholder from the project distribution list
- Proceed without the stakeholder's input
- Escalate to the stakeholder's manager immediately
- Investigate the cause of the disengagement and adjust the engagement approach Correct answer.
Explanation
Managing collaboration requires monitoring engagement and diagnosing the reasons for reduced participation before choosing a response. Adjusting the approach based on the cause is more effective than escalating or disengaging.
Question 47Elicitation and Collaboration
Which of the following is an example of a 'stated' requirement captured during elicitation?
- A requirement derived from industry regulations
- A requirement discovered through data analysis
- A requirement inferred from how users actually perform their work
- A requirement the stakeholder explicitly asks for Correct answer.
Explanation
Stated requirements are those stakeholders explicitly communicate during elicitation. Inferred, derived, and discovered requirements come from observation, regulation analysis, or data analysis rather than direct statements.
Question 48Elicitation and Collaboration
What distinguishes a 'facilitated workshop' from a 'focus group' in elicitation?
- A facilitated workshop is always conducted online
- A focus group produces formal requirements while a workshop does not
- A focus group requires more participants than a workshop
- A facilitated workshop aims to produce agreed outcomes through structured collaboration, while a focus group gathers opinions Correct answer.
Explanation
Facilitated workshops are structured sessions designed to reach agreement and produce outcomes, whereas focus groups primarily elicit attitudes and opinions. Participant count and delivery mode do not define the distinction.
Question 49Elicitation and Collaboration
A business analyst uses observation to study how clerks process orders. Which type of requirement is most likely to be revealed by this technique?
- Regulatory requirements from a compliance audit
- Contractual requirements from a service agreement
- Unstated requirements reflecting actual work practices Correct answer.
- Stated requirements from a policy manual
Explanation
Observation reveals how work is actually performed, often exposing unstated needs and workarounds that stakeholders do not articulate. Manuals, audits, and contracts are document-based sources rather than observational ones.
Question 50Elicitation and Collaboration
Which of the following best describes 'elicitation' as opposed to simply 'gathering requirements'?
- An iterative process of drawing out information from stakeholders and other sources and confirming understanding Correct answer.
- Copying requirements from a previous project
- Waiting for stakeholders to submit a complete requirements list
- Collecting whatever requirements stakeholders happen to send by email
Explanation
Elicitation is an active, iterative process of drawing out and confirming information from people and other sources, not passive collection. It emphasizes dialogue, discovery, and validation.