Salesforce Business Analyst Practice Test

How This Test Maps to the Exam Outline

Salesforce publishes six weighted sections for this exam. The 50 questions below are distributed to mirror those weightings, so a low score in one area tells you which section of the official study material to revisit.

Section weightings are taken from the official Salesforce Business Analyst certification preparation material. Always check the current exam guide on Trailhead before booking, as Salesforce revises outlines periodically.

Answer Key with Explanations

Every question is explained below, including why each incorrect option is wrong. Reading the distractor explanations is usually more valuable than reading the correct answer, because the real exam is built almost entirely from plausible-sounding wrong options.

1. 1. A business analyst is starting an engagement with a company whose only stated goal is to “improve sales productivity.” No further detail has been provided. What should the BA do first?

   Correct answer: A — Review the existing org configuration, current reports, and business metrics to establish a baseline of the current state

   Why it is correct: Discovery starts by understanding the current state. Reviewing existing configuration, reports, and operational metrics establishes a measurable baseline and surfaces where time is actually lost, so the eventual solution addresses a real problem rather than an assumed one.

   Why the others are wrong: C and D both jump to a solution before the problem has been defined — a classic discovery failure. B belongs at the end of the delivery lifecycle, after a solution has been built.

   Exam section: Customer Discovery  ·  Concepts tested: Current-state analysis, baseline metrics, org review

2. 2. A BA needs to understand how service agents genuinely handle an inbound case, rather than how the documented procedure says they should. Which elicitation technique is most appropriate?

   Correct answer: B — Job shadowing and direct observation of agents at work

   Why it is correct: Observation exposes the undocumented workarounds, shortcuts, and off-system steps that people forget to mention in interviews. It is the highest-fidelity technique for capturing actual behaviour.

   Why the others are wrong: C captures self-reported behaviour, which is often inaccurate for routine tasks. D describes structure, not behaviour. A is a governance forum, not an elicitation technique.

   Exam section: Customer Discovery  ·  Concepts tested: Elicitation techniques, observation, as-is analysis

3. 3. During discovery, stakeholders explain that sales reps spend roughly 40 minutes each day re-keying data from email into Salesforce. Which artifact best captures this so it can be prioritised later?

   Correct answer: C — A documented pain point recording the affected role, the frequency, and the quantified business impact

   Why it is correct: A pain point statement that names the role, frequency, and quantified cost turns an anecdote into evidence. Quantification is what allows the Product Owner to rank this against competing work later.

   Why the others are wrong: B documents data structure. D is a testing artifact produced much later. A tracks sprint progress, not business problems.

   Exam section: Customer Discovery  ·  Concepts tested: Pain point documentation, quantifying impact

4. 4. A BA must define a success metric for a project intended to shorten quote turnaround time. Which option is the strongest metric?

   Correct answer: D — Average elapsed time from opportunity creation to quote sent, measured before and after go-live

   Why it is correct: This is an outcome measure tied directly to the stated business objective, and it is expressed as a before-and-after comparison so improvement can actually be proven.

   Why the others are wrong: A, B, and C are activity or output measures. They describe how busy the project team was, not whether the business problem was solved.

   Exam section: Customer Discovery  ·  Concepts tested: Success metrics, KPIs, business case

5. 5. What is the primary purpose of an org review (sometimes called an org health check) during the discovery phase?

   Correct answer: A — To identify existing objects, automation, technical debt, and unused customisation that will constrain or enable the proposed solution

   Why it is correct: An existing org carries history: overlapping automation, abandoned custom objects, duplicated fields, and legacy sharing rules. Knowing what is already there prevents the team from designing something that conflicts with, or duplicates, existing functionality.

   Why the others are wrong: D is a commercial exercise. B is a delivery-methodology decision made by the team. C happens at the end of delivery, not during discovery.

   Exam section: Customer Discovery  ·  Concepts tested: Org review, technical debt, current-state analysis

6. 6. A BA discovers that the sales team calls a record a “deal” while the finance team calls the same record an “opportunity.” What should the BA produce to resolve this?

   Correct answer: B — A shared business glossary that defines the agreed term and is confirmed by both departments

   Why it is correct: Inconsistent terminology causes requirements to be misread and solutions to be built twice. A glossary agreed by both groups creates a single vocabulary that every later artifact — requirements, stories, test scripts — can rely on.

   Why the others are wrong: A duplicates data and multiplies maintenance. C addresses duplicate records, not duplicate vocabulary. D changes presentation but leaves the underlying ambiguity unresolved.

   Exam section: Customer Discovery  ·  Concepts tested: Business glossary, shared vocabulary, stakeholder alignment

