Your question is Index Design for a Query. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
Realpage's property management platform has a leases table (lease_id, property_id, tenant_id, status, start_date, end_date, monthly_rent) with tens of millions of rows across all managed properties. The application's property dashboard runs this query on every page load, and it currently does a full table scan.
SELECT lease_id,
tenant_id,
monthly_rent,
end_date
FROM leases
WHERE property_id = 4821
AND status = 'active'
ORDER BY end_date ASC;
Design an index to support this query well, and explain the reasoning behind each choice you make, including any naive index designs you're deliberately avoiding.