More isn’t always better when it comes to public cloud resilience, as over-the-top architecting for resilience can quickly result in overspending. You’ll need to assess whether and when to accept or avoid that risk. When designing your approach, start with business risk appetite, data protection needs, application criticality, licensing, as-a-service subscription costs, and other key considerations. This report looks at how to determine the best level of public cloud resilience for your organization, from must-have high availability to just-in-case cold sites.