New to Salesforce? Our Salesforce Administrator exam prep is the recommended first step, it builds the platform knowledge BAs need. See our certification path to understand where Business Analyst fits in your career. Below you'll find exam weightage, key concepts, and practice questions.
Free practice • No sign-up required
Independent study resource
Exam objectives and policies can change. Confirm current details with the certification issuer.
Check current objectives
Use the official exam guide as the source for current objectives and section weights.
Practice for learning
Use sample questions to review concepts and identify topics for further study.
Works on Any Device
Full practice experience on phone, tablet, or desktop
Free, No Sign-Up
Start practicing immediately, no account or email required
Salesforce Business Analyst Certification: Free Practice Exam & Study Guide (2026)
This exam covers the business analyst's work on Salesforce projects: discovering and documenting requirements, writing user stories, mapping processes, managing stakeholders and supporting testing and adoption. The exam is 60 scored questions in 105 minutes, with a 72% pass mark, weighted towards Collaboration with Stakeholders (23%) and Requirements (18%).
Recommended Prerequisites
We recommend completing this certification first to prepare you better.
| Official exam name and code | Salesforce Certified Business Analyst (Business Analyst) |
|---|---|
| Questions | 60 |
| Time allotted | 105 min |
| Passing score | 72% |
| Exam fee | $200 |
| Retake fee | $100 |
| Prerequisite certifications | Recommended preparation: Salesforce Certified Platform Administrator |
| Study guide release | Summer '26 |
Salesforce Certified Business Analyst Exam Weightage by Section
1. Customer Discovery (17%)
17%2. Collaboration with Stakeholders (23%)
23%3. Business Process Mapping (12%)
12%4. Requirements (18%)
18%5. User Stories (18%)
18%6. Development Support and User Acceptance (12%)
12%Exam Topics
Last updated:
Who is the Salesforce Business Analyst exam for?
- Business analysts: You gather requirements on Salesforce projects and want the credential that names the role.
- Admins expanding their role: You already configure Salesforce and are being asked to run discovery and write user stories.
- Project managers: You run Salesforce delivery and want to understand what good requirements look like.
Exam Fees & Registration
Exam Fee
$200
One-time registration fee
Retake Fee
$100
If you need to retake the exam
Comparing certs? View all Salesforce exam fees in one place →
Certification Validity
Maintenance and renewal requirements vary. Check the issuer’s current credential page for requirements that apply to you.
How to Register
Check current Salesforce Certified Business Analyst credential and registration details with the issuer.
View official credential detailsOfficial references: Use the issuer’s current materials to confirm exam objectives, format, and fees before booking.
Official sources: Exam guide·Salesforce exam pricing·Independent exam-prep resource; details may change.
Exam Tips
- 1Requirements and Solution Design are 50%. Practice discovery and documentation.
- 2Know stakeholder collaboration and how to translate business needs into Salesforce.
- 3Understand success metrics and analytics for solution validation.
- 4Be ready for “how would you gather requirements?” and “what would you recommend?”
Prerequisites
- •Business analysis or product experience
- •Salesforce basics
Focus Areas
- •Requirements and Discovery
- •Stakeholder Collaboration
- •Solution Design
- •Analytics
Study Strategy
Think like a BA: discovery, documentation, and recommendation.
Practice writing user stories and mapping them to Salesforce features.
Review the exam outline for deliverables.
Exam Format and First-Attempt Readiness
The Salesforce Certified Business Analyst exam has 60 questions in 105 min, passing score 72%. Most Salesforce exams test scenario-based decisions. Focus on when to use each feature, not just terms.
- Study Collaboration with Stakeholders and Requirements first, together they carry 41% of the exam.
- Do timed question sets. Build pacing and confidence.
- Review why wrong answers are wrong. It improves scenario reasoning.
- Book the exam once your mock scores are steady at 85%+.
Is the Business Analyst Exam Hard?
Is the Business Analyst Exam Hard?
It is a moderate exam with an unusually high pass mark. Roughly half of it is business analysis method, such as running discovery and writing user stories, and half is Salesforce knowledge, such as knowing what the platform can do before you promise it.
- 60 multiple-choice questions in 105 minutes.
- 72% to pass, about 44 correct answers out of 60. That is higher than most consultant exams, so there is little room for error. Confirm it in the official exam guide before you book.
- Method as well as product. Elicitation techniques, process mapping and user stories carry real weight.
- Salesforce judgement. You need to know when configuration will do and when something needs building.
Pass Rate Guidance
You are ready when you can run a discovery session in your head: who you would talk to, which technique you would use, what you would produce, and how you would get it agreed. Aim for 85% or more on practice tests, given the 72% bar.
Business Analyst Exam Format Explained
Business Analyst Exam Format Explained
You can take the exam online with a proctor or at a test centre. Here is what to expect:
Total Questions
60 scored questions
Time Limit
105 min
Passing Score
72%
Question Type
Multiple-choice & multiple-select
How Many Questions Are Scenario-Based?
Most questions describe a moment in a project, such as stakeholders who disagree or a requirement that keeps changing, and ask what the analyst should do next.
Best Way to Pass on Your First Attempt
- Know which technique fits which situation: Interviews, workshops, observation, surveys and document analysis each suit different problems.
- Write user stories properly: Role, goal and benefit, with acceptance criteria that can actually be tested.
- Map processes before solutions: Current state first, then future state, with the gaps named.
- Learn the Salesforce limits that matter: Enough to know when a requirement is cheap, expensive or impossible.
Business Analyst: Key Concepts
Discovery and Elicitation
Requirements have to be drawn out, not collected. Interviews suit depth with one person and sensitive topics. Workshops suit getting a group to agree, and are efficient when decisions need several people in the room. Observation, watching someone do the job, catches the steps people forget to mention. Surveys reach many people for simple questions but cannot probe. Document analysis and reviewing the existing system show what is really happening today. Choose by what you need: depth, agreement, breadth or evidence. Prepare questions in advance, record decisions, and send back what you heard so people can correct it.
User Stories and Acceptance Criteria
A user story names the role, the goal and the benefit: as a sales rep, I want to see a customer's open cases on the opportunity, so that I know about problems before a renewal call. The benefit matters because it is what gets the story prioritised or dropped. Acceptance criteria say how you will know it works, in terms a tester can check. Good stories are small enough to build in one iteration, independent of each other where possible, and negotiable in how they are implemented. A story that describes a screen layout rather than a need has usually jumped to a solution too early.
Stakeholders and Getting Decisions Made
Projects stall on people, not features. Map stakeholders by how much influence they hold and how much interest they have, and plan how often to involve each group. Name a decision-maker for each area before you need one, so disagreements have somewhere to go. When stakeholders want different things. Take it back to the business goal and the evidence from discovery rather than seniority. Keep a RAID style record of risks, assumptions, issues and dependencies, and make assumptions explicit, because an unspoken assumption is the usual cause of a late surprise.
Process Mapping and Gap Analysis
Map the current state before designing anything, because the described process and the real one usually differ. Then map the future state, and the difference between them is your gap analysis, which becomes the backlog. Keep maps at a level people can read: swimlanes showing who does what are usually enough. Note where work leaves Salesforce for email or spreadsheets, since those are where errors and delays live. A map also protects you later, when someone asks why a step was removed.
Requirements, Testing and Adoption
Separate functional requirements, what the system must do, from non-functional ones such as performance, security, accessibility and volume, which are easy to forget and expensive to retrofit. Keep traceability from a business need through to the story and the test, so you can show that each requirement was delivered. Plan user acceptance testing with real users against the acceptance criteria, not a demo given by the project team. Then plan adoption: training, communication and a measure of whether people are actually using it, because an unused solution has not solved the problem.
Every BA exam scenario maps to one of five stages. A Requirements Traceability Matrix ties each stage’s artifacts back to the original business requirement, so nothing is built, or tested, that wasn’t asked for.
How to Pass the Salesforce Business Analyst Exam
Most questions ask what the analyst should do next. The right answer usually moves toward better understanding or a recorded agreement, rather than jumping to build something.
Choosing an Elicitation Technique
Depth and sensitivity: interview. Agreement across a group: workshop. What people actually do: observation. Breadth on simple questions: survey.
User Stories
Role, goal, benefit, plus acceptance criteria a tester can check. If it describes a screen rather than a need, it is a solution in disguise.
Process Mapping
Current state first, then future state, then the gap. Swimlanes show who does what, and where work leaves the system.
Testing
User acceptance testing is run by users against the acceptance criteria. A project-team demo is not UAT.
Stakeholders
Map influence against interest, name decision-makers early, and settle disagreements with the business goal and discovery evidence.
Is the Salesforce Certified Business Analyst Exam Hard?
DifficultyModerate; plan about 4-8 weeks of focused prep.
Book When ReadyScore 85%+ on three timed mocks before scheduling.
Use Practice, Not DumpsOriginal practice questions build skill without risking your credential.
Exam format: 60 questions, 105 min, 72% passing score.
Salesforce Certified Business Analyst Practice Questions (With Explanations)
Test your knowledge with these 15 sample questions.
Question 1: What is the primary focus of a Certified Business Analyst in Salesforce projects?
Key takeaway: Certified Business Analysts understand business needs, capture requirements, and collaborate with stakeholders to develop Salesforce solutions that drive business improvements.
Show correct answer and explanation
Correct answer: A. Understanding business needs, capturing requirements, and collaborating with stakeholders
Certified Business Analysts understand business needs, capture requirements, and collaborate with stakeholders to develop Salesforce solutions that drive business improvements.
- Writing Apex code is a developer task, not the Business Analyst's core requirements-focused role.
- Designing email campaigns is a Marketing function, unrelated to business analysis.
- Managing server infrastructure is an IT operations task, unrelated to business analysis.
Question 2: Which technique is commonly used to discover and document business requirements?
Key takeaway: Stakeholder interviews and workshops are standard techniques for discovering and documenting business requirements.
Show correct answer and explanation
Correct answer: D. Stakeholder interviews and workshops
Stakeholder interviews and workshops are standard techniques for discovering and documenting business requirements.
- Deployment scripts are a technical release artifact, not a requirements-discovery technique.
- API development is a technical implementation task, not a requirements-discovery technique.
- Unit testing is a developer QA activity, not a requirements-discovery technique.
Question 3: What deliverable does a Business Analyst typically produce before development begins?
Key takeaway: Business Analysts produce requirements documents and user stories to guide solution development.
Show correct answer and explanation
Correct answer: A. Requirements document and user stories
Business Analysts produce requirements documents and user stories to guide solution development.
- Test classes are a developer QA artifact, not the BA's pre-development deliverable.
- Integration code is a technical implementation artifact, not the BA's pre-development deliverable.
- A deployed package is a technical release artifact, not the BA's pre-development deliverable.
Question 4: How should a Business Analyst prioritize requirements when conflicts exist?
Key takeaway: Prioritization should align with business objectives and involve stakeholder agreement.
Show correct answer and explanation
Correct answer: B. Align with business objectives and stakeholder agreement
Prioritization should align with business objectives and involve stakeholder agreement.
- Deferring all decisions to IT abdicates the BA's role in facilitating stakeholder alignment.
- Always choosing the technical option ignores stakeholder needs and business objectives entirely.
- Choosing the cheapest option ignores business objectives and stakeholder needs, which should drive prioritization.
Question 5: Which Salesforce artifact helps translate business requirements into implementable features?
Key takeaway: User stories and acceptance criteria translate business requirements into clear, implementable features for the team.
Show correct answer and explanation
Correct answer: B. User stories and acceptance criteria
User stories and acceptance criteria translate business requirements into clear, implementable features for the team.
- A deployment checklist is a release-management artifact, not a requirements-translation artifact.
- Process Builder is a legacy automation tool, not a requirements-translation artifact.
- A debug log is a technical troubleshooting artifact, unrelated to translating requirements into features.
Question 6: What is the standard format for writing a user story in Agile projects?
Key takeaway: The standard user story format is "As a [role], I want [goal] so that [benefit].
Show correct answer and explanation
Correct answer: A. "As a [role], I want [goal] so that [benefit]"
The standard user story format is "As a [role], I want [goal] so that [benefit]." This keeps focus on who needs the feature, what they need, and why, anchoring development decisions to real user outcomes.
- '[Actor] performs [action]...' isn't the standard Agile user story format, that's 'As a [role], I want [goal] so that [benefit]'.
- 'Given/when/then' describes a Gherkin/BDD acceptance-criteria format, not the standard user story format itself.
- 'The system shall...' is a traditional requirements-statement format, not the Agile user story format.
Question 7: What is the purpose of Acceptance Criteria in a user story?
Key takeaway: Acceptance Criteria are the pass/fail conditions for a user story, they define exactly what the product owner will test to confirm the story is complete.
Show correct answer and explanation
Correct answer: A. To define the specific conditions that must be met for the story to be considered done by the product owner
Acceptance Criteria are the pass/fail conditions for a user story, they define exactly what the product owner will test to confirm the story is complete. Without clear acceptance criteria, teams risk rework due to ambiguous definitions of done.
- Acceptance criteria don't describe technical implementation, that's a separate development concern.
- Acceptance criteria aren't about listing dependencies/risks, that's separate project documentation.
- Acceptance criteria aren't about performance benchmarks, that's a non-functional requirement, not what acceptance criteria define.
Question 8: A Business Analyst is documenting the current workflow of a business process before designing a new solution. What is this activity called?
Key takeaway: As-Is process analysis captures the current state of a business process to identify inefficiencies, pain points, and gaps before designing a To-Be (future state) solution, preventing the team from automating broken processes.
Show correct answer and explanation
Correct answer: B. As-Is process analysis (current state analysis)
As-Is process analysis captures the current state of a business process to identify inefficiencies, pain points, and gaps before designing a To-Be (future state) solution, preventing the team from automating broken processes.
- Solution validation confirms the built solution meets needs, it isn't the current-state documentation activity being described.
- Stakeholder mapping identifies stakeholder influence, it isn't about documenting current-state workflows.
- Requirements traceability links requirements to test cases, it isn't about documenting current-state workflows.
Question 9: Which technique helps a Business Analyst understand the relative importance of stakeholders and their influence on a project?
Key takeaway: The Power/Interest Grid plots stakeholders by their influence (power) and interest in the project, guiding the BA on how to engage each group: manage closely, keep satisfied, keep informed, or monitor.
Show correct answer and explanation
Correct answer: C. Stakeholder Analysis using a Power/Interest Grid
The Power/Interest Grid plots stakeholders by their influence (power) and interest in the project, guiding the BA on how to engage each group: manage closely, keep satisfied, keep informed, or monitor.
- Process Decomposition breaks down processes into steps, not stakeholder influence.
- Gap Analysis identifies shortfalls between current and desired state, not stakeholder influence specifically.
- User Story Mapping visualizes story sequencing, not stakeholder influence specifically.
Question 10: What is the purpose of a Requirements Traceability Matrix on a Salesforce project?
Key takeaway: A Traceability Matrix ensures end-to-end coverage: every business requirement maps to at least one user story, and every user story maps to test cases.
Show correct answer and explanation
Correct answer: D. To link each business requirement to specific user stories, features, and test cases, ensuring all requirements are addressed and tested
A Traceability Matrix ensures end-to-end coverage: every business requirement maps to at least one user story, and every user story maps to test cases. It prevents requirements from being missed during development or testing.
- A traceability matrix isn't about mapping database tables, that's a data architecture concern.
- Documenting role/permission hierarchy is a security configuration concern, not what a traceability matrix does.
- Tracking deployment history across sandboxes is a release-management concern, not what a traceability matrix does.
Question 11: A project team discovers the solution being built does not address several original business requirements. Which BA technique identifies this type of shortfall?
Key takeaway: Gap Analysis compares the current state (or planned solution) against the desired future state, identifying gaps where requirements are not addressed.
Show correct answer and explanation
Correct answer: C. Gap Analysis
Gap Analysis compares the current state (or planned solution) against the desired future state, identifying gaps where requirements are not addressed. It is typically performed during discovery and at key review points.
- A Process Flow Diagram visualizes process steps, not specifically the requirement-to-solution shortfall being described.
- A Risk Register tracks project risks generally, not specifically requirement-to-solution shortfalls.
- A RACI Chart defines roles and responsibilities, not requirement shortfalls.
Question 12: Which type of requirement describes system performance, security, usability, or scalability expectations rather than specific functionality?
Key takeaway: Non-Functional Requirements (NFRs) define quality attributes, how the system performs rather than what it does.
Show correct answer and explanation
Correct answer: C. Non-Functional Requirements
Non-Functional Requirements (NFRs) define quality attributes, how the system performs rather than what it does. Examples: page load times, concurrent user capacity, data security standards. They are often overlooked but critical for solution success.
- Functional Requirements describe specific features/functionality, not performance/security/usability characteristics.
- Technical Specifications describe implementation details, not the broader quality-attribute category being asked about.
- Business Requirements describe high-level business needs, not the specific technical quality attributes described.
Question 13: During a discovery workshop, stakeholders from two business units give conflicting requirements for the same field. What is the BA's best first action?
Key takeaway: Conflicting requirements should be documented and resolved through structured stakeholder facilitation, not unilaterally decided by the BA.
Show correct answer and explanation
Correct answer: D. Document both versions and facilitate a follow-up session to align stakeholders on a single agreed requirement
Conflicting requirements should be documented and resolved through structured stakeholder facilitation, not unilaterally decided by the BA. A dedicated alignment session surfaces the business rationale behind each request and builds consensus.
- Implementing the senior stakeholder's version without alignment risks alienating the other business unit and doesn't resolve the underlying conflict.
- Escalating immediately to the project manager skips the BA's own facilitation role in resolving stakeholder conflicts.
- Choosing the simpler option ignores the actual business needs driving each stakeholder's requirement.
Question 14: What does the DACI framework define in Salesforce project governance?
Key takeaway: DACI (Driver, Approver, Contributor, Informed) clarifies who is responsible for driving a decision to closure, who has final approval authority, who contributes expertise, and who only needs to be informed of the outcome.
Show correct answer and explanation
Correct answer: C. Decision-making roles: Driver (owns the process), Approver (final decision), Contributor (provides input), and Informed (kept updated)
DACI (Driver, Approver, Contributor, Informed) clarifies who is responsible for driving a decision to closure, who has final approval authority, who contributes expertise, and who only needs to be informed of the outcome.
- DACI isn't about deployment steps, that's a release-management concern, not a decision-making framework.
- DACI isn't about automation logic, that's a technical implementation concern, not a governance framework.
- DACI isn't about data architecture, that's an unrelated technical concept.
Question 15: What format do user stories typically follow in Salesforce projects?
Key takeaway: User stories follow the format: As a [role], I want [goal] so that [benefit].
Show correct answer and explanation
Correct answer: B. As a [role], I want [goal] so that [benefit]
User stories follow the format: As a [role], I want [goal] so that [benefit]. This connects the user, the capability, and the business value.
- 'As a [user], I need [permission]...' isn't the standard user story format, the standard format centers on role/goal/benefit.
- 'As a [admin], I need [field]...' isn't the standard user story format, it's overly specific to one scenario.
- 'As a [system]...' misrepresents the format, which centers on a human role/persona, not a system.
Get the Full Question Bank
Most candidates book the exam after scoring 85%+ on full mocks.
If you’re planning to test this quarter, aim to complete full mocks at least 10–14 days before your exam date.
Contact us for more information on our full 60-question mock exams and a personalized study plan. Use the contact form.
Request Mock Exams & Study PlanSalesforce Certified Business Analyst Exam FAQs
- What is covered on the Salesforce Certified Business Analyst exam?
- This page shows the section-wise exam weightage so you know exactly which topics carry the most weight. Use the exam topics and practice questions above to align your study with the official outline.
- What does a Salesforce Business Analyst do?
- Salesforce Business Analysts gather requirements, analyze business processes, design Salesforce solutions, and bridge the gap between business stakeholders and technical teams.
- Do I need technical experience for Business Analyst certification?
- No, Business Analyst focuses on business analysis skills rather than technical implementation. However, understanding Salesforce capabilities is essential.
- What is the Business Analyst passing score and exam fee in Summer '26?
- The Salesforce Business Analyst exam has 60 multiple-choice questions, 105 minutes, and a passing score of 72%. The exam fee is $200 USD (retake $100 USD). There is no formal prerequisite, though Salesforce recommends admin experience.
- What are the main topic areas in the Salesforce Business Analyst exam?
- The main sections are: Collaboration with Stakeholders (25%), Customer Discovery (17%), Business Analysis Planning (15%), and User Stories (18%). These four areas account for 75% of the exam. Focus on user story formats (As a... I want... So that...), acceptance criteria, process mapping, and eliciting requirements from stakeholders.
Next Consultant Certifications
Good next steps after Business Analyst:
Honest Cert Breakdown
Difficulty: Moderate
3/5Requirements gathering, user stories, process mapping, and stakeholder management. Good for non-technical Salesforce professionals building toward consulting.
Salary Range
$80,000–$110,000 / year
US average for certified professionals • Updated Summer '26 • Source: Salesforce Talent Ecosystem
Is it worth it?
Underrated cert for career switchers and BA-to-consultant paths. Not a top salary driver on its own but pairs well with a functional cert.
Exam Sections & Weightings
What Each Section Tests
Collaboration with Stakeholders
Facilitation techniques, workshops, interviews, observation, surveys. Managing conflicting requirements, building consensus, and communicating with executives vs end users.
Business Analysis Planning
Defining the BA approach, planning deliverables, estimating effort, and setting success metrics. Understanding project governance, roles, and agile vs waterfall BA activities.
Needs Assessment
Identifying business problems and opportunities, defining as-is vs to-be state, root cause analysis, solution scoping, and building a business case for Salesforce investment.
Customer Discovery
Uncovering stakeholder needs through empathy mapping, discovery sessions, and user story mapping. Documenting personas and journeys in a Salesforce context.
Analysis
Decomposing requirements into user stories, acceptance criteria, and process flows. Prioritisation techniques (MoSCoW, story points) and Salesforce backlog management.
Traceability & Monitoring
Maintaining requirements traceability matrices, tracking requirements through delivery sprints, and measuring solution performance post-deployment.
Solution Evaluation
Assessing solution value after go-live, measuring adoption metrics, identifying gaps, and recommending iterative improvements.
8-Week Study Plan
Scenario Strategy Tips
- 1.Choose the right elicitation technique: Use interviews for deep-dive stakeholder insights, workshops for consensus-building across groups, surveys for large audiences, and observation for understanding current workflows. The exam will present a scenario and ask which technique to use first.
- 2.Always start with as-is before to-be: When requirements are unclear, good BAs document the current state before designing future solutions. Exam scenarios testing Needs Assessment often hinge on this sequencing.
- 3.User stories follow the standard format: As a [role], I want [feature] so that [benefit]. Acceptance criteria must be measurable. Watch for exam options with missing “so that” components.
- 4.Traceability is bidirectional: Requirements trace forward to test cases and backward to business goals. If a change request arrives, always trace its impact on existing requirements and test plans.
Mock Exam Benchmark
Aim for 85%+ on practice exams before scheduling your real exam. The Business Analyst exam is scenario-heavy, if you can correctly identify the right BA technique in a given situation, you are ready. Focus extra time on Collaboration with Stakeholders (21%) and Business Analysis Planning (18%) as these carry the most weight.
Top 10 Concepts to Review
- Elicitation techniques: interviews, workshops, surveys, observation, when to use each
- User story format and acceptance criteria writing
- MoSCoW prioritisation and story point estimation
- As-is vs to-be process mapping and gap analysis
- Requirements traceability matrix (RTM) structure and maintenance
- Agile BA vs waterfall BA activities and deliverables
- Root cause analysis techniques (5 Whys, fishbone diagram)
- Stakeholder identification, analysis, and communication planning
- Business case components: problem statement, solution options, cost-benefit
- Adoption metrics and post-implementation solution evaluation
Frequently Asked Questions
- What is the Salesforce Business Analyst certification?
- The Salesforce Business Analyst (SBA) certification validates skills in gathering requirements, facilitating stakeholder workshops, writing user stories, and translating business needs into Salesforce solutions. It targets professionals who bridge the gap between business stakeholders and Salesforce implementation teams. The exam has 60 questions, a 105-minute time limit, 72% passing score, and a $200 fee.
- Is ADM-201 required before the Business Analyst exam?
- ADM-201 is not a formal prerequisite, but Salesforce strongly recommends it. The Business Analyst exam tests scenario-based Salesforce knowledge, understanding objects, automation, reporting, and the data model. Candidates without ADM-201 knowledge struggle with the Analysis and Solution Evaluation sections where Salesforce features are referenced directly.
- How long should I study for the Business Analyst certification?
- Most candidates spend 6–10 weeks preparing, averaging 8–12 hours per week. The exam heavily favours scenario-based thinking over feature memorisation, practising stakeholder scenarios, writing user stories, and tracing requirements through delivery is more effective than rote study. Candidates with prior BA experience often prepare in 4–6 weeks.
- What is the hardest section of the Business Analyst exam?
- Collaboration with Stakeholders (23%) and Business Analysis Planning (18%) are typically the hardest sections. They test nuanced facilitation skills, choosing the right elicitation technique for a given scenario (interview vs workshop vs survey) and planning BA activities across project types (agile, waterfall, hybrid).
- What resources are best for the Business Analyst exam?
- Salesforce provides the official Study Guide, the Business Analyst Trailmix, and the Business Analyst Superbadge on Trailhead. The study guide lists all seven exam sections with recommended Trailhead modules. Trailblaze Prep free practice questions cover all seven sections with scenario-based questions that mirror the actual exam format.
Topic Difficulty Heatmap
Which topics are a gimme vs which ones trap confident candidates. Use this to prioritise your final-week revision. These are our own topic groupings for study planning, not the official exam sections, those and their weightings are in the credential's exam guide.
| Topic | Difficulty | Study Tip |
|---|---|---|
| Requirements and Discovery | Hard | Stakeholder interviews vs workshops vs document analysis. Know when each technique is appropriate. |
| Stakeholder Collaboration | Moderate | Communication plans and change management appear in scenario questions, prioritise clarity. |
| Solution Design and Documentation | Trap ⚠ | User stories vs use cases vs requirements: exam often tests the right deliverable for the context. |
| Analytics and Success Metrics | Moderate | KPIs and success criteria definition, align with business objectives in scenario answers. |
| Salesforce Capabilities | Easy | Knowing which Salesforce feature maps to a requirement is factual, revise standard objects and clouds. |
Difficulty based on analysis of common candidate errors across each exam section.
Ready to Practice?
Test yourself with free Business Analyst practice questions covering all 7 exam sections.
Start Free Practice QuestionsQuick Answer: What the BA Exam Actually Tests
- BA methodology: Discovery workshops, requirements gathering, stakeholder management, and translating business needs into user stories with acceptance criteria.
- Collaboration skills: How to run effective meetings, manage competing stakeholder priorities, and drive consensus on requirements.
- Salesforce platform knowledge: Knowing which Salesforce features can meet specific business requirements, and how to document those decisions.
Highest-Weight Exam Sections
Stakeholder Collaboration + Customer Discovery + User Stories = 57%. Focus here first.
Scenario Strategy: How to Approach BA Questions
BA exam questions describe a business situation and ask what a Business Analyst should do next. The correct answer follows the BA methodology, discovery before solutioning, stakeholders before systems.
- When stakeholder conflict appears: facilitate, document, and escalate, never unilaterally choose a stakeholder’s preference.
- For user story questions: valid user stories follow "As a [role], I want [feature], so that [benefit]" with measurable acceptance criteria.
- Note the 72% passing threshold; it is higher than most Salesforce exams. You need stronger preparation than for Administrator-track certs.
Mock-Test Benchmark Before Booking
85%+ on 3 timed full mocks, the 72% threshold demands higher prep
3 Concepts That Fail Most Business Analyst Candidates
These are not the hardest topics; they are the ones where candidates are most confidently wrong. Learn the distinction early.
1. Process Mapping vs User Stories: Different Artefacts for Different Purposes
Process maps (swim lane diagrams, flow charts) document current-state workflows across people and systems. User stories document future-state requirements from the user’s perspective ("As a [role], I want [capability] so that [benefit]"). Candidates write user stories when asked for a process map and vice versa. The exam tests when each is the appropriate analysis output, process map for AS-IS documentation; user stories for development backlog requirements.
2. Acceptance Criteria vs Definition of Done: Two Different Quality Gates
Acceptance Criteria define the specific conditions a feature must meet to be accepted by the Product Owner; they are story-specific. Definition of Done is a team-wide checklist that all stories must pass (code reviewed, tested, deployed to staging). Candidates merge these concepts. The exam distinguishes them: acceptance criteria vary per story; Definition of Done is universal and does not change story-by-story.
3. Stakeholder Communication: RACI Matrix vs Communication Plan
A RACI matrix maps stakeholders to responsibilities: Responsible, Accountable, Consulted, Informed. A Communication Plan defines who receives what information, in what format, and at what frequency. They serve different purposes. Candidates use RACI to answer "how do you manage stakeholder updates?", the exam expects a Communication Plan for that use case. RACI is for clarifying decision ownership, not managing information flow.
Frequently Asked Questions
- What is the Salesforce Business Analyst exam format?
- The Salesforce Certified Business Analyst exam has 60 multiple-choice questions, a 105-minute time limit, a 72% passing score, and a $200 fee. The 72% passing score is higher than most Salesforce exams; preparation needs to be more thorough.
- What are the highest-weight Business Analyst exam sections?
- Collaboration with Stakeholders (23%) and Customer Discovery (17%) together account for 40% of the Salesforce Business Analyst exam. Requirements (18%) and User Stories (18%) come next. Mastering those four sections covers 76% of the exam.
- Is the Salesforce Business Analyst certification hard?
- The Business Analyst exam has a 72% passing threshold, significantly higher than the 65% required for most other Salesforce certifications. It tests soft skills like stakeholder management and requirements gathering, which are harder to study from documentation alone. Real project experience as a BA is strongly recommended.
- What is the best way to prepare for the Salesforce Business Analyst exam?
- Focus on the BA methodology: how to run discovery workshops, write user stories with acceptance criteria, facilitate UAT, and manage scope. Study the full BA lifecycle from discovery through deployment. Practice writing user stories in the As a / I want / So that format and understand how to translate stakeholder needs into Salesforce solutions.
- What concepts do most Business Analyst candidates get wrong?
- The most commonly misunderstood topics for the Business Analyst exam are: (1) Process Mapping vs User Stories: Different Artefacts for Different Purposes; (2) Acceptance Criteria vs Definition of Done: Two Different Quality Gates; (3) Stakeholder Communication: RACI Matrix vs Communication Plan. Candidates are most confidently wrong on these. Learn the distinctions early to avoid losing marks on questions you expect to get right.
- Why do most Business Analyst candidates fail questions about Process Mapping vs User Stories?
- Process maps (swim lane diagrams, flow charts) document current-state workflows across people and systems. User stories document future-state requirements from the user's perspective ("As a [role], I want [capability] so that [benefit]"). Candidates write user stories when asked for a process map and vice versa. The exam tests when each is the appropriate analysis output, process map for AS-IS...
- Why do most Business Analyst candidates fail questions about Acceptance Criteria vs Definition of Done?
- Acceptance Criteria define the specific conditions a feature must meet to be accepted by the Product Owner; they are story-specific. Definition of Done is a team-wide checklist that all stories must pass (code reviewed, tested, deployed to staging). Candidates merge these concepts. The exam distinguishes them: acceptance criteria vary per story; Definition of Done is universal and does not cha...
- Why do most Business Analyst candidates fail questions about Stakeholder Communication?
- A RACI matrix maps stakeholders to responsibilities: Responsible, Accountable, Consulted, Informed. A Communication Plan defines who receives what information, in what format, and at what frequency. They serve different purposes. Candidates use RACI to answer "how do you manage stakeholder updates?", the exam expects a Communication Plan for that use case. RACI is for clarifying decision owner...
Related Exam Tips
Compare Certifications
- → Salesforce Business Analyst full study guide
Start Business Analyst Prep
After this exam, consider Sales Cloud Consultant or Service Cloud Consultant next.
Share or cite this study guide
Free to link from a forum post, study repo or article. Copy the Markdown and paste it anywhere.