A city 311 portal team plans to insert a new Amazon ElastiCache lay…

Question

A city 311 portal team plans to insert a new Amazon ElastiCache layer in front of a hot RDS read path. Leadership wants the change promoted only after proving it under realistic citizen-traffic patterns. Which remediation approach best meets that continuous-improvement gate?

Accepted Answer

Load-test the proposed cache topology and key strategy in a pre-production environment against recorded or synthetic 311 traffic, then promote only candidates that meet latency and error budgets — New caches look shiny until Black Friday—or tax-deadline Monday—hits the 311 phones. Stage a dress rehearsal with real-ish load, then promote the winner. Skipping the load test is how you invent a citizen outage.

Answer

Deploy the cache straight to production during lunch hour and watch social media for complaints

Answer

Disable CloudWatch metrics on RDS so cache hit rates cannot create false alarms

Answer

Replace RDS with a single shared EBS volume mounted to every web tier host

A city 311 portal team plans to insert a new Amazon ElastiCache layer in front of a hot RDS read path. Leadership wants the change promoted only after proving it under realistic citizen-traffic patterns. Which remediation approach best meets that continuous-improvement gate?

Short Explanation

Full Explanation