The correct answer is A. Using asynchronous tasks or asynchronous service invocations for non-critical operations improves workflow responsiveness by decoupling the user-facing or critical path from work that does not need an immediate return value. Business Automation Workflow supports service flows and automation-service operations that can be invoked synchronously or asynchronously, and the design distinguishes service flows enabled for asynchronous invocation from those that invoke only synchronous operations. In solution architecture, this design prevents long-running integrations, notifications, enrichment calls, or background updates from holding up the main process thread or user interaction. Option B is unsafe as a general best practice because reducing logging indiscriminately weakens traceability, auditability, and troubleshooting. Option C is invalid because BAW relies on persistent state, process instance data, task data, and transactional storage. Option D is the opposite of the preferred pattern for non-critical work because synchronous tasks keep the caller waiting and can increase latency under load. References/topics: Business Automation Workflow, service flows, asynchronous invocation, workflow performance design, non-critical background operations.