Knowledge check

3 minutes

You use Copilot in the Azure SQL Database portal to investigate a performance issue. Copilot suggests that a stored procedure experienced a plan regression at 14:02 UTC yesterday and recommends forcing the previous plan. What should you do next?

Immediately force the previous plan using Query Store in the portal.

Validate the recommendation in Query Store in SSMS, confirm the plan regression occurred, check the plan difference, and test the forced plan in a nonproduction environment first.

Dismiss the recommendation. Copilot portal diagnostics aren't reliable for production databases.

You ask GitHub Copilot in SSMS to generate a stored procedure. The generated code includes GRANT EXECUTE ON SCHEMA::dbo TO AppServiceAccount. What should you do?

Accept the grant. Schema-level permission is standard practice.

Replace the schema-level grant with an object-level grant on the specific stored procedure.

Replace the grant with db_owner membership for simplicity.

You use GitHub Copilot to generate an Azure CLI command to set a long-term retention policy. Before you run the command in production, what is the most important thing to verify?

The command was generated from a descriptive enough comment.

The Azure CLI parameter names and syntax match the current CLI release, since Copilot's training data may be behind the current version.

You ran the command in production first to verify it works.

You must answer all questions before checking your work.

피드백

이 페이지가 도움이 되었나요?