Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
AWS Certified Solutions Architect - Professional · AWS
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Why not the others: B (ElastiCache Redis): Works, but adds always-on infrastructure, capacity planning, and operational overhead/cost. Not “minimizing cost increase” for a serverless stack. C (increase Aurora max memory): Treats the symptom by scaling up DB capacity, usually higher cost and doesn’t reduce duplicated work. D (throttling): Prevents overload by rejecting requests (429s). That harms partners/users and doesn’t “support additional usage.”
A is right, it's much cheaper to cache the GET endpoints at the edge location. Creating a redis ElastiCache cluster might prove much more expensive, don't forget about the transfer costs of data from the edge location to the cluster. It will be FAR more expensive. Lastly, caching in the edge WILL reduce database reads, as there wouldn't be as many requests to the database, because the cache is at the endpoint.
B. Use ElastiCache (Redis) as a caching layer ElastiCache for Redis provides a high-performance, in-memory cache that can handle frequent identical queries without hitting the database. Caching reduces database calls, which avoids memory errors and reduces Aurora Serverless compute scaling, thereby minimizing cost. Lambda functions can easily be updated to check Redis before querying the database. Ideal for read-heavy workloads with repeated identical queries, which is exactly the case here.