Salesforce Certified Business Analyst (BA-201) Exam - Topic 2 Question 52 Discussion

Actual exam question for Salesforce's Salesforce Certified Business Analyst (BA-201) exam

Question #: 52
Topic #: 2

[All Salesforce Certified Business Analyst (BA-201) Questions]

At the start of a new Agile development project, the Universal Containers' product owner asked the business analyst (BA) to clearly define the intended results of the work based on stakeholder needs. The development and implementation teams will use the intended results to plan product decisions. The definition should avoid assumptions and focus on stakeholder value.

Which element should the BA choose to define the intended results?

ARequirements

BUser stories

CEpics

Show Suggested Answer

Suggested Answer: B

The performance analyzer is a tool that helps business analysts and admins identify and troubleshoot performance issues on record pages. It shows the load time of each component on a record page and provides recommendations to improve performance. The first step to resolve the issue is to use the performance analyzer to view the assessment and identify the slowest components.

https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/optimize-performance

https://help.salesforce.com/s/articleView?id=sf.performance_analyzer.htm&type=5

by Yoko at Sep 16, 2024, 04:48 AM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified Business Analyst (BA-201) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Sharee

3 months ago

Agreed, user stories focus on value and avoid assumptions!

upvoted 0 times

...

Darrin

3 months ago

Wait, are we sure user stories are the best choice here?

upvoted 0 times

...

Van

3 months ago

Requirements are too rigid for Agile, user stories all the way!

upvoted 0 times

...

Lettie

4 months ago

I think epics are better for defining high-level goals.

upvoted 0 times

...

Kayleigh

4 months ago

Definitely user stories, they capture stakeholder needs well.

upvoted 0 times

...

Georgiana

4 months ago

I'm a bit confused; I thought requirements were the way to go, but now I'm leaning towards user stories after reviewing some examples.

upvoted 0 times

...

Lashaun

4 months ago

Epics could work too, but they seem more high-level. I feel like user stories are more specific to what stakeholders want.

upvoted 0 times

...

Eveline

4 months ago

I remember practicing a question like this, and I think requirements might be too broad for defining intended results.

upvoted 0 times

...

Yolande

5 months ago

I think the BA should go with user stories since they focus on stakeholder needs and value. But I'm not entirely sure if that's the best choice.

upvoted 0 times

...

Ula

5 months ago

User stories seem like the best fit to me. They allow the BA to define the intended results from the stakeholder's perspective, without getting bogged down in technical details.

upvoted 0 times

...

Tonette

5 months ago

Requirements might be the right answer here, as they provide a more comprehensive definition of the intended results. But I'll need to double-check how that compares to user stories and epics.

upvoted 0 times

...

Valentin

5 months ago

Okay, I think I've got this. The BA should choose user stories to define the intended results, as they capture the stakeholder's needs in a concise, value-focused way.

upvoted 0 times

...

Idella

5 months ago

Hmm, I'm a bit unsure here. The question mentions avoiding assumptions and focusing on stakeholder value, so I'll need to carefully consider which option best aligns with that guidance.

upvoted 0 times

...

Lili

5 months ago

This seems like a straightforward question about Agile project management. I'll focus on identifying the key elements that define the intended results based on stakeholder needs.

upvoted 0 times

...

Denae

5 months ago

Hmm, this looks like a classic weighted-ranking matrix question. I'll need to carefully review the criteria and scores to determine the best solution.

upvoted 0 times

...

Daniel

10 months ago

Ah, the age-old battle of user stories vs. epics. It's like choosing between a cup of coffee or an entire coffee plantation. Either way, you're going to get a caffeine buzz, am I right?

upvoted 0 times

Belen

8 months ago

A: User stories are more detailed and focused on specific user needs

upvoted 0 times

...

Alyssa

8 months ago

B: Epics

upvoted 0 times

...

Stefanie

9 months ago

A: User stories

upvoted 0 times

...

Deandrea

10 months ago

User stories all the way! They're like the MVP of requirements - just the essential bits to get the job done. And they're way more fun to write than those dry old requirements.

upvoted 0 times

Theron

9 months ago

Absolutely, user stories help us stay agile and adapt to changing stakeholder needs more easily.

upvoted 0 times

...

Herminia

9 months ago

User stories are great for breaking down the work into manageable chunks and keeping the focus on stakeholder value.

upvoted 0 times

...

Lashon

10 months ago

I agree, user stories are more user-friendly and easier to understand compared to traditional requirements.

upvoted 0 times

...

Ahmad

10 months ago

User stories are definitely the way to go. They help us focus on what really matters to the stakeholders.

upvoted 0 times

...

Shad

10 months ago

I think epics would be the best option, as they provide a high-level overview of the project goals.

upvoted 0 times

...

Trinidad

10 months ago

Requirements? Really? That's way too detailed and specific for this scenario. The BA needs to keep it high-level and focus on stakeholder value, so user stories are the way to go.

upvoted 0 times

Amie

10 months ago

User 2: Agreed, user stories are more high-level and focus on stakeholder value.

upvoted 0 times

...

Leana

10 months ago

User 1: User stories

upvoted 0 times

...

Fidelia

11 months ago

I think epics would be the best choice here. Epics provide a high-level overview of the project's objectives, which aligns with the need to define the intended results based on stakeholder needs.

upvoted 0 times

...

Leonie

11 months ago

I disagree, I believe requirements would be a better choice for defining the intended results.

upvoted 0 times

...

Kaitlyn

11 months ago

I think the BA should choose user stories to define the intended results.

upvoted 0 times

...

Alecia

11 months ago

The BA should choose user stories to define the intended results. User stories focus on stakeholder value and avoid assumptions, which is exactly what the question requires.

upvoted 0 times