When should prioritization of requirements take place?
Suggested Answer: C
Get Premium ECBA Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
12 comments · newest first
MI
Ming
1 year ago
I’ve always thought it’s best to do it after tracing tasks.
MA
Marla
1 year ago
Wait, can we really prioritize after maintaining requirements? Seems off.
CO
Cory
1 year ago
I think it should start at the beginning, though.
OR
Oretha
1 year ago
I totally agree, it’s not a one-time thing.
LE
Leah
1 year ago
Prioritization should happen continually!
LA
Laquita
1 year ago
I thought we only prioritize after maintaining requirements, but now I’m questioning if that’s too late in the process.
MA
Maile
1 year ago
I’m leaning towards option C, but I feel like there might be specific phases where it’s more critical.
AZ
Azalee
1 year ago
I think prioritization should happen at the beginning, but I’m not sure if that’s the only time it’s needed.
JE
Jenelle
1 year ago
I remember a practice question that emphasized the importance of continual prioritization throughout the project.
MA
Mable
1 year ago
Okay, I got this. Option B looks like the right approach - it iterates through the array and prints out the index and value for each element.
CE
Celeste
1 year ago
I'm a bit confused by this question. I know MySQL versions have that X.Y.Z format, but I can't remember the exact meaning of each part. I'll have to think about it more.
ER
Erinn
1 year ago
I'm pretty sure the stats command has functions like count, sum, and average, so I'll go with option C.