Salesforce Certified Business Analyst Free Sample Questions
Description
Covers business strategy and current state analysis, stakeholder elicitation and relationship building, process mapping and documentation, requirements and user stories, and UAT validation.
20 free sample questions203 in the full practice test Other version: BA-201(120)
Collaboration with Stakeholders · Elicitation Techniques
Momentum Financials, a wealth management firm, is undertaking a digital transformation project on Salesforce. The project sponsor, the VP of Client Relations, is highly influential but has limited availability. The lead Business Analyst (BA) needs to gather strategic goals. Which elicitation technique is most appropriate for this specific stakeholder?
Answer and explanation
Correct answer: B
For a high-influence, low-availability stakeholder like a VP, structured one-on-one interviews are the most effective technique. They respect the stakeholder's time by being focused and concise, while allowing the BA to gather critical strategic information directly. A multi-day workshop is impractical for their schedule, sending a survey is too impersonal for a project sponsor, and observation is irrelevant for gathering strategic goals.
Q2Question 2
IntermediateMultiple answers
Business Process Mapping · Current State Analysis
A business analyst (BA) is documenting the 'As-Is' process for a global company's convoluted expense reporting system. The process varies significantly by region and involves multiple legacy systems. The goal is to consolidate onto a single Salesforce solution. Which TWO actions are critical for the BA to take during this phase? (Select TWO)
Answer and explanation
Correct answers: B, D
To create a successful consolidated solution, the BA must understand the full scope of the current state, which includes all regional variations and exception paths. Ignoring them leads to a future state that fails to meet the needs of all users. Identifying pain points is crucial for justifying the project and designing a better future state.
Identifying pain points and inefficiencies is a core purpose of As-Is analysis; it provides the 'why' for the change and informs the requirements for the To-Be process. Documenting regional variations is also critical to ensure the new global solution accommodates necessary local differences.
Q3Question 3
Beginner
User Stories · Acceptance Criteria
True or False: A well-formed user story's acceptance criteria should primarily describe the technical implementation steps for the developer to follow.
Answer and explanation
Correct answer: B
Acceptance criteria should define 'what' the system must do to fulfill the user's need from a functional perspective, not 'how' it should be built. They describe the conditions of satisfaction that are testable and business-focused, leaving the technical implementation details to the development team.
Q4Question 4
Advanced
Collaboration with Stakeholders · Managing Competing Priorities
During a requirements validation session for a new Service Cloud implementation, the head of customer support insists on a feature for 'real-time case sentiment analysis.' The development lead states this would require a costly integration with a third-party AI service, pushing the project over budget and past its deadline. The head of sales argues that budget should instead be used to improve lead routing. As the BA, what is the most effective next step?
Answer and explanation
Correct answer: B
The BA's role is not to make unilateral decisions on competing priorities between department heads, but to facilitate a resolution. The most appropriate action is to clearly document the requirements, their impacts (cost, timeline), and the conflict, then present this information to the project sponsor or steering committee who has the authority to make a strategic decision based on overall business value and priorities.
A BA is analyzing a Salesforce org for a nonprofit that has been using it for five years with multiple, untrained administrators. They find over 300 reports in a folder named 'Important Reports,' many of which are duplicates or have no recent run history. This is causing user confusion and impacting adoption. What Salesforce tool should the BA recommend first to analyze the current state of reports and dashboards?
Answer and explanation
Correct answer: C
Salesforce Optimizer is the primary tool for analyzing an org's implementation and identifying ways to improve features, clean up customizations, and drive user adoption. It provides specific insights into areas like unused reports and dashboards, which directly addresses the problem described. Health Check is for security, and Setup Audit Trail tracks metadata changes, not usage.
Q6Question 6
Beginner
User Stories · User Story Components
A project team is using Agile methodology. The BA has written the following user story: 'As a Sales Manager, I want a dashboard to see my team's performance so that I can provide better coaching.' Which component is essential to add before this story can be considered 'Ready' for development?
Answer and explanation
Correct answer: D
A user story is not considered 'Ready' for development until it has clear, testable acceptance criteria. These criteria define the specific conditions that must be met for the story to be considered complete from the user's perspective. They remove ambiguity and provide the basis for testing.
Q7Question 7
Intermediate
Development Support and User Acceptance · User Acceptance Testing (UAT)
A BA is preparing for User Acceptance Testing (UAT) for a new custom Flow that automates opportunity stage updates. The business stakeholders who will be testing are non-technical and unfamiliar with formal testing processes. What is the BA's most critical responsibility to ensure UAT is successful?
Answer and explanation
Correct answer: B
For non-technical testers, the BA's most critical role is to remove ambiguity and make the process as easy as possible. Detailed test scripts that outline exact steps to follow (e.g., '1. Create a new Opportunity with Amount > $50,000. 2. Set Stage to 'Negotiation.' 3. Click Save.') and define what the expected outcome should be (e.g., 'The Stage automatically updates to 'Awaiting Approval'') are essential for enabling testers to validate the solution against the requirements effectively.
Q8Question 8
Intermediate
Requirements · Understanding Scope, Requirements, and User Stories
Which of the following best distinguishes a business requirement from a functional requirement?
Answer and explanation
Correct answer: B
This is the core distinction. A business requirement states the 'why' from the business perspective (e.g., 'Reduce average case resolution time by 15%'). A functional requirement describes a specific capability the system must have ('what') to help achieve that goal (e.g., 'The system must automatically route high-priority cases to a specialized queue').
Q9Question 9
Intermediate
Customer Discovery · Business Strategy and Goal Analysis
A BA at AquaSphere Solutions is defining the scope for a project to implement Salesforce CPQ (Configure, Price, Quote). The sales team wants complex bundling and pricing rules, while the finance team needs accurate revenue recognition reporting. The project has a fixed deadline. Which artifact is most crucial for documenting and gaining agreement on the project's boundaries?
Answer and explanation
Correct answer: C
A formal scope statement is the primary artifact for defining and agreeing upon project boundaries. It explicitly states what is included and, just as importantly, what is excluded from the project. For a complex implementation like CPQ with competing stakeholder interests and a fixed deadline, a clear, signed-off scope statement is essential to prevent scope creep and manage expectations.
Q10Question 10
Advanced
Customer Discovery · Salesforce Capabilities and Solution Recommendation
Case Study:
Company Background: Zenith Dynamics, a rapidly growing B2B manufacturing company, uses Sales Cloud for managing its sales pipeline. They have a direct sales team, a partner channel, and an inside sales team, all of whom use the same Opportunity record type and page layout. The company prides itself on its consultative sales approach, which involves multiple stages of technical validation and solution architecting.
Current Situation: Sales leadership is complaining about a lack of visibility into the distinct sales processes for each channel. The single page layout is cluttered with fields that are irrelevant to certain teams, leading to poor data quality. Partners, in particular, are frustrated with the complexity of creating and updating opportunities. The VP of Sales has stated a key business goal: 'I need to be able to forecast accurately for my direct, partner, and inside sales channels independently.'
Requirements: The solution must provide a tailored user experience for each sales team. It needs to capture different data points and follow distinct sales stages for each channel. Leadership requires separate reporting and forecasting capabilities for each channel. The solution should be implemented using declarative tools to minimize long-term maintenance overhead.
Question: As the business analyst on this project, which solution would you recommend to meet Zenith Dynamics' requirements?
Answer and explanation
Correct answer: C
This is the standard, best-practice Salesforce solution for this exact business problem. Sales Processes control the picklist values for the Opportunity Stage field. Record Types tie together different Sales Processes and Page Layouts. This combination allows for distinct stages, fields, and user experiences for each sales channel on the single, standard Opportunity object, which is critical for unified reporting while still allowing for channel-specific forecasting.
Register free for 10 more questions
Or unlock all 203 certified-business-analyst questions with explanations, timed mode and flashcards.
