Understand why a composite index's column order determines whether the optimizer can use it for filtering and joining.
A table has a composite B-tree index on (customer_id, order_date). A query runs: SELECT * FROM orders WHERE order_date >= '2024-01-01'. The optimizer performs a full table scan instead of using the index. What is the most likely reason?