Skills required for Microsoft test 70-551.

Skills required for Microsoft test 70-551.

Rating:

Microsoft has specified more than sixty objectives for the 70-551 test. These objectives are grouped under nineteen topics. Following are some important areas in which an individual should possess good knowledge before taking the 70-551 test:

1. Managing data in a .NET application by using system types.


2. Improving type safety and application performance in a .NET application by using generic collections.


3. Implementing .NET Framework interfaces to cause components to comply with standard contracts.


4. Embedding configuration management functionality into a .NET application.


5. Debugging and tracing a .NET application by using the System.Diagnostics namespace.


6. Serializing or deserializing an object or an object graph by using runtime serialization techniques and controlling the serialization of an object into XML format.


7. Controlling the serialization of an object into XML format by using the System.Xml.Serialization namespace.


8. Accessing files and folders by using the File System classes, managing byte streams by using Stream classes, and managing the .NET application data by using the Reader and Writer classes.


9. Compressing or decompressing stream information in a .NET application and improving the security of application data by using isolated storage.


10. Implementing access control by using the System.Security.AccessControl classes and a custom authentication scheme by using the System.Security.Authentication classes.


11. Encrypting, decrypting, and hashing data by using the System.Security.Cryptography classes.


12. Controlling permissions for resources by using the System.Security.Permission classes and controlling code privileges by using System.Security.Policy classes.


13. Accessing and modifying identity information by using the System.Security.Principal classes.


14. Sending e-mail to a Simple Mail Transfer Protocol (SMTP) server for delivery from a .NET application.


15. Enhancing the user interface of a .NET application by using the System.Drawing namespace.


16. Adding and configuring Web server controls.


17. Programming a Web application and configuring settings for the application.


18. Implementing data-bound controls.


19. Managing connections and transactions of databases.


20. Creating, deleting, and editing data in a connected environment.


21. Creating a composite server control.


22. Copying a Web application to a target server by using the Copy Web tool.


23. Precompiling a Web application by using the Publish Web utility.


24. Optimizing and troubleshooting a Web application.


25. Implementing a consistent page design by using master pages.


26. Customizing a Web page by using themes and user profiles.


27. Implementing Web Parts in a Web application.


28. Establishing a user's identity by using forms authentication.


29. Using authorization to establish the rights of an authenticated user.


30. Using login controls to control access to a Web application.


31. Creating a mobile Web application project.


32. Using device-specific rendering to display controls on a variety of devices.


33. Using adaptive rendering to modify the appearance of Web server controls.


34. Evaluating the technical feasibility of an application design concept.


35. Evaluating the technical specifications for an application to ensure that the business requirements are met.


36. Evaluating the design of a database.


37. Evaluating the logical design for performance, maintainability, extensibility, scalability, availability, security, use cases, recoverability, and data integrity of an application.


38. Evaluating the physical design for performance, maintainability, scalability, availability, security, recoverability, and data integrity of an application.


39. Choosing an appropriate layout for the visual interface.


40. Evaluating a strategy for implementing a common layout throughout the UI.


41. Choosing an appropriate control based on design specifications, evaluating the type of data that must be captured or displayed, and evaluating available controls.


42. Choosing an appropriate data validation method at the UI layer and a validation method based on the data type provided.


43. Choosing appropriate user assistance and application status feedback techniques.


44. Establishing the required characteristics of a component.


45. Creating a high-level design of a component, establishing the life cycle of the component, and deciding whether to use established design patterns for the component.


46. Developing the public API of a component, deciding the types of clients that can consume a component, and establishing the required component interfaces.


47. Developing the features of a component, deciding whether existing functionality can be implemented or inherited, and deciding how to handle unmanaged and managed resources.


48. Developing an exception handling mechanism. Deciding when it is appropriate to raise an exception and how a component will handle exceptions.


49. Developing the data access and data handling features of a component, analyzing data relationships, and data handling requirements of a component.


50. Consuming a reusable software component and identifying a reusable software component from available components to meet the requirements.


51. Choosing an appropriate exception handling mechanism, evaluating the current exception handling mechanism, and designing a new exception handling technique.


52. Choosing an appropriate implementation approach for the application design logic and an appropriate data storage mechanism.


53. Choosing an appropriate event logging method for an application. Deciding whether to log data.


54. Evaluating the application configuration architecture, deciding which configuration attributes to store, and choosing the physical storage location for the configuration attributes.


55. Evaluating the unit testing strategy, the integration testing strategy, and the stress testing strategy.


56. Resolving a bug, investigating a reported bug, reproducing a bug, fixing a bug, and evaluating the effect of the bug and the associated cost and timeline for fixing the bug.


57. Evaluating the performance of an application that is based on the performance analysis strategy.


58. Analyzing data received when monitoring an application.


59. Evaluating the deployment plan and identifying component-level deployment dependencies.


60. Validating the production configuration environment, verifying networking settings and the deployment environment.

Rating: