Salesforce Certified Business Analyst (BA-201) Exam - Topic 1 Question 51 Discussion

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

Question #: 51
Topic #: 1

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

Over the past month, a business analyst (BA) has worked with various stakeholders at Cloud Kicks to document requirements for an upcoming Tableau implementation. A stakeholder suggested a revision to the requirements. The BA sent the updated requirements to the stakeholders and they signed off.

Where should the BA track this milestone?

AStatement of work

BChange log

CSprint plan

Show Suggested Answer

Suggested Answer: B

Strategy analysis is the process of identifying and evaluating the risks and benefits of a proposed solution, as well as its alignment with the business goals and objectives. A business analyst performs strategy analysis to understand the impact of a solution on the project timeline, budget, scope, quality, and stakeholders.

https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/perform-strategy-analysis

https://www.iiba.org/standards-and-resources/babok/strategy-analysis/

by Verda at Sep 13, 2024, 05:25 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

Cyndy

8 months ago

Change log is the way to go! Keeps everything organized.

upvoted 0 times

...

In

8 months ago

Really? I thought sprint plans were for tracking progress, not changes.

upvoted 0 times

...

Jennifer

8 months ago

Wait, shouldn't this be in the statement of work?

upvoted 0 times

...

Layla

9 months ago

I agree, change log makes the most sense here.

upvoted 0 times

...

Josephine

9 months ago

Definitely the change log! It's all about tracking changes.

upvoted 0 times

...

Billy

9 months ago

I feel like the statement of work might be too broad for this specific milestone. The change log seems more focused on the updates we’re discussing.

upvoted 0 times

...

Brianne

9 months ago

I’m a bit confused about the sprint plan. I thought that was more for tracking tasks during development rather than documenting requirements changes.

upvoted 0 times

...

Maricela

9 months ago

I remember practicing a question about tracking changes, and I think the change log was the right answer there too. It’s important to keep everything documented.

upvoted 0 times

...

Mabel

9 months ago

I think the change log makes the most sense here since it tracks revisions and approvals. But I'm not entirely sure if the statement of work could also be relevant.

upvoted 0 times

...

Earlean

9 months ago

Based on the information provided, I'd say the change log is the best place for the BA to track this milestone. The question mentions the stakeholders signing off on the updated requirements, so that seems like a key change that should be documented in the change management process.

upvoted 0 times

...

Marva

9 months ago

I'm a bit confused on where exactly this should be tracked. Is the statement of work the right place, or the change log? I'll have to review the material again to make sure I understand.

upvoted 0 times

...

Theron

9 months ago

Okay, I think I've got this. The BA should track the milestone of the stakeholders signing off on the updated requirements in the change log, since that's where they're managing changes to the requirements.

upvoted 0 times

...

Ellsworth

9 months ago

Hmm, not sure about this one. Is the change log the right place to track the stakeholder sign-off on the updated requirements? I'll have to think this through.

upvoted 0 times

...

Rozella

10 months ago

This seems like a straightforward requirements management question. I'd focus on tracking the changes in the requirements documentation.

upvoted 0 times

...

Norah

10 months ago

Alright, this seems straightforward. The /etc/auto.home file is likely where the indirect maps for mounting file systems are defined, so I'll go with option A.

upvoted 0 times

...

Mila

1 year ago

Wait, are we sure the BA didn't just send the requirements to the stakeholders via carrier pigeon? Because that would be a whole different kind of milestone to track!

upvoted 0 times

...

Luis

1 year ago

I'm going with the change log. It's like a diary of all the ups and downs in the project - the BA can't afford to miss this juicy tidbit!

upvoted 0 times

Edelmira

1 year ago

Dorinda: It's like a roadmap of all the twists and turns in the project.

upvoted 0 times

...

Willow

1 year ago

User 3: The change log will help the BA keep track of the project's progress.

upvoted 0 times

...

Dorinda

1 year ago

User 2: Definitely, it's important to keep a record of all changes made.

upvoted 0 times

...

Timothy

1 year ago

User 1: I agree, the change log is the best place to track revisions.

upvoted 0 times

...

Carmelina

1 year ago

Hold up, what about the statement of work? Isn't that where the client and the BA agree on the project scope and deliverables? Seems like the perfect place to record this milestone.

upvoted 0 times

...

Barbra

1 year ago

Hmm, the sprint plan seems like a logical place. After all, the stakeholders have signed off on the changes, so it should be reflected in the project's roadmap.

upvoted 0 times