GCP Associate Cloud Engineer Practice Question 95: Memorystore Session Cache
Google Cloud Associate Cloud Engineer · Test 10 · question 5 of 10
A web application deployed on Compute Engine needs a fast, fully managed, in-memory cache to store user session data. The team does not want to install, patch, or operate their own Redis servers, and they want the cache to be compatible with the standard Redis client libraries their application already uses.
Which Google Cloud service should they use?
Show answer and explanation
Answer:
Memorystore for Redis is a fully managed, in-memory data store service that is protocol compatible with open source Redis, so existing Redis client libraries work without modification. Google handles provisioning, patching, replication, and failover, which fits a team that does not want to operate its own Redis instances, and its low-latency in-memory design is well suited to session caching.
Option B is wrong because Cloud SQL for MySQL is a managed relational database on disk-backed storage; it is not an in-memory cache and has far higher latency for the simple key-value lookups a session store needs. Option C is wrong because Firestore is a managed NoSQL document database built for durable application data with a different API and consistency model, not an in-memory Redis-compatible cache. Option D is wrong because Bigtable is a wide-column NoSQL database designed for very large analytical and time-series workloads, not a low-latency session cache with Redis compatibility.
Reference: Memorystore for Redis overview