You are designing a distributed application that runs on the Windows Azure platform. The
application must store a small amount of insecure global information that does not change
frequently. You need to configure the application to meet the requirements. Which serverside state management option should you use? (Each correct answer presents a complete
solution. Choose all that apply.)
A.
Windows Azure application state
B.
Sql Azure
C.
Profile properties of the Windows Azure application
D.
Windows Azure session state
Explanation:
SQL Database provides a relational database management system for Windows Azure and is based
on SQL Server technology. With a SQL Database instance, you can easily provision and deploy
relational database solutions to the cloud, and take advantage of a distributed data center that
provides enterprise-class availability, scalability, and security with the benefits of built-in data
protection and self-healing.
Session States in Windows Azure.
If you are a Web developer, you are probably very familiar with managing user state – that is
you are familiar with tracking user activity and actions across several request-response
exchanges that occur in Web applications. Since HTTP is a stateless protocol, developers
over the years have developed all sorts of means to manage state. You’ll even find an
MSDN page providing alternatives and recommendations for state management here.
Cookies, hidden fields, and query strings are some client-side options to tracking user state.
When it comes to managing that state on the server-side, most Web developers rely on
session objects.
Can someone explain in detail why D is a correct answer, especially since the question indicates this is a distributed application?
0
0
I believe the only correct answer is B.
0
0
Shouldn’t it be A & B? https://msdn.microsoft.com/en-us/library/z1hkazw7.aspx
1
0
You are right. If looked on the link provided by you and found this:
Application State: “Data that is shared by multiple sessions and does not change often is the ideal type of data to insert into application-state variables.”
Session State: “The ideal data to store in session-state variables is short-lived, sensitive data that is specific to an individual session.”
The request say to store “global information that does not change frequently”, so Session State is not ideal because session-state variables is short-lived.
0
0
Windows Azure application state does not exist
0
0
https://msdn.microsoft.com/en-us/library/1as0t7ff%28v=vs.80%29.aspx
0
0
It should be A & B
1
0
This is one of those vague questions, but two things count against (A):
1.) Application state is not suitable for server farms scenarios – it’s machine specific.
2.) “Windows Azure Application State” is not a thing.
If A was just “Application State,” I might be inclined to think that we’re supposed to assume a single server in our “distributed” application. But I don’t think that’s typical for enterprise apps.
I think the answer is (B), alone.
0
0
By the way, part of that new 231Q 70-486 dumps are available here:
https://drive.google.com/open?id=0B-ob6L_QjGLpflNtUWtkNlk3ODJFY0pqOUhqVFEwc0lrd0QtamRxUHFLLUdWZEVDaGtlQWM
Best Regards!
0
0