100% Latest & Updated Microsoft DP-800 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 610
A SQL project includes static region codes that change rarely. The team selects: Track reference data scripts in source control. Which implementation action puts this design into practice?
- Pin dependency reference and validate schema contract
- Use controlled post-deployment MERGE/upsert script
- Set branch protection and code owners for schema folders
- Enable data-loss blocking and inspect deployment report
Explanation
Correct Answer
B:Use controlled post-deployment MERGE/upsert script. This is the concrete setup for track reference data scripts in source control, and rebuild and confirm approved codes remain idempotent supplies a direct confirmation.
Incorrect Answers
A:Pin dependency reference and validate schema contract. This is relevant when a SQL project uses another team's shared database types. Instead, use controlled post-deployment MERGE/upsert script.
C:Set branch protection and code owners for schema folders. This concerns a branch introduces an unapproved table drop. Instead, use controlled post-deployment MERGE/upsert script.
D:Enable data-loss blocking and inspect deployment report. This concerns a deployment may delete production data through dacpac change. Instead, use controlled post-deployment MERGE/upsert script.
Question 611
A SQL project includes static region codes that change rarely. After implementing the design, which check most directly validates the expected behavior?
- Insert invalid reference and confirm stage blocks
- Rebuild with referenced model and check dependencies
- Build against chosen SQL Server/Azure SQL target
- Rebuild and confirm approved codes remain idempotent
Explanation
Correct Answer
D:Rebuild and confirm approved codes remain idempotent. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that reference-data script was destructive rather than reconciliatory.
Incorrect Answers
A:Insert invalid reference and confirm stage blocks. This concerns stopping deployment on SQL model validation errors. Here, rebuild and confirm approved codes remain idempotent.
B:Rebuild with referenced model and check dependencies. This is relevant when a SQL project uses another team's shared database types. Here, rebuild and confirm approved codes remain idempotent.
C:Build against chosen SQL Server/Azure SQL target. This concerns selecting engine-specific targets. Here, rebuild and confirm approved codes remain idempotent.
Question 612
A SQL project includes static region codes that change rarely. A test instead finds: Deploy overwrites custom production values. Which underlying issue best explains this finding?
- Potential data-loss gate was disabled
- Unpinned external reference changed unexpectedly
- Reference-data script was destructive rather than reconciliatory
- Project target platform mismatches deployed engine
Explanation
Correct Answer
C:Reference-data script was destructive rather than reconciliatory. It accounts for the specific observed failure: deploy overwrites custom production values. The intended solution is track reference data scripts in source control with the required setup.
Incorrect Answers
A:Potential data-loss gate was disabled. This concerns deployment silently drops a populated column. Here, reference-data script was destructive rather than reconciliatory.
B:Unpinned external reference changed unexpectedly. This concerns new dependency revision breaks stored procedures. Here, reference-data script was destructive rather than reconciliatory.
D:Project target platform mismatches deployed engine. This concerns feature script compiles locally but fails in azure. Here, reference-data script was destructive rather than reconciliatory.
Question 613
An engineer needs predictable schema model compilation in CI. Which TWO listed actions form the most appropriate database design and its concrete implementation? (Choose TWO.)
- Use dotnet build for SDK-style SQL project when configured
- Add a database reference to the SQL Database Project
- Enforce build and validation checks before publish
- Reference the shared project at compatible version
- Define Microsoft.Build.Sql SDK project and build target
Explanation
Correct Answers
A:Use dotnet build for SDK-style SQL project when configured. The implementation is define microsoft.build.sql sdk project and build target; success can be checked by check dacpac output and build diagnostics. The method addresses the stated data and workload constraint.
E:This is the concrete configuration of the specified design: define microsoft.build.sql sdk project and build target. The choice makes the implementation testable in the given workload.
Incorrect Answers
B:Add a database reference to the SQL Database Project. This is relevant when a project build fails because referenced object is in another database. Instead, use dotnet build for SDK-style SQL project when configured.
C:Enforce build and validation checks before publish. This concerns stopping deployment on SQL model validation errors. Instead, use dotnet build for SDK-style SQL project when configured.
D:Reference the shared project at compatible version. This is relevant when a SQL project uses another team's shared database types. Instead, use dotnet build for SDK-style SQL project when configured.
Question 614
An engineer needs predictable schema model compilation in CI. The team selects: Use dotnet build for SDK-style SQL project when configured. Which implementation action puts this design into practice?
- Fail workflow on project build or dacpac validation error
- Set SqlTargetPlatform or supported SDK configuration
- Define Microsoft.Build.Sql SDK project and build target
- Configure reference dacpac or project with SQLCMD variable
Explanation
Correct Answer
C:Define Microsoft.Build.Sql SDK project and build target. This is the concrete setup for use dotnet build for sdk-style sql project when configured, and check dacpac output and build diagnostics supplies a direct confirmation.
Incorrect Answers
A:Fail workflow on project build or dacpac validation error. This concerns stopping deployment on SQL model validation errors. Instead, define Microsoft.Build.Sql SDK project and build target.
B:Set SqlTargetPlatform or supported SDK configuration. This concerns selecting engine-specific targets. Instead, define Microsoft.Build.Sql SDK project and build target.
D:Configure reference dacpac or project with SQLCMD variable. This is relevant when a project build fails because referenced object is in another database. Instead, define Microsoft.Build.Sql SDK project and build target.
Question 615
An engineer needs predictable schema model compilation in CI. After implementing the design, which check most directly validates the expected behavior?
- Build dacpac and compare model to target schema
- Check dacpac output and build diagnostics
- Insert invalid reference and confirm stage blocks
- Compare deployed dacpac hash to approved build
Explanation
Correct Answer
B:Check dacpac output and build diagnostics. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that sdk project was not built correctly.
Incorrect Answers
A:Build dacpac and compare model to target schema. This concerns table definitions versioned with application code. Instead, check dacpac output and build diagnostics.
C:Insert invalid reference and confirm stage blocks. This concerns stopping deployment on SQL model validation errors. Instead, check dacpac output and build diagnostics.
D:Compare deployed dacpac hash to approved build. This concerns immutable artifact traceability. Instead, check dacpac output and build diagnostics.
Question 616
An engineer needs predictable schema model compilation in CI. A test instead finds: Pipeline reports no deployable model artifact. Which underlying issue best explains this finding?
- Reference-data script was destructive rather than reconciliatory
- Schema drift detection is disabled
- Pipeline rebuilt source differently per environment
- SDK project was not built correctly
Explanation
Correct Answer
D:SDK project was not built correctly. It accounts for the specific observed failure: pipeline reports no deployable model artifact. The intended solution is use dotnet build for sdk-style sql project when configured with the required setup.
Incorrect Answers
A:Reference-data script was destructive rather than reconciliatory. This concerns deploying overwrites custom production values. The relevant SQL or system operation is SDK project was not built correctly.
B:Schema drift detection is disabled. This concerns manual production hotfix goes undetected. The relevant SQL or system operation is SDK project was not built correctly.
C:Pipeline rebuilt source differently per environment. This concerns production uses artifacts different from test. The relevant SQL or system operation is SDK project was not built correctly.
Question 617
A branch introduces an unapproved table drop. Which database design or engineering approach most directly meets this requirement?
- Use dotnet build for SDK-style SQL project when configured
- Require schema code-owner approval in pull requests
- Enable repository secret scanning and review gates
- Require pull-request schema review and automated diff gates
Explanation
Correct Answer
D:Require pull-request schema review and automated diff gates. The implementation is set branch protection and code owners for schema folders; success can be checked by attempt merge without review and confirm blocked. The method addresses the stated data and workload constraint.
Incorrect Answers
A:Use dotnet build for SDK-style SQL project when configured. This concerns predictable schema model compilation in CI. Instead, require pull-request schema review and automated diff gates.
B:Require schema code-owner approval in pull requests. This concerns protecting database folder changes. Instead, require pull-request schema review and automated diff gates.
C:Enable repository secret scanning and review gates. This concerns avoiding secrets in prs. Instead, require pull-request schema review and automated diff gates.
Question 618
A branch introduces an unapproved table drop. The team selects: Require pull-request schema review and automated diff gates. Which implementation action puts this design into practice?
- Set branch protection and code owners for schema folders
- Store tables, views, procedures as project SQL files
- Create service principal and grant deployment permissions only
- Configure CODEOWNERS and protected branch rules
Explanation
Correct Answer
A:Set branch protection and code owners for schema folders. This is the concrete setup for require pull-request schema review and automated diff gates, and attempt merge without review and confirm blocked supplies a direct confirmation.
Incorrect Answers
B:Store tables, views, procedures as project SQL files. This concerns table definitions versioned with application code. Instead, set branch protection and code owners for schema folders.
C:Create service principal and grant deployment permissions only. This concerns using least privilege for database deploy. Instead, set branch protection and code owners for schema folders.
D:Configure CODEOWNERS and protected branch rules. This concerns protecting database folder changes. Instead, set branch protection and code owners for schema folders.
Question 619
A branch introduces an unapproved table drop. After implementing the design, which check most directly validates the expected behavior?
- Rebuild with referenced model and check dependencies
- Attempt merge without review and confirm blocked
- Test SQL folder change cannot merge without owner review
- Run against test copy with pending drop
Explanation
Correct Answer
B:Attempt merge without review and confirm blocked. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that branch protection is missing.
Incorrect Answers
A:Rebuild with referenced model and check dependencies. This is relevant when a SQL project uses another team's shared database types. Here, attempt merge without review and confirm blocked.
C:Test SQL folder change cannot merge without owner review. This concerns protecting database folder changes. Here, attempt merge without review and confirm blocked.
D:Run against test copy with pending drop. This concerns a deployment may delete production data through dacpac change. Here, attempt merge without review and confirm blocked.
Question 620
A branch introduces an unapproved table drop. A test instead finds: Destructive SQL merges directly to main. Which underlying issue best explains this finding?
- Secret was hard-coded or echoed
- Schema was maintained only by manual portal edits
- SQL folder code owners were not enforced
- Branch protection is missing
Explanation
Correct Answer
D:Branch protection is missing. It accounts for the specific observed failure: destructive sql merges directly to main. The intended solution is require pull-request schema review and automated diff gates with the required setup.
Incorrect Answers
A:Secret was hard-coded or echoed. This concerns database password leaks in build output. Here, branch protection is missing.
B:Schema was maintained only by manual portal edits. This concerns production objects are not reproducible from source. Here, branch protection is missing.
C:SQL folder code owners were not enforced. This concerns non-database developer merges unsafe schema modification. Here, branch protection is missing.
Developing AI-Enabled Database Solutions (DP-800) Practice Tests