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
Shouldn’t it be A and B?
0
1
IMO Session state is not suitable for GLOBAL information because it´s only valid for the session.
0
0
no puede ser B ya que este representa un cnjunto de variables definidas para el usuario per aqui dice guarda informacion global en lo que no cambiara con frecuencia cuando es global quiere decir que sera usada para todos los usuarios 😉
0
0
If you use Application State in a distributed environment, don’t you have to manually replicate the data across all servers? I don’t know that A is a good choice here.
Disadvantages of using application state are:
• Application scope: The scope of application state can also be a disadvantage. Variables stored in application state are global only to the particular process the application is running in, and each application process can have different values. Therefore, you cannot rely on application state to store unique values or update global counters in Web-garden and Web-farm server configurations.
https://msdn.microsoft.com/en-us/library/z1hkazw7.aspx
0
0
A & C are correct.
1
0
http://failedturing.blogspot.com/2014/06/microsoft-70-486-design-distributed.html
0
0
Yes so for people wondering about answer A: A is possible since the question states the data to be stored is (1) insecure and (2) does not change frequently but also importantly (3) it is a small amount. If it were a (1) secure (2) volatile (3) large amount of global data then A would presumably not be correct.
0
0
https://msdn.microsoft.com/en-us/library/z1hkazw7.aspx at the bottom of the page
State management option
Recommended usage
Application state
Use when you are storing infrequently changed, global information that is used by many users, and security is not an issue. Do not store large quantities of information in application state.
Session state
Use 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.
Profile properties
Use when you are storing user-specific information that needs to be persisted after the user session is expired and needs to be retrieved again on subsequent visits to your application.
Database support
Use when you are storing large amounts of information, managing transactions, or the information must survive application and session restarts. Data mining is a concern, and security is an issue.
I believe only A is a correct answer for this scenario.
0
0