Welcome to the final part of this study guide. If you are reading this cover to cover, thank you and congratulations on making it this far. If not, well, I suggest reviewing all the topics prior to here. Everything we have worked on and discussed so far goes into creating and operating a highly available Azure SQL Database platform. Steady, predictable performance, alerting and monitoring, security, and maintenance are “table stakes” that prevent most SQL Database service disruptions. What we have left are “external” factors like hardware, power, and data center failures. Problems with the platform or the environment that stop the host services from operating are what we need to anticipate and mitigate. Either way, we are starting my favorite topic – high availability/disaster resilience. This part is about how we plan for and react to such disruptions.