Which of the following is a typical dashboard use for monitoring processes after deployment?

• A. Process optimization
• B. Code generation
• C. Data entry
• D. Hardware procurement

Answer: (A)

Dashboards after deployment are used to observe how processes perform in real time and to drive improvements. By displaying metrics like throughput, cycle time, SLA compliance, bottlenecks, and queue lengths, teams can spot where the workflow slows down or deviates from targets and take action to optimize the process. This makes process optimization the natural purpose of such dashboards.

Generating code, data entry, or hardware procurement aren’t about monitoring and improving ongoing processes. Generating code is creating software, data entry is a data-input task, and hardware procurement is about acquiring physical assets. They don’t align with using dashboards to track and enhance process performance.