Salesforce Exam Business Analyst Topic 2 Question 52 Discussion

Actual exam question for Salesforce's Business Analyst exam

Question #: 52
Topic #: 2

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 Business Analyst Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Daniel

1 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

Alyssa

2 days ago

B: Epics

upvoted 0 times

...

Stefanie

5 days ago

A: User stories

upvoted 0 times

...

Deandrea

2 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

18 days ago

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

upvoted 0 times

...

Herminia

23 days ago

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

upvoted 0 times

...

Lashon

1 months ago

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

upvoted 0 times

...

Ahmad

1 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

2 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

2 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

1 months ago

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

upvoted 0 times

...

Leana

2 months ago

User 1: User stories

upvoted 0 times

...

Fidelia

2 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

2 months ago

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

upvoted 0 times

...

Kaitlyn

2 months ago

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

upvoted 0 times

...

Alecia

2 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