7. 7. Which statement best distinguishes a business problem from a proposed solution?

   Correct answer: C — “Sales managers cannot see pipeline broken down by region” is the problem; “add a Region field and a regional dashboard” is a solution

   Why it is correct: A problem describes an unmet business need in business language and leaves the design space open. A solution names a specific implementation. Separating them lets the team consider alternatives — a report type, a list view, or Salesforce reporting features — before committing to one build.

   Why the others are wrong: D confuses problem/solution with declarative/programmatic. A collapses the distinction that makes alternatives visible. B reverses the correct order and leads to solution-first thinking.

   Exam section: Customer Discovery  ·  Concepts tested: Problem framing, solution-agnostic requirements

8. 8. A BA is preparing a discovery workshop with 12 stakeholders drawn from four departments. Which preparation step will most improve the outcome of the session?

   Correct answer: D — Circulate an agenda in advance that states the objectives, the pre-read material, and the specific decisions the group must reach

   Why it is correct: A workshop with 12 people is expensive. Sending objectives, pre-reads, and the decision list in advance lets participants arrive prepared, keeps the session focused, and makes it clear what “done” looks like for the meeting.

   Why the others are wrong: A wastes the group's time on orientation. B loses the cross-functional perspective that justified the workshop. C turns discovery into a rubber-stamp exercise before requirements are understood.

   Exam section: Customer Discovery  ·  Concepts tested: Workshop planning, facilitation preparation

9. 9. What role does as-is documentation play during customer discovery?

   Correct answer: A — It records how work is actually performed today so that gaps, handoffs, and pain points can be identified before change is designed

   Why it is correct: You cannot measure improvement without a starting point. As-is documentation captures the real process — including workarounds and manual handoffs — giving the team an evidence base for what should change and why.

   Why the others are wrong: D describes to-be documentation. B and C are delivery-phase artifacts produced long after discovery.

   Exam section: Customer Discovery  ·  Concepts tested: As-is documentation, gap analysis

10. 10. In a RACI matrix, which description matches the “Consulted” role?

    Correct answer: B — Stakeholders whose input is actively sought in two-way dialogue before a decision is finalised

    Why it is correct: Consulted stakeholders participate in a two-way exchange before the decision is locked. Their expertise shapes the outcome, which is what distinguishes them from Informed stakeholders.

    Why the others are wrong: D is Responsible. A is Accountable. C is Informed — a one-way notification after the fact.

    Exam section: Collaboration with Stakeholders  ·  Concepts tested: RACI, stakeholder roles, governance

11. 11. A project sponsor and a department head disagree about whether a field should be mandatory at a particular stage. What is the most appropriate action for the BA?

    Correct answer: C — Facilitate a session that surfaces each party's underlying business driver, document the options with their trade-offs, then route any unresolved decision to the agreed decision-maker

    Why it is correct: Positional disagreements usually mask different underlying drivers — here, perhaps data quality versus speed of entry. Surfacing those drivers often reveals an option that satisfies both. Documenting trade-offs and escalating only what remains unresolved respects the governance model without stalling delivery.

    Why the others are wrong: A escalates prematurely and burns sponsor goodwill. B is outside the BA's authority and creates rework when overturned. D adds permanent configuration complexity to avoid a conversation.

    Exam section: Collaboration with Stakeholders  ·  Concepts tested: Conflict resolution, facilitation, decision governance

12. 12. Which stakeholder analysis output most directly helps a BA decide how much and how often to communicate with each stakeholder?

    Correct answer: D — A power and interest (influence/interest) grid

    Why it is correct: Plotting stakeholders by influence and interest produces four engagement strategies — manage closely, keep satisfied, keep informed, monitor — which translate directly into communication frequency and format.

    Why the others are wrong: A, B, and C are technical or delivery artifacts. None of them describes stakeholder engagement needs.

    Exam section: Collaboration with Stakeholders  ·  Concepts tested: Stakeholder analysis, communication planning

