State management in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does Cloud Storage maintain state for object versions?

Google Cloud Storage can keep multiple versions of the same object. What happens when you enable versioning on a bucket and upload a new file with the same name?

A The new upload creates a new version of the object, keeping the old version accessible.

B The new upload overwrites the existing object and deletes the old version permanently.

C The bucket rejects the upload because the object name already exists.

D The new upload merges the content with the existing object automatically.

💡 Hint

Think about how versioning helps you recover old files.

When versioning is enabled, Cloud Storage keeps old versions of objects. Uploading a file with the same name creates a new version, so old versions remain accessible.

❓ Architecture

intermediate

Choosing state storage for a Cloud Run service

You have a Cloud Run service that processes user requests. It needs to keep user session data between requests. Which storage option is best to maintain state across multiple instances?

A Use Cloud SQL to store session data persistently.

B Store session data in Cloud Run instance memory (RAM).

C Write session data to a local file on the Cloud Run container.

D Use environment variables to store session data.

💡 Hint

Remember that Cloud Run instances can scale and restart anytime.

Cloud Run instances are stateless and can restart or scale out. Storing session data in Cloud SQL ensures persistence and sharing across instances.

❓ security

advanced

Securing state data in Firestore

You store user preferences in Firestore. How can you ensure only the user can read and write their own preferences?

A Encrypt data on the client side and store encrypted blobs without rules.

B Store all preferences in a public collection with no security rules.

C Use IAM roles to grant all users read/write access to the Firestore database.

D Use Firestore security rules to allow read/write only if request.auth.uid matches the document ID.

💡 Hint

Think about how Firestore rules can restrict access based on user identity.

Firestore security rules can check the authenticated user's ID and allow access only to documents matching that ID, protecting user data.

❓ Configuration

advanced

Configuring Memorystore for Redis for session state

You want to use Memorystore for Redis to store session state for a GKE cluster. Which configuration is required to allow GKE nodes to connect securely to Memorystore?

A Deploy Memorystore in a different project without VPC peering.

B Expose Memorystore with a public IP and whitelist GKE node IPs.

C Create Memorystore in the same VPC network as GKE and allow private IP access.

D Use Memorystore with no network configuration; it is accessible by default.

💡 Hint

Consider network security and private connectivity.

Memorystore requires being in the same VPC or connected via VPC peering to allow secure private IP access from GKE nodes.

✅ Best Practice

expert

Designing state management for a multi-region app

You design a multi-region web app on GCP that requires low-latency access to user state globally. Which approach best balances consistency and performance?

A Use a single regional Cloud Spanner instance and route all requests there.

B Use multi-region Cloud Spanner with strong consistency and automatic replication.

C Store state in local instance memory and sync periodically with a central database.

D Use Firestore in native mode with multi-region replication and eventual consistency.

💡 Hint

Think about global consistency and replication features.

Multi-region Cloud Spanner provides strong consistency with automatic replication across regions, ideal for global low-latency state management.