Resolving System Object References in Azure SQL Database Projects
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have an SDK-style SQL database project stored in a Git repository. The project targets an Azure SQL database. The CI build fails with unresolved reference errors when the project references system objects. You need to update the SQL database project to ensure that dotnet build validates successfully by including the correct system objects in the database model for Azure SQL Database. Solution: Build the project by running dotnet build -bl -flp:v=diag. Does this meet the goal?
Community Insight
The exam tests knowledge of SQL Database Project configuration for Azure-specific system schemas; the trap is confusing diagnostic logging flags with actual dependency resolution.
This question addresses how to resolve unresolved reference errors for system objects in an SDK-style SQL Database Project targeting Azure SQL. The correct approach involves configuring the project model rather than altering build diagnostics.
Learners often select 'Yes' because they associate the command with troubleshooting, failing to realize that logging flags do not modify the compilation model or include missing references.
Community Discussion (1 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The proposed solution fails to meet the goal because the commanddotnet build -bl -flp:v=diag only enables detailed binary log and file logger output. These flags are purely diagnostic and do not change what files or references are included in the build process. To resolve unresolved references to system objects (like those in the sys schema) in an Azure SQL context, the project must be configured to include these specific references, typically by adding a SystemReferenceDirectoryPath or explicitly referencing the Azure SQL database schema files in the .sqlproj file.Why the Other Options Are Wrong
Since the solution does not add any references or modify the project structure, it cannot fix the build failure caused by missing system object definitions. Therefore, the answer is definitively 'No'. Any option suggesting that logging commands affect compilation dependencies is incorrect.Community Comment Notes
Community feedback confirms that the flags used in the solution "only change logging" and "don’t add anything to the project," leading users to correctly identify that the goal is not met.Exam Strategy
When evaluating CI/CD or build-related solutions in DP-800, distinguish between commands that provide visibility (logging/debugging) and commands that alter the build artifact or dependencies (referencing/modeling).
Frequently Asked Questions
How do I actually resolve system object references in SQL DB Projects?
You must configure the .sqlproj file to include the appropriate system reference paths or explicit references to Azure SQL system schemas.
What does the -bl flag do in dotnet build?
The -bl flag generates a binary log file for diagnostics; it does not affect which files are compiled or referenced.