Free Salesforce Business Analyst practice questions

Question 1

Get Cloudy Consulting has been engaged to restart a failing Salesforce initiative, and the business analyst is planning the discovery needed to redefine scope. Which three inputs should the business analyst gather? Choose 3 answers.
A. The organization's strategic plan and this year's stated business goals.
B. The Apex test coverage percentage currently reported for the production org.
C. The known business challenges and pain points, along with metrics that show their impact.
D. The annual license cost of every managed package installed in the org today.
E. Constraints such as budget, timeline, and dependencies on other active work streams.

Accepted Answer

Correct answer: A. The organization's strategic plan and this year's stated business goals. | C. The known business challenges and pain points, along with metrics that show their impact. | E. Constraints such as budget, timeline, and dependencies on other active work streams.
Redefining scope requires knowing where the business is trying to go, what is getting in the way, and what limits the possible solution, so the strategic plan and goals, the quantified challenges, and the constraints and dependencies are the essential discovery inputs. Apex test coverage is a code quality metric for the development team and tells the business analyst nothing about business direction or scope. Managed package license costs may matter to a procurement or ROI discussion, but building return on investment is outside the business analyst's responsibility and the figure does not shape which processes are in scope.

Question 2

A business analyst is new to Ursa Major Solar and must document requirements for a service improvement initiative. What should the business analyst do to understand the existing Salesforce environment?
A. Request a full copy sandbox and rebuild the proposed service-improvement solution there to see what breaks first.
B. Work with the administrator to review the org's existing objects, fields, automation, and reports in place.
C. Ask stakeholders to describe the org's configuration and record their descriptions as the current state.
D. Assume the org uses standard Salesforce functionality until a stakeholder reports otherwise.

Accepted Answer

Correct answer: B. Work with the administrator to review the org's existing objects, fields, automation, and reports in place.
Reviewing the org's actual metadata and reporting with the administrator produces a factual picture of existing configuration, which is what surfaces the opportunities and constraints a new initiative must work within. Building a speculative solution in a sandbox is design and build work performed before the environment is even understood. Relying on stakeholder descriptions captures perception, which routinely diverges from what is configured. Assuming standard functionality is exactly the blind spot that causes requirements to collide with existing customizations.

Question 3

Cloud Kicks service agents skip steps when creating warranty claims because the process is complex and spread across several screens. The business analyst must recommend a solution approach for the design discussion. What should the business analyst recommend?
A. An Apex trigger that validates the completed claim record after the agent has already saved and submitted it.
B. A workflow rule that emails the supervisor whenever a required claim step is missed.
C. A Process Builder process that silently populates the missing claim values after save.
D. A guided screen flow that walks agents through the claim steps and collects required information.

Accepted Answer

Correct answer: D. A guided screen flow that walks agents through the claim steps and collects required information.
A guided screen flow is the declarative capability designed for step-by-step data collection and is the right recommendation for agents who miss steps in a complex process. An Apex trigger validating after save is custom code that reports failure rather than guiding the agent, and code should not be recommended where declarative functionality meets the need. Workflow rules and Process Builder are retired for new automation, so neither is a valid recommendation today; Flow is the supported tool for new declarative automation, and an after-the-fact supervisor email would not fix the process anyway.

Question 4

Cloud Kicks delivers Salesforce changes with an agile team made up of a product owner, a scrum master, and developers. The business subject matter experts rarely attend ceremonies, and the team keeps guessing at intent. What should the business analyst do?
A. Decide the requirements independently so the team's sprint velocity is not affected by subject matter experts who rarely attend.
B. Require every subject matter expert to attend all ceremonies as a condition of the project continuing past this sprint.
C. Let the developers contact the subject matter experts directly and stop attending backlog refinement sessions themselves.
D. Act as the liaison: bring the experts' needs into refinement, and take the team's open questions back to them.

Accepted Answer

Correct answer: D. Act as the liaison: bring the experts' needs into refinement, and take the team's open questions back to them.
The BA's defining contribution on a delivery team is to act as a liaison between business and technical teams, carrying business intent into refinement and returning the team's questions to the people who can answer them. Deciding requirements alone protects velocity while quietly substituting the BA's assumptions for the business need, which is what UAT failures are made of. Mandating attendance at every ceremony ignores that subject matter experts have day jobs and is not a lever the BA controls. Sending developers directly to stakeholders with no analyst in the loop removes translation and tends to produce contradictory, undocumented direction.

Question 5

