Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

PMI Exam PMI-PBA Topic 2 Question 58 Discussion

Actual exam question for PMI's PMI-PBA exam
Question #: 58
Topic #: 2
[All PMI-PBA Questions]

A new project is in the planning phase. The business owner believes that, since the timeline is aggressive, requirements elicitation should begin as soon as possible.

Which activity should the business analyst initiate before beginning requirements elicitation?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Donte
1 months ago
I don't know about you, but I'm feeling a bit like a requirements detective here. Time to put on my thinking cap and solve this mystery!
upvoted 0 times
Cheryl
11 days ago
C: Let's make sure we have a clear plan in place before diving into the details.
upvoted 0 times
...
Dudley
30 days ago
B: I agree, that's an important step before starting requirements elicitation.
upvoted 0 times
...
Delfina
1 months ago
A: I think we should define how the solution will be evaluated.
upvoted 0 times
...
...
Royal
2 months ago
A) Prepare the requirements traceability matrix? Seriously? That's like trying to build a house before laying the foundation. Let's keep it simple, folks.
upvoted 0 times
Yuki
18 days ago
D) Document how the relevant systems interact.
upvoted 0 times
...
Madelyn
30 days ago
C) Draft a high-level data model.
upvoted 0 times
...
Benedict
1 months ago
B) Define how the solution will be evaluated.
upvoted 0 times
...
...
Cordelia
2 months ago
D) Document how the relevant systems interact seems like the way to go. Gotta understand the ecosystem before we dive into requirements, am I right?
upvoted 0 times
...
Rory
2 months ago
Hmm, I'm leaning towards C) Draft a high-level data model. That'll give us a good foundation to build upon during requirements elicitation.
upvoted 0 times
Albina
1 months ago
User 2: Definitely, it will provide a clear picture of the information we need to gather for the project.
upvoted 0 times
...
Isidra
2 months ago
User 1: I agree, starting with a high-level data model will help us understand the data flow.
upvoted 0 times
...
...
Renay
2 months ago
I disagree. We should document how the relevant systems interact to have a better understanding of the project scope.
upvoted 0 times
...
Mitzie
2 months ago
I'd say B) Define how the solution will be evaluated. That way, we can align the requirements with the success criteria from the get-go.
upvoted 0 times
Oliva
15 days ago
User 4: Let's make sure we have a solid evaluation plan in place before diving into requirements elicitation.
upvoted 0 times
...
Jennie
17 days ago
User 3: Agreed. It's important to have a clear understanding of how we will measure the success of the project.
upvoted 0 times
...
Loreta
18 days ago
User 2: That makes sense. It will help us ensure that the requirements meet the project goals.
upvoted 0 times
...
Arlyne
22 days ago
User 1: I think we should go with B) Define how the solution will be evaluated.
upvoted 0 times
...
...
Tarra
2 months ago
I agree with Novella. It's important to have a clear evaluation criteria before starting requirements elicitation.
upvoted 0 times
...
Novella
2 months ago
I think we should define how the solution will be evaluated first.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77