Skip to content

How to Pass Salesforce Business Analyst Certification Exam?

How to Pass Salesforce Business Analyst Certification Exam?

Salesforce Certified Business Analyst Badge LogoThe Salesforce Certified Business Analyst certification exam is designed for Business Analysts with Salesforce experience. The successful candidate understands business needs, captures requirements, and collaborates with stakeholders to support the development of Salesforce solutions which drive business improvements.

1. About the Salesforce Business Analyst Certification Exam

  • Content: 60 multiple-choice/single-select questions and 5 non-scored questions
  • Time allotted to complete the exam: 105 minutes (time allows for unscored questions)
  • Passing Score: 72% (44 Questions out of 60)
  • Registration fee: USD 200 plus applicable taxes as required per local law
  • Retake fee: USD 100 plus applicable taxes as required per local law
  • Prerequisites: Salesforce Certified Administrator credential

2. Salesforce Business Analyst Certification Exam Guide

3. Salesforce Certified Business Analyst Exam Outline

Business Analyst Exam Outline

3.1 Customer Discovery: 17%

  • Determine business strategies, goals, initiatives, and challenges to define the scope of business analysis.
  • Discover how a customer is leveraging and benefiting from Salesforce products to establish the current state.
  • Understand and explain Business Analyst roles and responsibilities in different phases of the implementation lifecycle.
  • Apply the implementation lifecycle for planning business analysis activities.
  • Analyze the customer’s Salesforce environment to identify opportunities and constraints.
  • Demonstrate knowledge of Salesforce capabilities and its potential to recommend solutions to the business.

3.2 Collaboration with Stakeholders: 24%

  • Plan discovery activities based on the target stakeholders to perform a thorough analysis of business needs.
  • Identify key stakeholders and develop relationships with them as a trusted advisor to act as a liaison between business and technical teams.
  • Given a scenario, choose the most effective technique for eliciting business needs from stakeholders.
  • Explain how to move from current state analysis to an agreed future state design.
  • Understand how Salesforce features and best practices impact solution options and business processes.
  • Given a scenario, manage competing priorities to obtain sign-off from stakeholders. 

3.3 Business Process Mapping: 16%

  • Demonstrate how to define the scope of a complex business process and break it down into manageable steps.
  • Apply understanding of hierarchical process mapping to engage stakeholders at different levels of an organization.
  • Analyze and document a business process to elicit requirements and identify resources to visualize a future state.
  • Apply governance on agreed future state processes to control scope. 

3.4 Requirements: 17%

  • Distinguish between requirements vs. user stories to engage business and technical stakeholders.
  • Verify and prioritize existing requirements and identify new requirements to develop the future state.
  • Document requirements in a version controlled repository to manage scope.

3.5 User Stories: 18%

  • Understand the components of a user story to perform thorough analysis.
  • Contrast the difference between acceptance criteria vs. definition of done.
  • Document user stories in a version controlled repository to manage scope.

3.6 User Acceptance: 8%

  • Define and prepare the User Acceptance Test plan to confirm the solution meets the business requirements.
  • Guide UAT and manage the results to determine whether the solution meets the requirements.
  • Given a scenario, make a go/no-go release decision when new business or technical issues arise.

4. Salesforce Business Analyst Certification Exam Trailmix

5. Important Topics for Salesforce Business Analyst Certification Exam

Note: One important point to note about Salesforce Business Analyst exam is that usually Salesforce Certifications have questions where you have to select:

# One correct answer from four options

#Two correct answers from four options

# Three correct answers from five options

In Salesforce Business Analyst Certification exam you have to select one correct answer from three options.

