Hey Now Everybody,
Microsoft .NET 4 was released Tuesday, there is a MCPD 4 beta exam 71-519 which real exam will be 70-519 that I’ve registered for. To prepare for this exam I’m going to study & start by reviewing the skills being measured on the exam. Below are is the list presented in three times each with a little more detail than the previous one. The links are some that I’ve been reading & reviewing mostly from the MSDN library. Let’s inspect what’s going to be on this brand new exam:
Skills Measured
1. Architecture
2. UX
3. Data
4. Security
5. Troubleshooting
6. Deployment
1 Designing the Application Architecture (19%)
- 1.1 Plan the division of application logic.
- 1.2 Analyze requirements and recommend a system topology.
- 1.3 Choose appropriate client-side technologies
- 1.4 Choose appropriate server-side technologies
- 1.5 Design state management.
2 Designing the User Experience (17%)
- 2.1 Design the site structure.
- 2.2 Plan for cross-browser and/or form factors.
- 2.3 Plan for globalization.
3 Designing Data Strategies and Structures (18%)
- 3.1 Design data access.
- 3.2 Design data presentation and interaction.
- 3.3.Plan for data validation
4 Designing Security Architecture and Implementation (17%)
- 4.1 Plan for operational security
- 4.2 Design an authentication and authorization model.
- 4.3 Plan for minimizing attack surfaces Input validation
5 Preparing For and Investigating Application Issues (15%)
- 5.1 Choose a testing methodology
- 5.2 Design an exception handling strategy.
- 5.3 Recommend an approach to debugging
- 5.4 Recommend an approach to performance issues
6 Designing a Deployment Strategy (14%)
- 6.1 Design a deployment process
- 6.2 Design configuration staging vs. production vs. development
- 6.3 Plan for scalability and reliability
- 6.4 Design a health monitoring strategy
Details on Skills Measured:
1 Designing the Application Architecture (19%)
- 1.1 Plan the division of application logic.
Choosing between client-side and server side processing,
Planning Separation of Concern
partitioning functionality between controllers and evaluating business
& data service consumption
planning for long-running processes
Synchronous vs. Asynchronous - 1.2 Analyze requirements and recommend a system topology.
Designing interaction between applications,
Mapping logical design to physical implementation,
Validating nonfunctional requirements and cross-cutting concerns
communications,
operations management
security
Evaluating baseline needs
scale
quality of service - 1.3 Choose appropriate client-side technologies
JavaScript
ASP.NET AJAX
jQuery
Microsoft Silverlight - 1.4 Choose appropriate server-side technologies
User controls
Server controls
Partials
Custom HtmlHelper extensions
Web parts
Inheriting controls
Dynamic data controls - 1.5 Design state management.
Designing an application for the proper use of application state, session state, and request state
ex. ViewState, ControlState, Cache object, cookies, and client-side persistence
2 Designing the User Experience (17%)
- 2.1 Design the site structure.
Designing application segmentation for manageability and security
Ex. using areas, shared views, master pages, and nested master pages
Appropriate use of style sheets
Client-side scripting
Themes
Client ID generation
Rendering element modes
Routing engine - 2.2 Plan for cross-browser and/or form factors.
Evaluating 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 vs. desktop) - 2.3 Plan for globalization.
Designing to support local, regional, language, or cultural preferences, including UI vs. data localization
ex. implementing at database level or resource level
When to use CurrentCulture vs. CurrentUICulture
Globalization rollout plan
ex setting base default language, planning localization
handling Unicode data
ex what fields to include, request encoding
right-to-left support
Vertical text and non-Latin topographies, calendars, data formatting, sorting
3 Designing Data Strategies and Structures (18%)
- 3.1 Design data access.
Choosing data access technologies such as ADO.NET Data Services, Entity Framework, Windows Communications Foundation (WCF), and ASP.NET Web Services - 3.2 Design data presentation and interaction.
Pulling data from data layer and binding into views, pages, and controls, and pulling data back to data layer by using ModelBinders, data source controls, and HtmlHelper extensions, or programmatically - 3.3 Plan for data validation
Contextual validation vs. data integrity, where to validate data, synchronization between UI and data layer, data annotations
4 Designing Security Architecture and Implementation (17%)
- 4.1 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 - 4.2 Design an authentication and authorization model.
Authentication providers, including WindowsForms, and custom user identity flowthrough
ex trusted subsystem
role management
membership providers
URL authorization
ex AuthorizationAttribute
File authorization, Authorization Manager (AzMan) - 4.3 Plan for minimizing attack surfaces
Input validation
Throttling inputs
Request filtering
Where to use Secure Sockets Layer (SSL)
5 Preparing For and Investigating Application Issues (15%)
- 5.1 Choose a testing methodology
black box, white box, integration, regression, coverage, API testing, performance testing, security testing - 5.2 Design an exception handling strategy.
HandleError attribute in MVC, common error pages, post-error processing, global vs. page level - 5.3 Recommend an approach to debugging
Tools and approaches for a given scenario
(for example, memory dumps, DebuggingAttributes, crashes vs. hangs, deadlocks, assembly binding), when to attach to process (Visual Studio Development Server vs. IIS vs. Internet Explorer), root cause analysis\ - 5.4 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
6 Designing a Deployment Strategy (14%)
- 6.1 Design a deployment process.
Windows Installer (MSI) vs. xcopy vs. Web Deployment Tool, scaling, rolling deployments - 6.2 Design configuration management
Using the ConfigSource attribute
(for example, connection strings),
staging vs. production vs. development, topologies, machine.config vs. web.config, using IIS vs. Visual Studio Development Server during development, application pools, configuration inheritance - 6.3 Plan for scalability and reliability
scaling up, scaling out, at physical level and at architectural level, impact of offloading technologies on load balancing, including state, synchronizing machine and encryption keys - 6.4 Design a health monitoring strategy
When to monitor application or business-related events (e.g., on UI every time clicked or in business layer), determining a strategy for using ASP.NET Health Monitoring, throttling, filtering, delivery method
Here is a link to the official Microsoft page of the skills measured.
Unfortunately there is no official Microsoft Self Paced Training Kit for this exam, therefore I’m going to continue to review this material. There we have it we now understand & reviewed the skills measured in to 70-519 MCPD 4 Web Dev exam.
That is all there will be more,
2 comments:
The links are really old...One page even had a disclaimer on it that the information given was obsolete.
Also, not many of the links have nothing to do with the design aspect of that feature, which I believe is the point of the exam. I've taken and passed the 3.5 version.
That said, you put a lot of time into this, and it was the only resource I found dealing specifically with the 70-519 exam. Thank you.
Have you taken the exam yet?
A book that may be of interest to you in studying for this exam is
ASP.Net 3.5 Application Architecture and Design: Build robust, scalable ASP.NET applications quickly and easily.
I took the exam yesterday. 48 questions, 12 of which covered a case study. One tip: read this article about MVC 2 and IIS 6.0, there's a question that it covers...
http://blogs.msdn.com/tmarq/archive/2010/04/01/asp-net-4-0-enables-routing-of-extensionless-urls-without-impacting-static-requests.aspx
Post a Comment