Important Salesforce Certified Business Analyst (BA-201) Exam Questions

Answer: B

Explanation:

The level of detail that the business analyst should use for the process map and why is somewhat detailed. This is because the process map should provide enough information to guide new users through the onboarding process, but not overwhelm them with too much detail that may be irrelevant or unnecessary. Since the process will be repetitive, new users will learn and remember the details over time, and they can always refer back to the process map if needed. The process map should include the main steps, decisions, inputs, outputs, and roles involved in the onboarding process, as well as any exceptions or variations. The process map should also use clear and consistent terminology, symbols, and notation to ensure readability and understanding. Reference: https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/business-process-mapping

Answer: C

Explanation:

This answer states that following these steps is the process that the BA should follow to draft and finalize the requirements for implementing a new Service Cloud feature for Cloud Kicks. Reviewing information from the discovery means that the BA revisits the information or data that was collected during the discovery phase, such as business goals, stakeholder needs, pain points, opportunities, etc. Asking clarifying questions means that the BA seeks to understand and verify the information or data that was collected, and to resolve any ambiguities or conflicts among them. Drafting requirements means that the BA writes down the statements that describe what the solution must do or have to meet the business goals and stakeholder needs. Refining and confirming requirements means that the BA revises and validates the requirements with the stakeholders, and ensures that they are clear, concise, consistent, and complete. Prioritizing which requirements will be included in the minimum viable product means that the BA determines which requirements are essential or desirable for delivering a solution that provides value to the stakeholders, and which requirements can be deferred or excluded from the scope. Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements

Answer: C

Explanation:

This answer states that using Salesforce terminology and language is what the BA should recommend to the project team to increase understanding when documenting requirements, process and potential solutions for reviewing the existing Salesforce manufacturing solution that has low adoption and a variety of customization including custom objects, custom fields, renamed standard fields. Salesforce terminology and language are the words and phrases that are commonly used in the Salesforce ecosystem, such as objects, fields, records, apps, tabs, profiles, roles, etc. Using Salesforce terminology and language can help the BA to communicate and document the requirements, process and potential solutions in a consistent and accurate way, and avoid confusion or misunderstanding among the project team members who are familiar with Salesforce. Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements

Answer: C

Explanation:

Users is the User Management term that is best described by this definition: ''Record created to identify a new employee that starts accessing Salesforce''. Profiles are User Management terms that define what users can do within an organization based on their job function and responsibilities. Roles are User Management terms that control data visibility and reporting hierarchy within an organization based on users' positions. Usernames are User Management terms that identify users when they log in to Salesforce. Reference: https://help.salesforce.com/s/articleView?id=sf.users_def.htm&type=5

Answer: A

Explanation:

This answer states that creating a value stream map is what the BA should do to engage stakeholders for improving the new customer onboarding experience at Cloud Kicks which involves complex handoffs between teams. A value stream map is a type of process map that shows how value flows from a customer request to a product or service delivery across different teams or departments. Creating a value stream map means that the BA works with stakeholders from different teams or departments to identify and visualize their inputs, outputs, activities, roles, etc. related to customer onboarding. Creating a value stream map is what the BA should do to engage stakeholders for improving customer onboarding because it helps them to collaborate and communicate their perspectives and expectations, and to discover and eliminate waste or inefficiencies in customer onboarding. Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-process-mapping-to-understand-your-business