Which of the following is NOT a typical reason for creating an internetwork?
A. groups of users should be logically separated
B. the LAN has grown and communication has become inefficient
C. you're running a legacy operating system on one of your servers
D. there is a long distance between groups of computers
Answer: C
You might also like to view...
Zipcar is an example of ownership
Indicate whether the statement is true or false
Developers often think of software quality in terms of faults and failures. Faults are problems, such as loops that never terminate or misplaced commas in statements, that developers can see by looking at the code. Failures are problems, such as a system crash or the invocation of the wrong function, that are visible to the user. Thus, faults can exist in programs but never become failures,
because the conditions under which a fault becomes a failure are never reached. How do software vulnerabilities fit into this scheme of faults and failures? Is every fault a vulnerability? Is every vulnerability a fault? What will be an ideal response?