When systems, hardware, or software are not supported by the original vendor, it is a vulnerability known as:
A. system sprawl
B. end-of-life systems
C. resource exhaustion
D. a default configuration
2 Comments on “When systems, hardware, or software are not supported b…”
blablasays:
B seems correct.
All systems eventually reach an end-of-life stage.
End-of-life is defined as when the system has reached a point where it can no longer function as intended.
End-of-life status can be reached for many reasons,
….. such as lack of vendor support,
…. a failure to instantiate on newer hardware,
…. or incompatibility with other aspects of a system.
Old software systems are frequently referred to as legacy systems, especially when they are still in use post end-of-life.
6
0
meacsays:
The question is badly written, once more.
Why would an original vendor not support its own systems, hardware, or software?
What sort of vendor does that?
The question should read: “When systems, hardware, or software are NO LONGER supported by the original vendor…” instead.
This makes “B- end-of-life systems “ is the only feasible answer
B seems correct.
All systems eventually reach an end-of-life stage.
End-of-life is defined as when the system has reached a point where it can no longer function as intended.
End-of-life status can be reached for many reasons,
….. such as lack of vendor support,
…. a failure to instantiate on newer hardware,
…. or incompatibility with other aspects of a system.
Old software systems are frequently referred to as legacy systems, especially when they are still in use post end-of-life.
6
0
The question is badly written, once more.
Why would an original vendor not support its own systems, hardware, or software?
What sort of vendor does that?
The question should read: “When systems, hardware, or software are NO LONGER supported by the original vendor…” instead.
This makes “B- end-of-life systems “ is the only feasible answer
2
0