Which combination of steps will meet this requirement?
(Choose two.)
Test recovery procedures.
Purchase instances weekly based on the previous week’s high traffic points.
Handle software failures automatically.
Scale the application vertically.
Make all changes in the environment manually.
Explanations:
Testing recovery procedures ensures that the company can quickly restore operations in the event of a failure, enhancing overall application reliability. Regular testing identifies any gaps in the recovery process, ensuring preparedness for high traffic situations.
Purchasing instances weekly based on previous high traffic does not ensure reliability during unpredictable traffic spikes. It may lead to under-provisioning or over-provisioning and does not adapt to sudden changes in demand effectively.
Automatically handling software failures (e.g., through mechanisms like auto-recovery or health checks) improves application reliability by ensuring that issues are resolved without manual intervention, thus maintaining availability during peak traffic times.
Vertical scaling (increasing the size of existing instances) has limits and may lead to single points of failure. It does not provide the elasticity needed to handle varying traffic loads effectively compared to horizontal scaling (adding more instances).
Making changes manually can introduce human error and delays, which undermine reliability. Automated processes for deployment and configuration management are more reliable, especially during high traffic periods.