Cumulus Financial is starting a Sales Cloud initiative. The business analyst (BA) has been given a list of 24 stakeholders that includes the CFO, two regional sales directors, and 20 loan officers who process applications every day. What should the BA do before scheduling any discovery sessions?
A. Analyze the stakeholder list for each group's role, influence, and availability, then match a discovery technique and format to each group.
B. Schedule one workshop so stakeholders hear the same leadership-approved questions at the same time.
C. Send the identical requirements questionnaire to 24 stakeholders so responses can be scored against one common rubric.
D. Begin with the CFO and work down the organization chart, using one standard one-hour interview format so time is allocated equally.

Accepted Answer

Correct answer: A. Analyze the stakeholder list for each group's role, influence, and availability, then match a discovery technique and format to each group.
Discovery must be planned around the target stakeholders, so the BA first analyzes who they are, what they know, how much influence they have, and how much time they can give, then selects a technique that fits each group. A single leadership-approved workshop would let senior voices dominate and waste the loan officers' time on topics they cannot speak to. Scoring identical questionnaire responses against one rubric ignores that the CFO speaks to strategy and outcomes while loan officers speak to daily process detail, so the rubric would be comparing unlike answers. Working strictly down the organization chart with an identical interview format treats availability and influence as the same thing and is inefficient for 20 frontline users.

Question 6

The Chief Operating Officer at Ursa Major Solar has 45 minutes available and is the only person who can explain the company's three-year service strategy and a politically sensitive reorganization. Which elicitation technique should the business analyst choose?
A. An open brainstorming session with the COO and the service leadership team.
B. A one-on-one interview with prepared, prioritized questions.
C. A survey sent to the COO and the other executives for written responses.
D. A requirements workshop that includes the COO and the frontline service managers.

Accepted Answer

Correct answer: B. A one-on-one interview with prepared, prioritized questions.
A prepared one-on-one interview is the most effective way to get depth from a single knowledgeable person in limited time, and it is the appropriate setting for sensitive information the executive may not share in a group. Brainstorming is designed to generate many ideas without judgment, not to extract an existing strategy, and the leadership audience would dilute the COO's own view. A survey wastes the rare access and offers no ability to probe or follow up on a nuanced answer. A workshop with frontline managers would discourage candid discussion of a sensitive reorganization and mixes strategy with operational detail.

Question 7

A Bloomington Caregivers business analyst needs sign-off on a prioritized backlog from clinical, billing, and compliance leaders who currently disagree about sequencing. Which two actions best support reaching consensus? Choose 2 answers.
A. Trace each requirement to the business objective it serves and quantify its impact, so leaders can compare requests on a common basis.
B. Document the agreed decisions and obtain explicit sign-off from the stakeholders who hold decision authority, for scope management.
C. Run an open majority vote among all end users across the clinical, billing, and compliance departments and adopt whichever sequencing wins.
D. Accept the sequencing proposed by whichever department leader responds first to the prioritization request.
E. Let the development team set the delivery order purely on which items are easiest to build first.

Accepted Answer

Correct answer: A. Trace each requirement to the business objective it serves and quantify its impact, so leaders can compare requests on a common basis. | B. Document the agreed decisions and obtain explicit sign-off from the stakeholders who hold decision authority, for scope management.
Consensus comes from making the comparison objective, and tracing every requirement back to a business objective with a quantified impact converts three competing opinions into one evaluable list. Capturing the decision and getting explicit sign-off from the stakeholders with authority is what makes the agreement durable and gives the BA a baseline for managing later scope changes. An open majority vote among all end users ignores that stakeholders have different levels of influence and accountability, and compliance requirements are rarely negotiable by popularity. Taking the first responder's ordering rewards availability rather than value. Ordering by build effort alone optimizes for the delivery team and can leave the highest-value or legally required work last.

Question 8

Northern Trail Outfitters' stakeholders describe the case escalation process differently in every interview. The BA needs a shared starting point before gathering requirements. What should the BA do?
A. Write user stories based on the most senior stakeholder's description of the process.
B. Ask the administrator to document the current Salesforce configuration and treat that as the process.
C. Document a current-state process map, validate it with stakeholders, and elicit requirements from it.
D. Begin designing the future state immediately, since the current state will be replaced anyway.

Accepted Answer

