Practice Free BA-201 Exam Online Questions
During a requirements gathering session, two stakeholders discuss the names of the fields they want to see when adding leads to the system. Each stakeholder has a different point of view on field names.
What should the business analyst do to help Influence the team and accurately capture the requirements?
- A . Find a middle ground where both stakeholders are satisfied with the field names.
- B . Ask the executive sponsor to make the final field name decisions.
- C . Allow the development team to make the final field name decisions.
A
Explanation:
The business analyst should find a middle ground where both stakeholders are satisfied with the field names, as this would ensure that the requirements are accurately captured and reflect the needs of the business. The business analyst should facilitate a discussion between the stakeholders to understand their perspectives and preferences, and help them reach a consensus on the field names. This would also foster collaboration and trust among the stakeholders, and avoid potential conflicts or confusion later in the project.
Reference: Learn About the Salesforce Business Analyst Role: This reference explains the key activities and skills of a Salesforce business analyst, including communication, elicitation, documenting requirements, and analyzing information.
Field Names: This reference provides guidelines on how to format and display field names in documentation and user interface text.
A business analyst at Universal Containers has begun user acceptance testing for a new Experience Cloud implementation with the project team. A major gap for one of the personas was identified in the documented scenarios.
What went wrong?
- A . Failure to include all stakeholders in the requirements gathering process
- B . Failure to perform thorough unit testing during the development process
- C . Failure to validate the application against the functional requirements
Northern Trail Outfitters (NTO) has completed a project with a third-party event organization platform to enhance its MVP Experience Site. Many features were left in the project backlog. NTO’s IT team is beginning a new phase of work on the Experience Site to build additional features requested by business stakeholders and wants to include the items that were left in the backlog in the first phase.
How should the business analyst coordinate the user stories to most efficiently manage the new project timeline?
- A . Include existing and new user stories to be completed within the duration of the project. Hire additional developers to accommodate both work streams to prevent delays within the schedule sprints.
- B . Reprioritize existing and new user storks to place the stories into each sprint of the project. Return an equivalent: amount of lower priority work to the project backlog,
- C . Prioritize user stories for the new enhancements for the initial sprints of the project to accommodate business stakeholder requests. Complete existing user stories in the final sprint of the project.
The development team at Universal Containers is reviewing several stories to be added to the current sprint. The team is having trouble with a particular story about an Opportunity email alert and is unsure about which type of testing is needed.
What should the business analyst review and revise to provide more clarity to the team?
- A . Definition of done
- B . User persona
- C . Acceptance criteria
C
Explanation:
The document that the BA should review and revise to provide more clarity to the team is acceptance criteria. Acceptance criteria are statements that define what conditions or requirements must be met for a user story or sprint to be accepted by the user or stakeholder. Acceptance criteria help to clarify the scope, functionality, and quality of the user story or sprint, provide a basis for testing and validating the work done, and ensure that it meets the user’s needs and expectations. By reviewing and revising acceptance criteria for the user story about an Opportunity email alert, the BA can provide more clarity to the team about what type of testing is needed.
Reference: https://trailhead.salesforce.com/en/content/learn/modules
The Cloud Kicks admin is getting ready to release a record-triggered flow that auto-generates Renewal Opportunity Order Line Items once an Opportunity is Closed/Won for a sales team user story.
During user acceptance testing, what should the business analyst do to ensure the solution fulfills the needs of the sales team?
- A . Draft a list of test cases and scripts and choose "Run flow as another user” to debug the flow as a sales team user to identify and fix bugs.
- B . Choose subject matter experts as testers and prepare a sandbox with quality test data, test cases, and scripts that match real-world scenarios.
- C . Collaborate with the admin and a power user to test the flow for scalability, robustness, and maintainability in a sandbox.
B
Explanation:
User acceptance testing is 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. To ensure that the solution fulfills the needs of the sales team, the business analyst should choose subject matter experts as testers and prepare a sandbox with quality test data, test cases, and scripts that match real-world scenarios. Subject matter experts are users who have extensive knowledge and experience with the business domain and processes. They can provide valuable feedback and insights on whether the solution meets their expectations and requirements. A sandbox is a copy of a production environment where users can test changes without affecting live data or users. Quality test data is data that is realistic, relevant, and representative of what users will encounter in production. Test cases are descriptions of specific scenarios or situations that users will perform with the solution. Test scripts are step-by-step instructions on how to execute each test case.
Reference: 1 https://trailhead.salesforce.com/en/content/learn/modules/user-acceptance-testing-video/learn-about-user-acceptance-testing
A business analyst (BA) is working with the support team at Cloud Kicks (CK) on a Service Cloud implementation. The BA has decided to create a process map to understand CK’s current merchandise return process.
What are the top three benefits of creating a process map?
- A . Engages stakeholders, identifies improvements, and starts the change process
- B . Builds accountability, increases revenue, and decreases overall time spent on requirements
- C . Identifies improvements, decreases project costs, and starts the change process
A
Explanation:
A process map is a visual representation of a business process that helps to engage stakeholders, identify improvements, and start the change process. By creating a process map, the business analyst can understand the current state of the process, identify pain points and opportunities for improvement, and communicate the findings and recommendations to the stakeholders. A process map also helps to initiate the change process by providing a baseline for measuring the impact of the proposed solutions.
Reference: https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/business-process-mapping
The business analyst at Cloud Kicks received verbal acceptance of all user stories by the product owner and set the status of the user stories to ‘’Ready for Development’’ on a spreadsheet. The development team later reports are unable to confirm which user stories are ready to be built.
- A . The user stories were save outside of a shared repository
- B . The definition of done of the user stories was unclear.
- C . The user stories were linked to the incorrect business process map.
A
Explanation:
This answer states that saving user stories outside of a shared repository is why UC’s development team reports they are unable to confirm which user stories are ready to be built after receiving verbal acceptance of all user stories by the product owner and setting their status to ‘Ready for Development’ on a spreadsheet by UC’s BA. A shared repository is a common or central location where documents or files can be stored, accessed, and updated by multiple users or teams. Saving user stories outside of a shared repository means that the BA stores user stories in a place where they are not visible or available to other users or teams, such as their personal computer, email, etc. Saving user stories outside of a shared repository is why UC’s development team reports they are unable to confirm which user stories are ready to be built because it prevents them from seeing or accessing the latest version or status of user stories, and it creates confusion or inconsistency among them.
Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills
The product development team at Northern Trail Outfitters is creating a process within Salesforce to onboard new retail employees. The business analyst (BA) creates a current state process map by interviewing a few members of the onboarding team using email questionnaires. After presenting the process map to the entire onboarding team, the BA receives feedback that it is incorrect.
What should the BA do to provide the product development team with more accurate information about the onboarding team’s process?
- A . Meet with key project stakeholders in a live workshop to build consensus on the current and desired onboarding processes.
- B . Review survey feedback again to better understand pain points in the existing onboarding process.
- C . Conduct individual interviews with each team member to gather more information about the existing onboarding process.
Cloud Kicks (CK) needs to integrate the industry standard due-diligence in its sales process to verify customers in Sales Cloud. CK asks the business analyst (BA) to identify which stage in the sales process the industry standard due-diligence should be embedded.
What should the BA do to meet the requirement?
- A . Develop a process map as a base, work with stakeholders to understand the trigger point, and locate the stage.
- B . Identify the triggers, locate the stage, and add the standard due-diligence as a subprocess.
- C . Locate the stage, add the standard due-diligence as a subprocess, and set the trigger point.
A
Explanation:
The best practice for identifying which stage in the sales process the industry standard due-diligence should be embedded is to develop a process map as a base, work with stakeholders to understand the trigger point, and locate the stage.
This practice helps to:
Develop a process map as a base: This provides a visual representation of the sales process, showing the steps, inputs, outputs, roles, and decisions involved in each stage.
Work with stakeholders to understand the trigger point: This helps to elicit feedback and insights from the stakeholders who are familiar with or affected by the sales process, and identify when or why the industry standard due-diligence is needed or required.
Locate the stage: This helps to determine where in the sales process the industry standard due-diligence should be embedded, based on the trigger point and the business logic.
Reference: https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-process-mapping/create-a-process-map
Cloud Kicks leadership wants to use custom code for functionality that can easily be created declaratively in Sates Cloud. The business analyst (BA) has been asked to advise leadership on how these approaches impact their solution options.
What is one of the BA’s strongest arguments for using configuration over code?
- A . Configuration leverages multiple programming languages.
- B . Configuration allows for any level of complexity.
- C . Configuration provides faster speed to market.
B
Explanation:
One of the BA’s strongest arguments for using configuration over code is that configuration provides faster speed to market. Speed to market is the time it takes to deliver a product or service from conception to launch. Speed to market is important for gaining competitive advantage, meeting customer demand, and maximizing revenue potential. Configuration provides faster speed to market than code because it allows for creating and modifying functionality in Salesforce without writing code or deploying changes. Configuration can be done by using point-and-click tools such as App Builder, Process Builder, Flow Builder, Lightning Web Components Builder, etc., which are easy to use and require less technical skills than coding. Configuration also reduces the risk of errors or bugs that may occur with code and require more testing or debugging time.
Reference: https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-functional-requirements/evaluate-s