5.1 Customer Discovery: 17% (10 Questions)

  • Salesforce business analysts help guide businesses to improve business processes and efficiency in Salesforce. They elicit, document, and analyze requirements around business challenges, and then produce data-driven solution.
  • Required Skills for Salesforce Business Analyst
    • Soft Skills
      • Needs analysis
      • Eliciting requirements
      • Business case definition
      • Requirements writing
      • Requirements review
      • Flow and process diagramming
      • Wireframing
      • Business data analytics
      • Problem solving
    • Technical Skills
      • AppExchange
      • Automation
      • Collaboration
      • Data management
      • Reports and dashboards
      • CRM
      • Platform
      • Sales and marketing
  • Key activities of Salesforce Business Analyst
    • Communication
    • Elicitation
    • Documenting requirements
    • Analyzing information
    • Facilitating solutions
    • Implementing solutions
    • Testing
  • Journey maps are documents that visually illustrate the experiences customers have with a business or an organization
  • Benefits of Journey Mapping
    • Better team alignment
    • Strategic thinking
    • Deeper understanding of customer pain points
    • Increased empathy
    • A strong case for innovation
    • A guide to measuring impact
  • Architecture of a Journey Map
    1. Phases
    2. Actions
    3. Thoughts
    4. Feelings
    5. Touchpoints
    6. Context
    7. Opportunities
  • Who to Invite to the Journey Mapping Workshop
    • People who know your customer
    • People who are generative
    • People who are optimists and realists
    • People who bring diversity
  • Consequence Scanning is a way for organisations to consider the potential consequences of their product or service on people, communities and the planet
  • Three Application Lifecycle management (ALM) development models.
    • Change set development
    • Org development
    • Package development
  • Benefits of Center of Excellence
    • Prioritize Across Teams
    • Streamline Processes
    • Plan for Growth
    • Reduce Risk
  • Top Skills of the Business Analyst
    • Information Discovery
    • Analysis and Synthesis
    • Communication, Collaboration, and Documentation
  • BA performs various types of analyses
    • Enterprise Analysis – learn and understand an organization’s structure, including who reports to whom
    • Strategy Analysis – identify the need of strategic or tactical importance
    • Stakeholder Analysis – individuals or groups who make decisions and who have an important role in determining the priorities and requirements
  • Tips for Engaging Stakeholders to Achieve Project Goals
    • Communicate by Making It a Conversation
    • Share How You Can Help
    • Get Commitment for Next Steps
    • Develop Relationships
  • Types of Documentation
Document TypeWhat It Is
Glossary of termsThis is a list of key terms and definitions that boosts understanding across teams involved in the project.
RACI chartRACI stands for responsible, accountable, consulted, and informed. It’s a matrix that delineates who is responsible for what in the context of the business analysis effort. 

Responsible: A person who performs an activity or does the work. 

Accountable: A person who is ultimately accountable for the outcome. 

