Free CompTIA Project+ PK0-005 Actual Exam Questions - Question 13 Discussion
the downtime after the scheduled window. Which of the following should be added to the issue log?
Maybe C here. Since the executive is upset about extended downtime, making sure customer notification is tracked seems key to improving communication next time. The issue log should reflect that gap.
If the downtime extended unexpectedly, wouldn’t adding the rollback plan to the issue log help prevent future delays by ensuring a clear fallback? Just tracking notifications might miss the technical root cause.
Maybe C here. If downtime went past schedule, letting customers know late is a big deal and should definitely be tracked in the issue log for accountability.
B/C? Rollback plan and customer notification both cover key failure points.
B vs C, but B seems more concrete for tracking what went wrong during the extension.
A/D? Automated testing (D) seems indirect since it’s more about preventing issues, but continuous integration (A) could relate because if the integration process had a failure that caused delays, logging that would help pinpoint the root cause.
B. Adding the rollback plan to the issue log makes sense because if the downtime went beyond the window, it might mean the rollback didn’t happen as expected or wasn’t effective. Having that documented helps identify if the plan was adequate or if it needs improvement to prevent future delays. It’s more about controlling the impact once things start to go wrong rather than just communication or testing details.
This one’s tricky, but I’d say C fits best here. The escalation came from an exec about the downtime extending beyond what was scheduled, so the key issue is probably about communication—making sure customers and stakeholders were properly notified about the delay. Adding customer notification to the issue log would highlight gaps in that process and could prevent similar surprises in future releases.
D imo. Automated testing results should definitely be in the issue log because if tests failed or were incomplete, that directly impacts downtime. Without that info, you can’t fully understand why downtime extended. It’s not just about notifying customers or rolling back but figuring out what went wrong technically.
B imo. Since the problem is about downtime going longer than planned, having a rollback plan logged could be crucial. If they had a solid rollback, maybe the downtime wouldn’t have extended as much. It’s more about managing the incident response than just notifying customers or testing stuff after the fact.
Guessing A here. Continuous integration issues could cause deployment delays leading to downtime extension, so logging that might help track the root cause beyond just customer notification.
Maybe D. Automated testing could be relevant here since extended downtime might indicate a failure in the deployment or testing process. If automated tests had caught issues earlier, the downtime might have been avoided or shortened. While customer notification (C) is important, the issue log should also capture root causes or technical gaps that led to the problem, and missing automated tests fits that angle. This could help prevent similar issues in future releases.
This definitely isn’t about plans like rollback, so B's out. The issue log should track what went wrong or caused the delay, so C fits better since it deals with customer notification problems. C
B/C? This sounds like a problem that might need a rollback plan if things went wrong, but also customers should’ve been notified about the delay. Both seem important to log.
Is the issue about why the downtime extended or how to fix it?