13. 13. Mid-sprint, a senior stakeholder approaches the BA directly and asks for “one small extra field, while you're in there.” What is the appropriate response?

    Correct answer: A — Capture it as a new backlog item, assess its impact, and route it through the agreed prioritisation or change process

    Why it is correct: Uncontrolled additions — scope creep — accumulate silently and destabilise the sprint commitment. Logging the request preserves the relationship (the idea is not lost) while protecting the process that keeps the release predictable.

    Why the others are wrong: D bypasses the Product Owner's prioritisation authority. B is unnecessarily rigid; backlogs are meant to absorb new ideas. C creates undocumented configuration that nobody can trace later.

    Exam section: Collaboration with Stakeholders  ·  Concepts tested: Scope management, change control, backlog hygiene

14. 14. What is the primary purpose of a project charter from a business analyst's perspective?

    Correct answer: B — To record the business case, objectives, scope boundaries, key stakeholders, and success criteria the team is accountable to

    Why it is correct: The charter is the reference point the BA returns to whenever a request arrives that may be out of scope, or whenever priorities are questioned. It makes the agreed boundaries and success criteria explicit and shared.

    Why the others are wrong: A, C, and D are all narrow technical or delivery artifacts that sit far below the charter's level of abstraction.

    Exam section: Collaboration with Stakeholders  ·  Concepts tested: Project charter, scope definition, business case

15. 15. A BA must present a proposed process change to a non-technical executive audience with 15 minutes on the agenda. Which approach is most effective?

    Correct answer: C — Show a simple current-state versus future-state visual, the quantified business impact, and the specific decision being requested

    Why it is correct: Executive audiences need the change, the value, and the ask. A side-by-side process visual communicates the change in seconds, the quantified impact justifies it, and naming the decision makes the meeting productive.

    Why the others are wrong: A and D operate at a level of detail that executives cannot act on. B shows mechanics rather than business outcome and consumes the whole slot.

    Exam section: Collaboration with Stakeholders  ·  Concepts tested: Executive communication, tailoring artifacts to audience

16. 16. In a requirements workshop, one participant dominates the discussion and quieter subject matter experts are not contributing. What is the best facilitation response?

    Correct answer: D — Introduce structured techniques — silent written brainstorming, round-robin input, affinity grouping, and a visible parking lot — so every participant's input is captured

    Why it is correct: Structured facilitation changes the format rather than confronting the individual. Silent brainstorming and round-robin turn-taking give equal airtime by design, and a parking lot lets the BA defer tangents without shutting anyone down.

    Why the others are wrong: C damages the relationship and loses genuine expertise. A loses the cross-pollination that makes workshops valuable. B avoids the facilitation problem entirely.

    Exam section: Collaboration with Stakeholders  ·  Concepts tested: Facilitation techniques, group dynamics

17. 17. On an agile Salesforce delivery team that has both a Business Analyst and a Product Owner, how are the two roles typically related?

    Correct answer: A — The BA elicits, analyses, and documents requirements and helps refine the backlog, while the Product Owner owns the product vision and final prioritisation

    Why it is correct: The BA supplies the analysis — well-formed requirements, acceptance criteria, process context — that lets the Product Owner make good prioritisation decisions. Prioritisation authority and product vision stay with the Product Owner.

    Why the others are wrong: C and D both hand the BA an authority the role does not hold. B describes a QA function, not a BA function.

    Exam section: Collaboration with Stakeholders  ·  Concepts tested: Agile roles, BA and Product Owner collaboration

18. 18. Which technique best builds shared understanding when the sales and service teams disagree about who owns a customer record after the sale closes?

    Correct answer: B — A cross-functional process mapping session using swimlanes to make the handoff and ownership rules explicit

    Why it is correct: Ownership disputes are handoff problems. A swimlane map forces the group to place each step in a specific lane, which makes the ambiguity visible and turns an abstract argument into a concrete decision about one transition point.

    Why the others are wrong: C looks at access, not process ownership. D excludes the very stakeholders who disagree. A is a technical rehearsal unrelated to the dispute.

    Exam section: Collaboration with Stakeholders  ·  Concepts tested: Cross-functional facilitation, swimlanes, handoff analysis

