Download Microsoft.70-486.TestBells.2018-06-15.110q.tqb
| Vendor: | Microsoft |
| Exam Code: | 70-486 |
| Exam Name: | Developing ASP.NET MVC 4 Web Applications |
| Date: | Jun 15, 2018 |
| File Size: | 11 MB |
Demo Questions
Question 1
You are developing an ASP.NET MVC application that will be deployed to servers on multiple networks.
The application must be compatible with multiple browsers. You must track the page number that the user is viewing in search results.
You need to program the location for storing state information.
Where should you persist state information?
- Session
- QueryString
- Application
- TempData
Correct answer: B
Question 2
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.)
- Application state
- Session state
- Database support
- Profile properties
Correct answer: AC
Explanation:
Application state is a data repository available to all classes in an ASP.NET application. Application state is stored in memory on the server and is faster than storing and retrieving information in a database. Unlike session state, which is specific to a single user session, application state applies to all users and all sessions. Therefore, application state is a useful place to store small amounts of often-used data that does not change from one user to another. The topics in this section provide information on how application state works and how to use it. 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. References: https://msdn.microsoft.com/en-us/library/azure/bf9xhdz4(v=vs.85).aspx Application state is a data repository available to all classes in an ASP.NET application. Application state is stored in memory on the server and is faster than storing and retrieving information in a database. Unlike session state, which is specific to a single user session, application state applies to all users and all sessions. Therefore, application state is a useful place to store small amounts of often-used data that does not change from one user to another. The topics in this section provide information on how application state works and how to use it.
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.
References: https://msdn.microsoft.com/en-us/library/azure/bf9xhdz4(v=vs.85).aspx
Question 3
You are developing an ASP.NET MVC application. The application is deployed in a web farm and is accessed by many users.
The application must handle web server failures gracefully. The servers in the farm must share the short-term state information.
You need to persist the application state during the session.
What should you implement?
- ASP.NET session state
- A local database
- A state server
- Profile properties
Correct answer: C
Explanation:
ASP.NET session state service provides a somewhat slower service than the in-process variant as we need to make calls to a remote server. All session data is stored in memory so shutting down the state machine will wipe out all session data as well. References: https://dotnetcodr.com/2013/07/01/web-farms-in-net-and-iis-part-5-session-state-management/ ASP.NET session state service provides a somewhat slower service than the in-process variant as we need to make calls to a remote server. All session data is stored in memory so shutting down the state machine will wipe out all session data as well.
References: https://dotnetcodr.com/2013/07/01/web-farms-in-net-and-iis-part-5-session-state-management/
