Share via

Exam 70-564 - Pro: Designing and Developing ASP.NET Applications Using the Microsoft .NET Framework 3.5

  • Article

Overview

Language(s): English
Audience(s): Developers
Technology: Microsoft Visual Studio 2008
Type: Proctored Exam

Audience Profile

Questions that contain code will be presented in either VB or C#. Candidates can select one of these languages when they start the exam.

Candidates for this exam work on a team in a development environment that uses Microsoft Visual Studio 2008 .NET 2008 and the Microsoft .NET Framework 3.5 to build ASP.NET applications. Candidates should have a minimum of three years of experience developing Web-based applications including one to two years of experience developing ASP.NET-based applications and a thorough understanding of the ASP.NET technologies in the .NET Framework 3.5.
Additionally, candidates should be able to demonstrate the following by using the .NET Framework 3.5:

  • A solid understanding of the ASP.NET applications event model
  • Experience creating ASP.NET applications that access data
  • Experience planning and designing user interaction solutions
  • Experience in the full cycle of software applications

Credit Toward Certification

Exam 70-564: Pro: Designing and Developing ASP.NET Applications Using the Microsoft .NET Framework 3.5 counts as credit toward the following certification(s):

Note This preparation guide is subject to change at any time without prior notice and at the sole discretion of Microsoft. Microsoft exams might include adaptive testing technology and simulation items. Microsoft does not identify the format in which exams are presented. Please use this preparation guide to prepare for the xam, regardless of its format.

Skills Measured

Designing and Implementing Controls (13%)

  • Choose appropriate controls based on business requirements.

    This objective may include but is not limited to: user controls, server controls, built-in controls, custom controls, third-party controls, Web parts

  • Design controls for reusability.

    This objective may include but is not limited to: user controls, server controls, inheritance for changing behavior

  • Manage states for controls.

    This objective may include but is not limited to: control state, view state, accessing form elements

  • Leverage data-bound controls.

    This objective may include but is not limited to: use gridviews, use sorting and paging callbacks when available, when to use custom sorting and paging, server-side pagination

  • Choose appropriate validation controls based on business requirements.

    This objective may include but is not limited to: server-side page validation (Page.IsValid), custom validator, validation groups, validation summary

  • Identify the appropriate usage of ASP.NET AJAX.

    This objective may include but is not limited to: implementing partial page updates with update panel, using ASP.NET AJAX controls, script services

  • Manage JavaScript dependencies with server controls.

Designing the Presentation and Layout of an Application (16%)

  • Design complex layout with Master Pages.

    This objective may include but is not limited to: strongly typed master pages, nested master pages

  • Plan for various user agents.

    This objective may include but is not limited to: markups for different browsers for mobile devices, screen readers, accessibility

  • Design a brandable user interface by using themes.

    This objective may include but is not limited to: shared themes across multiple applications, run time master page selection

  • Design site navigation.

    This objective may include but is not limited to: when to extend site map provider, treeview menu vs. site map path, programmatically manipulating site map nodes, overriding menu rendering by using control adapters, filtering site map nodes based on user roles

  • Plan Web sites to support globalization.

    This objective may include but is not limited to: custom resource provider vs. resource files, localize applications

Accessing Data and Services (18%)

  • Plan vendor-independent database interactions.

    This objective may include but is not limited to: IDBconnection, IDBcommand, IDBadapter, IdataReader, Datareader vs. dataset

  • Identify the appropriate usage of data source controls.

    This objective may include but is not limited to: SQLDataSource, ObjectDataSource, XMLDataSource

  • Leverage LINQ in data access design.

    This objective may include but is not limited to: LINQtoSQL, lambda expressions, LINQtoObjects, LINQtoXML

  • Identify opportunities to access and expose Web services.

    This objective may include but is not limited to: WCF, ASMX, REST

Establishing ASP.NET Solution Structure (13%)

  • Determine when to use the Web Site model vs. a Web Application Project.

    This objective may include but is not limited to: project file, references, namespace, user profile object, precompilation

  • Establish an error-handling strategy.

    This objective may include but is not limited to: Global.asax events, Web.config elements, TRY/CATCH blocks, error logging

  • Manipulate configuration files to change ASP.NET behavior.

    This objective may include but is not limited to: machine key, tracing, encrypting Web configuration data, custom configuration sections

  • Identify a deployment strategy.

    This objective may include but is not limited to: mangement application pools, Web deployment projects, pre-compilation, custom action classes

Leveraging and Extending ASP.NET Architecture (17%)

  • Design a state management strategy.

    This objective may include but is not limited to: Cache, ViewState, Application object, Session object, cookies, cookieless session

  • Identify the events of the page life cycle.

    This objective may include but is not limited to: appending controls, PostBack model, accessing state, data binding

  • Write HttpModules and HttpHandlers.

    This objective may include but is not limited to: URL rewriting, SSO application, dynamically retrieve data

  • Debug ASP.NET Web applications.

    This objective may include but is not limited to: debug JavaScript, tracing, debug tools in IDE, examining HTTP headers

  • Plan for long-running processes by using asynchronous pages.

    This objective may include but is not limited to: AddonPreRenderCompleteAsync, RegisterAsyncTask

Applying security principles (23%)

  • Identify appropriate security providers.

    This objective may include but is not limited to: membership, role, profile, extending custom providers

  • Decide which user-related information to store in a profile.

    This objective may include but is not limited to: create user profile properties, extend membership objects, custom types

  • Establish security settings in Web.config.

    This objective may include but is not limited to: identity/impersonation, authentication, authorization (location nodes in Web.config)

  • Identify vulnerable elements in applications.

    This objective may include but is not limited to: SQL injection, cross-site scripting, protecting against bots

  • Ensure that sensitive information in applications is protected.

    This objective may include but is not limited to: hash and salt passwords, encrypting information

Preparation Materials

Learning Plans and Classroom Training

Practice Tests

Community

If one of the posts in the following threads helps you answering your question, please vote them as helpful so other community members will find helpful information faster.