ViewState-based Session Management CASENET Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   In an ASP.NET Web Forms application, what is the primary purpose of ViewState?

   • ATo store user authentication tokens securely on the server for the entire application lifetime
   • BTo cache frequently used database query results for the duration of a user's visit
   • CTo maintain page and control state across postbacks without storing data on the server
   • DTo store server-side data that persists across user sessions and application restarts
   Reveal Solution Discussion Select an answer first
2. 7expert · hard

   An ASP.NET application has a page that uses ViewState to store a large collection of data for a data grid. The page is slow to load, and the developer wants to improve performance. The data is not sensitive, but it must be available after postback for sorting and paging. What is the best approach?

   • AEnable ViewState compression using a third-party library.
   • BStore the data in Session and use ViewState only for the grid's current page index and sort expression.
   • CDisable ViewState and reload the data from the database on every postback.
   • DIncrease the ViewState limit in web.config.
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   A developer is building a multi-step wizard in ASP.NET Web Forms. The wizard needs to preserve user input across postbacks, but the data is not sensitive. The developer wants to minimize the amount of data sent to the client while keeping the wizard functional. What is the recommended approach?

   • AUse a cookie to store the wizard data.
   • BStore the wizard data in server-side Session and use ViewState only to track the current step.
   • CStore all wizard data in ViewState to avoid server-side memory usage.
   • DDisable ViewState and use QueryString parameters to pass the data between steps.
   Reveal Solution Discussion Select an answer first
5. 9expert · hard

   A security audit reveals that an ASP.NET application's ViewState is not encrypted, and the application stores a user's account number in ViewState. The developer proposes to enable encryption. However, the compliance team also requires that the account number not be stored client-side at all. What should the developer do?

   • AMove the account number to Session and disable ViewState for the page.
   • BEnable ViewState MAC validation to prevent tampering.
   • CStore the account number in a hidden field and encrypt the page.
   • DEnable ViewState encryption to protect the account number.
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   An e-commerce site uses ViewState to store a user's shopping cart items so they persist across postbacks. The cart data is not sensitive, but the application is experiencing performance issues because the ViewState is large. The developer wants to reduce the ViewState size while keeping the cart available across postbacks. What should the developer do?

   • AIncrease the ViewState limit in the web.config to accommodate the large data.
   • BStore the cart in the server-side Session and keep only a session identifier in ViewState.
   • CEnable ViewState compression using the built-in compression attribute.
   • DMove the cart to a cookie and read it on every postback.
   Reveal Solution Discussion Select an answer first