Exam 70-565:

Pro: Designing and Developing Enterprise Applications Using the Microsoft .NET Framework 3.5

Published:February 23, 2009
Language(s):English, Japanese
Audience(s):Developers
Technology:Microsoft Visual Studio 2008
Type:Proctored Exam

How To Get It: Schedule your exam through the following exam provider:

Take exam

Show all itemsHide all items
Preparing for an Exam
This exam is scheduled to retire July 31, 2013.
The Microsoft Certification website and this preparation guide contain a variety of resources to help you prepare for an exam. Preparing for and Taking an Exam — FAQ provides answers to frequently asked questions about exam registration ,preparation ,scoring ,and policies , including:
  • The most effective way to prepare to take an exam.
  • The relationship between Microsoft training materials and exam content.
  • Microsoft policy concerning the incorporation of service pack and revision updates into exam content.
  • Exam question types and formats.
  • Exam time limits and number of questions asked.
We recommend that you review this preparation guide in its entirety and familiarize yourself with the FAQs and resources on the Microsoft Certification website before you schedule your exam.
Audience Profile
This exam is targeted at the Professional level developer seeking to prove skills using Visual Studio 2008 and the .NET Framework 3.5.
 
Questions that contain code will be presented in either VB or C#. Candidates can select one of these languages when they start the exam.
Credit Toward CertificationExam 70-565: Pro: Designing and Developing Enterprise Applications Using the Microsoft .NET Framework 3.5: counts as credit toward the following certification(s):
Microsoft Certified Professional Developer: Enterprise Application Developer 3.5
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 exam, regardless of its format.
Skills Being MeasuredThis 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.

The information after “This objective may include but is not limited to” is intended to further define or scope the objective by describing the types of skills and topics that may be tested for the objective. However, it is not an exhaustive list of skills and topics that could be included on the exam for a given skill area. You may be tested on other skills and topics related to the objective that are not explicitly listed here.
Envisioning and Designing an Application (21 percent)
  • Analyze and refine the logical design of the application
    • May include but is not limited to: clarify logical design; evaluate the layers; evaluate application workflow; evaluate data flow diagrams; evaluate performance; evaluate maintainability; evaluate extensibility; evaluate availability; evaluate design against use cases; evaluate recoverability; evaluate data integrity
  • Analyze and refine the physical design of the application
    • May include but is not limited to: evaluate the tiers; evaluate migration strategy; clarify physical design; evaluate component specification; evaluate performance; evaluate maintainability; evaluate extensibility; evaluate scalability; evaluate availability; evaluate recoverability; evaluate data integrity
  • Analyze and refine the database design of the application
    • May include but is not limited to: evaluate stored procedure requirements; evaluate schema requirements; identify whether triggers are required; identify required data types
  • Analyze and refine the integration strategy
    • May include but is not limited to: evaluate integration of application with other systems; internal vs. external integration; enable future integration with other systems; evaluate WCF as an integration component
  • Identify the appropriate technology
    • May include but is not limited to: identify the technology and format for transport; identify the technology and format for messages; identify the technology and format for required client interoperability; choose a platform—Windows vs. Web; choose a communication technology—Windows Communication Foundation (WCF), Web services, Remoting, message queueing; define a component communication strategy; recommend build vs. buy; choose a platform—Windows Presentation Foundation (WPF), ASP.NET, AJAX, Windows Forms, Windows service
  • Analyze technical feasibility
    • May include but is not limited to: develop a proof of concept; perform a technical risk assessment; recommend changes to the design to meet the same technical goals; analyze feasibility of design in planned environment; determine whether the proposed design could integrate with other systems by using WCF
  • Analyze security requirements
    • May include but is not limited to: recommend an authentication method; recommend an authorization method; recommend a secure communication method
