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

CompTIA Exam PK0-005 Topic 3 Question 7 Discussion

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

A project manager is overseeing the implementation of a major upgrade to a critical ERP system. The project sponsor is requiring that the upgrade should not exceed more than three hours of downtime for the implementation and validation in production. During cutover, the team runs into a validation issue after 2.5 hours, and the process is only 70% through the validation steps Which of the following actions should the project manager take?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Shasta
1 months ago
I'd go with C) and start that rollback plan - no point in trying to pull a rabbit out of a hat at this point. Unless, of course, the project manager has a time-traveling DeLorean hidden in their office. Then I'd say 'Floor it!'
upvoted 0 times
Lore
17 days ago
A) Notify customers the downtime will take longer than expected.
upvoted 0 times
...
Ciara
29 days ago
D) Record the issue and proceed with the implementation.
upvoted 0 times
...
Meghann
1 months ago
C) Begin executing the rollback plan.
upvoted 0 times
...
...
Leonor
1 months ago
A) Notify customers the downtime will take longer than expected. Honesty is the best policy, and the sponsor will understand if we communicate the issue proactively. After all, they'd probably be more upset if we just went over the deadline without warning.
upvoted 0 times
...
Crista
1 months ago
B) Add new team members to help speed up validation. With a little extra manpower, we might just be able to get the validation done within the 3-hour window. Plus, the sponsor will appreciate the effort to meet their requirement.
upvoted 0 times
...
Kristel
2 months ago
D) Record the issue and proceed with the implementation. The project is already 70% complete, and rolling back could create more issues. Plus, the sponsor didn't specify that the downtime had to be exactly 3 hours - just 'not exceed' that timeframe. Why not see if we can finish in the remaining 30 minutes?
upvoted 0 times
Solange
19 days ago
A) Notify customers the downtime will take longer than expected.
upvoted 0 times
...
Sylvia
26 days ago
D) Record the issue and proceed with the implementation.
upvoted 0 times
...
Daren
1 months ago
C) Begin executing the rollback plan.
upvoted 0 times
...
Clare
1 months ago
A) Notify customers the downtime will take longer than expected.
upvoted 0 times
...
...
Renato
2 months ago
I think notifying customers about the delay would be the best option to manage expectations.
upvoted 0 times
...
Donette
2 months ago
We should start executing the rollback plan to minimize the impact.
upvoted 0 times
...
Louvenia
2 months ago
C) Begin executing the rollback plan. The project sponsor clearly stated the downtime should not exceed 3 hours, and with the validation process only 70% complete after 2.5 hours, it's clear the deadline will be missed. Proceeding with the implementation at this point would be irresponsible.
upvoted 0 times
Cristen
1 months ago
A) Notify customers the downtime will take longer than expected.
upvoted 0 times
...
Jerry
1 months ago
C) Begin executing the rollback plan.
upvoted 0 times
...
...
Kami
2 months ago
We're in trouble, the downtime is taking longer than expected.
upvoted 0 times
...
Sherman
2 months ago
I agree with Mari, communication is key in situations like this. Let's go with option A.
upvoted 0 times
...
Mari
2 months ago
I think we should notify the customers about the delay and manage their expectations.
upvoted 0 times
...
Jeanice
2 months ago
We're in trouble, the validation is only 70% complete and we're almost out of time.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77