19. 19. A key stakeholder has missed three consecutive requirement review sessions and is now objecting to decisions made in their absence. What should the BA do?

    Correct answer: C — Reconfirm the stakeholder's RACI role, agree a workable cadence or a named delegate with the sponsor, and re-confirm the affected decisions in writing with a response deadline

    Why it is correct: Repeated non-attendance is a governance problem, not a scheduling accident. Clarifying whether the person is genuinely Accountable or merely Consulted, agreeing a delegate, and setting a written response deadline creates a decision path that no longer depends on their attendance.

    Why the others are wrong: B is technically defensible but guarantees the objection resurfaces later, often at the worst moment. D removes a stakeholder the sponsor may consider essential. A lets one calendar hold the whole project hostage.

    Exam section: Collaboration with Stakeholders  ·  Concepts tested: Stakeholder engagement, escalation, RACI in practice

20. 20. Which artifact is most useful for keeping geographically distributed stakeholders aligned on decisions taken between formal meetings?

    Correct answer: D — A decision log capturing each decision, its date, the decision-maker, and the rationale

    Why it is correct: A decision log with rationale prevents the same debate from being reopened months later and gives absent stakeholders a way to catch up without a meeting. Recording the rationale matters as much as the decision, because context is what fades first.

    Why the others are wrong: A, B, and C are technical artifacts. None of them records why a business choice was made or who made it.

    Exam section: Collaboration with Stakeholders  ·  Concepts tested: Decision log, distributed collaboration, traceability

21. 21. In a swimlane process diagram, what do the individual lanes represent?

    Correct answer: A — The roles, actors, or systems responsible for the steps placed within them

    Why it is correct: Lanes assign responsibility. Their real analytical value is that every arrow crossing a lane boundary is a handoff — and handoffs are where delay, rework, and ownership disputes concentrate.

    Why the others are wrong: D is shown by the left-to-right flow, not the lanes. B is captured in a data dictionary or CRUD matrix. C is an annotation on steps, not a lane property.

    Exam section: Business Process Mapping  ·  Concepts tested: Swimlane diagrams, role responsibility, handoffs

22. 22. While mapping a lead-to-opportunity process, a BA finds a step where a manager manually retypes data from an email into Salesforce. How should this appear on the map, and what does it signal?

    Correct answer: B — As a manual task, commonly annotated as a pain point and a candidate for automation or integration

    Why it is correct: Manual re-keying is a classic waste step: it costs time, introduces transcription errors, and usually indicates a missing integration or a broken upstream capture point. Annotating it as a pain point keeps it visible during prioritisation.

    Why the others are wrong: A misreads a task as a decision. C is a serious mapping error — off-system steps are often where the worst problems live. D confuses a mid-process activity with a trigger.

    Exam section: Business Process Mapping  ·  Concepts tested: Manual steps, waste identification, automation candidates

23. 23. What distinguishes a current-state (as-is) process map from a future-state (to-be) process map?

    Correct answer: C — As-is documents how the process genuinely runs today including workarounds; to-be documents the agreed redesigned process after the proposed change

    Why it is correct: The pair works as a before-and-after. The as-is provides the evidence base and the baseline metrics; the to-be provides the target the solution must deliver. The delta between them is the scope of change.

    Why the others are wrong: B invents a notation rule that does not exist — either notation can be used for either map. D places as-is mapping at the wrong end of the lifecycle. A erases the distinction that makes the technique useful.

    Exam section: Business Process Mapping  ·  Concepts tested: As-is versus to-be, gap analysis

24. 24. In standard flowchart and BPMN notation, which shape represents a point where the process branches based on a condition?

    Correct answer: D — A diamond, known in BPMN as a gateway

    Why it is correct: The diamond (gateway) marks a branch point with mutually exclusive or parallel outgoing paths, each labelled with its condition. Consistent notation lets any reader interpret the map without a legend.

    Why the others are wrong: C is an activity or task. A denotes start and end events. B traditionally denotes input or output in classic flowcharting.

    Exam section: Business Process Mapping  ·  Concepts tested: BPMN notation, flowchart symbols

25. 25. A case escalation process map has grown to 40 steps on one page and stakeholders can no longer follow it. What is the best remedy?

    Correct answer: A — Decompose it into a high-level end-to-end map with linked sub-process maps that hold the detail

    Why it is correct: Process decomposition gives each audience the level of detail it needs: executives read the level-1 map, and process owners drill into the sub-process that concerns them. No detail is lost, but no single view is overwhelming.

    Why the others are wrong: D destroys accuracy and may remove exactly the steps causing the problem. B loses the visual flow that makes maps easy to validate. C abandons the business audience the map exists to serve.

    Exam section: Business Process Mapping  ·  Concepts tested: Process decomposition, levelled maps, audience fit

