A city backup process writes unencrypted snapshots to the same account that runs production workloads, with no isolated copy for ransomware recovery. What secure backup redesign should architects implement?
Select an answer to reveal the explanation.
Short Explanation
Backups that live next to production without a lock are like spare house keys under the same doormat attackers already flipped. Encrypt them and park a copy in a separate account. Ransomware resilience is about distance and keys, not hope.
Full Explanation
A secure backup process encrypts recovery points and separates copies from the compromised blast radius—commonly via AWS Backup with KMS encryption and cross-account or vault-locked copies. Unencrypted same-account snapshots, laptop sync, or disabling backups undermine ransomware readiness. Continuous improvement of existing municipal backup designs should verify encryption, immutability or isolation controls, and tested restores aligned to RTO/RPO.