You are designing a distributed application. 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 server-side state management option should you use? (Each correct answer presents a complete
solution. Choose all that apply.)
A.
Application state
B.
Session state
C.
Database support
D.
Profile properties
Why the answer here is Session state?
Session state is used: when you are storing short-lived information that is specific to an individual session and security is an issue. Do not store large quantities of information in session state. Be aware that a session-state object will be created and maintained for the lifetime of every session in your application. In applications hosting many users, this can occupy significant server resources and affect scalability.
0
0
It can’t be applicationstate: Application state is not shared among multiple servers serving the same application, as in a Web farm, or among multiple worker processes serving the same application on the same server, as in a Web garden. Your application therefore cannot rely on application state containing the same data for application state across different servers or processes.
It can’t be profile properties or database support. So the only answer here that makes some sense: Session state (small amount…)
0
1
the test is for small amount of insecure data so why you going in another direction – Do not store large quantities of information in session state – exactly, so session state is ok and it doesn’t say how many users either so should be safe
0
1
The answer should be A and C. I have to disagree with someone_new as well as fsays.
Please check http://msdn.microsoft.com/en-us/library/ms178594%28v=vs.100%29.aspx
1
0
Yes I agree
0
0
why would you use database for a small amount of insecure data
0
0
For scalability reasons.
1
0
It should only be option C. database support. as Application state is not for distributed environment.
0
0
should be only C. wrong answer
0
0
neither application state or session state is available in distributed environment
0
0
Distributed application doesn´t mean necessarily having a web farm. You can have a distributed application if your DB is in a server and your only IIS instance in another.
As far as I understand A y C should be the answers.
1
0
Should be A,C
A: because it says global information, so storing at 1 places and this places is in MEMORY.
C: because the stored information should be retrieved from DB and loaded somewhere in this case it’s Application state. if you don’t choose this option (C), where should the information come from?
0
0
Answer is A .Application state because they clearly specify the server side state management. it says global information .
0
0
This question is confusing and can mean different scenarios. The one thing is for sure – it makes absolutely no sense to duplicate data for each user.
0
0
According to this link, answer is A & C: http://www.utestking.com/free-lead2pass-70-486-pdf-and-vce-dumps-100-percent-pass-guarantee-21-30.html
0
0
I think the key to the application state answer is that the data is ‘not frequently changed’. In other words we don’t have to synchronise the data across the servers. Each server can load it’s own copy of the global data. As a user session switches across the servers, the same data will be presented to the user from any server. An example of such data might be todays weather summary.
0
0
By the way, part of that new 231Q 70-486 dumps FYI:
https://drive.google.com/open?id=0B-ob6L_QjGLpflNtUWtkNlk3ODJFY0pqOUhqVFEwc0lrd0QtamRxUHFLLUdWZEVDaGtlQWM
Best Regards!
0
0