26. 26. Why is it valuable to annotate process map steps with cycle time and volume data?

    Correct answer: B — It quantifies where the bottlenecks are, so improvement effort and expected return can be prioritised on evidence rather than opinion

    Why it is correct: A step that takes two days but runs twice a year matters far less than a step that takes ten minutes but runs 4,000 times a month. Volume multiplied by cycle time turns a qualitative map into a business case for change.

    Why the others are wrong: A, C, and D describe unrelated technical or licensing concerns and have no bearing on process analysis.

    Exam section: Business Process Mapping  ·  Concepts tested: Cycle time, volume analysis, bottleneck identification

27. 27. Which of the following is a well-formed, testable requirement?

    Correct answer: C — When an Opportunity is set to Closed Won, the system must create a renewal Opportunity with a close date 12 months after the original close date.

    Why it is correct: It states a specific trigger, a specific system behaviour, and a measurable outcome, so a tester can prove unambiguously whether it was met.

    Why the others are wrong: A is subjective with no threshold. B names a wish, not a behaviour. D is a technical design constraint, not a business requirement — and locking design choices this early removes options the team may need.

    Exam section: Requirements  ·  Concepts tested: Well-formed requirements, testability, specificity

28. 28. A stakeholder tells the BA: “We need a button on the Account page.” Which response best uncovers the underlying requirement?

    Correct answer: D — Ask what outcome the user is trying to achieve, how often they need it, and what happens today when they cannot do it

    Why it is correct: “A button” is a solution the stakeholder has already designed. Asking about the outcome, frequency, and current workaround recovers the actual need — which might be better served by a Flow, a related list, or a report the stakeholder did not know existed.

    Why the others are wrong: B and C accept the stated solution and refine its details. A bakes an unexamined solution into the backlog, where it becomes difficult to challenge later.

    Exam section: Requirements  ·  Concepts tested: Elicitation, the five whys, avoiding solution bias

29. 29. What distinguishes a functional requirement from a non-functional requirement?

    Correct answer: A — A functional requirement describes what the system must do; a non-functional requirement describes qualities or constraints such as performance, security, availability, and usability

    Why it is correct: The distinction matters because non-functional requirements are easy to omit and expensive to retrofit. A page that returns the right data but takes 30 seconds to load has met its functional requirement and failed the business.

    Why the others are wrong: B confuses the category with the implementation approach. C is a common and costly misconception. D reverses the correct sequence.

    Exam section: Requirements  ·  Concepts tested: Functional versus non-functional requirements

30. 30. In MoSCoW prioritisation, what does a “Should have” item mean?

    Correct answer: B — Important and painful to omit, but the release can still deliver value without it because a workaround exists

    Why it is correct: Should-have items are genuinely important but survivable for one release. Distinguishing them from Must-have is what gives the team a safe contingency buffer when a sprint comes under pressure.

    Why the others are wrong: A describes Must have. C describes Could have. D describes Won't have (this time).

    Exam section: Requirements  ·  Concepts tested: MoSCoW prioritisation, release scoping

31. 31. A defect found during user acceptance testing must be traced back to the business objective it was meant to satisfy. Which artifact enables this?

    Correct answer: C — A requirements traceability matrix linking business objectives to requirements, user stories, and test cases

    Why it is correct: A traceability matrix creates a documented chain in both directions: from objective down to test case, and from a failing test back up to the business need. It also exposes orphaned requirements that no test covers.

    Why the others are wrong: D records who changed which configuration setting and when — useful for auditing changes, but it holds no requirement lineage. A and B contain no linkage between business objectives and delivered functionality.

    Exam section: Requirements  ·  Concepts tested: Traceability matrix, requirement lineage

32. 32. Finance requires manager approval on any discount above 10 percent. Sales requires that renewal quotes proceed without any approval step. Both requirements are documented. What should the BA do first?

    Correct answer: D — Document both requirements, record the conflict and its dependency explicitly, and facilitate a decision with the accountable decision-maker, capturing the outcome and the rationale

    Why it is correct: Conflicting requirements are a business decision, not an analyst's decision. Making the conflict explicit and taking it to the accountable owner produces a defensible outcome and a recorded rationale that prevents the argument recurring after go-live.

    Why the others are wrong: C silently overrides a documented business need. A is a disproportionate architectural response to a policy disagreement. B delays a decision that will be no easier later.

    Exam section: Requirements  ·  Concepts tested: Conflicting requirements, dependency analysis, escalation

