Google Professional Cloud Developer Question 457
Select 2Google Cloud PlatformYou are designing a serverless application that processes high-frequency API requests in Google Cloud. To optimize performance and reduce latency, you decide to cache the results of certain computations that rarely change. Which of the following strategies would be most appropriate for implementing caching in this scenario?
- A
Use Cloud Memorystore to cache results and retrieve them before invoking the computation.
- B
Implement client-side caching in the application using a JavaScript in-memory store.
- C
Use a Pub/Sub topic to store the computed results and query the topic when needed.
- D
Leverage Cloud Storage with versioning to store precomputed results and retrieve them using signed URLs.
- E
Use Cloud CDN to cache results at the edge for read-heavy workloads.
Show answer and explanation
Correct answers: A, E
Explanation
Caching is a critical strategy for optimizing performance in high-frequency API request scenarios. Cloud Memorystore provides a low-latency, in-memory caching solution that can be used to store and retrieve computation results quickly. Additionally, Cloud CDN is effective for caching and serving frequently accessed content at edge locations, especially for read-heavy workloads. These options are well-suited for serverless applications and align with Google Cloud's managed service offerings.
- A. Correct.
Cloud Memorystore is a managed Redis and Memcached service, ideal for caching frequently accessed data to reduce computation time and improve performance.
- B. Incorrect.
Client-side caching can be effective in some cases, but it is not scalable or reliable for high-frequency API requests in a distributed system.
- C. Incorrect.
Pub/Sub is designed for asynchronous messaging and event-driven architectures, not for caching or querying specific computation results.
- D. Incorrect.
Cloud Storage is a durable object storage solution, but it is not optimized for caching or low-latency access patterns required for high-frequency API requests.
- E. Correct.
Cloud CDN is suitable for caching static or computed content at edge locations, which significantly reduces latency for read-heavy workloads.