Designing and Developing an Application Framework (25 percent)
  • Choose an appropriate implementation approach for the application design logic
    • May include but is not limited to: choose data storage mechanisms; choose data flow structure; choose decision flow structure; state management techniques; security implementation; finalize component specification
  • Define the interaction between framework components
    • May include but is not limited to: determine types of clients that will access the application; define data APIs, security APIs, abstract classes, class interfaces, and data contracts; map data to object model; messaging and transport methods such as WCF, Remoting, Web services, MSMQ, Enterprise Services
  • Define a validation strategy
    • May include but is not limited to: define where in the framework each type of validation will happen; choose a validation method
  • Define an event-logging strategy
    • May include but is not limited to: choose a storage mechanism for logged events; choose a systemwide event logging method; decide logging levels based on severity or priority; define a reporting strategy
  • Define a monitoring strategy for specific characteristics or aspects of an application
    • May include but is not limited to: decide whether to monitor data; decide which characteristics to monitor; choose event monitoring mechanisms; decide monitoring levels based on requirements; choose a system-wide monitoring method from the available monitoring mechanisms; define a reporting strategy
Designing Application Components (23 percent)
  • Create the high-level design of a component
    • May include but is not limited to: establish the life cycle of a component; define user interface for each component; define interoperability requirements; identify and extract reusable components; document the design of a component by using pseudo code, class diagrams, sequence diagrams, activity diagrams, and state diagrams; decide whether to require constructor input
  • Define the internal architecture of a component
    • May include but is not limited to: decide whether existing functionality can be implemented or inherited; decide how to handle unmanaged and managed resources; decide which extensibility features are required; determine state management implementation; decide whether a component must be multithreaded; decide which functions to implement in the base class, abstract class, or sealed class
  • Define the data handling for a component
    • May include but is not limited to: define data access; analyze data relationships; analyze the data handling requirements of a component
  • Consume components
    • May include but is not limited to: identify reusable components; handle unmanaged components; identify whether a component needs to be extended; identify whether a component needs to be wrapped; identify whether any existing functionality needs to be hidden; test that reused components meet the specifications
  • Define a strategy for exceptions and other component feedback
    • May include but is not limited to: identify expected exceptions; decide how to deal with expected exceptions; decide how to deal with unhandled exceptions; decide how to deal with WCF faults; define other component feedback, such as events, callbacks, and messages; define a reporting strategy
Stabilizing and Testing an Application (17 percent)
  • Define a performance testing strategy
    • This objective may include but is not limited to: define how you will test an application's performance under a specified load; define how you will test an application's behavior when specified load is exceeded
  • Define a functional testing strategy
    • This objective may include but is not limited to: identify component interactions and dependencies; define how you will test a component in isolation; define how you will test a component's interactions with other components
  • Perform integration testing
    • This objective may include but is not limited to: run integration tests to determine whether the component interacts with other components as expected; verify results; test that endpoints are correct and service references are updated for communication methods such as WCF, Remoting, Web services, MSMQ, and Enterprise Services
  • Perform a code review
    • This objective may include but is not limited to: perform a security review; perform a functional review; perform a performance review; perform a regulatory compliance review
  • Resolve a bug
    • This objective may include but is not limited to: analyze root cause for problems in code, such as exception handling issues, performance problems, security issues, resource usage issues, and features that do not perform as expected
Migrating, Deploying, and Maintaining an Application (13 percent)
  • Create a deployment plan
    • This objective may include but is not limited to: identify component-level deployment dependencies; identify location of specific components for deployment; determine a deployment method; identify required assembly registration; document the physical deployment of the application
  • Analyze the configuration of the production environment
    • This objective may include but is not limited to: security environment; database environment; networking environment; .NET Framework versions; IIS versions; hardware and software requirements
  • Analyze performance monitoring data
    • This objective may include but is not limited to: identify performance spikes; identify performance trends; monitor and analyze resource usage; monitor and analyze security aspects
  • Analyze logs
    • This objective may include but is not limited to: review logs during deployment phase; review logs to determine source of failure; trace data to identify source of error
Preparation Tools and ResourcesTo help you prepare for this exam, Microsoft Learning recommends that you have hands-on experience with the product and that you use the following training resources. These training resources do not necessarily cover all of the topics listed in the "Skills Measured" tab.
Learning Plans and Classroom Training
  • LP565A: Learning Plan for Designing and Developing Enterprise Applications Using the Microsoft .NET Framework 3.5 (1 Forms)
Microsoft E-Learning There is no Microsoft E-Learning training currently available.
Microsoft Press Books There are no Microsoft Press books currently available.
Practice Tests
Have Questions? For advice about training and certification, connect with peers: For questions about a specific certification, chat with a Microsoft Certified Professional (MCP): To find out about recommended blogs, Web sites, and upcoming Live Meetings on popular topics, visit our community site:
Exam index