Things to practice for Microsoft test 70-554

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

1. Manage a solution environment using the Visual Studio 2005 Integrated development environment.
2. Understand the Microsoft .NET Framework 2.0 and the Common Language Runtime (CLR), Common Type System (CTS), and Common Language Specification (CLS).
3. Develop and deploy an application.
4. Use service configuration attributes.
5. Configure the Web service using either the Web.config file or the Machine.config file.
6. Create XML serialization of user-defined classes and pass complex data types between a Web service and a client.
7. Use the One-Way method with Web services.
8. Create and deploy asynchronous calls that are needed by Web service clients.
9. Configure remote channels and Activation Modes either programmatically or by configuration files.
10. Implement a simple remoting server and client.
11. Configure a remote service by using a configuration file.
12. Use Marshal-by-value and Marshal-by-reference.
13. Use Version Tolerant serialization.
14. Configure a communication channel to use different serialization formatters.
15. Call remote methods asynchronously and synchronously.
16. Raise and handle events in remote application.
17. Configure, initialize and renew the lifetime of remote objects.
18. Use response Queues and Time-Outs.
19. Place messages on a Queue by using either IIS or HTTP.
20. Understand COM+ services and use Enterprise Services in a Serviced Component.
21. Send and receive messages by using Microsoft Message Queuing Service (MSMQ).
22. Evaluate the technical feasibility of an application design concept and recommend the best technology.
23. 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.
24. Evaluate the design of a database and recommend a database schema.
25. Evaluate the logical design of an application for performance, maintainability, extensibility, scalability, availability, security, use cases, recoverability, and data integrity.
26. Evaluate the physical design of an application for performance, maintainability, scalability, availability, security, recoverability, and data integrity.
27. Choose an appropriate mechanism to deliver multimedia data from an application and evaluate available multimedia delivery mechanisms.
28. Establish the required characteristics of a component and decide when to create a single component or multiple components.
29. Create the high-level design of a component and establish the life cycle of a component.
30. Develop the public API of a component and decide the types of clients that can consume a component.
31. 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.
32. Develop an exception handling mechanism and decide when it is appropriate to raise an exception.
33. Develop the data access and data handling features of a component and analyze data relationships.
34. Develop a component to include profiling requirements and identify potential issues, such as resource leaks and performance gaps, by profiling a component.
35. Consume a reusable software component and identify a reusable software component from available components to meet the requirements.
36. Choose an appropriate exception handling mechanism and evaluate the current exception handling mechanism.
37. Choose an appropriate implementation approach for the application design logic.
38. Choose an appropriate event logging method for an application and decide whether to log data. Choose a storage mechanism for logged events. For example, database, flat file, event log, or XML file.
39. Monitor specific characteristics or aspects of an application and decide whether to monitor data. Considerations include administration, auditing, and application support.
40. Evaluate the application configuration architecture and decide which configuration attributes to store.
41. Evaluate the testing strategy for the unit testing, integration testing, stress testing, and performance testing.
42. Design a unit test, describe the testing scenarios, and decide the type of assertion tests to conduct.
43. Perform integration testing and determine if the component works as intended in the target environment.
44. Resolve a bug, investigate a reported bug, and evaluate the effect of the bug and the associated cost and timeline for fixing the bug.
45. Evaluate the performance of an application that is based on the performance analysis strategy.
46. Analyze the data received when monitoring an application and monitor and analyze resource usage.
47. Evaluate the deployment plan and identify component-level deployment dependencies and scripting requirements for deployment.
48. Create an application flow-logic diagram and evaluate the complexity of interactions with other components.