One database, many customers. How do you make it structurally hard for tenant A to read tenant B's data?
Answer it out loud before you open anything. The value of the flags below is in comparing them to what you actually said.
The situation behind the question
A B2B SaaS with a shared schema and a tenant_id column on every table. A recent incident: a report endpoint returned another customer's rows because one query was missing its tenant filter.
What it is really testing
Whether the candidate reaches for a mechanism that fails closed instead of a convention that relies on every developer remembering. "Always add tenant_id to the WHERE clause" is the answer that produced the incident in the scenario.