SALESFORCE CERTIFICATION
Certified Business Analyst Practice Exam
Exam Number: 3713 | Last updated 14-Apr-26 | 2137+ questions across 6 vendor-aligned objectives
The Certified Business Analyst credential validates your ability to gather requirements, model business processes, and translate stakeholder needs into Salesforce solutions. Unlike administrator or developer exams, this one focuses squarely on the analytical and facilitation skills that make or break a Salesforce implementation.
The largest portion of the exam — 24% — focuses on Collaboration with Stakeholders, covering elicitation techniques, facilitation, and communication planning. Roughly 17% of the questions address customer discovery, covering stakeholder identification, business process analysis, and current-state documentation. Requirements Documentation carries the heaviest weight at 17%, covering user stories, acceptance criteria, and traceability matrices. Combined, these sections account for the lion’s share of the exam and reflect the skills employers value most.
The remaining sections balance the blueprint. Business Process Mapping commands 16% of the blueprint, which spans process modeling, data flow diagrams, and gap analysis. Nearly 13% of questions test User Stories, which spans story writing, prioritization, and backlog management. The User Acceptance domain weighs in at 13%, which spans UAT planning, validation, and sign-off processes. These areas may carry less weight on paper, but they often underpin the complex scenarios that distinguish passing candidates.
Every answer links to the source. Each explanation below includes a hyperlink to the exact Salesforce documentation page the question was derived from. PowerKram is the only practice platform with source-verified explanations. Learn about our methodology →
1009
practice exam users
97.5%
satisfied users
98.4%
passed the exam
4.8/5
quality rating
Test your Certified Business Analyst knowledge
10 of 2137+ questions
Question #1 - Assess and recommend stakeholder identification, business process analysis, and current-state documentation to align platform investments with measurable business outcomes and stakeholder priorities
A business analyst is starting a new Salesforce project for a logistics company. The project sponsor has a high-level vision but the detailed requirements are unclear.
What should the business analyst do first?
A) Conduct a stakeholder analysis to identify all relevant parties, then schedule discovery sessions to understand current processes and pain points
B) Start configuring Salesforce based on assumptions about logistics industry needs
C) Begin writing user stories based on the sponsor’s vision statement
D) Create a project timeline and budget estimate before gathering requirements
Show solution
Correct answers: A – Explanation:
Stakeholder analysis identifies everyone who influences or is affected by the project. Discovery sessions with these stakeholders uncover current processes, pain points, and requirements. Writing stories from a vision statement alone leads to gaps. Configuration without requirements wastes effort. Timelines cannot be accurately created without understanding scope. Source: Trailhead: Business Analysis
Question #2 - Discover and prioritize elicitation techniques, facilitation, and communication planning to align platform investments with measurable business outcomes and stakeholder priorities
A business analyst is facilitating a requirements workshop with 12 stakeholders from different departments. The discussion keeps going off-topic, and dominant voices are drowning out quieter participants.
What facilitation technique should the business analyst use?
A) Ask the project sponsor to direct the conversation
B) Cancel the workshop and switch to individual interviews only
C) Use structured facilitation techniques like timeboxing topics, round-robin input gathering, and parking lot for off-topic items
D) Let the discussion continue naturally and capture whatever comes up
Show solution
Correct answers: C – Explanation:
Structured facilitation maintains focus and ensures all voices are heard. Timeboxing keeps topics on track, round-robin ensures every participant contributes, and a parking lot captures off-topic items for future discussion. Unstructured discussion wastes time. Abandoning workshops loses cross-functional collaboration. Sponsor-directed conversations may bias outcomes. Source: Trailhead: Data Modeling
Question #3 - Design and deploy process modeling, data flow diagrams, and gap analysis to eliminate repetitive manual work and enforce consistent business logic across teams
A business analyst has documented a complex order management process that involves five departments. The stakeholders are struggling to understand the textual description of the process.
What artifact should the business analyst create to improve understanding?
A) A longer, more detailed textual description with additional context
B) A visual business process map using standard notation that shows swim lanes for each department, decision points, and handoffs
C) An email summary highlighting the most important steps
D) A spreadsheet listing every step in chronological order
Show solution
Correct answers: B – Explanation:
Visual process maps with swim lanes clearly show department responsibilities, handoffs, decision points, and process flow in a way that text cannot. Standard notation (like BPMN) ensures universal understanding. Longer text amplifies the original problem. Spreadsheets lack visual flow representation. Email summaries lose detail. Source: Trailhead: Flow Builder
Question #4 - Assess and recommend user stories, acceptance criteria, and traceability matrices to align platform investments with measurable business outcomes and stakeholder priorities
A business analyst is writing user stories for a Salesforce Service Cloud implementation. The development team complains that the stories are too vague and lack clear acceptance criteria.
How should the business analyst improve the user stories?
A) Add more technical implementation details to each story
B) Let the development team write their own stories based on the business requirements document
C) Make each story shorter to reduce ambiguity
D) Follow the standard format ‘As a [role], I want [goal], so that [benefit]’ and add specific, testable acceptance criteria using Given-When-Then format
Show solution
Correct answers: D – Explanation:
Well-structured user stories with the standard role-goal-benefit format plus Given-When-Then acceptance criteria provide clear intent and testable success conditions. Technical details belong in the implementation, not the story. Shorter stories increase ambiguity. Developer-written stories may miss business context. Source: Trailhead: Reports & Dashboards
Question #5 - Design and deploy process modeling, data flow diagrams, and gap analysis to eliminate repetitive manual work and enforce consistent business logic across teams
During a gap analysis, a business analyst discovers that the client’s requirement for automatic credit approval routing does not match any out-of-the-box Salesforce functionality.
What should the business analyst recommend?
A) Modify the requirement to match existing Salesforce features
B) Immediately request custom Apex development without exploring alternatives
C) Tell the client the requirement cannot be met and should be dropped
D) Document the gap, evaluate options including custom development, AppExchange solutions, and process workarounds, and present trade-offs to stakeholders
Show solution
Correct answers: D – Explanation:
Gap analysis should document gaps and evaluate multiple solution options with trade-offs (cost, time, risk, maintainability). Options include custom code, AppExchange packages, declarative workarounds, or process changes. Dropping requirements loses business value. Jumping to custom development ignores potentially simpler solutions. Modifying requirements without stakeholder agreement risks solving the wrong problem. Source: Trailhead: Change Management
Question #6 - Design and deploy process modeling, data flow diagrams, and gap analysis to eliminate repetitive manual work and enforce consistent business logic across teams
A business analyst is managing the requirements backlog for an agile Salesforce project. The product owner and two key stakeholders disagree on the priority of a feature related to automated reporting versus manual data entry improvements.
How should the business analyst help resolve this prioritization conflict?
A) Defer both features to a later release to avoid the disagreement
B) Let the product owner decide unilaterally since they own the backlog
C) Implement both features simultaneously to avoid the conflict
D) Facilitate a prioritization discussion using objective criteria like business impact, user reach, effort, and alignment with project goals
Show solution
Correct answers: D – Explanation:
Objective prioritization frameworks remove personal bias from decision-making. Evaluating features against criteria like business impact, number of affected users, implementation effort, and strategic alignment provides a data-driven basis for the decision. Unilateral decisions risk stakeholder disengagement. Implementing both may exceed capacity. Deferring avoids the problem without resolving it. Source: Trailhead: Data Quality
Question #7 - Design and deploy process modeling, data flow diagrams, and gap analysis to eliminate repetitive manual work and enforce consistent business logic across teams
A business analyst has completed requirements gathering and needs to ensure that all requirements are tracked through design, development, testing, and deployment.
What tool should the business analyst create?
A) A requirements traceability matrix that maps each requirement to its design component, test case, and deployment status
B) A risk register documenting potential project risks
C) A Gantt chart showing the project timeline
D) A project status email sent weekly to all stakeholders
Show solution
Correct answers: A – Explanation:
A requirements traceability matrix (RTM) ensures every requirement is tracked from origin through implementation and testing, preventing scope gaps and verifying complete coverage. Status emails communicate progress but do not track requirements. Gantt charts show schedule, not requirement coverage. Risk registers manage risks, not requirement fulfillment. Source: Trailhead: Strategy Design
Question #8 - Design and deploy process modeling, data flow diagrams, and gap analysis to eliminate repetitive manual work and enforce consistent business logic across teams
A business analyst is preparing a current-state data flow diagram for a client’s lead management process. The client uses three separate systems that exchange data through manual CSV exports.
What should the data flow diagram capture?
A) All data sources, destinations, manual and automated data transfers, transformation points, and data quality issues in the current state
B) A list of all fields that will be migrated to Salesforce
C) Only the Salesforce-specific data flows that will exist after implementation
D) The technical architecture of each system’s database schema
Show solution
Correct answers: A – Explanation:
Current-state data flow diagrams must capture the complete picture — all systems, data movement (manual and automated), transformation points, and quality issues. This baseline informs the future-state design and identifies integration requirements. Showing only future state skips root cause analysis. Field lists are too granular for data flow context. Database schemas are too technical for this artifact. Source: Trailhead: UX Design
Question #9 - Design and deploy process modeling, data flow diagrams, and gap analysis to eliminate repetitive manual work and enforce consistent business logic across teams
A business analyst is conducting a post-implementation review three months after a Salesforce Sales Cloud go-live. User adoption is lower than expected at 45%.
What analysis should the business analyst perform?
A) Recommend mandatory usage policies to force adoption to 100%
B) Analyze adoption data by user group, identify barriers through user feedback sessions, and compare delivered functionality against original requirements
C) Conclude that the project failed and recommend starting over
D) Wait another three months to see if adoption improves on its own
Show solution
Correct answers: B – Explanation:
Root cause analysis of low adoption requires examining adoption patterns by user group, collecting qualitative feedback on barriers (training gaps, workflow misalignment, usability issues), and verifying that delivered features meet actual needs. Mandatory policies create resentment without addressing root causes. Declaring failure is premature. Waiting loses critical momentum for corrective action. Source: Trailhead: Lightning Experience
Question #10 - Design and deploy process modeling, data flow diagrams, and gap analysis to eliminate repetitive manual work and enforce consistent business logic across teams
A business analyst is working on a Salesforce project where the client’s legal department requires that all business requirements be formally signed off before any development begins.
What approach should the business analyst take to balance formal sign-off with agile delivery?
A) Get sign-off on a complete, detailed specification document before starting any work
B) Skip the sign-off requirement since the project is agile
C) Abandon agile and switch to a purely waterfall methodology
D) Document requirements at an epic/feature level for formal sign-off, while using detailed user stories within sprints for iterative delivery
Show solution
Correct answers: D – Explanation:
A hybrid approach satisfies governance requirements while maintaining agile flexibility. High-level requirements (epics/features) receive formal sign-off, providing the legal team with documented approval. Detailed user stories within sprints allow iterative refinement. Pure waterfall loses agile benefits. Skipping sign-off violates organizational requirements. Complete specifications before work delays delivery and assumes perfect upfront knowledge. Source: Trailhead: Data Security
Get 2137+ more questions with source-linked explanations
Every answer traces to the exact Salesforce documentation page — so you learn from the source, not just memorize answers.
Exam mode & learn mode · Score by objective · Updated 14-Apr-26
Learn more...
What the Certified Business Analyst exam measures
- Assess and recommend stakeholder identification, business process analysis, and current-state documentation to align platform investments with measurable business outcomes and stakeholder priorities
- Discover and prioritize elicitation techniques, facilitation, and communication planning to align platform investments with measurable business outcomes and stakeholder priorities
- Design and deploy process modeling, data flow diagrams, and gap analysis to eliminate repetitive manual work and enforce consistent business logic across teams
- Assess and recommend user stories, acceptance criteria, and traceability matrices to align platform investments with measurable business outcomes and stakeholder priorities
- Implement and maintain story writing, prioritization, and backlog management to deliver reliable platform solutions that meet real-world business demands
- Deliver and support UAT planning, validation, and sign-off processes to deliver reliable platform solutions that meet real-world business demands
How to prepare for this exam
- Review the official exam guide for final preparation
- Complete the Business Analyst trail on Trailhead, emphasizing requirements gathering and process mapping modules
- Practice facilitating a requirements workshop — recruit colleagues to role-play stakeholders with competing priorities
- Lead or participate in the requirements phase of a Salesforce project, documenting user stories and acceptance criteria
- Focus first on Collaboration with Stakeholders at 24% — it is the single largest exam section
- Use PowerKram’s learn mode to practice scenario-based BA questions
- Run timed exams in PowerKram’s exam mode to build confidence
Career paths and salary outlook
Business analysts with Salesforce expertise are in high demand for implementation and optimization projects:
- Salesforce Business Analyst — $90,000–$130,000 per year, bridging business and technology teams (Glassdoor salary data)
- Senior Business Analyst — $110,000–$150,000 per year, leading complex requirements gathering across multiple clouds (Indeed salary data)
- Salesforce Product Owner — $115,000–$160,000 per year, owning the product backlog and prioritizing features (Glassdoor salary data)
Official resources
Follow the Business Analyst Learning Path on Trailhead. The official exam guide provides the complete blueprint.