A production engineering interviewer asks for decisions that survive deployment, concurrency and recovery failures. This hard round combines actual schema and policy work with operational judgment. The fictional evidence is complete enough to choose a safe action without assuming an invisible service or backup exists.
Read each output contract before writing SQL or choosing a response. Use the supplied evidence and keep missing values distinct from zeros, blanks and absent keys. For an operational scenario, select the option that satisfies every stated requirement rather than the one that sounds fastest.
The SQL tasks run on fresh fictional records and are checked again after those records change. You may use any equivalent query that produces the required result and preserves the stated database contract. The concurrency tasks use a clearly labeled session model. No question claims access to a live backup, a standby or a production connection pool.
Dependency statistics describe correlation between the named filter columns.