routers and routing technologies is very challenging; security and isolation must also be kept in mind. Packet core design: The packet core design should be aligned to the use cases planned, the transactions per second, the user throughput, latency, and the quality of service requirements. Based on the data center design selected, the packet core can be distributed or centralized. It is possible to have a centralized control plane and distributed user plane functions. It is also possible to have distributed data and control plane functions that are collocated in regional data centers. Since the control plane transactions are all HTTP-based and transported via TCP, latency can cause retransmissions, which, in turn, causes a huge signaling overhead. Hence, it is also important to tune the timers SO that unnecessary retransmissions can be avoided. Scaling: After the network has been built initially, it is just a matter of time before it will need to be scaled. Hence, it is important to bear in mind the future scope of expansion while planning network. This headroom for expansion should be accommodated in every stage and component of the network, from the rack space and power requirements in the data center to the server's routers/switches and IP allocation. Automation comes in handy for scaling applications in or out as 5G cloud-native design tasks such as orchestrating and configuring servers and network functions can be done at the click of a button. Test framework design: A robust test framework that can easily onboard test cases and scenarios goes a long way when building a robust and resilient network. Tests should aim to verify functionality and test the performance of each network function, as well as test failure scenarios such as reboot or server replacement scenarios, test other component failure scenarios, and test geo-redundancy, latency, performance under load conditions, border scenarios, alarm testing, upgrades, KPI dashboard verification, and so on. Hence, each aspect of the network, including its fu