Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Certified Business Analyst (BA-201) Exam - Topic 7 Question 25 Discussion

Actual exam question for Salesforce's Salesforce Certified Business Analyst (BA-201) exam
Question #: 25
Topic #: 7
[All Salesforce Certified Business Analyst (BA-201) Questions]

During a requirements gathering session, two stakeholders discuss the names of the fields they want to see when adding leads to the system. Each stakeholder has a different point of view on field names.

What should the business analyst do to help Influence the team and accurately capture the requirements?

Show Suggested Answer Hide Answer
Suggested Answer: C

This answer states that enabling history in the shared spreadsheet is what the BA should recommend to ensure UAT results are documented securely after receiving verbal acceptance of all user stories by the product owner for developing a new Commerce Cloud implementation at CK. History is a feature that allows users to view, restore, or compare previous versions of a document or a file. Enabling history in the shared spreadsheet means that the BA turns on this feature in the spreadsheet where user stories are stored, such as Google Sheets, Microsoft Excel, etc. Enabling history in the shared spreadsheet is what the BA should recommend to ensure UAT results are documented securely because it helps the BA to track and record who made what changes to user stories and when, and to prevent or recover any accidental or unauthorized changes to user stories. Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-stakeholder-engagement-skills


by Elke at Aug 29, 2023, 02:19 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:

0/2000 characters
Submit Cancel
Chuck
6 months ago
Wait, are we really letting developers decide names? That’s surprising!
upvoted 0 times
...
Shantay
6 months ago
C? No way, they might not know the business needs!
upvoted 0 times
...
Altha
6 months ago
B seems risky, what if the sponsor doesn't understand the context?
upvoted 0 times
...
Ilona
7 months ago
Definitely agree with A, collaboration is important.
upvoted 0 times
...
Kristian
7 months ago
I think finding a middle ground is key!
upvoted 0 times
...
Gearldine
7 months ago
I feel like we practiced a similar scenario where we had to mediate between conflicting views. Finding a middle ground might be the best way to ensure everyone feels heard.
upvoted 0 times
...
Lindsey
7 months ago
I’m not sure about letting the development team decide, like in option C. They might not understand the business context as well as the stakeholders do.
upvoted 0 times
...
Alline
7 months ago
I think asking the executive sponsor, like in option B, could be a way to resolve the conflict, but it feels a bit top-down.
upvoted 0 times
...
Hayley
7 months ago
I remember we talked about finding a compromise in class, so option A seems like a good approach. But what if they can't agree?
upvoted 0 times
...
Carli
8 months ago
Okay, I think the key here is to really understand the different viewpoints and try to find a solution that satisfies both stakeholders. Compromise is probably the way to go, but I'd want to dig into their reasoning first.
upvoted 0 times
...
Dorothy
8 months ago
Letting the dev team decide the field names? I don't know, that doesn't seem like the best approach. They need to understand the business requirements, so the stakeholders should have the final say.
upvoted 0 times
...
Charlette
8 months ago
This seems like a classic requirements gathering scenario where stakeholders have different perspectives. I'd focus on facilitating a discussion to find a middle ground that works for everyone.
upvoted 0 times
...
Shawna
8 months ago
Hmm, not sure about this one. Letting the exec make the final call seems like it could bypass the actual stakeholders. Maybe I'd try to get them to compromise first before escalating it.
upvoted 0 times
...
Marylin
8 months ago
Hmm, I'm a bit unsure about this one. The options seem to cover different types of governance, but I'm not sure which one specifically refers to managing enterprise architecture. I'll have to think this through carefully.
upvoted 0 times
...
Maia
8 months ago
This question seems pretty straightforward. I think the key is to focus on the reliability requirements and the solution that can increase resiliency.
upvoted 0 times
...
Annamaria
8 months ago
This one seems pretty straightforward. I'm going to think through the processes and see which one is external to the cloud data center.
upvoted 0 times
...
Hershel
1 year ago
I heard the stakeholders were arguing over whether to call it 'Lead Name' or 'Customer Name'. Apparently, one of them wanted to future-proof it for when they start selling to superheroes.
upvoted 0 times
Nada
11 months ago
We should consider the long-term implications of the field names and how they will be used in the future.
upvoted 0 times
...
Laurel
11 months ago
Maybe we can use a more generic term that can apply to both leads and customers.
upvoted 0 times
...
Nguyet
11 months ago
Let's find a compromise and come up with a name that works for both of you.
upvoted 0 times
...
Delmy
12 months ago
A) Find a middle ground where both stakeholders are satisfied with the field names.
upvoted 0 times
...
Irving
12 months ago
B) Ask the executive sponsor to make the final field name decisions.
upvoted 0 times
...
Matthew
1 year ago
A) Find a middle ground where both stakeholders are satisfied with the field names.
upvoted 0 times
...
...
Horace
1 year ago
A business analyst who can't wrangle a couple of stakeholders and get them to agree on field names? That's like a traffic cop who can't direct a three-car pileup. Better brush up on those negotiation skills!
upvoted 0 times
...
Dorothea
1 year ago
Allowing the development team to make the final decision? That's like letting the fox guard the henhouse! They'll probably just name everything 'field1', 'field2', and call it a day.
upvoted 0 times
Annelle
1 year ago
Stakeholder 1: That sounds like a good approach, we want the system to be user-friendly.
upvoted 0 times
...
Corazon
1 year ago
Business Analyst: Let's work together to find a compromise that meets both of your needs.
upvoted 0 times
...
Glendora
1 year ago
Stakeholder 2: I agree, we want to avoid confusion for the users.
upvoted 0 times
...
Sol
1 year ago
Stakeholder 1: We need to make sure the field names are clear and descriptive.
upvoted 0 times
...
...
Mozelle
1 year ago
Letting the executive sponsor decide feels like an easy way out. The business analyst should be facilitating the discussion, not passing the buck.
upvoted 0 times
Phil
1 year ago
B) Ask the executive sponsor to make the final field name decisions.
upvoted 0 times
...
James
1 year ago
A) Find a middle ground where both stakeholders are satisfied with the field names.
upvoted 0 times
...
...
Adolph
1 year ago
Finding a middle ground seems like the best approach. Both stakeholders' perspectives need to be considered to reach a consensus.
upvoted 0 times
Kallie
12 months ago
A) Finding a middle ground seems like the best approach. Both stakeholders' perspectives need to be considered to reach a consensus.
upvoted 0 times
...
Tiffiny
1 year ago
B) Ask the executive sponsor to make the final field name decisions.
upvoted 0 times
...
Stephane
1 year ago
A) Find a middle ground where both stakeholders are satisfied with the field names.
upvoted 0 times
...
...
Rolande
1 year ago
I believe allowing the development team to make the final decision could lead to a more efficient process.
upvoted 0 times
...
Naomi
1 year ago
I agree with Azalee, it's important to make sure both stakeholders are satisfied.
upvoted 0 times
...
Azalee
1 year ago
I think the business analyst should find a middle ground.
upvoted 0 times
...

Save Cancel