Evaluation shows that Copilot code review repeatedly misses unsafe SQL string concatenation in migration files. The team adds path-specific instructions for database migrations. Evaluate the following statements. 1. These instructions are scoped to files matching db/migrations/**/*.sql. 2. These instructions replace the need to review Copilot’s output. 3. The next evaluation run should check whether review comments changed on migration PRs.
.github/instructions/migrations.instructions.md
---
applyTo: "db/migrations/**/*.sql"
---
When reviewing migration files:
- Flag string-concatenated SQL built from request or environment values.
- Require an explicit rollback note for destructive schema changes.
- Mention the migration identifier in each review comment.Choose an answer
Tap an option to check your answer.
Correct answer: 1=Yes 2=No 3=Yes.
Why this is the answer
Statement 1 is correct because the applyTo: "db/migrations//.sql" directive explicitly scopes these instructions to files matching that glob pattern, meaning they will only be active for SQL files within the db/migrations directory and its subdirectories. Statement 2 is incorrect; Copilot is an AI assistant, and its output, especially concerning security-sensitive areas like SQL, always requires human review. These instructions are meant to guide the human reviewer, not replace them. Statement 3 is correct because the goal of adding these instructions is to improve the review process. The next evaluation should verify if the instructions are effective by observing changes in review comments, specifically if the previously missed issues (like unsafe SQL concatenation) are now being flagged.
Pass your exam — without the endless answer hunt
Get every verified question and explanation for this exam in one place, and save hours of prep. 1,000+ certifications · 20+ languages · free to start.
Pass your exam faster → No card needed