A company has implemented a change management process that allows standard changes during business hours. The company's private cloud hardware needs firmware updates and supports rolling upgrades…

Implementing it as a standard change is about internal process adherence, not directly about transparency to external users.

Even with rolling upgrades designed for minimal disruption, notifying users before applying firmware updates during business hours is crucial for transparency, allowing them to anticipate any minor, transient issues or plan around the maintenance window. This proactive communication manages user expectations and reduces potential frustration, aligning with the goal of making the change as transparent as possible.

Failing over the application might be a method to achieve high availability but rolling upgrades already aim to keep services available, and the question is about user transparency for the upgrade process.

Performing the change during off-hours contradicts the scenario's allowance for standard changes during business hours and the objective of making it transparent within that context.