Free Certified Business Analyst Exam Braindumps
Salesforce Certified Business Analyst Questions 66–70 (page: 15)

Updated On: 10-Feb-2026

A business analyst (BA) at Northern Trail Outfitters was asked to create a new user story for a Sales

Cloud update requested by the inside sales team. The BA created the following story:
"As a user, I need visibility to customers' purchase history details so I can increase efficiencies and improve closure rates by better tailoring sales offerings." Which mistake did the BA make when creating this story?

  1. The goal is undefined.
  2. The persona is undefined.
  3. The need is undefined.

Answer(s): B

Explanation:

The mistake that the business analyst made when creating this story is that the persona is undefined. A persona is a fictional representation of an end user who has a specific role, goal, or need. A user story should specify the persona as part of its format: "As a [persona], I need [need], so I can [goal]". Specifying the persona can help the business analyst communicate who will use the feature and why it matters to them. The goal and the need are defined in this user story. The goal is to increase efficiencies and improve closure rates by better tailoring sales offerings. The need is visibility to customers' purchase history details.


Reference:

https://trailhead.salesforce.com/content/learn/modules/salesforce-business-analyst-certification- prep/user-stories https://trailhead.salesforce.com/content/learn/modules/salesforce-business- analyst-certification-prep/customer-discovery



A business analyst (BA) at Northern Trail Outfitters has been asked to prepare documentation including acceptance criteria and definition of done for a Heroku project.
Which way should the BA approach creation of this documentation?

  1. Include the personal perspective for acceptance criteria and the overall perspective for definition of done.
  2. Create one consolidated set of documentation as the two terms are synonymous and used interchangeably.
  3. Include the overall perspective for acceptance criteria and the persona's perspective for definition of done.

Answer(s): A



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?

  1. 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.
  2. 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,
  3. 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.

Answer(s): C



The business analyst at Cloud Kicks is using a checklist to assess the quality of user stones for an upcoming Experience Cloud implementation.
Which characteristics make a user story successful?

  1. Clean Direct, Concise, Cross Functional, Configurable
  2. Actionable., Concise, Testable, Solution-oriented, Defined
  3. Independent, Negotiable, Valuable, Estimable. Small, Testable

Answer(s): C

Explanation:

these are the characteristics that make a user story successful, according to the INVEST acronym. A user story should be independent of other user stories, negotiable in terms of scope and details, valuable to the user or customer, estimable in terms of effort and time, small enough to fit in a sprint or iteration, and testable with clear acceptance criteria.


Reference:

https://trailhead.salesforce.com/content/learn/modules/user-story-creation/learn-about-user- stories



The business analyst is working with a stakeholder on a Salesforce project. The stakeholder needs an approval process on contract submissions. Sales managers want to see all contracts when the discount is greater than 20%. They will decline any contracts with a discount that is greater than 25%, but they want visibility into other highly discounted contracts.
Which acceptance criteria is the most effective for this scenario?

  1. A sales manager wants to be notified when a contract has been submitted with a discount greater than 20% so the manager can approve or decline a discounted price.
  2. Users in a sales manager role should have access to a button on contracts to click to approve or decline a contract with a discounted price of 2G% or more.
  3. A sales manager wants to be able to approve contracts with a large discount and they need a validation rule related to contract discounts greater than 25%

Answer(s): A

Explanation:

This answer provides an example of effective acceptance criteria for the scenario of creating an approval process on contract submissions. Acceptance criteria are statements that define the conditions that a solution must meet to be accepted by the stakeholders or users. Acceptance criteria should be clear, concise, testable, and measurable. This answer meets these criteria by stating what a sales manager wants to do (be notified, approve or decline), when they want to do it (when a contract has been submitted with a discount greater than 20%), and how they can verify it (a discounted price).


Reference:

https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst- certification-prep/prepare-for-the-salesforce-business-analyst-certification-exam



Viewing page 15 of 64
Viewing questions 71 - 75 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!