Correct Answer: Data Protection keys are not shared across instances, causing session decryption to fail on different instances
ASP.NET Core encrypts session data using Data Protection keys. When multiple app instances each have their own keys, a session written by Instance A cannot be decrypted by Instance...
Correct Answer
Data Protection keys are not shared across instances, causing session decryption to fail on different instances
Why This Answer Is Correct
ASP.NET Core encrypts session data using Data Protection keys. When multiple app instances each have their own keys, a session written by Instance A cannot be decrypted by Instance B. The fix is to configure Data Protection to persist keys to a shared store (e.g., Azure Blob Storage) so all instances share the same keys.
This question evaluates your knowledge of Azure Cache for Redis — a core concept tested in Microsoft Certified: Azure Developer Associate (AZ-204). Understanding Azure Cache for Redis is essential for designing scalable, secure, and cost-effective cloud architectures. Mastery of this topic will help you answer scenario-based questions confidently on exam day.
Your ASP.NET Core application experiences database overload during peak traffic because the same product catalog queries run thousands of times per minute. You add Azure Cache for Redis to cache query results. Which caching pattern should you implement to ensure stale data is never served indefinitely?
Your ASP.NET Core API queries the same product catalog data from SQL Database on every request. Under load, the database becomes a bottleneck with high DTU consumption. You want to add a caching layer that stores catalog data for 10 minutes and automatically refreshes stale data. Which implementation pattern should you use with Azure Cache for Redis?