33. 33. Which is the strongest evidence that a requirement has been properly verified with the business before development begins?

    Correct answer: A — The requirement was played back to the stakeholders, they confirmed it in writing, and the acceptance criteria were agreed

    Why it is correct: Playback surfaces misunderstandings while they are still cheap to fix. Written confirmation plus agreed acceptance criteria means the business has stated in advance what “correct” looks like — the only reliable defence against “that's not what I asked for” at UAT.

    Why the others are wrong: D is unverified assumption. B reflects scheduling, not validation. C shows the topic was raised, not that the written requirement is accurate.

    Exam section: Requirements  ·  Concepts tested: Requirement validation, playback, sign-off

34. 34. Why should requirements be maintained in a single, version-controlled repository?

    Correct answer: B — To provide one source of truth with a change history, preventing scope disputes and stopping conflicting versions from circulating by email

    Why it is correct: Version control answers three questions that decide scope disputes: what was agreed, when it changed, and who approved the change. Without it, several conflicting spreadsheet versions circulate and every stakeholder believes theirs is current.

    Why the others are wrong: A, C, and D describe technical concerns unrelated to requirements management. Salesforce imposes no such deployment prerequisite.

    Exam section: Requirements  ·  Concepts tested: Requirements repository, version control, scope management

35. 35. A BA identifies a requirement that cannot be delivered until a third-party billing system releases a change scheduled for next quarter. How should this be handled?

    Correct answer: C — Record it as a documented dependency with a named owner and target date, assess the risk to the release plan, and raise it with the Product Owner for sequencing

    Why it is correct: External dependencies are among the most common causes of missed release dates. Naming an owner and a date makes the dependency trackable, and surfacing the risk lets the Product Owner sequence around it deliberately.

    Why the others are wrong: B leaves the risk invisible until it becomes a crisis. D creates undocumented technical debt and hides a material risk. A discards a valid business need instead of scheduling it.

    Exam section: Requirements  ·  Concepts tested: Dependency management, risk identification, release planning

36. 36. Which format is the standard structure of a user story?

    Correct answer: D — As a <role>, I want <capability>, so that <benefit>.

    Why it is correct: The three clauses carry the persona, the capability, and — most importantly — the benefit. The “so that” clause is what lets the Product Owner judge value and lets the team suggest a cheaper way to achieve the same outcome.

    Why the others are wrong: A is Gherkin syntax, used for acceptance criteria rather than the story statement itself. B is traditional specification style. C is pseudocode for a business rule.

    Exam section: User Stories  ·  Concepts tested: User story format, personas, value statement

37. 37. A story covers making Close Date mandatory before an Opportunity can be saved in the Negotiation stage. Which is the best acceptance criterion?

    Correct answer: A — Given an Opportunity in the Negotiation stage, when the user saves the record without a Close Date, then an error is displayed and the record is not saved.

    Why it is correct: It follows Given/When/Then, states one precondition, one action, and one observable result. A tester can execute it without asking a single clarifying question.

    Why the others are wrong: D is subjective and untestable. B prescribes the implementation instead of the expected behaviour. C is a task, not a criterion.

    Exam section: User Stories  ·  Concepts tested: Acceptance criteria, Given/When/Then, testability

38. 38. In the INVEST model for user stories, what does the “S” stand for and why does it matter?

    Correct answer: B — Small — the story should be completable within a single sprint, which improves estimation accuracy and keeps work flowing

    Why it is correct: Large stories hide complexity, are estimated badly, and block the sprint when they overrun. Small stories are easier to estimate, easier to test, and deliver visible progress sooner.

    Why the others are wrong: A contradicts INVEST's Negotiable principle, which deliberately leaves implementation detail open. C directly contradicts Negotiable. D is a prioritisation practice, not part of INVEST.

    Exam section: User Stories  ·  Concepts tested: INVEST criteria, story sizing

39. 39. A backlog item reads: “As an admin, I want the org to be improved so that users are happier.” Which INVEST criteria does it most clearly fail?

    Correct answer: C — Valuable and Testable — it has no measurable outcome and no criterion that could prove it was delivered

    Why it is correct: “Improved” and “happier” cannot be tested, so no one can ever declare the story done. Nor does it identify a specific business value, since the benefit clause is a generic sentiment rather than an outcome. It also fails Estimable as a direct consequence.

    Why the others are wrong: B is not the clearest failure — the story's size cannot even be judged. A and D each name a single criterion while ignoring the more fundamental problem that the story cannot be verified at all.

    Exam section: User Stories  ·  Concepts tested: INVEST assessment, story quality review

