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

PMI-PBA Exam - 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

by Filiberto at Sep 21, 2022, 11:00 PM

Limited Time Offer

25%

Off

Get Premium PMI-PBA Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Sueann
5 months ago
I thought preparing the traceability matrix was the first step?
upvoted 0 times
...
Nikita
6 months ago
Wait, why are we rushing into requirements? Shouldn't we plan better?
upvoted 0 times
...
Rosendo
6 months ago
Agree with Amos, evaluation criteria set the stage.
upvoted 0 times
...
Vilma
6 months ago
I think drafting a high-level data model is more important.
upvoted 0 times
...
Amos
6 months ago
Definitely need to define how the solution will be evaluated first!
upvoted 0 times
...
Glenn
6 months ago
I keep thinking that drafting a high-level data model could help clarify what we need, but I’m not confident if that’s the right first move.
upvoted 0 times
...
Arlene
6 months ago
I practiced a question similar to this, and I feel like preparing the requirements traceability matrix is more of a later step.
upvoted 0 times
...
Thora
6 months ago
I'm not entirely sure, but I remember something about documenting system interactions being important. Maybe that's what we should do first?
upvoted 0 times
...
Domitila
7 months ago
I think we might need to define how the solution will be evaluated first. It seems like a logical step before diving into requirements.
upvoted 0 times
...
Izetta
7 months ago
Hmm, I'm a bit unsure about Type 4 LSAs and how they're generated in this scenario. I'll need to review that part of the material.
upvoted 0 times
...
Catalina
7 months ago
I think this question is pretty straightforward. The Cisco Switch Selector sounds like a tool to help customers find the right switch for their needs, so I'll go with option A.
upvoted 0 times
...
Raelene
7 months ago
Okay, I've got a strategy for this. I'll focus on the settings that directly impact the location and proximity of resources, like the starting location and resource synchronization. That should point me in the right direction.
upvoted 0 times
...
Myrtie
7 months ago
This question seems straightforward, I'm pretty confident I know the answer.
upvoted 0 times
...
Donte
11 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
10 months ago
C: Let's make sure we have a clear plan in place before diving into the details.
upvoted 0 times
...
Dudley
11 months ago
B: I agree, that's an important step before starting requirements elicitation.
upvoted 0 times
...
Delfina
11 months ago
A: I think we should define how the solution will be evaluated.
upvoted 0 times
...
...
Royal
12 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
11 months ago
D) Document how the relevant systems interact.
upvoted 0 times
...
Madelyn
11 months ago
C) Draft a high-level data model.
upvoted 0 times
...
Benedict
11 months ago
B) Define how the solution will be evaluated.
upvoted 0 times
...
...
Cordelia
12 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
1 year 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
11 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
12 months ago
User 1: I agree, starting with a high-level data model will help us understand the data flow.
upvoted 0 times
...
...
Renay
1 year ago
I disagree. We should document how the relevant systems interact to have a better understanding of the project scope.
upvoted 0 times
...
Mitzie
1 year 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
11 months ago
User 4: Let's make sure we have a solid evaluation plan in place before diving into requirements elicitation.
upvoted 0 times
...
Jennie
11 months 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
11 months ago
User 2: That makes sense. It will help us ensure that the requirements meet the project goals.
upvoted 0 times
...
Arlyne
11 months ago
User 1: I think we should go with B) Define how the solution will be evaluated.
upvoted 0 times
...
...
Tarra
1 year ago
I agree with Novella. It's important to have a clear evaluation criteria before starting requirements elicitation.
upvoted 0 times
...
Novella
1 year ago
I think we should define how the solution will be evaluated first.
upvoted 0 times
...

Save Cancel