Q: 12
A company is offering APIs as a service over the internet to provide unauthenticated read access to
statistical information that is updated daily. The company uses Amazon API Gateway and AWS
Lambda to develop the APIs. The service has become popular, and the company wants to enhance
the responsiveness of the APIs.
Which action can help the company achieve this goal?
Options
Discussion
Makes sense to pick A. API caching in API Gateway is great for read-heavy, rarely-changing data since it cuts down on backend calls and speeds up responses. Not 100% but that's how I'd tackle this type of scenario.
C or A? Had something like this in a mock and pretty sure A is the way to go.
Its A, pretty sure. BatchGetItem lets you fetch from both tables in one call, so that cuts down network chattiness. The others either require extra queries or scans which isn't efficient. Bit confused if there's a smarter way but this matches what I've seen in practice exams. Anyone else get stuck on this?
A is right here, not D. Usage plans and API keys (D) are more about controlling access and throttling, not about speeding up response time. Only caching in API Gateway (A) actually improves responsiveness for read-heavy unauthenticated APIs. Unless I'm missing some edge case, it's A.
API caching gives you faster responses since data updates are only daily. A
D imo. People might pick C by mistake because CORS is about access, but responsiveness will improve way more with caching (A).
A tbh
Be respectful. No spam.