40. 40. What is the purpose of an epic in a Salesforce product backlog?

    Correct answer: D — A large body of work representing a business capability, decomposed into multiple related user stories delivered over several sprints

    Why it is correct: Epics let the backlog hold both altitudes at once: leadership can see and prioritise whole capabilities such as “Renewals Automation,” while the delivery team works from small, sprint-sized stories underneath.

    Why the others are wrong: C describes a defect. A describes acceptance criteria. B describes a deployment artifact such as a change set or package.

    Exam section: User Stories  ·  Concepts tested: Epics, backlog hierarchy, decomposition

41. 41. During backlog refinement the team cannot estimate a story because the behaviour of an external integration is unknown. What should happen?

    Correct answer: A — Create a time-boxed spike to investigate the unknown, then re-estimate the story with what was learned

    Why it is correct: A spike is a deliberately time-boxed research task whose output is knowledge rather than working functionality. It converts an unknown into an informed estimate without gambling a sprint commitment on guesswork.

    Why the others are wrong: D commits the team to work it does not understand, the most common cause of a failed sprint. B discards a valid need. C asks someone with no delivery knowledge to size technical work.

    Exam section: User Stories  ·  Concepts tested: Spikes, estimation, managing uncertainty

42. 42. How does a team's Definition of Done differ from a story's acceptance criteria?

    Correct answer: B — Acceptance criteria are conditions specific to one story; the Definition of Done is a team-wide standard — built, peer reviewed, tested, documented, deployed to the test environment — applied to every story

    Why it is correct: Acceptance criteria answer “did we build the right thing for this story?” The Definition of Done answers “did we build it to our agreed standard?” A story needs both before it can be considered complete.

    Why the others are wrong: A collapses two genuinely different concepts. C describes acceptance criteria, not a team standard. D reverses the two scopes.

    Exam section: User Stories  ·  Concepts tested: Definition of Done, acceptance criteria, quality standards

43. 43. A single story carries 14 acceptance criteria spanning three different personas and two separate workflows. What is the most likely correct action?

    Correct answer: C — Split the story by persona or by workflow so each resulting story is small, independently valuable, and testable

    Why it is correct: Three personas and two workflows are a clear signal that several distinct needs have been bundled together. Splitting them allows independent prioritisation, independent testing, and partial delivery if the sprint comes under pressure.

    Why the others are wrong: B confuses volume with quality; the story violates both Small and Independent. D swaps one artifact for another without addressing the size problem. A defers the issue rather than resolving it.

    Exam section: User Stories  ·  Concepts tested: Story splitting, INVEST, backlog refinement

44. 44. Who is primarily accountable for accepting a completed user story as meeting the business need?

    Correct answer: D — The Product Owner or designated business decision-maker, usually supported by the BA's verification against the acceptance criteria

    Why it is correct: Acceptance is a business judgement about value delivered, so it belongs with the person accountable for the product. The BA supports that decision by confirming each acceptance criterion has been demonstrably met.

    Why the others are wrong: C cannot objectively accept their own work. A and B hold technical responsibilities that do not include judging business value.

    Exam section: User Stories  ·  Concepts tested: Story acceptance, Product Owner accountability

45. 45. What is the primary objective of User Acceptance Testing?

    Correct answer: A — To confirm that business users can complete their real-world processes end to end in the delivered solution and that it satisfies the agreed acceptance criteria

    Why it is correct: UAT is the business's own verification, run by the people who will live with the solution. It tests whole processes rather than isolated components, which is why it catches gaps that unit and system testing cannot.

    Why the others are wrong: D is a developer responsibility enforced at deployment. B is performance testing. C is a release management check.

    Exam section: User Acceptance  ·  Concepts tested: UAT purpose, business verification

46. 46. Which environment is most appropriate for running UAT on a Salesforce release that requires representative data volumes and realistic business scenarios?

    Correct answer: B — A Full or Partial Copy sandbox seeded with production-like data

    Why it is correct: Full and Partial Copy sandboxes include records copied from production, so testers exercise the solution against realistic data shapes, volumes, and edge cases — the conditions under which most defects actually surface.

    Why the others are wrong: A and D provide metadata but essentially no data, so realistic scenarios cannot be run. C risks corrupting live business data and is not an acceptable UAT environment.

    Exam section: User Acceptance  ·  Concepts tested: Sandbox types, test data strategy, UAT environments

