You are designing a solution to implement a cache to track all the products which are browsed by users on an ecommerce website, using a key-value database. Your solution needs to have the ability to…

Question

Options

• AChoose Bigtable and connect using Private Google Access API endpoint(s).
• BChoose Memorystore for Redis Cluster and Private Service Connect for networking connectivity.
• CChoose a Memorystore for Redis instance and Private Service Access for networking connectivity.
• DChoose a Redis instance on a VM in the Shared VPC network.

• A
  4% (3)
• B
  82% (56)
• C
  3% (2)
• D
  10% (7)

Explanation

Memorystore for Redis Cluster with Private Service Connect (PSC) satisfies all requirements. Redis is a high-performance in-memory key-value store, ideal for caching browsed products with low latency and high throughput. Memorystore is Google's fully managed Redis service, meeting the managed service requirement. Critically, Private Service Connect (PSC) is the correct networking technology here because it allows connectivity from multiple VPC networks to a single service endpoint - this is a key differentiator. Option A (Bigtable) is a wide-column store suited for analytics, not caching, and Private Google Access does not support multi-VPC connectivity. Option C uses Private Service Access (VPC Peering), which is limited to a single VPC and does not support multi-VPC scenarios. Option D (Redis on a VM) is not a managed service.

No community discussion yet for this question.