-
How is the risk of updating legacy systems relatively greater than with regular software?
- Answer: Legacy systems are risky to update as they are built on obsolete tools and technologies.
-
Suppose an operating system is no longer supported by the organization and is costly to buy now. Would it be considered a legacy system?
- Answer: Yes, it can be considered as a legacy system.
-
What can be the consequences of updating only one module of legacy software irrespective of its effect on other modules?
- Answer: It is a potential source of causing incompatibilities between multiple modules.
How is the risk of updating legacy systems relatively greater than with regular software?(1 point)
Legacy systems are risky to update as they are built on obsolete tools and technologies.
Legacy systems have a lot of risks because they are already not working.
Legacy systems can never be updated successfully, so the risk involved is relatively greater.
The legacy system has a lot of documentation, making it more prone to failure.
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)
Yes, it can be considered as a legacy system.
Operating systems cannot be considered legacy systems.
Yes, because it is costly to buy now.
It is not a legacy system as the organization does not support it anymore.
What can be the consequences of updating only one module of legacy software irrespective of its effect
on other modules?(1 point)
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 potential source of causing incompatibilities between multiple modules.
It is a perfectly healthy way to update legacy software, and there are no associated risks.
1 answer