PK0-005 · Question #61
A developer identifies a resolution to a minor issue the day before a product is scheduled to go live, but the fix will require additional work and testing. Which of the following is the BEST…
The correct answer is B. Log the resolution in the issue log, but resolve it after the product goes live. Since the issue is minor and the fix requires additional work and testing that cannot be safely completed in one day, the safest approach is to document it in the issue log and address it post-launch. Rushing an untested fix into production the day before go-live introduces…
Question
A developer identifies a resolution to a minor issue the day before a product is scheduled to go live, but the fix will require additional work and testing. Which of the following is the BEST approach for the project?
Options
- AMake the decision to push the fix before the product goes live.
- BLog the resolution in the issue log, but resolve it after the product goes live.
- CIgnore the fix because there is not enough time to implement it.
- DHold an impromptu meeting with the CAB to fix the issue.
How the community answered
(40 responses)- A5% (2)
- B78% (31)
- C3% (1)
- D15% (6)
Explanation
Since the issue is minor and the fix requires additional work and testing that cannot be safely completed in one day, the safest approach is to document it in the issue log and address it post-launch. Rushing an untested fix into production the day before go-live introduces significant risk of new defects or system instability. Ignoring the fix is irresponsible. Pushing it live without testing is reckless. Holding a CAB (Change Advisory Board) meeting for a minor issue at the last minute is disproportionate and would likely delay the launch.
Topics
Community Discussion
No community discussion yet for this question.