Practice Free BA-201 Exam Online Questions
Northern Trail Outfitter is eliciting feedback from a small number of key stakeholders within the organization for improvements to the current opportunity pipeline process. One of the stakeholders has a tendency to dominate the conversation which takes the group off topic and interfaces with meeting the objective.
How should the business analyst collaborate with the key stakeholder’s?
- A . Conduct individual interviews to gather input.
- B . Conduct a group brainstorming session to generate ideas.
- C . Conduct a focus group to identify pain points.
A
Explanation:
The business analyst should conduct individual interviews to gather input from the key stakeholders. Interviews are a technique that involves asking open-ended questions to stakeholders or users to gather information and feedback about their needs, expectations, preferences, pain points, goals, etc. Interviews help to elicit requirements and user stories from the key stakeholders by allowing them to express their opinions and experiences in their own words, as well as clarifying any doubts or ambiguities. Interviews also help to avoid the influence or dominance of one stakeholder over others, as well as reduce the risk of groupthink or conformity.
Reference: https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/customer-discovery
Cloud Kicks uses declarative change set development to deliver its Salesforce customizations. The business analyst (BA) works with the technical leas on the project to track changes that require manual migration.
Which resources should the BA use to determine which changes must be made manually in each environment?
- A . Metadata coverage report
- B . Object Schema Builder
- C . Setup Audit Trail
A
Explanation:
The business analyst should use the metadata coverage report to determine which changes must be made manually in each environment. The metadata coverage report is a tool that shows which metadata types and components are supported in different development models and tools, such as change sets, Metadata API, Salesforce CLI, etc. The business analyst should use the metadata coverage report to identify which changes can be deployed automatically using declarative change sets and which changes must be made manually using other tools or methods. The object schema builder is not a resource to determine which changes must be made manually in each environment. The object schema builder is a tool that lets you create and modify custom objects and fields using a graphical interface. It does not show which metadata types and components are supported in different development models and tools. The setup audit trail is not a resource to determine which changes must be made manually in each environment. The setup audit trail is a tool that tracks the recent setup changes that you and other admins have made to your org. It does not show which metadata types and components are supported in different development models and tools.
Reference: https://trailhead.salesforce.com/en/content/learn/modules/application-lifecycle-and-development-models/understand-what-application-lifecycle-management-is
A business analyst JBA) for Northern Trail Outfitters (NTO) is reviewing the business backlog and determines that many of the requirements would require custom code that is expensive and hard to maintain. The BA knows that the backlog should be prioritized by people who have knowledge of the features and functionary of the Salesforce Platform.
Who should own the process of prioritizing the business backlog?
- A . The third-party implementation team, with support from the internal technology teams affected by the project who understand NTO’s vision and strategy
- B . The business teams affected, with support from the internal technology teams who understand ways to maximize Salesforce’s declarative features
- C . The project manager, with support from the third-party implementation and business teams who understand both platform and business priorities.
B
Explanation:
The process of prioritizing the business backlog should be owned by the business teams affected, with support from the internal technology teams who understand ways to maximize Salesforce’s declarative features. The business backlog is a list of requirements or user stories that describe the features or functionality that the business needs or wants from a project or enhancement. The business backlog should be prioritized by the business teams affected because they are the ones who have the most knowledge and interest in the business value and impact of each requirement or user story. The business backlog should also be supported by the internal technology teams who understand ways to maximize Salesforce’s declarative features because they are the ones who have the most knowledge and expertise in the technical feasibility and complexity of each requirement or user story.
Reference: https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/requirements-management
Universal Containers uses Kanban to complete its Salesforce development. In the middle of a sprint, the sales manager submits an important item to the team.
What should the business analyst do next?
- A . Ask the team to reprioritize the backlog and work on the item at the top.
- B . Ask the team to commit to the work for the next sprint.
- C . Ask the team to pivot and complete the work immediately.
A
Explanation:
The business analyst should ask the team to reprioritize the backlog and work on the item at the top. This is because Kanban is a development model that focuses on continuous delivery and flow of work, rather than fixed iterations or sprints. Kanban uses a visual board that shows the status of work items across different stages, such as backlog, in progress, done, etc. Work items are pulled from one stage to another when there is available capacity or demand, rather than according to a predefined schedule or plan. Reprioritizing the backlog can help the team accommodate the new item and ensure that the most important or urgent work is done first. Asking the team to commit to the work for the next sprint may not be a good option because Kanban does not use sprints or time-boxed iterations. Asking the team to pivot and complete the work immediately may not be a good option because it may disrupt the flow of work or create bottlenecks or waste in Kanban.
Reference: https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/user-acceptance https://trailhead.salesforce.com/en/content/learn/modules/agile-development-with-scrum
Northern Trail Outfitters (NTO) has moved its inventory systems to Salesforce to track the clothing it manufactures and sells. As a part of this project, NTO wants to implement several features which will also improve how its inventory is restocked. In order to manage the discovery phase of the project, the project team plans to hire a business analyst (8A).
What should a BA do to be successful during the first phase of the project?
- A . Elicit requirements, build automation, and deploy a solution,
- B . Architect a solution, configure a sandbox, and build a proof of concept.
- C . Elicit requirements, create flows and process diagrams, and understand business analytics.
C
Explanation:
The tasks that a business analyst should do to be successful during the first phase of an inventory project are elicit requirements, create flows and process diagrams, and understand business analytics. These tasks will help them understand the current state of NTO’s inventory system, capture the needs and expectations of stakeholders, map out how NTO tracks its clothing manufacturing and sales processes, and measure how NTO’s inventory affects its business performance. Building automation and deploying a solution are tasks for later phases of the project after validating and testing prototypes. Architecting a solution and configuring a sandbox are tasks for developers or architects based on user stories.
Reference:
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/customer-discovery
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/business-process-mapping
https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/user-stories
Northern Trail Outfitters has decided to implement Sales Cloud. A business analyst (BA) has been assigned to document the requirements for this project.
What should the BA include in these requirements?
- A . Detailed documentation of technical solution
- B . Test scripts to validate requirements
- C . High-level description of required functionality
C
Explanation:
The business analyst should include a high-level description of required functionality in the requirements for Sales Cloud implementation. A high-level description of required functionality is a brief and general statement that describes what a system or solution must do or provide to meet a business need or goal. A high-level description of required functionality helps to capture and communicate the scope and value of a requirement or feature. The business analyst should include a high-level description of required functionality in the requirements for Sales Cloud implementation by using clear and concise language, avoiding technical jargon or details, and focusing on outcomes rather than solutions.
Reference: https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/requirements-management
The project manager for Universal Container tells the business analyst (BA) that the developers on the team are having trouble understanding what to build because the acceptance criteria for the Sales Cloud user stories are confusing.
How should the BA respond to the feedback effectively?
- A . Recommend additional training resources.
- B . Ask for specific examples to review.
- C . Confirm that best practices are being followed.
B
Explanation:
This answer states that asking for specific examples to review is how the BA should respond to feedback from UC’s project manager who tells the BA that the developers on the team are having trouble understanding what to build because the acceptance criteria for the Sales Cloud user stories are confusing. Asking for specific examples to review means that the BA requests the project manager or the developers to provide concrete instances or scenarios of where and how the acceptance criteria for the Sales Cloud user stories are confusing, such as ambiguous, inconsistent, or incomplete acceptance criteria. Asking for specific examples to review is how the BA should respond to feedback from UC’s project manager because it helps the BA to clarify and verify the feedback, and to revise and update the acceptance criteria accordingly.
Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills
The technical team at Cloud Kicks is trying to deliver one of its Salesforce customizations. The business analyst (BA) has been asked to put assignments, test plans, decisions, and milestones in writing and share this document with stakeholders so there is less potential for confusion.
Which tactical document should the BA use to capture features?
- A . Business analysis plan
- B . User Acceptance Test plan
- C . Release plan
C
Explanation:
The tactical document that the business analyst should use to capture features is a release plan. A release plan is a document that outlines the scope, schedule, resources, and deliverables of a project or enhancement that will be released to production. A release plan helps to communicate and align with stakeholders on what features will be delivered, when they will be delivered, how they will be delivered, and who will be involved in delivering them. A release plan also helps to manage expectations, risks, dependencies, and changes throughout the project lifecycle.
Reference: https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification-prep/project-planning
As a part of discovery, the business analyst (BA) at Universal Containers is trying to understand how Salesforce was implemented.
What should the BA utilize to help uncover any technical constraints or potential problems in a Salesforce implementation?
- A . Salesforce Optimizer
- B . Setup Audit Trail
- C . Reports and Dashboards
A
Explanation:
The tool that the business analyst should use to help uncover any technical constraints or potential problems in a Salesforce implementation is Salesforce Optimizer. Salesforce Optimizer is a feature that analyzes a Salesforce org and provides recommendations for improving its performance, security, usability, and maintenance. It can help the business analyst identify any issues or risks in a Salesforce implementation such as unused features or components, complex configurations or customizations, low adoption rates or user satisfaction scores, etc. Setup Audit Trail is a tool that monitors and logs changes made by administrators in Setup. It can help the business analyst track who made what changes and when, but not uncover any technical constraints or potential problems in a Salesforce implementation. Reports and Dashboards are tools that display data or metrics in visual formats such as charts or tables.
A business analyst (BA) is preparing for user acceptance testing for case management scenarios in Service Cloud.
What should the BA do to help prevent gaps from being discovered after go live?
- A . Focus more on happy path testing and less on edge case testing.
- B . Write test scripts that reflect real life and cover the requirements.
- C . Streamline testing by limiting the number of testers involved.
B
Explanation:
The business analyst should write test scripts that reflect real life and cover the requirements to help prevent gaps from being discovered after go live. Test scripts are step-by-step instructions on how to execute a test scenario on a specific user or level of access using expected inputs and outputs. Test scripts should reflect real life situations that users may encounter when using the solution in production, such as creating cases, updating records, generating reports, etc. Test scripts should also cover all the requirements that were defined for the project or enhancement, as well as any exceptions or variations that may occur. Writing test scripts that reflect real life and cover the requirements can help ensure that the solution works as intended and meets stakeholder needs.
Reference: https://trailhead.salesforce.com/content/learn/modules/user-acceptance-testing-video/create-test-scripts