AZ-305 Question 185
Single answerYou manage an e-commerce platform that experiences heavy read traffic for product pricing data during peak shopping events. The pricing data changes only a few times a day, but the system must handle large volumes of read requests with minimal latency. You want to reduce the load on your primary database and provide fast lookup times. Which of the following solutions would best meet these requirements?
- A
Use Azure Cache for Redis to store frequently accessed product pricing data in memory.
- B
Enable geo-redundant read replicas in the Azure SQL database to offload read requests.
- C
Implement Azure Storage queues to retrieve cached data across multiple consumer instances.
- D
Deploy an Azure Files share and regularly copy product pricing data for faster reads.
Show answer and explanation
Correct answer: A
Explanation
Using Azure Cache for Redis is a recommended approach for reducing the load on backend data sources while providing sub-millisecond data retrieval. It stores frequently accessed data in memory, enabling high throughput and low latency. More guidance can be found in the official Microsoft documentation on caching strategies in Azure: https://docs.microsoft.com/azure/architecture/best-practices/caching.
- A. Correct.
Option 1 is correct. Azure Cache for Redis is designed to provide extremely low-latency data access, making it ideal for caching frequently accessed data such as product pricing. It also helps reduce database read load by serving data from an in-memory store.
- B. Incorrect.
Option 2 is incorrect. While geo-redundant read replicas can distribute the read load geographically, they are not primarily designed to serve as an in-memory cache. Latency remains higher compared to an in-memory caching solution, and you still incur underlying SQL database read costs.
- C. Incorrect.
Option 3 is incorrect. Azure Storage queues are meant for decoupling and buffering messages between application components, not for caching data. They do not provide sub-millisecond retrieval for read-heavy operations.
- D. Incorrect.
Option 4 is incorrect. Azure Files is useful for shared file storage but is not optimized for high-volume, low-latency data retrieval. It also lacks the in-memory capabilities needed to significantly reduce database load in a read-heavy scenario.