The Problem: We intended to perform a simple M30 to M40 scale-up but accidentally enabled the 'Global Cluster Configuration' option in the UI. This unintended action triggered sharding, leading to a severe and unexpected two-hour outage that resulted in revenue loss. The Feature Request: We need to implement a more robust system for these critical changes to protect customers from operational mistakes. A good solution would include: Clear Warning Message: When a user attempts to activate the 'Global Cluster Configuration' option, a prominent and clear warning should appear, stating: "This action will initiate cluster sharding and may cause a service outage. Do you want to proceed?" Detailed Impact Analysis: The warning should provide a summary of the consequences, such as estimated downtime, the scope of the service interruption, and the fact that converting a sharded cluster back to a replica set is not supported. Clear message to User for the changes: Before the change is applied, message should be clearly displayed as "CHANGE: Replica Set to Geo-Sharding" to confirm they fully understand and intend to proceed with the action.