Consulted: A person who needs to provide feedback or contribute to the activity.
Informed: A person who needs to know of a decision or action.
Interview and elicitation recordsThese documents capture important information from stakeholders.
Stakeholder analysisThis document identifies:
Who you should talk with to understand the business problem
Who can help flesh out the requirements
The individuals who can give you a range of perspectives
User storiesA user story describes the functionality that a business system should provide so that it can be developed. It is often called a ticket or work item. The format is “As a….  I want to…  So that I can…”
Use casesA use case identifies, defines, and organizes the system requirements from the perspective of a user.
Business analysis planThis plan lists all the business analysis activities that will take place throughout the project.
Current state analysisIf the current business process or domain is not well understood, the BA analyzes and documents the current state before scoping a project to improve upon it. 
Scope statement specificationThis is the most fundamental deliverable on any project. It is a clear definition of what needs to be achieved and the work that must be done to deliver the project or product.
Functional requirements specification (FRS)This is the business requirements that are defined from an end user or business perspective. It will specify the expected outcomes.
System requirements specification (SRS)This document details how the complete system should function and enumerates hardware, software, and functional and behavioral requirements of the system.
Gap analysis documentThis document describes the gaps between the current processes and the intended processes.
Change request logsThis document is a log of all the change requests in the project including date of request, requester, and any other key information.
Wireframes and other visual documentationThis document contains renderings of the user interface, often in the form of low-fidelity wireframes.
Test plans, test cases, or user acceptance test plansThese documents describe the test plans and detailed test cases that the team will use to validate the functional requirements.
Change managementThis document describes the method for pushing out changes to the business.
Types of Documentation
  • Salesforce Optimizer: a powerful, free, and simple tool that takes a snapshot of your Salesforce org and looks for potential problems in your implementation. 
  • Optimizer can help you address common challenges such as
    • I want to clean up my org, but I don’t know where to start.
    • My users are complaining about slow performance and busy page layouts.
    • What Salesforce governor limits am I approaching?
    • I can barely keep up with Salesforce’s releases. What new features am I missing out on?
    • We’re planning the move from Classic to Lightning Experience.
  • Most common and critical issues that Optimizer flags
    • Object with more than 350 fields
    • Too much automation (sharing, flows, validation rules) on a single object
    • Too many users with Modify All Data and Customize Application permissions
    • Multiple Triggers per Object
    • My Domain not activated
  • Lightning Usage App: lets you monitor adoption metrics, such as daily active users and the most visited pages in Lightning Experience. The available metrics include:
    • Daily and monthly active users in Lightning Experience and the Salesforce mobile app
    • Daily and monthly switches to Salesforce Classic by total number of switches and the number of unique users that switched
    • Profiles and users that switched to Salesforce Classic the most
    • Types of browsers used to access Lightning Experience and the Salesforce mobile app
    • Slowest desktop record pages
    • Pages viewed most often in Lightning Experience
    • Number of active user, feature, and permission set licenses

  • The User Interface box in the system overview page shows usage information for:
    • Custom apps
    • sites: Only published sites
    • Active Salesforce Sites
    • Flows: Only active flows
    • Custom tabs
    • Visualforce pages
  • Review Org Health: A Session (Exclusive to Premier and Signature Success Plan customers) where you’ll learn how to check your system’s overall health and get recommendations on how to improve it. A Salesforce expert who will guide you through this process:
    • Discovery
      • Discuss current challenges
      • Demonstrate and use Salesforce Optimizer and Security Health Check
    • Analysis
      • Assess key areas of platform performance, including declarative and programmatic customizations
      • Identify key areas of improvement and share best practices
    • Outcomes
      • Readout of Salesforce Org Health
      • Provide additional learning resources
  • A prototype is a first pass, a simple sketch of an idea you want to implement
  • Why Prototyping is important?
    • Prototypes make concrete the ideas that are in our heads
    • Prototypes are cheap and fast
    • Prototypes help creators take ownership of the solutions 

5.2 Collaboration with Stakeholders: 24% (14 Questions)

  • Scrum core values
    1. Focus
    2. Courage
    3. Openness
    4. Commitment
    5. Respect
  • Scrum Roles
    • The ScrumMaster
    • The Product Owner
    • The Team
    • The Shared Service Subject Matter Expert (SMEs)
    • The Technical Program Manager (TPMs)
    • The Functional Manager
  • Scrum elements of delivery
    • Product Backlog
    • Sprint Backlog
    • Potentially Shippable Work
  • Four key traits of Kanban
    • Visualize workflow
    • Limit work in progress (WIP)
    • Incremental and evolutionary change
    • Kanban includes metrics
      • Lead time: Average time to complete one item, sometimes called cycle time
      • Throughput: Amount of work completed in a single period of time
  • Key differences between the Scrum and Kanban workflow
