Interview Tips Interview Tips, Interview Questions and Answers

21Dec/090

Interview questions for ASP.NET (UI) Developers

    1. What three Session State providers are available in ASP.NET 1.1? What are the pros and cons of each?
    2. What is Web Gardening? How would using it affect a design?
    3. Given one ASP.NET application, how many application objects does it have on a single proc box? A dual? A dual with Web Gardening enabled? How would this affect a design?
    4. Describe how a browser-based Form POST becomes a Server-Side event like Button1_OnClick.
    5. What is a PostBack?
    6. What is ViewState? How is it encoded? Is it encrypted? Who uses ViewState?
    7. What is the <machinekey> element and what two ASP.NET technologies is it used for?
    8. Describe ways to present an arbitrary endpoint (URL) and route requests to that endpoint to ASP.NET.
    9. Explain how cookies work. Give an example of Cookie abuse.
    10. Explain the importance of HttpRequest.ValidateInput()?
    11. How does VaryByCustom work?
    12. How would one implement ASP.NET HTML output caching, caching outgoing versions of pages generated via all values of q= except where q=5 (as in http://localhost/page.aspx?q=5)?
    13. What kind of data is passed via HTTP Headers?
    14. Juxtapose the HTTP verbs GET and POST. What is HEAD?
    15. Name and describe at least a half dozen HTTP Status Codes and what they express to the requesting client.
    16. How does if-not-modified-since work? How can it be programmatically implemented with ASP.NET?
      Explain <@OutputCache%> and the usage of VaryByParam, VaryByHeader.
    17. Are threads reused in ASP.NET between reqeusts? Does every HttpRequest get its own thread? Should you use Thread Local storage with ASP.NET?
    18. Is the [ThreadStatic] attribute useful in ASP.NET? Are there side effects? Good or bad?
    19. Give an example of how using an HttpHandler could simplify an existing design that serves Check Images from an .aspx page.
    20. What kinds of events can an HttpModule subscribe to? What influence can they have on an implementation? What can be done without recompiling the ASP.NET Application?