Resolving System Object References in Azure SQL Database Projects
Short answer
B Running dotnet build with logging flags does not include necessary system object references to fix the build error.
Question
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?
Key Takeaways
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.
Common mistake: 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.
Expert Analysis
Why the Answer Is Correct
The proposed solution fails to meet the goal because the command dotnet 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?
What does the -bl flag do in dotnet build?
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
gangreja 👍 1 Answered BThose flags only change logging. They don’t add anything to the project
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.