Who prioritizes it?Product owner prioritizes on product backlogProduct owner prioritizes on product backlog
Where does it go?The product backlog is reordered for the next sprint.The product backlog is continuously reordered for the next available person with capacity.
When does the work start?During sprint planning, the team commits to the work in the next sprint.As soon as there is capacity to work on it.
Why is there a delay?Scrum focuses the team to deliver on their sprint commitments, and interruptions mid-sprint are discouraged.Kanban focuses on efficient flow of work, so the top of the backlog is always the next thing to be worked on.
How long does it take to deliver?It can be 2 weeks or more, depending on sprint status.As soon as it is completed.
Key differences between the Scrum and Kanban workflow
  • Empathy is the ability to recognize and understand others’ emotions, and take active interest in their concerns.
  • Difference between Sympathy and Empathy
    • Sympathy. A sympathetic response can include emotion, but it’s focused on keeping distance, makes a judgement about the person or how they should react, and doesn’t take the other person’s perspective into account.
    • Empathy. An empathetic response recognizes the other person’s perspective and emotions, communicates these back to them, and withholds judgement.
  • Guidelines for developing positive, healthy relationships at work
    • Accept and celebrate a diverse workplace
    • Develop active listening skills
    • Expand other communication skills
    • Take time to support those you lead
    • Manage technology and anticipate its impact
    • Share your wisdom and invite the wisdom of others
    • Develop honesty and trust
  • Process improvement is a set of best practices and steps to identify and simplify existing processes in a business. 
  • Sales enablement is the process of giving your sales team everything they need to close deals.
  • How do you succeed in sales enablement?
    • Goal Setting
    • Communication
    • Time Management
    • Content Creation
    • Learning and Development
    • Digital Transformation
    • Sales Enablement Plan
    • Stakeholder Commitment
    • Sales Enablement Team
  • Sales enablement best practices
    • Size your enablement to fit your needs
    • Lead from the top and be open to feedback
    • Build a sum that’s more than its parts
  • Content is:
    • product that requires research, design, development, delivery, and iteration.
    • system that connects people, processes, and technologies.
    • A set of data that must be structured and modeled.
    • business asset that can be tied to objectives, metrics, and results.
  • Content strategy helps you provide the right content to the right people in the right place at the right time… and for the right reason. 

5.3 Business Process Mapping: 16% (10 Questions)

  • Process mapping: Creates visual representations of business processes. It includes any activity that defines what a business does, who is responsible for what, how standard business processes are completed, and how success is measured.
  • Benefits of Process Mapping
    • Make understanding and communicating the process much easier among teams, stakeholders, or customers.
    • Help identify flaws in the process and where improvements should be made.
  • UPN (universal process notation) is a simple way to document processes
  • A process mapped using UPN answers, “Who needs to do what, when, why, and how?” at a glance

  • 5 Principles of UPN
    1. No more than 8-10 activity boxes on a screen
    2. Drill down from an activity box to a lower level to describe the detail
    3. Attach supporting information to an activity box
    4. View and edit controlled by access rights
    5. Version control and history of changes at a diagram level
  • Other Process Diagrams
    • Capability Models or Industry Blueprints: List out the high level process areas
    • Detailed Process Map: A flowchart that shows a drill-down version of a process that contains all the details of each step of the process and any subsequent steps along the way. 
    • SIPOC: A SIPOC map shows the key elements of a process such as Suppliers, Inputs, Process, Outputs, and Customers.
    • Value Stream Map: Used to visualize the flow of material and information that is needed to bring a product to the customer.
  • Why Business Analysis skills are important
    • Business analysis increases Salesforce adoption
    • Business analysis reduces rework
    • Business analysis impacts architecture
    • Business analysis increases agility and drives digital transformation
  • Jobs to Be Done (JTBD) is a framework designed to help us define success from a customer perspective. It starts with a deeper inquiry that seeks to answer a simple question: What jobs are customers hiring your product or service to do for them?

5.4 Requirements: 17% (10 Questions)

  • Requirements elicitation is the practice of researching and discovering the requirements of a system from users, customers, and other stakeholders.
  • Requirement Elicitation techniques
    • Brainstorming
    • Document analysis
    • Focus groups
    • Interface analysis
    • Interviews
    • Observation
    • Process modeling
    • Prototyping
    • Requirements workshops
    • Surveys/questionnaires
  • Stakeholders to engage for business alignment
    • Program Executive Sponsor
    • Senior IT & Business Leaders
    • Middle Management
    • End Users
  • Setup Audit Trail tracks the recent setup changes that you and other admins make
  • To view the audit history, from Setup, in the Quick Find box, enter View Setup Audit Trail, then select View Setup Audit Trail.
  • To download your org’s complete setup history for the past 180 days, click Download. After 180 days, setup entity records are deleted.

