The Microsoft test 70-551 is designed to measure an individual’s ability to build interactive, data-driven Web-based applications with Web forms, ASP.NET, and the .NET Framework for both intranet and Internet uses. Before taking the 70-551 test, you should practice the following:

  1. Develop .NET Framework applications by using system types.
  2. Improve type safety and application performance by using generic collections.
  3. Develop .NET Framework applications by implementing interfaces that comply with standard contracts.
  4. Embed configuration management functionality into .NET applications.
  5. Debug and trace .NET Framework applications by using the System.Diagnostics namespace.
  6. Use runtime serialization techniques to serialize or deserialize an object or an object graph.
  7. Control the serialization of an object into XML format by using the System.Xml.Serialization namespace.
  8. Access files and folders by using the File System classes of the System.IO namespace.
  9. Compress or decompress stream information in .NET Framework applications.
  10. Implement access control to improve the security of .NET Framework applications.
  11. Implement a custom authentication scheme and control permissions for resources by using the System.Security.Authentication and System.Security.Permission classes respectively.
  12. Encrypt, decrypt, and hash data as well as control code privileges in .NET applications.
  13. Send e-mail to a Simple Mail Transfer Protocol server from .NET Framework applications.
  14. Enhance the user interface of .NET Framework applications by using the System.Drawing namespace.
  15. Add Web server controls to a Web Form and configure their properties programmatically.
  16. Configure system-wide settings in the Machine.config file, and settings for a Web application in the Web.config file.
  17. Manage configuration of a Web application by using the Web Site Administration Tool.
  18. Redirect users to another Web page by using a server-side method.
  19. Implement cross-page postbacks.
  20. Convert HTML server controls to HTML elements.
  21. Use tabular and hierarchical data source controls to return tabular and hierarchical data respectively.
  22. Display data by using simple, composite, and hierarchical data-bound controls.
  23. Configure a connection to a database graphically by using the Connection Wizard, Server Explorer, and the connection class.
  24. Control connection pooling by configuring ConnectionString values based on database type.
  25. Perform transactions by using the ADO.NET Transaction object.
  26. Retrieve data by using a DataReader object and build SQL commands visually in Server Explorer.
  27. Perform database operations by using a command object.
  28. Store and retrieve binary large object (BLOB) data types in a database.
  29. Create a composite Web application control.
  30. Handle user control events within the user control code-declaration block or code-behind file.
  31. Copy a Web application to a target server by using the Copy Web tool.
  32. Precompile a Web application by using the Publish Web utility.
  33. Troubleshoot a Web application by using ASP.NET tracing.
  34. Optimize performance by using the ASP.NET Cache object.
  35. Implement a consistent page design by using master pages.
  36. Customize a Web page by using themes and user profiles.
  37. Implement Web Parts in a Web application.
  38. Establish a user’s identity by using forms authentication.
  39. Use authorization to establish the rights of an authenticated user.
  40. Use login controls to control access to a Web application.
  41. Create a mobile Web application project.
  42. Use device-specific rendering to display controls on a variety of devices.
  43. Use adaptive rendering to modify the appearance of Web server controls.
  44. Evaluate the technical feasibility of an application design concept and recommend the best technology for the features and goals of the application.
  45. Evaluate the technical specifications for an application to ensure that the business requirements are met.
  46. Evaluate the design of a database by recommending a database schema and identify the stored procedures that are required for an application.
  47. Evaluate the logical design of an application for performance, maintainability, extensibility, scalability, availability, security, use cases, recoverability, and data integrity.
  48. Evaluate the physical design of an application for performance, maintainability, scalability, availability, security, recoverability, and data integrity.
  49. Choose an appropriate layout for the visual interface by deciding the content flow across pages.
  50. Evaluate a strategy for implementing a common layout throughout the UI.
  51. Choose an appropriate control based on design specifications by evaluating the type of data that must be captured or displayed and also by evaluating the user demographic and the user environment.
  52. Choose an appropriate data validation method at the UI layer by identifying the source of invalid data and the cause of an invalid entry.
  53. Choose appropriate user assistance and application status feedback techniques.
  54. Choose an appropriate data storage mechanism, data flow structure, and decision flow structure for the application design logic.
  55. Choose an appropriate event logging method for the application.
  56. Evaluate the application configuration architecture by deciding which configuration attributes to store and choosing when to use ASP.NET Administrative tools.
  57. Evaluate the testing strategy for the unit testing, integration testing, stress testing, and performance testing.
  58. Design a unit test, describe the testing scenarios, and decide the type of assertion tests to conduct.
  59. Perform integration testing and determine if the component works as intended in the target environment.
  60. Resolve a bug, investigate a reported bug, and evaluate the effect of the bug and the associated cost and timeline for fixing the bug.
  61. Evaluate the performance of an application that is based on the performance analysis strategy.
  62. Analyze the data received when monitoring an application by monitoring and analyzing resource usage and by tracking bugs that result from customer activity.
  63. Evaluate the deployment plan by identifying component-level deployment dependencies and scripting requirements for deployment.
  64. Validate the production configuration environment. Considerations include load balancing, Web farms, and Web gardens.

Leave a reply

required

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>