New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

CompTIA PK0-005 Exam - Topic 4 Question 15 Discussion

Actual exam question for CompTIA's PK0-005 exam
Question #: 15
Topic #: 4
[All PK0-005 Questions]

During the testing phase of a project, the regression test fails due to a specific item that is disrupting the entire system. Which of the following documents should the project manager use to identify who requested this item?

Show Suggested Answer Hide Answer
Suggested Answer: D

A traceability matrix is a document that maps the requirements of a project to the deliverables, test cases, and changes that are produced to meet those requirements. It helps the project manager to track the origin, status, and impact of each requirement throughout the project life cycle. A traceability matrix can also identify who requested or approved each requirement. Therefore, the project manager can use the traceability matrix to identify who requested the specific item that caused the regression test to fail12.


Contribute your Thoughts:

0/2000 characters
Isaac
3 months ago
I always thought the risk register was for potential issues, not requests.
upvoted 0 times
...
Rosalind
3 months ago
Wait, are we sure the traceability matrix is the right choice?
upvoted 0 times
...
Tommy
3 months ago
I disagree, the defect log should be the go-to for this.
upvoted 0 times
...
Justa
4 months ago
I think the issue log is more relevant here.
upvoted 0 times
...
Tequila
4 months ago
Definitely the traceability matrix! It tracks who requested what.
upvoted 0 times
...
Ressie
4 months ago
I’m leaning towards the traceability matrix too, but I wonder if the risk register could also provide some insights about who was involved in the request.
upvoted 0 times
...
Chaya
4 months ago
I feel like the issue log could help identify who raised the concern, but I’m not confident if that’s the best document for this situation.
upvoted 0 times
...
Annabelle
4 months ago
I remember practicing a question like this, and I think the defect log is more about tracking issues rather than who requested something.
upvoted 0 times
...
Rasheeda
5 months ago
I think the traceability matrix might be the right choice since it tracks requirements and changes, but I'm not completely sure.
upvoted 0 times
...
Torie
5 months ago
Ugh, I'm drawing a blank on the different project management documents and what kind of information is typically stored in each one. I'll have to make an educated guess and hope for the best on this question.
upvoted 0 times
...
Tracey
5 months ago
Ah, I think the traceability matrix is the way to go here. That document should link the requirements to the specific items implemented, so it should show who originally requested the problematic item. I'm feeling confident about this one.
upvoted 0 times
...
Aleisha
5 months ago
Hmm, I'm a bit unsure about this one. The issue log, risk register, and defect log all seem like they could potentially have the relevant information. I'll need to review my notes on project management documentation to make the best guess.
upvoted 0 times
...
Lajuana
5 months ago
This seems like a straightforward question about project documentation. I'll need to think carefully about which document would contain the information about who requested the item that's causing the regression test failure.
upvoted 0 times
...
Willard
5 months ago
Hmm, this looks like a tricky one. I'll need to think through the different inspection points and what they represent.
upvoted 0 times
...
Yolande
5 months ago
Hmm, I'm not too familiar with the NetSuite interface, so I'm not sure where to look for this. The Scripting tab might be a good place to start, but I'm not confident about that.
upvoted 0 times
...
Ming
2 years ago
That's a good point, the Traceability matrix links requirements to test cases and can show who requested specific items.
upvoted 0 times
...
France
2 years ago
In that case, the Traceability matrix might help in identifying the origin of the item in the system.
upvoted 0 times
...
Ming
2 years ago
But what if the item was requested by someone during the planning phase and it wasn't logged as a defect?
upvoted 0 times
...
Ming
2 years ago
I agree with France, the Defect log usually contains information on who reported the issue.
upvoted 0 times
...
France
2 years ago
I think the project manager should use the Defect log to identify who requested the disrupting item.
upvoted 0 times
...
Micah
2 years ago
Haha, I bet the project manager is just wishing they had a crystal ball right about now. But in all seriousness, I think Precious makes a good point. The issue log is probably the best place to start looking for who requested this disruptive item.
upvoted 0 times
...
Precious
2 years ago
I disagree, I think the issue log is the way to go. If this item was previously identified as a potential problem, it should be documented there. The traceability matrix is more for tracking requirements, not necessarily change management.
upvoted 0 times
...
Buck
2 years ago
You know, I was just thinking the same thing. This seems like the kind of problem that could have been avoided if the traceability matrix was properly maintained. That's got to be the way to go here.
upvoted 0 times
...
Harrison
2 years ago
Good point, Mei. The risk register is definitely worth a look. Although, I have to say, if this is causing the entire system to go haywire, I'm a little surprised it wasn't caught earlier. Maybe the project manager needs to work on their risk assessment skills.
upvoted 0 times
Alpha
2 years ago
A) Issue log
upvoted 0 times
...
Patrick
2 years ago
D) Traceability matrix
upvoted 0 times
...
Laura
2 years ago
C) Defect log
upvoted 0 times
...
Lezlie
2 years ago
A) Issue log
upvoted 0 times
...
...

Save Cancel