The Salesforce Business Analyst exam preparation guide is designed to provide candidates with necessary information about the Business Analyst exam. It includes exam summary, sample questions, practice test, objectives and ways to interpret the exam objectives to enable candidates to assess the types of questions-answers that may be asked during the Salesforce Certified Business Analyst exam.
It is recommended for all the candidates to refer the Business Analyst objectives and sample questions provided in this preparation guide. The Salesforce Business Analyst certification is mainly targeted to the candidates who want to build their career in Salesforce Consultant domain and demonstrate their expertise. We suggest you to use practice exam listed in this cert guide to get used to with exam environment and identify the knowledge areas where you need more work prior to taking the actual Salesforce Business Analyst exam.
Salesforce Business Analyst Exam Summary:
|
Exam Name
|
Salesforce Business Analyst |
| Exam Code | Business Analyst |
| Exam Price |
Registration fee: USD 200 Retake fee: USD 100 |
| Duration | 105 minutes |
| Number of Questions | 60 |
| Passing Score | 72% |
| Recommended Training / Books |
Prepare for Your Salesforce Business Analyst Credential Salesforce Business Analyst Certification Prep |
| Schedule Exam | Kryterion Webassessor |
| Sample Questions | Salesforce Business Analyst Sample Questions |
| Recommended Practice | Salesforce Certified Business Analyst Practice Test |
Salesforce Business Analyst Syllabus:
| Section | Objectives | Weight |
|---|---|---|
| Customer Discovery |
- 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. |
17% |
| Collaboration with Stakeholders |
- 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. |
24% |
| Business Process Mapping |
- 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. |
16% |
| Requirements |
- 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. |
17% |
| User Stories |
- 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. |
18% |
| User Acceptance |
- 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. |
8% |