AZ-305 Question 184
Select 2You have an Azure-based social media application that experiences unpredictable traffic spikes. The application frequently retrieves and updates session and feed data, and your team wants to offload frequent reads from your database to reduce latency and improve throughput. Which two actions should you recommend as part of your caching solution?
- A
Deploy a dedicated Azure Cache for Redis instance to store ephemeral session and feed data
- B
Use Basic tier Azure Cache for Redis combined with ephemeral disk caching to handle traffic spikes
- C
Implement Azure HPC Cache to store frequently accessed session data for lower latency
- D
Leverage Azure Cache for Redis Premium tier with eviction policies to handle peak loads efficiently
Show answer and explanation
Correct answers: A, D
Explanation
For applications that experience frequent reads and updates to session or feed data, Azure Cache for Redis offers low-latency, in-memory caching. The Premium tier is recommended for production workloads with unpredictable spikes because it supports advanced features like clustering, data persistence, and eviction policies. By contrast, the Basic tier is better suited for development or test scenarios. Azure HPC Cache is tailored for specialized HPC workloads rather than typical application caching. For more information, see the official Azure Cache for Redis documentation: https://learn.microsoft.com/azure/azure-cache-for-redis.
- A. Correct.
Option 1 is correct because a dedicated Azure Cache for Redis instance offers a fully managed, in-memory data store that can efficiently handle ephemeral session and feed data. It helps offload read queries from the primary database and provides low latency.
- B. Incorrect.
Option 2 is incorrect because the Basic tier of Azure Cache for Redis lacks features such as replication and high availability, making it less suitable for highly unpredictable traffic spikes that require robust resilience and scale. Also, ephemeral disk caching is not designed to reliably store session or feed data.
- C. Incorrect.
Option 3 is incorrect because Azure HPC Cache is built for high-performance computing scenarios using NFS-based workloads. It is not intended for typical application-level caching of rapidly changing data like user sessions and feeds.
- D. Correct.
Option 4 is correct because the Premium tier of Azure Cache for Redis includes features such as clustering, data persistence, and eviction policies, which are essential for handling large or unpredictable workloads efficiently.