Free Certified Business Analyst Exam Braindumps
Salesforce Certified Business Analyst Questions 111–115 (page: 24)

Updated On: 10-Feb-2026

A business analyst is working with a new customer on a Sales Cloud implementation. The executive sponsor for the project is new to the company and their role as VP. The sponsor has inherited functional requirements from the previous VP that were gathered 9 months ago. The project start date has yet to be defined. The sponsor wants to use the inherited requirements in lieu of a traditional discovery process.
What is the largest risk with this approach?

  1. The previous VP's requirements fail to meet current formatting standards.
  2. The previous VP's requirements may differ from those of the new executive.
  3. The previous VP's requirements are outside of the Salesforce framework.

Answer(s): B

Explanation:

This answer points out that the previous VP's requirements may differ from those of the new executive as the largest risk with this approach of using the inherited requirements in lieu of a traditional discovery process for a Sales Cloud implementation. Requirements are statements that describe what a solution must do or have to meet the needs and expectations of the stakeholders or users. Requirements may change over time due to various factors, such as business goals, market trends, customer feedback, or stakeholder preferences. Using the previous VP's requirements without validating them with the new executive may result in a solution that does not align with their vision, strategy, or value proposition.


Reference:

https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick- look/use-user-stories-to-capture-requirements



After reviewing a technical demo, the Northern Trail Outfitters sales leadership team wants to mate adjustments to the original requirements around Sales Cloud opportunity management.
What should the business analyst do to manage the requested changes?

  1. Update the gap analysis document and scope statement specification.
  2. Update the change request log and draft a new user story.
  3. Update the change management document and user acceptance testing plans.

Answer(s): B

Explanation:

The best practice for managing requested changes to the original requirements is to use a change request log and user stories. A change request log is a document that tracks and records any changes that are requested by stakeholders or identified by the project team during the project lifecycle. A user story is a concise statement that describes what a user wants to do and why they want to do it in Salesforce. The BA should update the change request log with the details of the requested change, such as the description, source, priority, impact, status, and approval. The BA should also draft a new user story that captures the requested change in terms of who, what, and why, and add it to the backlog for prioritization and development.


Reference:

https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-change- management/manage-change-requests https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-user-stories/write- user-stories



The business analyst (BA) at Universal Containers is responsible for defining the enhancement features for the current Salesforce CPQ implementation that must be configured in the next phase of the project.
Which type of document should the BA create to achieve the objective?

  1. Business analysis plan
  2. Scope statement specification
  3. Functional requirements specification

Answer(s): C

Explanation:

A functional requirements specification (FRS) is a document that defines what features and functions a system should provide to meet the business needs and objectives. It describes how users will interact with the system and what outcomes they expect from it. An FRS typically includes use cases, user stories, acceptance criteria, data models, business rules, workflows, diagrams, mockups, and other details that describe how the system should work. A BA should create an FRS to define the enhancement features for the current Salesforce CPQ implementation that must be configured in the next phase of the project.


Reference:

https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-functional- requirements/understand-functional-requirements



The business analyst (BA) at Universal Containers is meeting with business leaders to elicit and document functional requirements specifications related to its new Salesforce implementation. The BA will also document the functionality this system should provide so it can be developed into a work item.
What is the name of this documentation type?

  1. Business analysis plan
  2. Use case
  3. User story

Answer(s): A

Explanation:

A user story is a type of documentation that describes what functionality a system should provide from a user's perspective. It is written in simple language that anyone can understand and follows a standard format of "As a [user role], I want [functionality], so that [benefit]". A user story helps to capture the user's needs and expectations from the system and provides a basis for developing test cases and acceptance criteria. A BA should use user stories to document the functionality that a system should provide so it can be developed into a work item.


Reference:

https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-user-stories/write- user-stories



A business analyst (BA) is working on a request from a sales leader at Universal Containers. The sales leader has noticed the quality of information on new leads has declined recently. After completing their initial research, the BA concludes that the Salesforce lead intake form needs to be updated to include only essential information. Since several sales teams use the intake form, the BA must get alignment from all of the groups.
How does whiteboarding help the BA collaborate with multiple stakeholders?

  1. It provides a script to follow with suggested questions and prompts, identifies exactly what each group needs in order to be successful, and the final version acts as the business requirements document.
  2. It builds a shared understanding of the current state, creates a space for everyone to contribute since the activity feels shared, and guides the conversation while maintaining engagement.
  3. It provides a single document in a central location for stakeholders to contribute, allowing each group to provide feedback on their own, instead of requiring everyone to meet and discuss together.

Answer(s): B

Explanation:

Whiteboarding is a technique that involves using a whiteboard or a similar tool to visually represent a process, problem, or solution.
Whiteboarding helps the BA collaborate with multiple stakeholders by building a shared understanding of the current state, creating a space for everyone to contribute since the activity feels shared, and guiding the conversation while maintaining engagement.
Whiteboarding also helps to identify issues, gaps, opportunities, and dependencies in the process, and to generate ideas and feedback from stakeholders.


Reference:

https://trailhead.salesforce.com/en/content/learn/modules/business-analysis-process- mapping/plan-and-facilitate-a-process-mapping-session



Viewing page 24 of 64
Viewing questions 116 - 120 out of 311 questions


Post your Comments and Discuss Salesforce Certified Business Analyst exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!