Log In
Or create an account -> 
Imperial Library
  • Home
  • About
  • News
  • Upload
  • Forum
  • Help
  • Login/SignUp

Index
Exam Ref 70-486: Developing ASP.NET MVC 4 Web Applications Introduction
Microsoft certifications Acknowledgments Errata & book support We want to hear from you Stay in touch
Preparing for the exam 1. Design the application architecture
Objective 1.1: Plan the application layers
Planning data access
Data access options Design approaches Data access from within code
Planning for separation of concern (SoC) Using models, views, and controllers appropriately
Model Controllers
Actions and Action Results Routes and Routing Asynchronous Controllers
Views
The Razor View and Web Forms View Engines Extending the View Engines
Choosing between client-side and server-side processing Designing for scalability Objective summary Objective review
Objective 1.2: Design a distributed application
Integrating web services Designing a hybrid application Planning for session management in a distributed environment Planning web farms Objective summary Objective review
Objective 1.3: Design and implement the Windows Azure role life cycle
Understanding Windows Azure and roles Identifying startup tasks Identifying and implementing Start, Run, and Stop events Objective summary Objective review
Objective 1.4: Configure state management
Choosing a state management mechanism Planning for scalability Using cookies or local storage to maintain state
Cookies HTML5 Web Storage
Applying configuration settings in the Web.config file Implementing sessionless state Objective summary Objective review
Objective 1.5: Design a caching strategy
Implementing page output caching
Donut caching Donut hole caching Distribution caching
Implementing data caching Implementing application caching
Create the application cache manifest Reference the manifest Transfer the manifest
Implementing HTTP caching Objective summary Objective review
Objective 1.6: Design and implement a WebSocket strategy
Reading and writing string and binary data Choosing a connection loss strategy Deciding when to use WebSockets Objective summary Objective review
Objective 1.7: Design HTTP modules and handlers
Implementing synchronous and asynchronous modules and handlers Choosing between modules and handlers in IIS Objective summary Objective review
Chapter summary Answers
Objective 1.1: Thought experiment Objective 1.1: Review Objective 1.2: Thought experiment Objective 1.2: Review Objective 1.3: Thought experiment Objective 1.3: Review Objective 1.4: Thought experiment Objective 1.4: Review Objective 1.5: Thought experiment Objective 1.5: Review Objective 1.6: Thought experiment Objective 1.6: Review Objective 1.7: Thought experiment Objective 1.7: Review
2. Design the user experience
Objective 2.1: Apply the user interface design for a web application
Creating and applying styles using CSS Using HTML to structure and lay out the user interface Implementing dynamic page content based on design Objective summary Objective review
Objective 2.2: Design and implement UI behavior
Implementing client validation
Models Views Controllers
Using remote validation Using JavaScript and the DOM to control application behavior Extending objects by using prototypal inheritance Using AJAX to make partial page updates Implementing the UI using jQuery Objective summary Objective review
Objective 2.3: Compose the UI layout of an application
Implementing partials for reuse in different areas of the application Designing and implementing pages by using Razor templates Designing layouts to provide visual structure Implementing master/application pages Objective summary Objective review
Objective 2.4: Enhance application behavior and style based on browser feature detection
Detecting browser features and capabilities Creating a web application that runs across multiple browsers and mobile devices Enhancing application behavior and style by using vendor-specific extensions Objective summary Objective review
Objective 2.5: Plan an adaptive UI layout
Planning for applications that run in browsers on multiple devices Planning for mobile web applications Objective summary Objective review
Chapter summary Answers
Objective 2.1: Thought experiment Objective 2.1: Review Objective 2.2: Thought experiment Objective 2.2: Review Objective 2.3: Thought experiment Objective 2.3: Review Objective 2.4: Thought experiment Objective 2.4: Review Objective 2.5: Thought experiment Objective 2.5: Review
3. Develop the user experience
Objective 3.1: Plan for search engine optimization and accessibility
Using analytical tools to parse HTML Viewing and evaluating conceptual structure by using plugs-in for browsers Writing semantic markup for accessibility Objective summary Objective review
Objective 3.2: Plan and implement globalization and localization
Planning a localization strategy Creating and applying resources to the UI Setting cultures Creating satellite resource assemblies Objective summary Objective review
Objective 3.3: Design and implement MVC controllers and actions
Applying authorization attributes and global filters Implementing action behaviors Implementing action results Implementing model binding Objective summary Objective review
Objective 3.4: Design and implement routes
Defining a route to handle a URL pattern Applying route constraints Ignoring URL patterns Adding custom route parameters Defining areas Objective summary Objective review
Objective 3.5: Control application behavior by using MVC extensibility points
Implementing MVC filters and controller factories Controlling application behavior by using action results Controlling application behavior by using view engines Controlling application behavior by using model binders Controlling application behavior by using route handlers Objective summary Objective review
Objective 3.6: Reduce network bandwidth
Bundling and minifying scripts
Bundling Minifying
Compressing and decompressing data Planning a content delivery network (CDN) strategy Objective summary Objective review
Chapter summary Answers
Objective 3.1: Thought experiment Objective 3.1: Review Objective 3.2: Thought experiment Objective 3.2: Review Objective 3.3: Thought experiment Objective 3.3: Review Objective 3.4: Thought experiment Objective 3.4: Review Objective 3.5: Thought experiment Objective 3.5: Review Objective 3.6: Thought experiment Objective 3.6: Review
4. Troubleshoot and debug web applications
Objective 4.1: Prevent and troubleshoot runtime issues
Troubleshooting performance, security, and errors
Using Performance Wizard Using Visual Studio Profiler Using Performance Monitor
Troubleshooting security issues Implementing tracing, logging, and debugging Enforcing conditions by using code contracts Enabling and configuring health monitoring Objective summary Objective review
Objective 4.2: Design an exception handling strategy
Handling exceptions across multiple layers Displaying custom error pages, creating your own HTTPHandler, and setting Web.config attributes Handling first chance exceptions Objective summary Objective review
Objective 4.3: Test a web application
Creating and running unit tests
Running integration tests Creating mocks
Creating and running web tests
Types of load tests Test planning
Objective summary Objective review
Objective 4.4: Debug a Windows Azure application
Collecting diagnostic information Choosing log types Debugging a Windows Azure application Objective summary Objective review
Chapter summary Answers
Objective 4.1: Thought experiment Objective 4.1: Review Objective 4.2: Thought experiment Objective 4.2: Review Objective 4.3: Thought experiment Objective 4.3: Review Objective 4.4: Thought experiment Objective 4.4: Review
5. Design and implement security
Objective 5.1: Configure authentication
Authenticating users
Anonymous authentication Basic authentication Digest authentication Forms authentication Windows authentication ASP.NET Impersonation authentication Client Certificate authentication and IIS Client Certificate authentication Custom authentication
Enforcing authentication settings Choosing between Windows, Forms, and custom authentication Managing user session by using cookies Configuring membership providers Creating custom membership providers Objective summary Objective review
Objective 5.2: Configure and apply authorization
Creating roles Authorizing roles by using configuration Authorizing roles programmatically Creating custom role providers Implementing WCF service authorization Objective summary Objective review
Objective 5.3: Design and implement claims-based authentication across federated identity stores
Implementing federated authentication by using Windows Azure Access Control Service Creating a custom security token by using Windows Identity Foundation Handling token formats for SAML and SWT tokens Objective summary Objective review
Objective 5.4: Manage data integrity
Understanding encryption terminology Applying encryption to application data Applying encryption to the configuration sections of an application Signing application data to prevent tampering Objective summary Objective review
Objective 5.5: Implement a secure site with ASP.NET
Securing communication by applying SSL certificates Salting and hashing passwords for storage Using HTML encoding to prevent cross-site scripting attacks (AntiXSS Library) Implementing deferred validation and handle unvalidated requests Preventing SQL injection attacks by parameterizing queries Preventing cross-site request forgeries (XSRFs) Objective summary Objective review
Chapter summary Answers
Objective 5.1 Thought experiment Objective 5.1 Review Objective 5.2 Thought experiment Objective 5.2 Review Objective 5.3 Thought experiment Objective 5.3 Review Objective 5.4 Thought experiment Objective 5.4 Review Objective 5.5 Thought experiment Objective 5.5 Review
A. About the Author Index About the Author Copyright
  • ← Prev
  • Back
  • Next →
  • ← Prev
  • Back
  • Next →

Chief Librarian: Las Zenow <zenow@riseup.net>
Fork the source code from gitlab
.

This is a mirror of the Tor onion service:
http://kx5thpx2olielkihfyo4jgjqfb7zx7wxr3sd4xzt26ochei4m6f7tayd.onion