Beyond uptime, which measures are used to assess deployment success?

Beyond uptime, which measures are used to assess deployment success?

• A. Latency, error rate, customer impact, feature adoption, compliance with policies, and cost.
• B. Only uptime.
• C. Number of commits.
• D. Number of virtual machines.

Answer: (A)

Deployment success is about how the release performs for users and in operations, not just whether it is online. Latency shows if response times stay fast after the change, while the error rate indicates reliability and whether failures have crept in. Customer impact reflects the real-world effect on users, including any negative experiences or improvements they notice. Feature adoption reveals whether the new functionality is actually being used, signaling value and acceptance. Compliance with policies ensures the deployment meets security, privacy, and governance requirements. Cost covers the economic side of running and maintaining the release. If you focus only on uptime, you miss these important dimensions where a deployment can be technically available but still perform poorly, be unpopular, or be unjustified cost-wise. Metrics like number of commits or number of virtual machines track development activity or infrastructure size, not the outcome for users or the business.

Deployment success is about how the release performs for users and in operations, not just whether it is online. Latency shows if response times stay fast after the change, while the error rate indicates reliability and whether failures have crept in. Customer impact reflects the real-world effect on users, including any negative experiences or improvements they notice. Feature adoption reveals whether the new functionality is actually being used, signaling value and acceptance. Compliance with policies ensures the deployment meets security, privacy, and governance requirements. Cost covers the economic side of running and maintaining the release.

If you focus only on uptime, you miss these important dimensions where a deployment can be technically available but still perform poorly, be unpopular, or be unjustified cost-wise. Metrics like number of commits or number of virtual machines track development activity or infrastructure size, not the outcome for users or the business.