How is the risk of updating legacy systems relatively greater than with regular software?(1 point)

Question

Responses

The legacy system has a lot of documentation, making it more prone to failure.
The legacy system has a lot of documentation, making it more prone to failure.

Legacy systems can never be updated successfully, so the risk involved is relatively greater.
Legacy systems can never be updated successfully, so the risk involved is relatively greater.

Legacy systems have a lot of risks because they are already not working.
Legacy systems have a lot of risks because they are already not working.

Legacy systems are risky to update as they are built on obsolete tools and technologies

Answer 1

The most accurate response is:

Legacy systems are risky to update as they are built on obsolete tools and technologies.

This is because updating legacy systems often involves dealing with outdated programming languages, lack of vendor support, and potential incompatibility with newer systems, all of which contribute to greater risk compared to updating more modern software.

Answer 2

Suppose an operating system is no longer supported by the organization and is costly to buy now. Would it be considered a legacy system?(1 point)
Responses

Operating systems cannot be considered legacy systems.
Operating systems cannot be considered legacy systems.

It is not a legacy system as the organization does not support it anymore.
It is not a legacy system as the organization does not support it anymore.

Yes, because it is costly to buy now.
Yes, because it is costly to buy now.

Yes, it can be considered as a legacy system.

Answer 3

The correct response is:

Yes, it can be considered as a legacy system.

A legacy system is typically defined as an older system that is still in use, but may not be supported or maintained by the organization or its vendor. The cost of buying or maintaining it further emphasizes its status as a legacy system.

Answer 4

What can be the consequences of updating only one module of legacy software irrespective of its effect on other modules?(1 point)
Responses

It is a perfectly healthy way to update legacy software, and there are no associated risks.
It is a perfectly healthy way to update legacy software, and there are no associated risks.

It is the source of introducing latency to the processes of legacy software.
It is the source of introducing latency to the processes of legacy software.

It is a reason for one module to outperform the other modules and potentially cause problems.
It is a reason for one module to outperform the other modules and potentially cause problems.

It is a potential source of causing incompatibilities between multiple modules.

Answer 5

The correct response is:

It is a potential source of causing incompatibilities between multiple modules.

Updating only one module of legacy software without considering its interaction with other modules can lead to compatibility issues, as the newly updated module may not work correctly with the older, unmodified modules. This can cause errors, system failures, or degraded performance.