MENU
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?
Suggested Answer: C
Get Premium PMI-PBA Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
33 comments · newest first
SU
Sueann
12 months ago
I thought preparing the traceability matrix was the first step?
NI
Nikita
1 year ago
Wait, why are we rushing into requirements? Shouldn't we plan better?
RO
Rosendo
1 year ago
Agree with Amos, evaluation criteria set the stage.
VI
Vilma
1 year ago
I think drafting a high-level data model is more important.
AM
Amos
1 year ago
Definitely need to define how the solution will be evaluated first!
GL
Glenn
1 year 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.
AR
Arlene
1 year ago
I practiced a question similar to this, and I feel like preparing the requirements traceability matrix is more of a later step.
TH
Thora
1 year ago
I'm not entirely sure, but I remember something about documenting system interactions being important. Maybe that's what we should do first?
DO
Domitila
1 year 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.
IZ
Izetta
1 year 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.
CA
Catalina
1 year 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.
RA
Raelene
1 year 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.
MY
Myrtie
1 year ago
This question seems straightforward, I'm pretty confident I know the answer.
DO
Donte
2 years 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!
CH
Cheryl
1 year ago
C: Let's make sure we have a clear plan in place before diving into the details.
DU
Dudley
1 year ago
B: I agree, that's an important step before starting requirements elicitation.
DE
Delfina
1 year ago
A: I think we should define how the solution will be evaluated.
RO
Royal
2 years 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.
YU
Yuki
1 year ago
D) Document how the relevant systems interact.
MA
Madelyn
1 year ago
C) Draft a high-level data model.
BE
Benedict
1 year ago
B) Define how the solution will be evaluated.
CO
Cordelia
2 years 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?
RO
Rory
2 years 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.
AL
Albina
1 year ago
User 2: Definitely, it will provide a clear picture of the information we need to gather for the project.
IS
Isidra
2 years ago
User 1: I agree, starting with a high-level data model will help us understand the data flow.
RE
Renay
2 years ago
I disagree. We should document how the relevant systems interact to have a better understanding of the project scope.
MI
Mitzie
2 years 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.
OL
Oliva
1 year ago
User 4: Let's make sure we have a solid evaluation plan in place before diving into requirements elicitation.
JE
Jennie
1 year ago
User 3: Agreed. It's important to have a clear understanding of how we will measure the success of the project.
LO
Loreta
1 year ago
User 2: That makes sense. It will help us ensure that the requirements meet the project goals.
AR
Arlyne
1 year ago
User 1: I think we should go with B) Define how the solution will be evaluated.
TA
Tarra
2 years ago
I agree with Novella. It's important to have a clear evaluation criteria before starting requirements elicitation.
NO
Novella
2 years ago
I think we should define how the solution will be evaluated first.