You manage an Azure SQL Database supporting an OLTP application. Over the past weeks, several queries have degraded because commonly filtered columns lack supporting indexes, while other unused indexes consume write overhead. Your team wants Azure SQL to automatically create beneficial indexes and drop redundant ones, but only after validating that each change actually improves performance—and to revert changes that cause regressions. Which configuration should you enable?