Dataford
Interview QuestionsInterview GuidesExperiencesMock InterviewsPricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan
Database Indexing Trade-Offs
00:00
5 left

Database Indexing Trade-Offs

HardSQL · PostgreSQL

Problem

Explain the trade-offs between different database indexing strategies for a food-ordering system.

Use the supplied tables and query workload to produce the requested order totals, then explain which indexes would support this access pattern and their costs.

Output

  1. One row per completed order created in January 2026, excluding orders outside the date range or with another status.
  2. Columns: order_id, restaurant_id, created_at, and order_total.
  3. Include completed orders with no items as 0.00. Order by created_at ascending, then order_id ascending.

Schema

orders
ColumnTypeDescription
order_idPKINTUnique food order identifier
customer_idINTCustomer identifier
restaurant_idINTRestaurant identifier
statusVARCHAR(40)Current order status
created_atTIMESTAMPOrder creation timestamp
order_items
ColumnTypeDescription
order_item_idPKINTUnique order line identifier
order_idINTReferenced order identifier
menu_item_idINTReferenced menu item identifier
quantityINTQuantity ordered
menu_items
ColumnTypeDescription
menu_item_idPKINTUnique menu item identifier
item_nameVARCHAR(100)Menu item name
unit_priceNUMERIC(10,2)Price per item
is_availableBOOLEANWhether the item is currently available
Tablesordersorder_itemsmenu_items
Interviewer

Your question is Database Indexing Trade-Offs. Start with the requirements and the three tables in the Question tab.

Run and submit as often as you like. When you're ready, talk me through your approach or go straight to the code.

You need to log in / sign up to run or submit.
CodePostgreSQL
Sign up free to run your codeLog inLn 1
Run your query to see results here.