Exam Associate Cloud Engineer topic 1 question 62 discussion

I agree with you

and what about HTTP, how are you supporting that with Redis?

Using pricing calculator matching 730 hrs per month for both.. Memorystore is 537.28 per month and vm (6 cpus 32 gb memory) is 174.41 per month. So vm is still cheaper even with 6 cpus.

$0.023 * 32 = $0.736 is it cheaper?

Just to complement the answer: We are looking for "latency-sensitive website" What it's good for Memorystore for Redis provides a fast, in-memory store for use cases that require fast, real-time processing of data. From simple caching use cases to real time analytics, Memorystore for Redis provides the performance you need. Caching: Cache is an integral part of modern application architectures. Memorystore for Redis provides low latency access and high throughput for heavily accessed data, compared to accessing the data from a disk based backend store. Session management, frequently accessed queries, scripts, and pages are common examples of caching. https://cloud.google.com/memorystore/docs/redis/redis-overview#what_its_good_for

INCORRECT: ANSWER B is not a cost-effective solution since it requires a custom instance type with 6 vCPUs and 32 GB of memory, which is over-provisioned for a caching HTTP reverse proxy. ANSWER C is also not a cost-effective solution since it uses Kubernetes Engine, which has a higher management overhead and may not be necessary for a single caching HTTP reverse proxy. Additionally, using n1-standard-32 instances as nodes is over-provisioned for the requirements of the caching HTTP reverse proxy. ANSWER D is not a viable solution since the instance type n1-standard-1 only provides 3.75 GB of memory, which is insufficient for the 30-GB cache and the additional 2 GB of memory required for the rest of the processes. Adding an SSD persistent disk of 32 GB will not provide enough memory for the reverse proxy.