How is the risk of updating legacy systems relatively greater than with regular software?
A) legacy systems are risky to update as they are built on obsolete tools and technologies.
B) The legacy system has a lot of documentation, making it more prone to failure.
C) Legacy systems can never be updated successfully, so the risk involved is relatively greater.
D) Legacy systems have a lot of risks because they are already not working.
A) legacy systems are risky to update as they are built on obsolete tools and technologies.
C) Yes, it can be considered as a legacy system.
D) It is a potential source of causing incompatibilities between multiple modules.
You're welcome! That's great to hear. Congratulations on your score! If you have any more questions, feel free to ask.
Thank you. I got a 100% on the Consequences of Adding Functionality quickcheck.
Suppose an operating system is no longer supported by the organization and is costly to buy now. Would it be considered a legacy system?
A) It is not a legacy system as the organization does not support it anymore.
B) Operating systems cannot be considered legacy systems.
C) Yes, it can be considered as a legacy system.
D) Yes, because it is costly to buy now.
What can be the consequences of updating only one module of legacy software irrespective of its effect on other modules?
A) It is a reason for one module to outperform the other modules and potentially cause problems.
B) It is a perfectly healthy way to update legacy software, and there are no associated risks.
C) It is a source of introducing latency to the processes of legacy software.
D) It is a potential source of causing incompatibilites between multiple modules.