A developer runs the following query frequently against a container that uses the default indexing policy: SELECT * FROM c WHERE c.temperature > 30 AND c.status = 'active'. The container is read-heavy with modest write volume. Query metrics show a low index hit ratio and higher-than-expected RU charges because the query performs a large scan after the index seek. Which single change will most effectively reduce the RU charge of this specific query?