The 70-548 test measures an individual’s ability to build rich client applications on the Windows Forms platform by using the .NET Framework 2.0. Before taking the 70-548 test, you should practice the following:

  1. Evaluate the technical feasibility of an application design concept.
  2. Recommend the best technologies for the features and goals of the application.
  3. Investigate existing solutions for similar business problems.
  4. Evaluate the risks associated with ASP.NET 2.0 technology or implementation.
  5. Evaluate the technical specifications for an application to ensure that the business requirements are met.
  6. Evaluate the design of a database.
  7. Identify the stored procedures that are required for an application.
  8. Evaluate the logical design of an application for performance, maintainability, extensibility, scalability, security, recoverability, and data integrity.
  9. Evaluate the physical design of an application for performance, maintainability, scalability, availability, security, recoverability, and data integrity.
  10. Choose an appropriate layout for the visual interface.
  11. Evaluate a strategy for implementing a common layout throughout the UI.
  12. Evaluate the manner in which available controls are implemented in previous and ongoing projects or applications.
  13. Evaluate the user demographic and user environment.
  14. Choose an appropriate data validation method at the UI layer.
  15. Evaluate whether an exception must be thrown, logged, and handled.
  16. Choose appropriate user assistance and application status feedback techniques.
  17. Choose an appropriate mechanism to deliver multimedia data from an application.
  18. Decide which tier of the application a component should be located.
  19. Document the design of a component by using pseudo code, class diagrams, sequence diagrams, activity diagrams, and state diagrams.
  20. Develop the public API of a component.
  21. Decide the types of clients that can consume a component.
  22. Decide how to handle unmanaged and managed resources.
  23. Decide which functions to implement in the base class, abstract class, or sealed class.
  24. Develop an exception handling mechanism.
  25. Develop the data access and data handling features of a component.
  26. Identify potential issues, such as resource leaks and performance gaps, by profiling a component.
  27. Decide whether to redesign a component after analyzing the profiling results.
  28. Identify a reusable software component from available components to meet the requirements.
  29. Choose an appropriate exception handling mechanism.
  30. Choose an appropriate implementation approach for the application design logic.
  31. Choose an appropriate event logging method for the application.
  32. Choose a storage mechanism for logged events. For example, database, flat file, event log, or XML file.
  33. Decide whether to monitor data. Considerations include administration, auditing, and application support.
  34. Choose event monitoring mechanisms, such as System Monitor and logs.
  35. Choose the physical storage location for the configuration attributes.
  36. Evaluate the integration testing, stress testing, and performance testing strategies.
  37. Describe the testing scenarios and decide coverage requirements.
  38. Determine if the component works as intended in the target environment.
  39. Investigate a reported bug and evaluate the affect of the bug and the associated cost and timeline for fixing the bug.
  40. Evaluate the performance of an application that is based on the performance analysis strategy.
  41. Analyze the data received when monitoring an application.
  42. Identify scripting requirements for deployment. Considerations include database scripting.
  43. Create an application flow-logic diagram.
  44. Validate the production configuration environment.

Leave a reply

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