10 free Salesforce Business Analyst practice questions with the correct answer and a full explanation for each, taken from the CertStash pack of 231 questions. Work through them, then open each answer to check your reasoning.
Get all 231 questions (US$39) · Download these 10 as a PDF
Question 1
Cloud Kicks (CK) wants its sales team to use Sales Cloud to decrease its lead conversion time. The business analyst (BA) will analyze and break down CK's typical sales cycle.
How can process mapping help the BA get started on this project?
Show answer and explanation
Correct answer: A. It can show the relationship between the steps and actions in the sales cycle to communicate and understand the current state, and to identify areas for improvement.
actions in the sales cycle to communicate and understand the current state, and to identify areas for improvement. Process mapping is a visual technique that illustrates the sequential steps and relationships in a workflow. It enables the BA to communicate the current state of the sales cycle clearly to stakeholders, identify inefficiencies and bottlenecks, and pinpoint specific areas where Sales Cloud can provide improvements. This foundational understanding is essential before designing solutions.
Why the other options are wrong
- B. While modeling changes and analyzing impact are important, they occur after process mapping reveals the current state; this describes activities that follow process mapping, not what process mapping itself accomplishes.
- C. Process mapping does not directly display project timelines; it focuses on workflow steps rather than project scheduling or timeline visualization.
Question 2
One retail location of Cloud Kicks has been getting complaints from shoppers about being unable to find items in the store. The general manager has asked IT to configure tablets for the sales clerks so they can move freely around the store to assist customers.
The IT team writes a functional requirement:
Tablets running the Salesforce mobile app must allow users to access store inventory records which Include current item count and item location.
Which user story should the business analyst write to describe the functional requirement,
Show answer and explanation
Correct answer: B. As a sales clerk, I want to see item availability and locations to help customers find items.
locations to help customers find items. A user story should be written from the perspective of the end user who directly benefits from the functionality. The sales clerk is the actual user who needs to access inventory information to perform their job. The user story format 'As a [role], I want [capability] so that [benefit]' with the sales clerk as the role directly maps to the functional requirement about accessing store inventory records.
Why the other options are wrong
- A. The general manager is not the end user who will directly interact with the tablets to access inventory; they are a stakeholder but not the primary beneficiary of this functionality.
- C. While customers benefit indirectly, they are not the users accessing the system; the story should focus on the sales clerk who is the actual system user interacting with the tablets.
Question 3
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?
Show answer and explanation
Correct answer: C. Work with business stakeholders to collaborate in writing, reviewing, and executing UAT scenarios, providing feedback, and approval for release.
writing, reviewing, and executing UAT scenarios, providing feedback, and approval for release. User acceptance testing is most effective when business stakeholders are directly involved in writing, reviewing, and executing test scenarios. Their participation ensures that UAT validates real business requirements and user workflows. The BA facilitates this collaboration rather than handing off ownership entirely or restricting input to QA analysts alone.
Why the other options are wrong
- A. Completely handing off ownership to business stakeholders removes the BA's critical role in facilitating, guiding, and ensuring alignment between business needs and test execution.
- B. While QA analysts contribute to UAT execution, they should not be the primary collaborators for writing and reviewing scenarios; business stakeholders must drive this process to ensure business relevance.
Question 4
Cloud Kicks is planning to create a new Service Cloud console app for its services team to resolve issues with delayed shipments to customers.
The business analyst (BA) wrote the user stories based on a written list of requirements provided by the manager of the services team. Upon stakeholder review with the entire services team, many of the user stories were rejected and the BA had to revise them.
When the BA wrote the initial user stories, what was the likely cause of the issue?
Show answer and explanation
Correct answer: B. The project team failed to discuss the user stories as a group.
a group. User stories rejected by the entire services team indicate that the initial stories did not reflect the team's actual needs and perspectives. This suggests the BA wrote stories based solely on a manager's written requirements without collaborative discussion with the full team. Engaging the entire services team during story creation ensures diverse viewpoints are captured and stories are accepted by those who will use the system.
Why the other options are wrong
- A. Well-defined personas would actually help ensure user stories address real user needs and are less likely to be rejected; the problem was the opposite, insufficient stakeholder involvement, not overly-focused personas.
- C. Acceptance criteria being too specific would not typically cause widespread rejection; rather, vague or misaligned acceptance criteria would be the concern when stories are rejected.
Question 5
After the first round of user acceptance testing for a Sales Cloud project, the business analyst discovered that a high number of test cases failed.
What is a possible reason why the test cases failed?
Show answer and explanation
Correct answer: A. Missing test script details
Test cases fail when they lack sufficient detail in test scripts, including unclear steps, missing preconditions, ambiguous expected results, or insufficient data specifications. These details are necessary for testers to execute tests accurately and determine whether the system meets requirements. Missing script details directly cause test execution failures.
Why the other options are wrong
- B. Missing test result details would be discovered after test execution, not a cause of initial test failures; results are captured after running tests, not before.
- C. Missing test org access details would prevent test execution from beginning, but would be identified during test setup rather than manifesting as a high number of test case failures during execution.
Question 6
As a business analyst (BA) starts engaging stakeholders for a user story writing workshop, an executive sponsor questions why the Commerce Cloud project is creating user stories rather than standard requirements.
What is one benefit of creating user stories that the BA can share with the executive sponsor?
Show answer and explanation
Correct answer: C. It saves time when prioritizing and implementing functionality.
functionality. User stories provide business value through their concise, role-based format that enables faster prioritization discussions and phased implementation. Because stories focus on user needs rather than technical specifications, teams can quickly assess which capabilities deliver the most business value and implement them incrementally, saving time in both prioritization and delivery cycles.
Why the other options are wrong
- A. While user stories do inform testing, helping testers determine validation methods is a secondary benefit; the primary advantage is improved prioritization and implementation efficiency.
- B. User stories explicitly avoid defining technical specifications early; they describe what users need, leaving technical implementation decisions to the development team.
Question 7
The project team at Universal Containers has started to review the existing Salesforce manufacturing solution that has low adoption and a variety of customizations including custom objects, custom fields, renamed standard objects, and renamed standard fields.
What should the business analyst recommend to the project team to increase understanding when documenting requirements, processes, and potential solutions?
Show answer and explanation
Correct answer: B. Use customer terminology and language.
In an organization with extensive customizations and renamed objects and fields, the business analyst must use the customer's own terminology to ensure clear communication with stakeholders. Using customer-specific language prevents confusion about what standard terms refer to in their system and ensures requirements are documented in terms the business actually uses and understands.
Why the other options are wrong
- A. Industry terminology may not align with how this specific customer has customized and renamed their system components, potentially causing miscommunication.
- C. While Salesforce terminology is important for technical documentation, stakeholders understand their own business language better and should be engaged in their familiar terminology; using Salesforce terms could confuse business stakeholders.
Question 8
The Salesforce development team is strictly following scrum to govern its releases. An executive trying to plan a vacation wants to know when work on the feature will begin so they can be available for additional implementation questions. After consulting with the product owner, the business analyst (BA) learns the team has decided to adopt Kanban instead for all future releases.
What should the BA tell the executive?
Show answer and explanation
Correct answer: B. Work will begin when capacity becomes available.
Kanban is a pull-based system where work begins when capacity becomes available, not on a fixed schedule like sprint-based Scrum. In Kanban, items flow from the backlog into active work as team members complete current tasks. The executive cannot predict a specific start date based on a pre-planned sprint; instead, work will be pulled into development when the team has available capacity.
Why the other options are wrong
- A. Work in Kanban is not gated by executive approval at the start of each item; approval typically occurs earlier in the process before items enter the backlog.
- C. Kanban does not use sprints; this answer reflects Scrum terminology and is incompatible with the team's adopted Kanban methodology.
Question 9
A business analyst at Universal Containers has begun user acceptance testing for a new Experience Cloud implementation with the project team.
A major gap for one of the personas was identified in the documented scenarios.
What went wrong?
Show answer and explanation
Correct answer: A. Failure to include all stakeholders in the requirements gathering process
gathering process A gap identified during user acceptance testing in documented scenarios indicates that the requirements gathering phase failed to capture all necessary user needs and personas. This occurs when stakeholders representing all user groups are not included in the initial requirements process. Unit testing (B) validates code functionality, not requirements alignment. Validating against functional requirements (C) is what UAT does, but the problem originated earlier in requirements definition.
Why the other options are wrong
- B. Unit testing focuses on code quality and individual component functionality, not on whether business requirements were properly captured.
- C. Validating against functional requirements is a UAT activity, but it cannot catch gaps that exist in the documented requirements themselves due to missing stakeholder input.
Question 10
Northern Trail Outfitters has a large Salesforce org with sales, marketing, and billing teams pushing for the development of a large number of items in the backlog.
Which management process should the business analyst suggest to help the teams align on their competing priorities?
Show answer and explanation
Correct answer: A. Vision, Values. Methods, Obstacles, and Measures (V2MOM)
(V2MOM) V2MOM (Vision, Values, Methods, Obstacles, and Measures) is a strategic planning and alignment methodology used to help teams with competing priorities align around a common vision and shared goals. BPMN (B) is a notation for modeling business processes, not for priority management. IDEF3 (C) is a process modeling technique focused on capturing process details, not organizational alignment or priority prioritization.
Why the other options are wrong
- B. BPMN is a visual notation for documenting and analyzing business processes, not a management tool for aligning competing priorities.
- C. IDEF3 is a process description capture method used for detailed process modeling, not for strategic alignment or priority management.
That was 10 of 231.
The full Salesforce Business Analyst pack has all 231 questions, each with the answer, the explanation and why the other options are wrong, plus a questions-only copy for timed runs. US$39, paid once, with free monthly updates and a pass-or-your-money-back guarantee.