SQL Server Interview Topic 22: Scenario Mock Round
Use this topic as a mock interview. These questions combine design, queries, performance, APIs, and production safety.
You should answer each scenario like a full stack developer who understands both application code and SQL Server.
Q145. A student list screen is slow. What do you check?
Quick interview answer:
Check filters, returned columns, row count, pagination, indexes, and the execution plan. Also check whether the API loads extra related data that the screen does not need.
Study in detail: Performance Case Studies and API Integration - These articles explain full stack performance thinking.
Q146. A report is missing students with no exam marks. What is likely wrong?
Quick interview answer:
The query may be using INNER JOIN instead of LEFT JOIN. If students without marks must appear, the student table should be the main table and marks should be left joined.
Study in detail: LEFT and RIGHT JOIN - This lesson explains unmatched rows.
Q147. Fees were updated but history was not inserted. How should this be handled?
Quick interview answer:
Fee update and history insert should be inside one transaction. If either step fails, both should roll back so the database does not become inconsistent.
Study in detail: Transactions and Concurrency - This article explains all-or-nothing changes.
Q148. A new report needs sensitive student details. What do you ask first?
Quick interview answer:
Ask who needs the report, why they need the sensitive columns, and whether access is approved. Return only required columns and protect the report with proper permissions.
Study in detail: Security and Compliance and Audit - These lessons explain data safety.
Q149. A release adds a new required column. What is your plan?
Quick interview answer:
Plan the schema change, handle existing rows, test migration scripts, update the application, verify in staging, confirm backup, and then release carefully. Required columns need special care because old records may not have values.
Study in detail: Schema Evolution - This article explains production-safe schema changes.
Answer scenario questions in this order: problem, checks, SQL concept, safe fix, and how you verify.