Correct answer: C. Document a current-state process map, validate it with stakeholders, and elicit requirements from it.
Documenting and validating a current-state process map gives every stakeholder one agreed picture of how work happens today, and it is that map which surfaces the gaps and pain points requirements are then written against. Taking the most senior stakeholder's version treats seniority as accuracy and ignores the people who actually perform the steps. The current configuration shows how the system is set up, not the end-to-end business process, much of which happens outside Salesforce. Jumping to future-state design without an agreed current state means the design rests on conflicting assumptions, and disagreements resurface later as change requests.

Question 9

AW Computing's quote-to-order process spans five systems and dozens of exceptions, and stakeholders keep adding more detail during the workshop. Which two actions should the BA take to keep the work manageable? Choose 2 answers.
A. Capture every exception on the same diagram, adding a box each time one comes up, so nothing raised in the room gets lost.
B. Agree the process boundaries -- the starting input and the final outcome -- and park detail that falls outside them.
C. Replace the process map with a flat list of requirements, since the workshop diagramming is taking too long.
D. Break the process into levels, keeping the top level high level and drilling into the boxes that need detail.
E. Ask the development team to set the process boundaries based on the existing system integrations.

Accepted Answer

Correct answer: B. Agree the process boundaries -- the starting input and the final outcome -- and park detail that falls outside them. | D. Break the process into levels, keeping the top level high level and drilling into the boxes that need detail.
Defining a complex process means agreeing its input and outcome so anything outside those boundaries is explicitly out of scope, then breaking it into levels so the top level stays high level and detail lives in drill-down diagrams. Putting every exception on one diagram is what created the problem, and it breaks the 8-10 box guideline that keeps a map readable. Abandoning the map for a requirements list loses the shared visual that stakeholders use to agree the flow and spot gaps. Letting the development team set boundaries from existing integrations scopes the process around today's technology rather than the business outcome, and the integrations are likely to change.

Question 10

A program manager at Northern Trail Outfitters questions why the business analyst (BA) insists on keeping requirements in a version controlled repository rather than in ad hoc documents. Which two risks does the repository mitigate? Choose 2 answers.
A. Scope creep goes undetected because there is no approved baseline to compare new requests against.
B. Teams build and test against outdated requirement versions, causing rework and failures during user acceptance testing.
C. Story point estimates become mathematically inaccurate because nobody can tell which requirement version was actually estimated.
D. The BA loses the ability to run interviews and workshops with stakeholders once ad hoc documents replace the repository.
E. Stakeholders lose their access to the Salesforce production org, since repository permissions and org permissions are managed by the same admin.

Accepted Answer

Correct answer: A. Scope creep goes undetected because there is no approved baseline to compare new requests against. | B. Teams build and test against outdated requirement versions, causing rework and failures during user acceptance testing.
Without a versioned baseline the BA has nothing to compare incoming requests against, so scope grows unnoticed, and without one current version teams build and test from stale requirements and discover the mismatch only when users reject the result. Estimation accuracy depends on how well stories are understood and sized rather than on where requirements are stored, even though clearer requirements help. Elicitation techniques such as interviews and workshops are unaffected by the storage approach, since they produce the content the repository holds. Access to the production org is governed by profiles, permission sets, and licences, which has nothing to do with requirements documentation.

Question 11

After two elicitation workshops, a business analyst (BA) at Ursa Major Solar has drafted 40 requirements. Before the requirements are used for design, the BA must be confident they reflect what the business actually needs. What should the BA do?
A. Send the requirements to the development team so that technical feasibility and estimation confirm their correctness before design starts.
B. Facilitate a review session that plays the documented requirements back to the stakeholders for confirmation and formal agreement.
C. Treat the requirements as validated because the stakeholders were present and engaged when they were elicited in the workshops.
D. Ask the technical architect to approve the requirements on the stakeholders' behalf, since the architect attended the workshops too.

Accepted Answer

Correct answer: B. Facilitate a review session that plays the documented requirements back to the stakeholders for confirmation and formal agreement.
Confirming elicitation results is a distinct step: the BA plays the documented requirements back to the stakeholders, checks that each one states the real need, and obtains agreement before the requirements drive design. Feasibility review by developers answers whether something can be built, not whether it is what the business wants. Assuming validation happened because stakeholders attended the workshop ignores how often the BA's written interpretation differs from what participants meant. Letting the architect approve on the stakeholders' behalf transfers ownership of the business need to a technical role that cannot speak for it, and it removes the accountability that sign-off is meant to create.

Question 12

