The correct answer is D. Business Automation Workflow projects should be authored so that workflow assets are clear to maintain, reusable across implementations, and scalable under production load. IBM positions workflow automation as a way to orchestrate straight-through, human-assisted, and case-based business processes while providing visibility into each step. That goal is undermined by overloading a process with unnecessary tasks, avoiding testing, or artificially limiting integration. Good workflow design separates concerns into services, tasks, user interfaces, toolkits, business objects, and reusable automation services where appropriate. Clarity helps business and technical stakeholders understand process responsibility. Reusability reduces duplication and improves governance. Scalability ensures that process instances, service flows, human tasks, and integrations remain manageable as volume grows. Therefore, the best-practice posture is disciplined modular authoring, not task proliferation or shortcut-based development. References/topics: Business Automation Workflow, workflow automation, reusable automation services, service flows, client-side human services, reusable views and toolkits.