Microsoft
AZ-204 · Question #123
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution. Determine whether the solution meets the stated goals…
The correct answer is B. No. The worst solution from a performance and scalability standpoint is to use a database backed session state provider. Instead use Azure Cache for Redis.
Submitted by sofia.br· Mar 30, 2026Develop for Azure storage
Question
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution. Determine whether the solution meets the stated goals. You are developing and deploying several ASP.Net web applications to Azure App Service. You plan to save session state information and HTML output. You must use a storage mechanism with the following requirements: - Share session state across all ASP.NET web applications - Support controlled, concurrent access to the same session state data for multiple readers and a single writer - Save full HTTP responses for concurrent requests You need to store the information. Proposed Solution: Deploy and configure an Azure Database for PostgreSQL. Update the web applications. Does the solution meet the goal?
Options
- AYes
- BNo
How the community answered
(34 responses)- A18% (6)
- B82% (28)
Explanation
The worst solution from a performance and scalability standpoint is to use a database backed session state provider. Instead use Azure Cache for Redis.
Topics
#session state#Azure Cache for Redis#distributed caching#App Service
Community Discussion
No community discussion yet for this question.