Business Analyst Study Guide
The CertifyForce Business Analyst study guide covers the official Salesforce Business Analyst exam outline in 22 units across all 6 exam sections, one unit per exam-guide topic. The exam itself has 60 scored questions plus 5 unscored, a 105-minute limit and a 72% passing score, and its largest section is Collaboration with Stakeholders at 23%. Every unit is verified against official Salesforce documentation, cites its sources, and links to the practice questions that test it. Last updated October 15, 2026.
Validates capturing requirements, mapping business processes, writing user stories, and collaborating with stakeholders to deliver Salesforce solutions.
22 lessons · 6 exam sections · about 3 h of reading ·
Exam sections
Unlock the full guide
Every lesson's summary, exam expectations, key facts and self-check questions are free to read. The Business Analyst pack unlocks the self-check answers, core concepts, exam traps and worked scenarios, reading progress, personalized “read next”, and unlimited practice exams.
Customer Discovery
17% of the exam- Business goals, challenges and project scope~8 minHow a business analyst sorts discovery statements into goals, strategies, initiatives and challenges, turns vague goals and pain points into measurable targets, traces initiatives to goals, and writes an in-scope and out-of-scope boundary that resists scope creep.
- Current-state discovery from real usage evidence~8 minHow a business analyst establishes the current state from evidence rather than opinion: usage and login data, observation, product and license inventory, cross-product hand-offs and spreadsheet workarounds, and how to scope that review when time is short.
- BA roles across the implementation lifecycle~8 minWhat the business analyst owns in each phase of a Salesforce implementation, how the role differs from admin, developer, architect, project manager and business owner, and why the BA supplies analysis and raises gaps while others decide, design and build.
- Planning analysis work across lifecycle phases~7 minHow a business analyst sequences analysis work across the implementation lifecycle: discovery first, a business analysis plan per phase, high-level scope up front with just-in-time detail in iterative delivery, reuse of current-state maps, and routing newly found scope to the sponsor.
- Org assessment: opportunities and constraints~8 minHow a business analyst reviews a Salesforce org with the admin (configuration, automation, data model and quality, access, reports, adoption) and sorts findings into constraints such as managed packages, integrations, release calendars, parallel work streams and multiple orgs, versus opportunities such as unused metadata, using a sandbox to explore changes safely.
- Matching business needs to Salesforce capabilities~7 minHow a business analyst maps a stated need to the Salesforce capability built for it (screen flows and approvals, case management with entitlements, Experience Cloud for external users, Field Service with an offline mobile app), checks standard features before AgentExchange or custom builds, validates feasibility, and tests 'replicate the legacy layout' requests against the real outcome.
Collaboration with Stakeholders
23% of the exam- Planning discovery and preparing for elicitation~8 minHow to build a discovery plan around who your stakeholders are, what each group uniquely knows and how much time it can give, and what to prepare before the first elicitation session: the business need, project history, enterprise analysis and a draft current-state flow.
- Stakeholder analysis and the trusted advisor role~8 minHow to find every stakeholder (internal, external and the ones discovered late), record their influence, earn trusted-advisor status by speaking the customer's language and following up with the people who matter, and carry meaning both ways between the business and the technical team.
- Choosing the right elicitation technique~8 minWhich elicitation technique fits which scenario signal (scale, a gap between what people say and do, a need for agreement, sensitive or single-source knowledge, group dynamics, idea generation, people who cannot describe what they want), how to prepare and run a workshop, and what the conduct and confirm stages involve.
- Gap analysis from current to future state~7 minThe path from a validated current state to an agreed, stored future state: define the future state with stakeholders, run a gap analysis, assess the options against value, effort and risk, challenge steps that only exist for legacy reasons, build shared understanding with side-by-side maps, whiteboarding and journey maps, and phase the change when it exceeds the budget.
- Resolving conflicts to reach stakeholder consensus~7 minHow a BA facilitates (not dictates) agreement when stakeholders compete: joint prioritization against agreed criteria, evidence-based sessions with the sponsor and SMEs, escalation with documented options when deadlocked, trade-off conversations for late 'critical' requests, and decision records, sign-off and decision rights that stop agreements being reopened.
Business Process Mapping
12% of the exam- Scoping and decomposing complex business processes~8 minHow to bound a complex process by its input and outcome, set its context with a capability model or SIPOC, and break it into readable levels of 8-10 verb-first activity boxes that drill down without losing scope.
- Documenting processes with UPN and other notations~8 minHow to document a process in Universal Process Notation (activity boxes, lines with text, RACI resources, attachments, drill-downs), when a SIPOC or value stream map fits better, and how to build and validate maps live with the people who do the work to elicit requirements and agree a future state.
- Governing process maps in a versioned repository~7 minWhy approved process maps belong in one version-controlled, web-published repository with diagram-level history, view and edit rights, named owners and a sign-off cycle, and how that repository controls scope, links implementation and operational assets, and supports regulated processes.
Requirements
18% of the exam- Scope vs requirements vs user stories~8 minHow the scope statement, requirements and user stories differ in purpose, point of view and timing, and how a business need flows down through them without losing business rules.
- Eliciting, validating and prioritizing requirements~8 minHow a business analyst finds the right stakeholders, fills gaps and reconciles conflicts, checks each requirement is testable and traceable, confirms it with its owners, and facilitates a priority order the business agrees.
- Requirements baselines, traceability and change control~7 minWhy requirements live in one version-controlled repository, how a baseline and its change history expose scope creep, how change requests are logged and decided, and how unique IDs trace each requirement to the stories and tests that prove it.
User Stories
18% of the exam- User story anatomy, INVEST and splitting~7 minThe three parts of a user story and why each matters, how to keep stories about intent rather than implementation, how to diagnose a weak story with the INVEST checklist, and how to split a story that is too big.
- Writing testable acceptance criteria~8 minWhat acceptance criteria are, how to write each one as a single pass/fail statement of intent, how they differ from the team's definition of done, and how they decide whether a story is ready and whether it is accepted.
- Managing user stories in a versioned backlog~7 minHow a version-controlled story repository becomes the system of record for scope: per-story revision history, recording mid-sprint and post-delivery changes, stakeholder access, deferral decisions, links to requirements and releases, and moving an existing document in as the baseline.
Development Support and User Acceptance
12% of the exam- Supporting the build and validating delivery~8 minWhat the BA does while the solution is built: clarifying story intent and updating acceptance criteria, working the Scrum meetings, accepting or returning stories against their criteria, protecting existing functionality, and preparing the evidence, training and communications the business needs before release.
- Planning and running user acceptance testing~8 minHow the BA plans UAT (testers, scripts, schedule, sandbox and test data, defect process, sign-off), runs it (triaging defects, enhancements and usability issues, retesting, reporting progress), and gives decision makers the facts for a go/no-go call backed by written sign-off.
Common questions about the Business Analyst study guide
Is the Business Analyst study guide free?
Partly. Every unit's summary and its "What the exam expects", "Key facts" and "Check yourself" sections are free to read without an account. The "Core concepts", "Exam traps" and "Worked scenario" sections, reading progress and unlimited timed mock exams come with the Business Analyst pack (USD $19).
How current is the Business Analyst study guide?
It is written to the current official Salesforce Business Analyst exam outline, and each unit is checked against Salesforce documentation before it is published. The most recent update was October 15, 2026, and every unit shows its own last-updated date.
How does the study guide map to the official Business Analyst exam guide?
There is one unit per topic in the official exam guide, grouped under its 6 weighted sections: Customer Discovery (17%), Collaboration with Stakeholders (23%), Business Process Mapping (12%), Requirements (18%), User Stories (18%), Development Support and User Acceptance (12%). Each unit quotes the exam objective it covers word for word.
How do the practice questions link to the study guide?
Each unit lists the reviewed practice questions that test it (306 questions are linked across the guide), so you can read a topic and practice it in one click. After a practice exam, every missed question links back to the unit that teaches it.