You've delivered a solution that met every documented requirement, but adoption is low. What's the mature response?
- A. Conclude that users are simply resistant to change
- B. Investigate why adoption is low, since the requirements may have missed the real need or context ✓
- C. Declare the project a success because all requirements were met
- D. Add more features to try to force engagement
Correct answer: B. Low adoption is a signal that the requirements may not have captured the real need worth investigating.
A powerful executive insists on an approach you have data showing won't work. How do you handle it?
- A. Comply, because they outrank you
- B. Present the evidence respectfully, propose a small test, and let data inform the decision ✓
- C. Refuse to work on the approach at all
- D. Go around them to their boss with your concerns
Correct answer: B. Respectful evidence plus a low-cost test lets facts, not hierarchy, drive the decision.
You need buy-in from a team that doesn't report to you and is resistant. How do you influence without authority?
- A. Escalate to force them to comply
- B. Understand their concerns, show how the change benefits them, and build trust over time ✓
- C. Simply proceed without their involvement
- D. Point out their resistance publicly in meetings
Correct answer: B. Understanding concerns and showing mutual benefit builds durable buy-in that force can't.
How do you determine whether your solution actually delivered business value?
- A. Count the number of features that shipped
- B. Define success metrics tied to business outcomes upfront and measure against them ✓
- C. Ask stakeholders whether they feel happy with it
- D. Track how many requirements were implemented
Correct answer: B. Outcome-linked metrics defined upfront are the only credible test of real value delivered.
A long-running project's original business case no longer holds. What's your responsibility?
- A. Keep going, since the project was already approved
- B. Raise it with the sponsor and recommend re-evaluating or stopping ✓
- C. Quietly reduce your effort on it
- D. Wait for someone else to eventually notice
Correct answer: B. A BA's duty is to keep the work tied to value, even when that means recommending a stop.
Two departments are in open conflict over a shared process you're redesigning. How do you proceed?
- A. Side with the more powerful department
- B. Facilitate neutrally, focus on shared business goals, and find common ground ✓
- C. Design it yourself and impose the result
- D. Refuse to work until they resolve the conflict on their own
Correct answer: B. Neutral facilitation toward shared goals produces a solution both sides can accept.
You're pushed to deliver fast, but skipping discovery risks solving the wrong problem. How do you handle the pressure?
- A. Skip discovery entirely to hit the date
- B. Run a lean, time-boxed discovery to de-risk before committing to a build ✓
- C. Refuse to start until a full discovery phase is complete
- D. Build something quickly and iterate blindly afterward
Correct answer: B. A time-boxed discovery de-risks the biggest unknowns without derailing the schedule.
A stakeholder constantly changes their mind, causing repeated rework. How do you address it professionally?
- A. Stop engaging with that stakeholder
- B. Explore the root cause, use prototypes to firm up decisions, and make the cost of changes visible ✓
- C. Lock them out of the process going forward
- D. Build to their first version and ignore later changes
Correct answer: B. Prototypes and visible change costs help unstable requirements settle without souring the relationship.
Your analysis contradicts what leadership wants to hear. What do you do?
- A. Soften the data so it aligns with their expectations
- B. Present the findings honestly with evidence and clear implications ✓
- C. Withhold the findings to avoid conflict
- D. Show only the parts of the analysis they'll like
Correct answer: B. Honest, evidence-backed findings are the value a BA provides, even when they're unwelcome.
How do you judge when you've gathered "enough" requirements to proceed?
- A. When the requirements document reaches a certain length
- B. When you understand the problem well enough to deliver value and can iterate on the rest ✓
- C. When you've captured every conceivable edge case
- D. When the deadline forces you to stop
Correct answer: B. Enough is when you can deliver value and refine the remainder iteratively, not exhaustive coverage.
A solution you championed is underperforming. In the retrospective, what's the best posture?
- A. Defend the decisions you made at the time
- B. Own the outcome, examine what was missed, and share the learnings openly ✓
- C. Point the blame at the development team
- D. Attribute it to requirements that kept changing
Correct answer: B. Owning the outcome and extracting learnings builds trust and improves future delivery.
Leadership wants a big-bang launch; you believe a phased rollout reduces risk. How do you make your case?
- A. Comply without raising your view
- B. Present the risk and benefit trade-offs with evidence and recommend a path, leaving the decision to them ✓
- C. Refuse to support a big-bang launch under any circumstances
- D. Quietly plan a phased rollout without telling them
Correct answer: B. A clear, evidence-based recommendation informs the decision while respecting who owns it.
You inherit a project with vague goals and no clear sponsor. What's your first priority?
- A. Start gathering detailed requirements right away
- B. Establish clear ownership, objectives, and success criteria before going deeper ✓
- C. Build a prototype to spark some interest
- D. Wait for leadership to clarify things on their own
Correct answer: B. Without ownership and objectives, detailed requirements have no anchor and risk being wasted.
A key metric improved after your project, but you're unsure your change caused it. How do you report it?
- A. Claim full credit for the improvement
- B. Present the correlation honestly, note confounding factors, and suggest how to isolate the impact ✓
- C. Attribute the improvement entirely to your solution
- D. Report the improvement without mentioning the uncertainty
Correct answer: B. Honest attribution with caveats preserves credibility and points toward proper measurement.
Stakeholders want to track many KPIs, several of which are vanity metrics. How do you guide them?
- A. Track everything they ask for
- B. Focus on a few actionable metrics tied to real decisions and outcomes ✓
- C. Pick whichever metrics will look best in reports
- D. Let each stakeholder track their own preferred metrics
Correct answer: B. A few decision-linked metrics drive action; vanity metrics create noise and false comfort.
A requirement everyone agreed on turns out to conflict with a compliance rule you've just learned about. What do you do?
- A. Proceed, since the stakeholders already approved it
- B. Flag it immediately, bring in compliance, and rework the requirement ✓
- C. Quietly adjust the requirement yourself
- D. Wait until testing to raise the issue
Correct answer: B. Raising compliance conflicts early and involving experts prevents costly, risky rework later.
You're facilitating a workshop that's going off the rails with tangents and rising conflict. What's the best facilitation move?
- A. Let the discussion run its natural course
- B. Refocus on the agreed objectives, park tangents in a list, and address the conflict openly ✓
- C. End the meeting to cut the tension
- D. Side with the loudest group so the session can move on
Correct answer: B. Refocusing, parking tangents, and naming the conflict keeps the session productive and fair.
How should you decide between gold-plating a solution and shipping a simpler version?
- A. Add every nice-to-have while you have the chance
- B. Ship what solves the core problem and delivers value, then iterate based on feedback ✓
- C. Build the most impressive version so the project stands out
- D. Ask developers which version they'd most enjoy building
Correct answer: B. Delivering the core value first and iterating avoids waste and gets real feedback sooner.
A senior stakeholder asks you to omit an inconvenient finding from your report to the steering committee. How do you respond?
- A. Comply in order to protect the relationship
- B. Explain why transparency matters and find a constructive way to present the finding ✓
- C. Omit it from the report but mention it privately to others
- D. Report the stakeholder for making the request
Correct answer: B. Maintaining transparency while presenting findings constructively protects both integrity and the relationship.
Your recommended solution requires a behavior change users are resistant to. How do you maximize its chance of success?
- A. Mandate the change and enforce compliance
- B. Involve users early, address their concerns, and plan change management and support ✓
- C. Launch it and hope users adapt over time
- D. Water the solution down until no change is needed, even if it loses most of its value
Correct answer: B. Early involvement and change management turn resistance into adoption where mandates fail.