A Salesforce Business Analyst sits between two groups that speak different languages: business stakeholders who know the problem, and technical teams who build the solution. The analyst's job is to turn a business need into a requirement that is clear, testable, and worth building, then to check that what was built actually solves the original problem. This practice set gives you 563 multiple-choice questions for the Salesforce Certified Business Analyst credential, covering all six domains of the official blueprint. Every question includes an explanation for each option, so a wrong answer teaches you just as much as a right one.

This is an intermediate-level credential intended for people who act as the bridge between business stakeholders and technical teams in Salesforce implementations, including business analysts, Salesforce administrators moving into analytical roles, product owners, and junior Salesforce consultants. . There are no strict prerequisites to register, although Salesforce recommends one to two years of experience in business analysis, requirements gathering, or Salesforce implementation projects, plus familiarity with basic Salesforce administration and Agile methodologies. This practice set follows the official domain weights, so you can practise the areas that matter most in proportion to their exam weight.

Business Analysis Fundamentals: 75 questions

The first section carries 15 percent of the exam weight and establishes the analyst's role. You will practise the BA role and its boundaries versus admin, developer, and architect, value-driven analysis and outcome versus output, the Salesforce implementation lifecycle across Discover, Design, Build, Test, and Deploy, out-of-the-box functionality, metadata, multi-tenant architecture, org and standard objects, relationships, subject matter expert versus stakeholder, product owner, RACI and Power/Interest stakeholder management, requirements hierarchy, functional versus non-functional requirements, Waterfall, Scrum, Kanban, and Hybrid methodologies, SMART goals, 5 Whys, return on investment and cost-benefit ratio, MoSCoW, scope creep, and change control. A BA who cannot draw these boundaries cleanly will struggle in every later domain, so this section is worth mastering first.

Elicitation: 105 questions

The second section is the largest in the set after user stories, at 20 percent, and it covers how requirements are actually gathered. Questions test elicitation techniques, stakeholder identification and engagement, interview and workshop facilitation, observation, document analysis, prototyping, surveys, and the judgement calls that decide which technique fits which situation. Elicitation is not just asking questions: it is knowing whose input counts, how to surface conflicting needs, how to confirm what you heard, and how to keep a session on track when stakeholders disagree. Strong elicitation prevents the most expensive failure in a Salesforce project, which is building the wrong thing well.

User Stories and User Acceptance Testing: 98 questions

The third section carries the highest single weight, 25 percent, and it is where requirements become something a team can build and test. You will practise writing user stories in a form that states who benefits, what they need, and why it matters, acceptance criteria that make a story testable, the difference between a story and a task, story splitting and refinement, backlog prioritisation, and user acceptance testing from planning through execution to sign-off. The acceptance criteria are the hinge of the whole section: if they are vague, testing becomes a matter of opinion, and sign-off becomes a negotiation. If they are precise, the team knows when the work is done and the business knows what it is signing.

Process Modeling: 96 questions

The fourth section, at 15 percent, covers how work actually flows. Questions cover BPMN fundamentals and symbol identification including start, end, and intermediate events, rounded-rectangle tasks, user versus service tasks, exclusive and parallel gateways, sequence versus message flows, and timer events, swimlanes and handoff risk, As-Is versus To-Be analysis, the eight wastes, and the trap of paving the cow path by automating a broken process, process ownership, happy versus exception paths, stakeholder validation, SIPOC and Value Stream Mapping, cycle time versus process time, bottlenecks, touchpoints, Process Cycle Efficiency and touchpoint-reduction calculations, and Salesforce automation mapping across Record-Triggered Flow, Approval Process, Assignment Rules, Validation Rules, and Schedule-Triggered Flow. Workshop facilitation is tested too, including participant numbers, steps per map, sub-processes, probing questions, and handling subject matter expert disagreement. A good process map makes a broken process visible before anyone builds on top of it.

Solution Assessment and Validation: 93 questions

The fifth section, at 10 percent, tests what happens after a solution is proposed or built. You will practise assessing whether a solution meets business needs, measuring value delivered against the original requirement, identifying gaps between what was promised and what was delivered, recommending changes or alternatives, and validating that a solution is ready for release. This is the section where an analyst proves they are not just documenting requirements but judging outcomes. It rewards the habit of returning to the original business problem rather than accepting a technically impressive answer that solves a different problem.

Agile Project Management: 96 questions

The final section, at 15 percent, covers how Salesforce work is actually delivered in Agile teams. Questions cover Agile principles and values, Scrum roles, events, and artifacts, sprint planning, daily standups, sprint reviews, and retrospectives, backlog refinement, velocity and capacity, Kanban boards and work-in-progress limits, release planning, and the BA's role inside an Agile team versus a traditional project structure. The section tests practical judgement: when to refine, when to split, when to push back on scope, and how to keep the backlog honest when stakeholders keep adding work.

Who this set is for

This set is for business analysts preparing for the Salesforce Certified Business Analyst credential, including Salesforce administrators transitioning into analytical roles, product owners, junior Salesforce consultants, and anyone who gathers requirements, models processes, or validates solutions on Salesforce projects. It is also useful for experienced analysts who want a structured review of elicitation, user stories, process modeling, and Agile delivery in one place.

Important Course Disclaimer

This is an independent practice resource. It is not produced by, sponsored by, or affiliated with Salesforce, and it does not reproduce any official exam material. It is designed to help you practise, identify gaps, and approach your Salesforce Business Analyst exam with a clear picture of where you stand.

These are not leaked questions from the actual exam, These are original content created through thorough study and sophisticated digital curation methods to conform to the most recent 2026 exam blueprints; they are not leaked exam questions.