Designing And Developing Web Applications Using Microsoft .NET Framework 4

Code: 70-519
Price:

Exam 70-519 - Designing and developing web applications using Microsoft .NET Framework 4

Skills measured

This exam measures your ability to accomplish the technical tasks listed below. The percentages indicate the relative weight of each major topic area on the exam. The higher the percentage, the more questions you are likely to see on that content area on the exam.

Please note that the questions may test on, but will not be limited to, the topics described in the bulleted text.

Design the application architecture (19%)

  • Plan the division of application logic
    • Choose between client-side and server-side processing; plan separation of concern (partitioning functionality between controllers and evaluating business and data service consumption); plan for long-running processes (synchronous versus asynchronous)
  • Analyze requirements and recommend a system topology
    • Design interaction between applications; mapping logical design to physical implementation; validate nonfunctional requirements and cross-cutting concerns (communications, operations management, and security); evaluate baseline needs (scale and quality of service)
  • Choose appropriate client-side technologies
    • JavaScript; ASP.NET AJAX; jQuery; Microsoft Silverlight
  • Choose appropriate server-side technologies
    • User controls; server controls; partials; custom HtmlHelper extensions; web parts; inheriting controls; dynamic data controls
  • Design state management
    • Design an application for the proper use of application state, session state, and request state (ViewState, ControlState, Cache object, cookies, and client-side persistence)

Design the user experience (17%)

  • Design the site structure
    • Design application segmentation for manageability and security (using areas, shared views, master pages, and nested master pages); appropriate use of style sheets; client-side scripting; themes; client ID generation; render element modes; routing engine
  • Plan for cross-browser and/or form factors
    • Evaluate the impact on client side behaviors; themes; bandwidth; style sheets (including application design–task based or scaled rendering of existing page); when to apply Browsers file; structural approaches; user agents; different platforms (mobile versus desktop)
  • Plan for globalization
    • Design to support local, regional, language, or cultural preferences, including UI versus data localization (for example, implementing at database level or resource level); when to use CurrentCulture versus CurrentUICulture; globalization rollout plan (setting base default language, planning localization); handle Unicode data (what fields to include, request encoding); right-to-left support; vertical text and non-Latin topographies; calendars; data formatting; sorting

Design data strategies and structures (18%)

  • Design data access
    • Choose data access technologies, such as ADO.NET Data Services, Entity Framework, Windows Communications Foundation (WCF), and ASP.NET Web Services
  • Design data presentation and interaction
    • Pull data from data layer and binding into views, pages, and controls, and pull data back to data layer by using ModelBinders, data source controls, and HtmlHelper extensions, or programmatically
  • Plan for data validation
    • Contextual validation versus data integrity; where to validate data; synchronization between UI and data layer; data annotations

Design security architecture and implementation (17%)

  • Plan for operational security
    • Approaches for process- and resource-level security, including local and remote resources; Code Access Security (CAS), including trust level, process identity, application pool, and identity tag
  • Design an authentication and authorization model
    • Authentication providers, including WindowsForms; and custom user identity flowthrough (trusted subsystem); role management; membership providers; URL authorization (AuthorizationAttribute); file authorization; Authorization Manager (AzMan)
  • Plan for minimizing attack surfaces
    • Input validation; throttling inputs; request filtering; where to use Secure Sockets Layer (SSL)

Prepare for and investigate application issues (15%)

  • Choose a testing methodology
    • Black box; white box; integration; regression; coverage; API testing; performance testing; security testing
    • This objective does not include: load testing, web testing, or unit testing
  • Design an exception handling strategy
    • HandleError attribute in MVC; common error pages; post-error processing; global versus page level
  • Recommend an approach to debugging
    • Tools and approaches for a given scenario (memory dumps, DebuggingAttributes, crashes versus hangs, deadlocks, assembly binding); when to attach to process (Visual Studio Development Server versus Internet Information Services [IIS] versus Internet Explorer); root cause analysis
    • This objective does not include basic breakpoints
  • Recommend an approach to performance issues
    • Which instrumentation to watch or create (including performance counters and event tracing) to analyze performance issues; page and fragment caching

Design a deployment strategy (14%)

  • Design a deployment process
    • Windows Installer (MSI) versus xcopy versus Web Deployment Tool; scaling; rolling deployments
  • Design configuration management
    • Using the ConfigSource attribute (connection strings); staging versus production versus development; topologies; machine.config versus web.config; using IIS versus Visual Studio Development Server during development; application pools; configuration inheritance
  • Plan for scalability and reliability
    • Scale up, scale out, at physical level and at architectural level; impact of offloading technologies on load balancing, including state, synchronizing machine, and encryption keys
  • Design a health monitoring strategy
    • Built-in and custom HTML helpers (for example, HTML.RenderAction and HTML.RenderPartial); strongly typed views; static page checking; templated input helpers; ViewMasterPage; ViewUserControl

Course Reviews

No reviews found for this course.

Be the first to write a review