Go-Live Approach for New System Implementation: Fallback Plan Best Practices

Fallback Plan Best Practices

Prev Question Next Question

Question

While reviewing the project plan for a new system prior to go-live, an IS auditor notes that the project team has not documented a fallback plan.

Which of the following would be the BEST go-live approach in this situation?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

A.

In this situation, the best go-live approach would be to use parallel processing (Option A).

Parallel processing is a deployment strategy in which both the old and new systems are run in parallel for a certain period of time to ensure that the new system is working properly before the old system is retired. This approach allows for a fallback plan in case something goes wrong with the new system.

In contrast, immediate cutover (Option B) is a deployment strategy in which the old system is turned off and the new system is turned on at the same time. This approach does not allow for a fallback plan, and if something goes wrong, it could result in significant downtime for the organization.

Real-time replication (Option C) is a data backup strategy in which data is continuously backed up to a secondary system in real-time. This approach does not provide a fallback plan for the new system and is not a suitable go-live approach.

Load balancing (Option D) is a technique used to distribute workloads across multiple computing resources to optimize performance, and is not a suitable go-live approach.

Therefore, parallel processing is the best go-live approach in this situation, as it allows for a fallback plan in case something goes wrong with the new system.