Things to practice for Microsoft test 70-552

The Microsoft test 70-552 is designed to measure an individual’s ability and skills in MCPD Windows development by using the Microsoft .NET Framework. Before taking the 70-552 test, you should practice the following:

1. Develop .NET Framework applications by using system types, generics, collections, and specialization collections.
2. Develop .NET Framework applications by implementing interfaces that comply with standard contracts.
3. Control interactions between .NET Framework application components by using events and delegates.
4. Implement service processes and application domains in .NET Framework applications.
5. Develop multithreaded .NET Framework applications.
6. Embed configuration management functionality into .NET applications and create a custom Microsoft Windows Installer for the .NET Framework components.
7. Manage an event log, and debug and trace a .NET Framework application by using the System.Diagnostics namespace.
8. Compress or decompress stream information in .NET Framework applications.
9. Implement code access security and access control to improve the security of .NET Framework applications.
10. Implement a custom authentication scheme and control permissions for resources by using the System.Security.Authentication and System.Security.Permission classes respectively.
11. Encrypt, decrypt, and hash data as well as control code privileges in .NET applications.
12. Send e-mail to a Simple Mail Transfer Protocol server from .NET Framework applications.
13. Enhance the user interface of .NET Framework applications by using the System.Drawing namespace.
14. Add a Windows Form to a project at design time.
15. Configure a Windows Form to control accessibility, appearance, behavior, and other functionality.
16. Group and arrange controls by using the container controls.
17. Use the IDE to add a control to a Windows Form or other container control of a project at design time and runtime.
18. Create and configure a MenuStrip and ContextMenuStrip component on a Windows Form.
19. Use the Windows Forms Designer to create event handlers.
20. Use the DataGridView control to display and update the tabular data contained in a data source.
21. Configure a connection to a database by using the Connection Wizard and Server Explorer.
22. Retrieve data by using a DataReader object.
23. Create a DataSet graphically and programmatically.
24. Read, write, and validate XML by using the XmlReader and XmlWriter class.
25. Perform drag-and-drop operations within a Windows Forms application and between applications.
26. Create and configure multiple-document interface (MDI) forms.
27. Configure the PropertyGrid component and the ProgressBar control to indicate progress graphically.
28. Implement asynchronous programming techniques to improve a user’s experience.
29. Install a Windows Forms application on a client computer and server by using ClickOnce deployment.
30. Create a Windows Forms application setup project and set deployment project properties.
31. Evaluate the technical feasibility of an application design concept and recommend the best technology.
32. Create a proof-of-concept prototype, evaluate the risks associated with ASP.NET 2.0 technology, and validate that the proposed technology can be used in a Web application.
33. Evaluate the technical specifications for an application to ensure that the business requirements are met, and translate the functional specification into developer terminology, such as pseudo code and UML diagrams.
34. Evaluate the design of a database and recommend a database schema.
35. Evaluate the logical design of an application for performance, maintainability, extensibility, scalability, availability, security, use cases, recoverability, and data integrity.
36. Evaluate the physical design of an application for performance, maintainability, scalability, availability, security, recoverability, and data integrity.
37. Choose an appropriate layout for the visual interface, decide the content flow across pages, and ensure the congruency and consistency of the user experience throughout an application.
38. Evaluate a strategy for implementing a common layout throughout the UI and suggest when to use style sheets, master pages, Web parts, custom controls, scripting, and user controls.
39. Choose an appropriate control based on design specifications and evaluate the type of data that must be captured or displayed. Evaluate the user demographic and the user environment.
40. Choose an appropriate data validation method at the UI layer and identify the source of invalid data and the cause of an invalid entry.
41. Choose appropriate user assistance and application status feedback techniques. Choose an appropriate application status feedback technique based on available control types and an appropriate application status feedback technique to support accessibility.
42. Choose an appropriate mechanism to deliver multimedia data from an application and evaluate available multimedia delivery mechanisms.
43. Establish the required characteristics of a component and decide when to create a single component or multiple components.
44. Create the high-level design of a component and establish the life cycle of a component.
45. Develop the features of a component and decide whether existing functionality can be implemented or inherited, how to handle unmanaged and managed resources, and which functions to implement in the base class, abstract class, or sealed class.
46. Develop an exception handling mechanism and decide when it is appropriate to raise an exception.
47. Develop the data access and data handling features of a component and analyze data relationships.
48. Develop a component to include profiling requirements and identify potential issues, such as resource leaks and performance gaps, by profiling a component.
49. Consume a reusable software component and identify a reusable software component from available components to meet the requirements.
50. Choose an appropriate exception handling mechanism and evaluate the current exception handling mechanism.
51. Choose an appropriate implementation approach for the application design logic.
52. Evaluate the application configuration architecture and decide which configuration attributes to store.
53. Evaluate the testing strategy for the unit testing, integration testing, stress testing, and performance testing.
54. Design a unit test, describe the testing scenarios, and decide the type of assertion tests to conduct.
55. Resolve a bug, investigate a reported bug, and evaluate the effect of the bug and the associated cost and timeline for fixing the bug.
56. Evaluate the performance of an application that is based on the performance analysis strategy.
57. Analyze the data received when monitoring an application and monitor and analyze resource usage.
58. Evaluate the deployment plan and identify component-level deployment dependencies and scripting requirements for deployment.
59. Create an application flow-logic diagram and evaluate the complexity of interactions with other components.
60. Validate the production configuration environment. Considerations include load balancing, Web farms, and Web gardens.