You work as the Enterprise application developer at Domain.com. The Domain.com network consists of a single Active Directory domain named Domain.com. All servers in the domain run Windows Server 2003. Your responsibilities at Domain.com include the support and deployment of applications. You are currently developing an enterprise order fulfillment application for Domain.com. Upon completion this application will allow customers to place orders for their respective chosen products that they intend to purchase. At present Domain.com handles its own payment processing. However, it is foreseen that as Domain.com grows, they will make use of a third party company in the future. The exhibit below illustrates the application flow diagram that represents the order process. A factor that should be kept in mind is that the process is subject to future alterations.

You now need to create components to manage the order process.

What should you do?

A.
Create one business entity component and four user process components.

B.
Create one business workflow component and four business components.

C.
Create two service agent components and two user process components.

D.
Create two service agent components and two service interface components.

Explanation:
Business components encapsulate the business logic. Business workflow components manage business activities or workflows. Thus you should create four business components and one business workflow component. I.e. you create Order, Charge, Receipt, and Fulfillment business components as this will allow you to implement all business logic. By implementing a sequence of activities in a business workflow, you can decouple the application flow logic from the business logic which will allow you to accommodate changes to the sequence of activities in future in a very easy manner.
Incorrect answers:
A: Service agents hide the complexity of calling multiple services to access external functionality. This is not what is required in this scenario.
C: User Process components manage user or screen flow throughout an application. In this case the activities indicate a business workflow and not a user workflow. Thus this option is not the solution.
D: There is no need to create service interfaces as this will expose an application’s business logic to external systems.