100% Latest & Updated Microsoft DP-800 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 670
A staging environment should use least privilege for database deploy. The team selects: Use separate deployment identity with scoped DDL rights. Which implementation action puts this design into practice?
- Create service principal and grant deployment permissions only
- Use controlled post-deployment MERGE/upsert script
- Use test containers or clean seeded SQL schema
- Set SqlTargetPlatform or supported SDK configuration
Explanation
Correct Answer
A:Create service principal and grant deployment permissions only. This is the concrete setup for use separate deployment identity with scoped ddl rights, and test deployment works but unrelated data export denied supplies a direct confirmation.
Incorrect Answers
B:Use controlled post-deployment MERGE/upsert script. This concerns a SQL project includes static region codes that change rarely. Instead, create service principal and grant deployment permissions only.
C:Use test containers or clean seeded SQL schema. This is relevant when a database test suite requires consistent fixtures. Instead, create service principal and grant deployment permissions only.
D:Set SqlTargetPlatform or supported SDK configuration. This concerns selecting engine-specific targets. Instead, create service principal and grant deployment permissions only.
Question 671
A staging environment should use least privilege for database deploy. After implementing the design, which check most directly validates the expected behavior?
- Test deployment works but unrelated data export denied
- Run against test copy with pending drop
- Repeat test run and compare stable outcomes
- Build dacpac and compare model to target schema
Explanation
Correct Answer
A:Test deployment works but unrelated data export denied. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that deployment principal is overprivileged.
Incorrect Answers
B:Run against test copy with pending drop. This concerns a deployment may delete production data through dacpac change. Instead, test deployment works but unrelated data export denied.
C:Repeat test run and compare stable outcomes. This is relevant when a database test suite requires consistent fixtures. Instead, test deployment works but unrelated data export denied.
D:Build dacpac and compare model to target schema. This concerns table definitions versioned with application code. Instead, test deployment works but unrelated data export denied.
Question 672
A staging environment should use least privilege for database deploy. A test instead finds: Pipeline credential can read sensitive business data. Which underlying issue best explains this finding?
- Backfill or compatibility sequencing was omitted
- Pipeline rebuilt source differently per environment
- Deployment principal is overprivileged
- External database reference is missing
Explanation
Correct Answer
C:Deployment principal is overprivileged. It accounts for the specific observed failure: pipeline credential can read sensitive business data. The intended solution is use separate deployment identity with scoped ddl rights with the required setup.
Incorrect Answers
A:Backfill or compatibility sequencing was omitted. This concerns new application reads nulls immediately after release. Here, deployment principal is overprivileged.
B:Pipeline rebuilt source differently per environment. This concerns production uses artifacts different from test. Here, deployment principal is overprivileged.
D:External database reference is missing. This concerns object names are unresolved at build time. Here, deployment principal is overprivileged.
Question 673
A team updates views and stored procedures in one change. Which database design or engineering approach most directly meets this requirement?
- Enforce build and validation checks before publish
- Use separate deployment identity with scoped DDL rights
- Require destructive-change review and deployment-block policy
- Build and publish model with dependency validation
Explanation
Correct Answer
D:Build and publish model with dependency validation. The implementation is ensure view and proc compile against latest schema; success can be checked by execute integration tests after deployment. The method addresses the stated data and workload constraint.
Incorrect Answers
A:Enforce build and validation checks before publish. This concerns stopping deployment on SQL model validation errors. Instead, build and publish model with dependency validation.
B:Use separate deployment identity with scoped DDL rights. This concerns using least privilege for database deploy. Instead, build and publish model with dependency validation.
C:Require destructive-change review and deployment-block policy. This concerns a deployment may delete production data through dacpac change. Instead, build and publish model with dependency validation.
Question 674
A team updates views and stored procedures in one change. The team selects: Build and publish model with dependency validation. Which implementation action puts this design into practice?
- Create repeatable tests that seed and clean temporary data
- Generate and retain build artifact once per source commit
- Store tables, views, procedures as project SQL files
- Ensure view and proc compile against latest schema
Explanation
Correct Answer
D:Ensure view and proc compile against latest schema. This is the concrete setup for build and publish model with dependency validation, and execute integration tests after deployment supplies a direct confirmation.
Incorrect Answers
A:Create repeatable tests that seed and clean temporary data. This concerns testing a stored procedure without using production data. Instead, ensure view and proc compile against latest schema.
B:Generate and retain build artifact once per source commit. This concerns immutable artifact traceability. Instead, ensure view and proc compile against latest schema.
C:Store tables, views, procedures as project SQL files. This concerns table definitions versioned with application code. Instead, ensure view and proc compile against latest schema.
Question 675
A team updates views and stored procedures in one change. After implementing the design, which check most directly validates the expected behavior?
- Run against test copy with pending drop
- Run suite against representative boundary cases
- Attempt merge without review and confirm blocked
- Execute integration tests after deployment
Explanation
Correct Answer
D:Execute integration tests after deployment. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that dependent modules were not validated against model.
Incorrect Answers
A:Run against test copy with pending drop. This concerns a deployment may delete production data through dacpac change. Instead, execute integration tests after deployment.
B:Run suite against representative boundary cases. This concerns testing a stored procedure without using production data. Instead, execute integration tests after deployment.
C:Attempt merge without review and confirm blocked. This concerns a branch introduces an unapproved table drop. Instead, execute integration tests after deployment.
Question 676
A team updates views and stored procedures in one change. A test instead finds: Procedure references an obsolete column. Which underlying issue best explains this finding?
- Dependent modules were not validated against model
- Tests were not isolated from production database
- SDK project was not built correctly
- Build failure was not configured as release blocker
Explanation
Correct Answer
A:Dependent modules were not validated against model. It accounts for the specific observed failure: procedure references an obsolete column. The intended solution is build and publish model with dependency validation with the required setup.
Incorrect Answers
B:Tests were not isolated from production database. This concerns unit tests mutate live business rows. Here, dependent modules were not validated against model.
C:SDK project was not built correctly. This concerns pipeline reports no deployable model artifact. Here, dependent modules were not validated against model.
D:Build failure was not configured as release blocker. This concerns invalid SQL reaches deployment step. Here, dependent modules were not validated against model.
Question 677
A new SQL database project must select engine-specific targets. Which database design or engineering approach most directly meets this requirement?
- Add a database reference to the SQL Database Project
- Choose target SQL platform and compatibility accurately
- Resolve merge conflicts with schema-level tests
- Create a SQL Database Project with source-controlled schema
Explanation
Correct Answer
B:Choose target SQL platform and compatibility accurately. The implementation is set sqltargetplatform or supported sdk configuration; success can be checked by build against chosen sql server/azure sql target. The method addresses the stated data and workload constraint.
Incorrect Answers
A: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, choose target SQL platform and compatibility accurately.
C:Resolve merge conflicts with schema-level tests. This concerns two developers edit the same view concurrently. Instead, choose target SQL platform and compatibility accurately.
D:Create a SQL Database Project with source-controlled schema. This concerns table definitions versioned with application code. Instead, choose target SQL platform and compatibility accurately.
Question 678
A new SQL database project must select engine-specific targets. The team selects: Choose target SQL platform and compatibility accurately. Which implementation action puts this design into practice?
- Set SqlTargetPlatform or supported SDK configuration
- Define Microsoft.Build.Sql SDK project and build target
- Configure reference dacpac or project with SQLCMD variable
- Pin dependency reference and validate schema contract
Explanation
Correct Answer
A:Set SqlTargetPlatform or supported SDK configuration. This is the concrete setup for choose target sql platform and compatibility accurately, and build against chosen sql server/azure sql target supplies a direct confirmation.
Incorrect Answers
B:Define Microsoft.Build.Sql SDK project and build target. This concerns predictable schema model compilation in CI. Instead, set SqlTargetPlatform or supported SDK configuration.
C:Configure reference dacpac or project with SQLCMD variable. This is relevant when a project build fails because referenced object is in another database. Instead, set SqlTargetPlatform or supported SDK configuration.
D:Pin dependency reference and validate schema contract. This is relevant when a SQL project uses another team's shared database types. Instead, set SqlTargetPlatform or supported SDK configuration.
Question 679
A new SQL database project must select engine-specific targets. After implementing the design, which check most directly validates the expected behavior?
- Build dacpac and compare model to target schema
- Build against chosen SQL Server/Azure SQL target
- Build and resolve external reference warnings
- Rebuild with referenced model and check dependencies
Explanation
Correct Answer
B:Build against chosen SQL Server/Azure SQL target. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that project target platform mismatches deployed engine.
Incorrect Answers
A:Build dacpac and compare model to target schema. This concerns table definitions versioned with application code. Instead, build against chosen SQL Server/Azure SQL target.
C:Build and resolve external reference warnings. This is relevant when a project build fails because referenced object is in another database. Instead, build against chosen SQL Server/Azure SQL target.
D:Rebuild with referenced model and check dependencies. This is relevant when a SQL project uses another team's shared database types. Instead, build against chosen SQL Server/Azure SQL target.
Question 680
A new SQL database project must select engine-specific targets. A test instead finds: Feature script compiles locally but fails in Azure. Which underlying issue best explains this finding?
- Project target platform mismatches deployed engine
- Deployment principal is overprivileged
- Unpinned external reference changed unexpectedly
- External database reference is missing
Explanation
Correct Answer
A:Project target platform mismatches deployed engine. It accounts for the specific observed failure: feature script compiles locally but fails in azure. The intended solution is choose target sql platform and compatibility accurately with the required setup.
Incorrect Answers
B:Deployment principal is overprivileged. This concerns pipeline credential can read sensitive business data. Here, project target platform mismatches deployed engine.
C:Unpinned external reference changed unexpectedly. This concerns new dependency revision breaks stored procedures. Here, project target platform mismatches deployed engine.
D:External database reference is missing. This concerns object names are unresolved at build time. Here, project target platform mismatches deployed engine.
Developing AI-Enabled Database Solutions (DP-800) Practice Tests