An organization wants to duplicate critical system components to enhance reliability and mitigate single points of failure. Which design consideration should the organization use?

Redundancy involves provisioning duplicate instances of critical system components - such as servers, network links, or databases - so that no single failure can bring down the entire system. This design consideration directly addresses single points of failure by ensuring that the failure of one component does not interrupt service availability. Common redundancy patterns include active-active and active-passive configurations across multiple zones or regions.

Backups are a data protection mechanism for restoring information after loss or corruption, not a real-time duplication strategy that keeps services running during component failures.

Latency refers to the time delay in data transmission across a network and is a performance consideration, not a method for duplicating system components.

Security refers to protecting systems from unauthorized access and threats, which is separate from the reliability concern of eliminating single points of failure through component duplication.