47. 47. A UAT tester reports only that “it doesn't work.” What should the BA do first?

    Correct answer: C — Work with the tester to capture the exact steps taken, the expected result versus the actual result, the user profile, the affected record, and any screenshots, so the issue can be reproduced and triaged

    Why it is correct: A defect that cannot be reproduced cannot be fixed or verified. Capturing steps, expected versus actual behaviour, and the user context also frequently reveals that the real cause is a permissions issue or a training gap rather than a code defect.

    Why the others are wrong: B assigns a severity with no evidence and distorts the defect queue. D dismisses a potentially real problem. A wastes developer time on speculation.

    Exam section: User Acceptance  ·  Concepts tested: Defect triage, reproduction steps, UAT support

48. 48. During UAT, a business user requests a capability that was never in scope and was not part of any acceptance criterion. How should the BA classify it?

    Correct answer: D — As a change request or new backlog item, assessed for impact and prioritised — it is not a defect, because the delivered solution matches the agreed acceptance criteria

    Why it is correct: A defect is a failure to meet an agreed criterion. A request for something never agreed is new scope. Classifying it correctly protects the release date while ensuring the idea is captured rather than lost.

    Why the others are wrong: C mislabels new scope as failure and distorts quality metrics. A surrenders scope control at the most expensive moment. B dismisses a possibly valid business need as a user misunderstanding.

    Exam section: User Acceptance  ·  Concepts tested: Defect versus change request, scope control during UAT

49. 49. A BA notices that end users have not been engaged since the project kickoff three sprints ago, although the Product Owner has attended every review. What is the most significant risk?

    Correct answer: A — The solution may satisfy every documented requirement yet fail in adoption because it does not match how users actually work

    Why it is correct: Product Owners represent business value but rarely perform the day-to-day task. Without regular exposure to the people who will use the solution, teams build something that is technically correct and practically unusable — and adoption failure is only discovered at UAT or go-live, when change is most expensive.

    Why the others are wrong: B, C, and D are unrelated technical or delivery metrics that end-user engagement does not influence.

    Exam section: User Acceptance  ·  Concepts tested: User engagement, adoption risk, feedback loops

50. 50. Which is the strongest indicator that UAT is complete and the release can proceed?

    Correct answer: B — All planned test scripts have been executed, every remaining defect has been triaged with an agreed severity and disposition, and formal sign-off has been recorded by the accountable business stakeholder

    Why it is correct: Exit criteria must be objective: coverage is demonstrated by executed scripts, risk is understood because open defects carry an agreed severity and decision, and accountability is explicit through recorded sign-off.

    Why the others are wrong: C is a personal opinion with no evidence. D confuses a calendar boundary with a quality gate. A may equally mean testers stopped testing, and says nothing about defects already open.

    Exam section: User Acceptance  ·  Concepts tested: UAT exit criteria, sign-off, defect disposition

How to Prepare for the Salesforce Business Analyst Exam

Know what the exam is really testing

Salesforce states that this credential is aimed at candidates with roughly two years of business analysis experience and two years working on the Salesforce Platform. In practice that means questions are written as short workplace scenarios where several options look defensible and one reflects sound analysis practice. Candidates who study feature lists rather than practice tend to struggle.

Answer from the analyst's chair

A recurring pattern in this exam is that the correct answer keeps the decision with the person accountable for it. Options where the analyst unilaterally decides, quietly implements, or refuses to engage are usually wrong. Options that clarify, document, facilitate, and route the decision correctly are usually right.

Practise the vocabulary precisely

Several sections turn on precise definitions: Responsible versus Accountable versus Consulted in a RACI, Must have versus Should have in MoSCoW, acceptance criteria versus Definition of Done, and defect versus change request. These distinctions are worth memorising because they are easy marks.

Use the official material alongside practice tests

Work through the official Trailhead certification preparation module and the Business Analyst trailmix, then use practice tests like this one to find gaps. When you get a question wrong here, note the exam section listed in the answer key and go back to that unit rather than re-reading everything.

Continue Your Business Analyst Preparation

Business analysts are usually expected to hold the Administrator credential as well, and many Salesforce BA roles overlap with functional consulting. These related practice resources are a natural next step.