A city property-lookup API saturates its origin database during peak citizen traffic. Which design best protects the database while improving response times?
Select an answer to reveal the explanation.
Short Explanation
Caching is the librarian’s card catalog—citizens get common parcel answers from ElastiCache or CloudFront instead of waking the whole records vault every time. Killing replicas or ditching TLS doesn’t protect the origin; it just makes the vault lonelier or less safe.
Full Explanation
Caching frequently requested property data with ElastiCache and/or CloudFront reduces origin database load and improves latency for read-heavy civic lookups. Removing read capacity, disabling TLS, or relying on ephemeral instance store do not form a scalable caching strategy and introduce availability or security problems.