Salesforce Certified Business Analyst (BA-201) Exam Topics and Questions
These Salesforce Certified Business Analyst (BA-201) exam topics are organized according to official exam domains to help candidates quickly verify coverage and focus on assessment rather than theory. Each domain is paired with topic-wise Salesforce Certified Business Analyst (BA-201) sample questions that reflect how objectives are tested in the actual exam. This structure enables efficient review, targeted self-assessment, and rapid identification of weak areas when preparing for the Salesforce Certified Business Analyst certification exam.
Let's Practice Free Salesforce Certified Business Analyst (BA-201) Questions Aligned with Official Exam Topics
Requirements is where most Salesforce BA candidates lose points they didn't expect to lose. The domain looks straightforward on paper, but the exam tests precision: scope is not a requirement, and a requirement is not a user story. If those three things blur together in your mind, you will consistently pick the wrong option. This topic also pushes you to think about who validates requirements, how priorities get set, and why version control matters for managing scope creep. How Requirements...
Requirements is where most Salesforce BA candidates lose points they didn't expect to lose. The domain looks straightforward on paper, but the exam tests precision: scope is not a requirement, and a requirement is not a user story. If those three things blur together in your mind, you will consistently pick the wrong option. This topic also pushes you to think about who validates requirements, how priorities get set, and why version control matters for managing scope creep.
How Requirements is tested
At 18%, this topic will show up enough that a shaky understanding will compound across the paper. Items tend to present a scenario where a stakeholder meeting has produced a mix of scope statements, constraints, and feature requests, and you have to classify or act on them correctly. The trap is treating all of it as requirements when the exam draws a hard line between scope, requirements, and user stories.
Other items focus on stakeholder engagement: who should validate a requirement, when prioritization happens, and what to do when two stakeholders disagree on priority. Candidates lose marks by defaulting to a technical answer when the scenario is still in the discovery and validation phase.
Version control questions are deceptively simple. Items reward knowing that requirements live in a managed, versioned repository specifically to control scope, not just to keep a record. Read the scenario carefully for signals about which phase the project is in before choosing an action.
The ITExamsTopics practice test for the Salesforce Certified Business Analyst covers every topic, including Requirements. Working through a full bank lets you spot which of the three concepts (scope, requirements, user stories) you keep misclassifying, so you can fix the gap before exam day.
The question below puts you in a stakeholder meeting scenario and asks you to make a judgment that turns on the distinction between scope and requirements.
The business analyst (BA) at Cloud Kicks (CK) has been tasked with optimizing CK's lead process. In the weekly sales meeting, the BA outlines the project and asks for input. A new entry-level employee reaches out multiple times with ideas and suggestions for improvements.
What should the BA do when responding to the new employee's input?
Where Requirements asked you to classify and document, Customer Discovery asks you to investigate and align. You are building a picture of a customer's business from the outside in: their strategy, their goals, what Salesforce products they already use, and where their environment creates constraints. The BA's role shifts depending on the implementation phase, and the exam expects you to know exactly what that role looks like at each stage, not just in general terms. β Business strategy and current-state...
Where Requirements asked you to classify and document, Customer Discovery asks you to investigate and align. You are building a picture of a customer's business from the outside in: their strategy, their goals, what Salesforce products they already use, and where their environment creates constraints. The BA's role shifts depending on the implementation phase, and the exam expects you to know exactly what that role looks like at each stage, not just in general terms.
β Business strategy and current-state analysis
Discovery starts with understanding why the project exists. That means connecting a customer's stated goals and challenges to a defined project scope before any solution conversation begins. The exam tests whether you know how to draw that line: a business initiative is not a scope statement, and a challenge is not a requirement. You also need to map the current state accurately, which means examining how the customer actually uses their existing Salesforce products today, not how they were designed to use them. Gaps between intended and actual use are where constraints and opportunities live, and items will ask you to identify both. Candidates who skip current-state analysis and jump to recommending features tend to pick options that sound helpful but are premature for the phase described in the scenario.
β BA roles, the implementation lifecycle, and Salesforce capabilities
The BA's responsibilities change as a project moves through its lifecycle, and the exam is specific about this. Planning business analysis activities means knowing which phase calls for which type of work: discovery activities belong early, validation activities belong later, and confusing them in a scenario question will cost you the point. Items also test your ability to analyze a Salesforce environment for opportunities and constraints, which requires knowing enough about Salesforce capabilities to recognize when a business need can be met natively and when it cannot. The exam rewards recommending solutions that align with what the platform can actually do, not solutions that are technically possible but architecturally expensive. Know the difference between what Salesforce offers out of the box and what requires customization, because scenario items will hinge on that boundary.
How Customer Discovery is tested
At 17%, Customer Discovery is the second-heaviest topic, and its items almost always arrive as scenarios. You will be given a situation: a customer has a stated goal, an existing Salesforce environment, and an implementation in some phase. You then have to choose the action or output that fits the BA role at that moment.
The most common trap is answering with what a solution architect or developer would do. The exam is testing BA judgment, which means stakeholder alignment and current-state understanding come before solution recommendations. Items also catch candidates who treat all phases of the lifecycle as interchangeable. Knowing that planning activities precede execution activities, and that discovery precedes design, is not background knowledge; it is directly examinable.
Salesforce capability questions reward practical alignment: matching a business need to a platform feature correctly. Vague answers about customization lose to specific answers about native capability when the scenario supports the native option.
Seeing how Customer Discovery items are phrased across a large question bank helps you recognize the lifecycle-phase signals buried in scenario stems. The ITExamsTopics practice test lets you work under timed conditions so those signals register before the real exam.
The question below places you at a specific point in a customer engagement and asks you to choose the action that fits the BA role at that stage.
A business analyst (BA) at Northern Trail Outfitters is preparing for a user acceptance testing (UAT) session for a global Sales Cloud project.
What should the BA do to engage the business most effectively during UAT"?
At 23%, this is the heaviest topic on the exam, and it earns that weight. Stakeholder collaboration is where the BA role is most visible and most vulnerable to error. You are not just facilitating meetings; you are choosing techniques, managing conflicting priorities, and moving a group from a documented current state to an agreed future state. Every decision in this topic is context-dependent, which is exactly why the exam tests it through scenarios rather than definitions. β Planning discovery...
At 23%, this is the heaviest topic on the exam, and it earns that weight. Stakeholder collaboration is where the BA role is most visible and most vulnerable to error. You are not just facilitating meetings; you are choosing techniques, managing conflicting priorities, and moving a group from a documented current state to an agreed future state. Every decision in this topic is context-dependent, which is exactly why the exam tests it through scenarios rather than definitions.
β Planning discovery and choosing elicitation techniques
Discovery planning is not one-size-fits-all. The exam expects you to tailor your approach based on who the stakeholders are, what phase you're in, and what kind of information you need. A workshop works in some contexts; a structured interview works in others; observation works where neither of those would. Items present a scenario with specific stakeholder characteristics and ask you to select the technique that fits. The trap is defaulting to the most familiar technique rather than the one the scenario calls for. Read the stakeholder profile in the question carefully: their seniority, availability, and relationship to the subject matter all point toward or away from specific methods. Candidates who treat elicitation as a single undifferentiated activity consistently pick options that are defensible in the abstract but wrong for the situation described.
β Building stakeholder relationships and acting as a liaison
The trusted advisor framing matters on this exam. Identifying key stakeholders is only the beginning; the BA is expected to build relationships that allow them to bridge business and technical teams effectively. Items test what that looks like in practice: when do you escalate a disagreement, when do you facilitate a resolution yourself, and how do you communicate a technical constraint to a non-technical stakeholder without losing their confidence? The liaison role also means you are accountable for keeping both sides aligned. Scenarios will describe a breakdown in that alignment and ask you to choose the action that repairs it. Answers that are technically correct but ignore the relationship dimension tend to be distractors here. The exam rewards options that preserve stakeholder trust while still moving the project forward.
β Current state to future state and managing competing priorities
Moving from current state to future state is a structured transition, not a creative leap. The exam tests whether you understand the steps between documenting how things work today and getting stakeholder sign-off on how they will work tomorrow. That means gap analysis, options assessment, and consensus-building are all in scope. Competing priorities are the other pressure point. When two stakeholders want different things, the BA's job is to surface the conflict, facilitate a resolution, and arrive at consensus: not to pick a winner or defer indefinitely. Items present priority conflicts and ask what the BA should do next. Options that avoid the conflict or escalate prematurely are common distractors. The exam rewards structured facilitation that brings stakeholders to an agreed position.
How Collaboration with Stakeholders is tested
This topic's weight means you will face more scenario-based items here than anywhere else on the exam. Each one embeds a specific stakeholder situation: a conflict, an elicitation challenge, a transition from current to future state, or a priority dispute. Your job is to identify the BA response that fits the scenario, not the response that sounds most professional in isolation.
The dominant trap is choosing an answer that is correct in general but wrong for the phase or stakeholder profile described. Elicitation technique questions are particularly prone to this: candidates pick the technique they know best rather than the one the scenario supports.
Items also reward knowing that stakeholder consensus is an outcome you facilitate, not one you declare. Scenarios where a BA makes a unilateral decision about priorities or future state are almost always distractors. The exam consistently favors options where the BA creates the conditions for agreement rather than imposing one. Managing relationships and managing scope are treated as inseparable here.
Because Collaboration with Stakeholders generates more items than any other topic, checking your weak areas with a targeted question bank is more efficient than re-reading the material. The ITExamsTopics practice test lets you filter by topic and work through this domain until your miss rate drops.
The question below gives you a stakeholder conflict scenario and asks you to identify the BA action that moves the group toward consensus.
Business Process Mapping is where abstract requirements become something a room full of stakeholders can actually see and argue about. Shifting from Stakeholder Collaboration, the work here is analytical and visual: you are breaking down complex processes, documenting them precisely, and using that documentation to drive both requirement elicitation and scope control. At 12%, this topic is not the exam's centerpiece, but the skills it tests feed directly into User Stories and Development Support. How Business Process Mapping is tested...
Business Process Mapping is where abstract requirements become something a room full of stakeholders can actually see and argue about. Shifting from Stakeholder Collaboration, the work here is analytical and visual: you are breaking down complex processes, documenting them precisely, and using that documentation to drive both requirement elicitation and scope control. At 12%, this topic is not the exam's centerpiece, but the skills it tests feed directly into User Stories and Development Support.
How Business Process Mapping is tested
Items in this topic present a process scenario and ask you to choose the mapping approach, the level of decomposition, or the next step in documentation. The exam rewards knowing that breaking a complex process into manageable steps is a deliberate analytical act, not just drawing boxes and arrows. Candidates lose marks when they treat process mapping as a documentation formality rather than an elicitation tool.
The version control angle appears here just as it does in Requirements. Items test whether you understand that storing process maps in a version-controlled repository is specifically tied to scope management: it creates a traceable record of what was agreed and when. Answers that treat version control as optional housekeeping are distractors.
Stakeholder engagement within process mapping is also examinable. The exam expects you to know that visualizing a future-state process is a collaborative activity, not a BA deliverable handed over after the fact. Options that position the BA as working in isolation before presenting a finished map tend to be wrong.
The ITExamsTopics practice test covers Business Process Mapping items alongside all other topics in a single purchase. Running through the full bank once gives you a clear picture of how this topic's questions are weighted against the rest of the exam.
The question below asks you to apply process decomposition judgment to a complex scenario involving scope boundaries and stakeholder visualization.
User Stories shares its 18% weight with Requirements, and the two topics are deliberately connected: a user story is the output of a requirements process, not a synonym for it. By the time you reach this topic in the exam, you need to know not just how to write a user story but what makes one ready for development. Acceptance criteria are where most candidates leave points on the table, because writing them precisely enough to constrain a developer is...
User Stories shares its 18% weight with Requirements, and the two topics are deliberately connected: a user story is the output of a requirements process, not a synonym for it. By the time you reach this topic in the exam, you need to know not just how to write a user story but what makes one ready for development. Acceptance criteria are where most candidates leave points on the table, because writing them precisely enough to constrain a developer is harder than it looks.
How User Stories is tested
Items here split roughly across three areas: the components of a well-formed user story, the quality of acceptance criteria, and version control for scope management. The component questions are the most straightforward: the exam tests whether you can identify what belongs in a user story and what signals that one is incomplete or misformed.
Acceptance criteria items are where the real discrimination happens. The exam rewards criteria that are specific enough to be testable and that leave no ambiguity for a developer to exploit. Vague or aspirational criteria are common distractors presented as if they are complete. Candidates who cannot distinguish between a criterion that describes an outcome and one that merely restates the feature request will miss these consistently.
Version control questions follow the same logic as in Requirements and Business Process Mapping: the exam treats the repository as a scope management tool, not an archive. Items reward understanding that managing user stories in a versioned system is how a BA controls what is and isn't in scope at any point in the project.
User Stories and Requirements together make up more than a third of the exam. Using the ITExamsTopics practice test in its PDF format lets you review these two linked topics side by side and confirm that you're not conflating them under time pressure.
The question below focuses on acceptance criteria and asks you to evaluate whether a given story component meets the standard for development readiness.
This is the final phase topic on the exam, and it covers what the BA does once building has started. The work shifts from defining and documenting to validating and supporting. At 12%, it carries the same weight as Business Process Mapping, and the items are consistently practical: given a delivery situation, what does the BA do to make sure the solution actually meets what was agreed? The answer almost never involves writing new requirements. How Development Support and User...
This is the final phase topic on the exam, and it covers what the BA does once building has started. The work shifts from defining and documenting to validating and supporting. At 12%, it carries the same weight as Business Process Mapping, and the items are consistently practical: given a delivery situation, what does the BA do to make sure the solution actually meets what was agreed? The answer almost never involves writing new requirements.
How Development Support and User Acceptance is tested
Items in this topic are scenario-driven and phase-sensitive. The exam places you in a delivery or UAT context and asks you to identify the BA action that keeps the project on track. The dominant trap is applying discovery or requirements-phase thinking to a delivery-phase scenario. By this stage, the BA's job is validation, not exploration.
For development support items, the exam rewards actions that confirm the solution is being built to the agreed requirements, and that surface misalignments early rather than at UAT. Candidates who choose options that reopen scope or revisit requirements without a change-control trigger are picking the wrong answer.
UAT items focus on the BA's role in supporting users through testing, not executing it for them. The exam distinguishes between facilitating UAT and performing it. Items reward options where the BA ensures test coverage maps to the requirements and acceptance criteria already documented, closing the loop back to User Stories and Requirements. That connection to earlier topics is deliberate, and recognizing it in a scenario is itself a test of end-to-end BA thinking.
The free demo of the ITExamsTopics practice test includes questions from across the exam, so you can check whether Development Support and User Acceptance items feel different in style from the discovery-phase topics before you commit to the full bank.
The question below puts you in a UAT scenario and asks you to choose the BA action that correctly validates solution delivery against the original requirements.
Ready to Start Practicing?
Access all questions and start your exam preparation journey
Upgrade to Full Salesforce Certified Business Analyst (BA-201) Exam Questions π