A stakeholder at Ursa Major Solar submits the statement, "The system must allow service agents to close cases from the mobile app." The business analyst (BA) needs to turn this requirement into a user story for the delivery team. Which statement is the best user story?
A. The requirement should be moved into the backlog unchanged, because a clearly written requirement is already a user story.
B. As a service agent, I want to close a case from the Salesforce mobile app so that I can finish my work without returning to a desk.
C. Add a Close Case quick action to the mobile page layout, assign it to the service profile, and deploy it to the production org.
D. Case closure on a mobile device must be possible in no more than two taps, a target the delivery team commits to during planning.

Accepted Answer

Correct answer: B. As a service agent, I want to close a case from the Salesforce mobile app so that I can finish my work without returning to a desk.
A user story is a short description of a feature from the user's point of view and names who wants it, what they want, and why, which is exactly what the agent-centred statement provides. Leaving the requirement statement unchanged skips that translation: a requirement is written for business and technical stakeholders and does not carry the persona and business value that the delivery team needs. Adding a quick action to a page layout is a solution task that assumes a design before the need is agreed. The two-tap statement is a non-functional constraint or a candidate acceptance criterion, not a story describing who benefits and why.

Question 13

Northern Trail Outfitters is standing up a multi-year, multi-region rollout, and the business analyst (BA) needs every requirement to stay traceable from the original need through to proof that it was delivered. Which two practices should the BA build into the requirements repository to support that traceability? Choose 2 answers.
A. Give each requirement a unique identifier linked to the stories that deliver it and the test cases that verify it.
B. Capture every change with a revision entry showing author, date, and approval, so the approved baseline is always known.
C. Delete deferred requirements so the active list stays short, easy to read, and free of anything not being built right now.
D. Maintain a separate copy of the requirements for each stakeholder group so every group can filter and format the list to its own preferences.
E. Restrict the repository so only the BA can open it, which the BA believes prevents stakeholders from introducing errors.

Accepted Answer

Correct answer: A. Give each requirement a unique identifier linked to the stories that deliver it and the test cases that verify it. | B. Capture every change with a revision entry showing author, date, and approval, so the approved baseline is always known.
Unique identifiers plus links to stories and test cases create the traceability that lets the BA prove what is being built and how it will be proven, and a revision entry for every change keeps the approved baseline identifiable so any growth in scope is visible. Deleting deferred requirements destroys the record of decisions and the rationale for them, and those items usually resurface in a later release. Per-group copies recreate the divergent-version problem a repository is meant to solve. Locking stakeholders out may prevent stray edits but also prevents the review, comment, and confirmation that keeps requirements accurate, and controlled edit rights with full history achieve the same protection without the loss.

Question 14

Ursa Major Solar's business analyst receives this story from a technical lead: "As a VP of Service, I want a custom Lightning web component on the Case record page that calls an Apex class so that I can see open cases by region." What should the business analyst recommend?
A. Approve the story as written, because naming the web component and Apex class gives the developer clear direction.
B. Convert the story into an epic and split it into separate stories by technical component.
C. Add the Apex class name to the story so testing can confirm the class exists in the org.
D. Rewrite the story to express the need and the benefit, leaving the technical design to the delivery team.

Accepted Answer

Correct answer: D. Rewrite the story to express the need and the benefit, leaving the technical design to the delivery team.
A user story should state intent rather than a solution: it captures the what and the why, not the how. Naming a Lightning web component and an Apex class hard-codes one design into the story and closes off simpler options such as a report, list view, or dashboard that might meet the VP's need. Approving it as written locks in that premature design, and splitting it by technical component compounds the problem by creating slices that deliver no standalone user value. Adding the Apex class name to the story makes the coupling worse, because acceptance criteria should describe observable outcomes, not implementation artifacts.

Question 15

Two business analysts at Cumulus Financial edited the same user story on the same afternoon, and one analyst's rewrite silently replaced the other's. What should the BA team do to prevent this recurring?
A. Assign a single analyst to own every story edit across the whole project.
B. Have analysts email their intended edits to each other first, so nobody's changes get silently overwritten.
C. Lock each story once it has been written, so no further edits to it are possible during the project.
D. Work in the version controlled repository, where concurrent edits are tracked and conflicts must be reconciled.

Accepted Answer

Correct answer: D. Work in the version controlled repository, where concurrent edits are tracked and conflicts must be reconciled.
Version control exists to handle exactly this situation: each change is a tracked revision, and when two people change the same content the conflict is surfaced and reconciled instead of one edit overwriting the other. Making one analyst the sole editor removes the collision but creates a bottleneck and does not scale on a large backlog. Emailing intended edits relies entirely on discipline and leaves no record inside the artefact itself. Locking stories after they are written conflicts with iterative refinement, where stories are expected to change as understanding improves.

