Complete an original production-engineering set in 55 minutes. You will inspect plans, choose transaction and migration boundaries, and reason about recovery and service behavior. A correct answer must preserve the stated data and access requirements as well as address the operational symptom.
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.
ANALYZE executes the requested filtered query and adds actual execution rows.