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 5 Question 17 Discussion

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

A developer recommends modifying an existing portion of code that is not part of the scope and is causing low performance on the current solution. Which of the following actions should the project manager most likely take?

Show Suggested Answer Hide Answer
Suggested Answer: A

The project manager should ask the developer to create a change request, which is a formal document that describes the proposed change, its benefits, costs, risks, and impacts on the project scope, schedule, budget, and quality. A change request is the first step in the change control process, which involves evaluating, approving, or rejecting changes to the project baselines. The project manager should not do nothing, because ignoring the recommendation could result in poor performance and customer dissatisfaction. The project manager should not ask the developer to implement the recommendation without following the change control process, because that could cause scope creep, which is the uncontrolled expansion of the project scope without proper authorization or adjustment of the project resources and objectives. The project manager should not communicate the change status before the change request is submitted and approved, because that could create confusion and false expectations among the project stakeholders. Reference = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 4: Project Integration Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 4: Project Integration Management2; What is a Change Request and How to Manage It3


Contribute your Thoughts:

0/2000 characters
Joanna
3 months ago
I’m surprised they’d suggest changing something out of scope.
upvoted 0 times
...
Dianne
3 months ago
Wait, modifying existing code? That sounds risky!
upvoted 0 times
...
Carli
3 months ago
Scope creep is a real concern, so option B makes sense.
upvoted 0 times
...
Leah
4 months ago
I disagree, doing nothing might hurt the project in the long run.
upvoted 0 times
...
Laila
4 months ago
A change request is definitely the way to go.
upvoted 0 times
...
Felicitas
4 months ago
I feel like implementing the recommendation directly could lead to issues later. I’m leaning towards option B, but I’m not completely confident.
upvoted 0 times
...
Arthur
4 months ago
I think we practiced a similar question where the project manager had to weigh performance against scope. Maybe communicating the change status is key?
upvoted 0 times
...
Lorean
4 months ago
I’m not sure, but I feel like asking for a change request could be a good way to handle it.
upvoted 0 times
...
Tonette
5 months ago
I remember we discussed scope creep in class, so I think doing nothing might be the right choice here.
upvoted 0 times
...
Kerry
5 months ago
This is a tricky one. I'm not sure if I should just do nothing or if I should try to get the recommendation implemented. I'll need to carefully review the project scope and potential impact before deciding.
upvoted 0 times
...
Inocencia
5 months ago
Hmm, I'm a bit confused on this one. Is the recommendation really considered scope creep, or could it potentially improve the overall performance? I'll need to weigh the pros and cons.
upvoted 0 times
...
Ernie
5 months ago
This seems like a tricky one. I'm not sure if the recommendation is really out of scope or if it's worth pursuing. I'll need to think it through carefully.
upvoted 0 times
...
Mitsue
5 months ago
Okay, I think I've got a handle on this. The key is to determine if the recommendation is truly outside the project's scope. If it is, then a change request would be the appropriate action. If not, then implementing the recommendation could be beneficial.
upvoted 0 times
...
Mari
5 months ago
This seems like a straightforward question about access control and security. I'll need to think through the implications of the HR Admin role and system Admin role.
upvoted 0 times
...
Edelmira
2 years ago
I see your point, Misty, but making sure the change is properly documented is crucial for accountability and tracking.
upvoted 0 times
...
Misty
2 years ago
But wouldn't that just slow down the process? Maybe the project manager should just communicate the change status.
upvoted 0 times
...
Kenda
2 years ago
I agree with Teddy. It's important to properly document any changes outside of the scope.
upvoted 0 times
...
Teddy
2 years ago
I think the project manager should ask a developer to create a change request.
upvoted 0 times
...
Tula
2 years ago
I believe communication about the change status is also crucial for transparency.
upvoted 0 times
...
Lorriane
2 years ago
In that case, we can review the scope and consider implementing the recommendation.
upvoted 0 times
...
Louis
2 years ago
But what if the recommendation is really necessary for improving performance?
upvoted 0 times
...
Tula
2 years ago
I agree with Lorriane, it's important to follow proper procedures for modifications.
upvoted 0 times
...
Lorriane
2 years ago
I think we should ask the developer to create a change request.
upvoted 0 times
...
Alline
2 years ago
Haha, I can just see the project manager's face if we tried to implement this without their approval. 'You did what now?' Not a good look, my friends.
upvoted 0 times
...
Chantell
2 years ago
Yeah, I don't know about this one. Scope creep is a real problem, and we don't want to end up with a project that's completely off the rails. Better to stick to the plan and communicate the issue to the project manager.
upvoted 0 times
...
Elmer
2 years ago
I agree, we can't just start making random changes without going through the proper channels. A change request seems like the way to go here. That way, we can properly evaluate the impact and get the necessary approvals.
upvoted 0 times
Penney
2 years ago
D
upvoted 0 times
...
Irma
2 years ago
A
upvoted 0 times
...
Shawna
2 years ago
C
upvoted 0 times
...
...
Maira
2 years ago
Hmm, this is a tricky one. On one hand, the developer is trying to improve performance, which is a good thing. But making changes outside the scope seems risky. I'd be hesitant to just go for it without proper documentation and approval.
upvoted 0 times
...

Save Cancel