Question 16

Before sprint planning, an Ursa Major Solar business analyst finds a story in the ready column with no acceptance criteria at all. What should the business analyst do?
A. Let the story enter the sprint, because acceptance criteria are written by testers after the build.
B. Delete the story from the backlog and ask the stakeholder to resubmit it.
C. Work with stakeholders to define at least one testable acceptance criterion before the story is treated as ready.
D. Copy the definition of done into the story so that it has criteria.

Accepted Answer

Correct answer: C. Work with stakeholders to define at least one testable acceptance criterion before the story is treated as ready.
Every user story needs at least one acceptance criterion, each independently testable with a true or false result, so the business analyst should elicit and validate the conditions of satisfaction with stakeholders before the story is considered ready for development. Deferring criteria to testers after the build leaves the team with no shared definition of success and invites rework. Deleting the story discards captured business need when the gap is simply missing criteria that can be elicited. Copying the definition of done supplies generic completion activities that apply to all stories and still leaves this story without its own testable conditions.

Question 17

Bloomington Caregivers' business analyst wants to demonstrate to the steering committee that the delivered solution meets the agreed requirements. Which two pieces of evidence are most appropriate? Choose 2 answers.
A. Completed test results showing each requirement's acceptance criteria were met.
B. The traceability matrix showing requirement-to-story-to-test coverage with nothing left unaddressed.
C. The number of story points the team completed per sprint throughout the release, tracked on the burndown chart.
D. The count of stakeholder interviews conducted during the discovery phase of the project, before the build began.
E. The size of the deployment package in the change set, measured by number of metadata components.

Accepted Answer

Correct answer: A. Completed test results showing each requirement's acceptance criteria were met. | B. The traceability matrix showing requirement-to-story-to-test coverage with nothing left unaddressed.
Evidence that a solution meets requirements comes from test results tied to acceptance criteria and from a traceability matrix proving every requirement has a story and a test with no gaps. Story points completed per sprint measure team throughput, which can be high while requirements remain unmet. The number of discovery interviews reflects effort spent eliciting needs, not whether those needs were delivered. Deployment package size is a purely technical measure and carries no information about business coverage.

Question 18

Cumulus Financial's steering committee must make a go/no-go decision for a Service Cloud release. Which two inputs should the business analyst provide? Choose 2 answers.
A. The status of user acceptance testing, including scripts passed, scripts failed, and the business impact of any open defects.
B. Confirmation of business readiness items such as end-user training completion and stakeholder sign-off.
C. The development team's story point velocity for the last three sprints, compared against the sprint average.
D. The number of stakeholders interviewed during the discovery phase of the project, months before the build began.
E. A commitment from the project team that no further defects will surface once the release goes live.

Accepted Answer

Correct answer: A. The status of user acceptance testing, including scripts passed, scripts failed, and the business impact of any open defects. | B. Confirmation of business readiness items such as end-user training completion and stakeholder sign-off.
A go/no-go decision needs an honest picture of test outcomes, including failures and the impact of open defects, alongside confirmation that the business itself is ready through training and formal sign-off. Velocity describes how fast the team delivered work and tells the committee nothing about whether the release is safe. The number of discovery interviews is historical effort, not readiness. Promising that no post-release defects will appear is not something anyone can guarantee and would misrepresent residual risk rather than describe it.

Free Salesforce Business Analyst
Practice Questions

What is the Business Analyst exam like?

Questions by exam section

Customer Discovery

Question 1 · Medium · Choose 3

Question 2 · Easier

Question 3 · Medium

Collaboration with Stakeholders

Question 4 · Medium

Question 5 · Medium

Question 6 · Easier

Question 7 · Medium · Choose 2

Business Process Mapping

Question 8 · Easier

Question 9 · Harder · Choose 2

Requirements

Question 10 · Medium · Choose 2

Question 11 · Medium

Question 12 · Medium

Question 13 · Harder · Choose 2

User Stories

Question 14 · Medium

Question 15 · Medium

Question 16 · Medium

Development Support and User Acceptance

Question 17 · Medium · Choose 2

Question 18 · Harder · Choose 2

Where to go after these 18 questions

Ready for a full Business Analyst practice exam?

Free Salesforce Business AnalystPractice Questions