AZ-204 · Question #47
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 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…
Question
Options
- AYes
- BNo
How the community answered
(42 responses)- A81% (34)
- B19% (8)
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
Topics
Community Discussion
No community discussion yet for this question.