What describes having extra components not strictly necessary to function, but used in case of a failure in another component?

What describes having extra components not strictly necessary to function, but used in case of a failure in another component?

• A. Redundancy
• B. Redundant Hardware
• C. Load Balancing
• D. Clustering

Answer: (A)

Redundancy is the idea here. It describes having extra components that aren’t strictly needed to perform the function under normal operation, but are kept so they can take over if another component fails. This setup provides fault tolerance and helps ensure the system stays available even when something goes wrong, such as a power supply or network path failing and a spare kicking in without noticeable downtime. This isn’t about distributing work to multiple systems for performance (that would be load balancing) or about having several machines that work together as a single service (that’s clustering). Redundant hardware is simply a way to implement redundancy, but the fundamental concept is the presence of those spare components ready to assume responsibility in a failure.

Redundancy is the idea here. It describes having extra components that aren’t strictly needed to perform the function under normal operation, but are kept so they can take over if another component fails. This setup provides fault tolerance and helps ensure the system stays available even when something goes wrong, such as a power supply or network path failing and a spare kicking in without noticeable downtime.

This isn’t about distributing work to multiple systems for performance (that would be load balancing) or about having several machines that work together as a single service (that’s clustering). Redundant hardware is simply a way to implement redundancy, but the fundamental concept is the presence of those spare components ready to assume responsibility in a failure.