ls and parts inventory control, remote maintenance, and collaborative autonomous robots. Private networks can be widely deployed in the transport and utilities sector and consumer-focused IoT. With that, we have gone over the design considerations and use cases of a private network. Another important part of the design is the stability and resilience of the network against failures. We will examine this in the next section. 5G network resilience and failure design 5G networks are expected to cater to mission-critical applications, SO there will be circumstances where network failure can have a disastrous effect. Hence, tolerance to failure should be considered at every step during the design. Let us go through each consideration one by one, from the highest level to the finest granularity: Multiple control aggregation routers Multiple site aggregation Multiple site aggregation routers routers Site 1 Site 2 Multiple TOR switches for redundancy 2 instances of NF across 2 racks Multiple servers for server redundancy K8s API K8s API Node Pool Node Pool Multiple instance of containers and multiple nodes in a cluster Figure 11.12 - Levels of redundancy built into a network Network performance analysis The idea behind failure design is to have an alternative path along which traffic can flow in case of a single component failure. Most networks are expected to experience no impact from a single failure; some highly resilient networks have tolerances for more than one failure. Let us go into the details of the various redundancies built into the network shown in the preceding diagram: Data center redundancy: Every data center should have another data center in a geographically separate site as a standby - this is known as geo-redundancy. In the preceding figure, Site 1 and Site 2 are geo-redundant. Hence, if there is a complete failure of Site 1 for some reason, Site 2 will be fully equipped to carry the traffic seamlessly. Rack redundancy: Every cluster that comprises an application should span more than one rack. If the