5.5 User Stories: 18% (11 Questions)

  • Three components of every user story
    • Who: From whose perspective (aka user persona) within Salesforce will this user story be written?
    • What: What goal will be accomplished or implemented within the Salesforce org as the result of the user story?
    • Why: Why does the user need the Salesforce functionality or feature outlined in the user story?
  • Acceptance criteria are a set of statements, each with a clear pass/fail result, added to a user story.
  • Acceptance criteria should state intent, but not a solution.

  • Acceptance criteria benefits:
    • Clarifying the scope for the project team
    • Assisting the development/implementation team
    • Ensuring testers know what should be tested
  • A successful user story is (INVEST):
    • Independent
    • Negotiable
    • Valuable
    • Estimable
    • Small
    • Testable
  • Mistakes to avoid when writing a user story
    • The project team didn’t engage in story writing
    • The who of the user story is an undefined user
    • The why in the user story is feature specific
    • The acceptance criteria is too vague
    • The user story was assigned to the implementation team without a team discussion
  • Scaled Agile Center of Excellence basic principles are:
    • Integrate every 2 weeks (once per sprint) and test all apps together to demo the new features to the Product Owners on one single sandbox.
    • If we need to re-prioritize or move user stories to the next sprint, we must ensure that an equivalent amount of effort with the lowest priority, goes back to the backlog.
    • The last Sprint is used to stabilize the app, not to add new features.- As an example, at the end maybe only 70% of the app will be done on time, but that’s Ok. If the prioritization was done correctly, the MVP will have been achieved with the 70%.
    • Low priority user stories which couldn’t be completed will be moved to the next release window.
  • Debug Log: contains information about each transaction, such as whether it was successful and how long it took.
  • To view a debug log, from Setup, enter Debug Logs in the Quick Find box, then select Debug Logs.

5.6 User Acceptance: 8% (5 Questions)

  • Testing Types
    • Unit Tests: Focus on the smallest bits (also known as units) of low-level code you’ve added to your org
    • Integration Tests: Required if you have code interacting with anything not native in your org.
    • Functional Tests : verify that features work as defined in your technical requirements
    • User Acceptance Tests (UAT): End-user testing performed in a sandbox or test environment to verify that a project or enhancement works as intended, and what was originally requested is actually being delivered. 
    • Performance Testing: Evaluates how your system responds when large volumes of records or operations are being handled.

  • Some of the key responsibilities of Business Analyst during UAT phase are:
    • Validate test data setup
    • Identify UAT testers
    • Coordinate UAT sessions
    • Write UAT test scripts
    • Triage UAT defects
    • Get UAT sign off
  • Scope UAT for large data volume scenarios should include:
    • Volume: production like data or a sample data
    • Average vs Peak performance: Should the test simulate both average and peak load and measure associated performance
    • Load simulation pattern and equipment: How test going to simulate the required loads and how realistic is the simulation?
    • Actual production data vs test data: Does the test have all the variants of data points that an actual production data exhibit? 
    • Timing of the tests: Tests should be conducted at least three to four weeks before the actual live date, so that there is sufficient time to fix bugs
  • Key preparatory steps involved in conducting performance tests:
    • Test environment: Designate a dedicated sandbox environment for conducting the load tests
    • Static load simulator: Test should have a way to simulate static load anticipated on the platform 
    • Dynamic request simulator:  Methodology and frequency by which the dynamic requests are simulated
    • Metrics and measuring performance: Clarity in terms of metrics that are going measured during tests and the associated tools and data points are suitably captured 

6. Salesforce BA Exam Practice Questions and Flashcards

7. Additional Resources

Salesforce Business Analyst Certification

Recommend Articles

18 thoughts on “How to Pass Salesforce Business Analyst Certification Exam?”

  1. Extremely useful as an exam prep. Great to freshen up on concepts right before taking the exam. I passed on my first attempt.

  2. This is very crisp and precisely put together.
    Thanks you !
    Would someone recommend any additional reading or just the official resource ?

  3. Great initiative has been taken and also share the informative detail on BA analytics certification documents.

    Could you please share the B2C commerce architect certification related documents?

  4. Great article! Please share any other tips that you have for the cert preparation. There are no flashcards or lot of information out there except few and the trailmix. This article is definitely very helpful overall.

Please Leave a Comment