Memorystore for Redis caching in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does Memorystore for Redis handle failover?

When a primary Redis instance in Memorystore fails, what happens to maintain availability?

A The service deletes all data and creates a new instance from scratch.

B The service requires manual intervention to restart the primary instance.

C The service automatically promotes a replica to primary and redirects traffic without downtime.

D The service pauses all client connections until the primary is fixed.

💡 Hint

Think about how cloud services keep your app running smoothly even if one part breaks.

Memorystore for Redis uses replicas to ensure high availability. If the primary fails, a replica is promoted automatically, minimizing downtime.

❓ Configuration

intermediate

Which Redis version is supported by Memorystore for Redis?

You want to use a specific Redis version with Memorystore. Which version is officially supported?

A Redis 6.x

B Redis 2.8

C Redis 3.0

D Redis 5.0

💡 Hint

Check the latest stable Redis versions supported by cloud providers.

Memorystore for Redis supports Redis 6.x, which includes modern features and security improvements.

❓ security

advanced

What is the best way to secure access to a Memorystore for Redis instance?

Which method ensures only your application can access your Memorystore Redis instance?

A Enable public IP and use Redis AUTH password only.

B Use SSL/TLS encryption without network restrictions.

C Allow all IPs and rely on Redis AUTH password.

D Use VPC Service Controls and private IP with firewall rules restricting access.

💡 Hint

Think about network isolation and limiting who can reach your Redis instance.

Memorystore instances use private IPs inside a VPC. Combining this with firewall rules and VPC Service Controls restricts access securely.

❓ Architecture

advanced

How to design a caching layer with Memorystore for Redis for a global app?

You have users worldwide and want low latency caching. What is the best architecture using Memorystore?

A Deploy one Memorystore instance in a single region and serve all users from it.

B Deploy multiple Memorystore instances in regional GCP zones near users and route traffic accordingly.

C Use Memorystore only in the US region and rely on CDN for caching.

D Deploy Memorystore instances in multiple regions but do not sync data between them.

💡 Hint

Think about placing caches close to users to reduce delay.

Deploying regional Memorystore instances near users reduces latency. Traffic routing ensures users connect to the nearest cache.

✅ Best Practice

expert

What is the recommended approach to handle Redis data persistence in Memorystore?

Memorystore for Redis does not support persistence by default. How should you ensure data durability?

A Use application-level backups by exporting data regularly and storing in Cloud Storage.

B Rely on Memorystore's built-in snapshot backups automatically enabled.

C Enable Redis AOF persistence directly in Memorystore settings.

D Configure Redis to write to local disk on the instance for persistence.

💡 Hint

Memorystore is a managed service with limited persistence options. Think about external backups.

Memorystore does not support persistence or AOF. Best practice is to export data from Redis and store backups externally, such as in Cloud Storage.