Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
You are designing the caching layer for a real-time multiplayer gaming platform running on Google Cloud. The total dataset fits within 100 GB, write throughput stays below 10 Gbps, and read traffic frequently exceeds 20 Gbps.
Your caching solution must meet the following requirements:
Which Memorystore configuration should you select?
Memorystore for Memcached is a fully managed, distributed in-memory key-value store built on open source Memcached. It acts like a large distributed hash table optimized for simple, high-speed caching across up to 20 nodes (up to 5 TB total capacity).
Memcached would be appropriate if the workload only needed simple key-value caching of database query results, required multi-terabyte horizontal scale, and could tolerate partial cache flushes during zonal failures without snapshot recovery.
Distributing Memcached nodes across zones improves node availability for remaining shards during an outage, but it is fundamentally different from cross-zone data replication in Memorystore for Redis Standard Tier. Additionally, Memorystore for Memcached is deprecated in favor of newer Redis-compatible offerings like Memorystore for Valkey.
Memorystore for Redis in the Basic Tier provisions a standalone, single-node ephemeral cache with no replication or failover infrastructure. It is designed purely for cost-effective caching of easily regenerated data.
The Basic Tier would be the right choice if the application needed Redis data structures for non-critical caching, had total traffic below 16 Gbps, and could tolerate losing the entire cache during a restart or zonal failure.
Developers sometimes select the Basic Tier assuming they can easily toggle high availability on later. In practice, because tier upgrades are not supported in-place, choosing the right tier up front is critical.
Memorystore for Redis is a fully managed, in-memory data structure store on Google Cloud. Selecting the Standard Tier with read replicas enabled provisions a primary Redis node alongside up to five read replica nodes distributed across multiple zones within a region.
This configuration is the only managed option that simultaneously satisfies rich data structure support, multi-zone replication with automatic failover, RDB snapshot persistence, and read throughput scaling beyond 16 Gbps without requiring self-managed cluster orchestration.
Memorystore for Redis in the Standard Tier (read replicas disabled) deploys a primary node paired with a standby replica node in a different zone to provide high availability and automatic failover without exposing extra endpoints for read scaling.
This configuration would be ideal if the application required high availability, automatic failover, and Redis data structures, but combined read and write traffic remained comfortably under 16 Gbps.
A common misconception is that the Standard Tier automatically distributes read queries to its failover replica. Unless read replicas are explicitly enabled, the replica acts strictly as a standby backup for failover rather than a read-scaling node.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated