AZ-204 · Question #47
AZ-204 Question #47: Real Exam Question with Answer & Explanation
The correct answer is A: Yes. We should use stateful services when we want data to persist, and stateless service when data must not persist. For stateful services, the Reliable Services programming model allows you to consistently and reliably store your state right inside your service by using Reliable Coll
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 develop an entertainment application where users can buy and trade virtual real estate. The application must scale to support thousands of users. The current architecture includes five Azure Virtual Machines (VM) that connect to an Azure SQL Database for account information and Azure Table Storage for backend services. A user interacts with these components in the cloud at any given time Routing Service - Routes a request to the appropriate service and must not persist data across sessions Account Service - Stores and manages all account information and authentication and requires data to persist across sessions. User Service - Stores and manages all user information and requires data to persist across sessions. Housing Network Service - Stores and manages the current real-estate economy and requires data to persist across sessions. Trade Service - Stores and manages virtual trade between accounts and requires data to persist across sessions. Due to volatile user traffic, a microservices solution is selected for scale agility. You need to migrate to a distributed microservices solution on Azure Service Fabric. Solution: Create a Service Fabric Cluster with a stateless Reliable Service for Routing Service. Create stateful Reliable Services for all other components. Does the solution meet the goal?
Options
- AYes
- BNo
Explanation
We should use stateful services when we want data to persist, and stateless service when data must not persist. For stateful services, the Reliable Services programming model allows you to consistently and reliably store your state right inside your service by using Reliable Collections. A stateless service is one where there is no state maintained within the service across calls. Any state that is present is entirely disposable and doesn't require synchronization, replication, persistence, or high availability. https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-reliable-services-introduction
Community Discussion
No community discussion yet for this question.