Question
Your development team uses GitHub Copilot Chat in Microsoft SQL Server Management Studio (SSMS) to generate and run Transact-SQL queries against an Azure SQL database named DB1. DB1 contains tables that store sensitive customer data.
You need to ensure that any Transact-SQL queries that run from GitHub Copilot Chat in SSMS are restricted by the same permissions as the developer's database login.
What prevents the GitHub Copilot Chat-run queries from accessing data beyond the developer's access?
- A. GitHub Copilot Chat runs queries in a read-only sandbox that is isolated from production database permissions.
- B. GitHub Copilot Chat runs queries by using the developer's database identity and permissions. Correct
- C. GitHub Copilot Chat filters query results on the client side to remove rows the developer is unauthorized to see.
- D. GitHub Copilot Chat uses different row-level security (RLS) policies than the developer.
Explanation
GitHub Copilot in SSMS executes queries based on the permissions of your login, so a query against a table you cannot select from simply fails. The database engine enforces this with the developer's own identity. There is no separate read-only sandbox, no client-side row filtering, and no separate set of RLS policies for Copilot.
