100% Latest & Updated Microsoft DP-800 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
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.
Question 621
Two developers edit the same view concurrently. Which database design or engineering approach most directly meets this requirement?
- Resolve merge conflicts with schema-level tests
- Use a controlled GitHub Actions pipeline
- Use isolated SQL unit tests with synthetic fixtures
- Reset database baseline before every test class
Explanation
Correct Answer
A:Resolve merge conflicts with schema-level tests. The implementation is review both versions and rebuild combined sql model; success can be checked by validate final view shape and dependencies. The method addresses the stated data and workload constraint.
Incorrect Answers
B:Use a controlled GitHub Actions pipeline. This concerns a github workflow deploys SQL to azure after a merge. Instead, resolve merge conflicts with schema-level tests.
C:Use isolated SQL unit tests with synthetic fixtures. This concerns testing a stored procedure without using production data. Instead, resolve merge conflicts with schema-level tests.
D:Reset database baseline before every test class. This is relevant when a database test suite requires consistent fixtures. Instead, resolve merge conflicts with schema-level tests.
Question 622
Two developers edit the same view concurrently. The team selects: Resolve merge conflicts with schema-level tests. Which implementation action puts this design into practice?
- Fail workflow on project build or dacpac validation error
- Ensure view and proc compile against latest schema
- Review both versions and rebuild combined SQL model
- Generate and retain build artifact once per source commit
Explanation
Correct Answer
C:Review both versions and rebuild combined SQL model. This is the concrete setup for resolve merge conflicts with schema-level tests, and validate final view shape and dependencies 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, review both versions and rebuild combined SQL model.
B:Ensure view and proc compile against latest schema. This concerns a team updates views and stored procedures in one change. Instead, review both versions and rebuild combined SQL model.
D:Generate and retain build artifact once per source commit. This concerns immutable artifact traceability. Instead, review both versions and rebuild combined SQL model.
Question 623
Two developers edit the same view concurrently. After implementing the design, which check most directly validates the expected behavior?
- Build and resolve external reference warnings
- Validate final view shape and dependencies
- Test SQL folder change cannot merge without owner review
- Rebuild with referenced model and check dependencies
Explanation
Correct Answer
B:Validate final view shape and dependencies. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that only text conflict was resolved without semantic test.
Incorrect Answers
A:Build and resolve external reference warnings. This is relevant when a project build fails because referenced object is in another database. Here, validate final view shape and dependencies.
C:Test SQL folder change cannot merge without owner review. This concerns protecting database folder changes. Here, validate final view shape and dependencies.
D:Rebuild with referenced model and check dependencies. This is relevant when a SQL project uses another team's shared database types. Here, validate final view shape and dependencies.
Question 624
Two developers edit the same view concurrently. A test instead finds: Resolved merge compiles but changes expected columns. Which underlying issue best explains this finding?
- SQL folder code owners were not enforced
- Only text conflict was resolved without semantic test
- Shared mutable state leaks between tests
- Tests were not isolated from production database
Explanation
Correct Answer
B:Only text conflict was resolved without semantic test. It accounts for the specific observed failure: resolved merge compiles but changes expected columns. The intended solution is resolve merge conflicts with schema-level tests with the required setup.
Incorrect Answers
A:SQL folder code owners were not enforced. This concerns non-database developer merges unsafe schema modification. Here, only text conflict was resolved without semantic test.
C:Shared mutable state leaks between tests. This concerns tests fail depending on execution order. Here, only text conflict was resolved without semantic test.
D:Tests were not isolated from production database. This concerns unit tests mutate live business rows. Here, only text conflict was resolved without semantic test.
Question 625
A deployment pipeline needs SQL authentication secret. Which database design or engineering approach most directly meets this requirement?
- Publish a versioned DACPAC with SHA in artifact store
- Store password in protected CI/CD secret store
- Run end-to-end integration tests on temporary environment
- Enable repository secret scanning and review gates
Explanation
Correct Answer
B:Store password in protected CI/CD secret store. The implementation is reference masked secret variable and limit pipeline scope; success can be checked by check job logs do not show credential values. The method addresses the stated data and workload constraint.
Incorrect Answers
A:Publish a versioned DACPAC with SHA in artifact store. This concerns immutable artifact traceability. Instead, store password in protected CI/CD secret store.
C:Run end-to-end integration tests on temporary environment. This concerns prove its API and database integration work together. Instead, store password in protected CI/CD secret store.
D:Enable repository secret scanning and review gates. This concerns avoiding secrets in prs. Instead, store password in protected CI/CD secret store.
Question 626
A deployment pipeline needs SQL authentication secret. The team selects: Store password in protected CI/CD secret store. Which implementation action puts this design into practice?
- Reference masked secret variable and limit pipeline scope
- Configure secret scanning and pre-commit detection
- Configure reference dacpac or project with SQLCMD variable
- Fail workflow on project build or dacpac validation error
Explanation
Correct Answer
A:Reference masked secret variable and limit pipeline scope. This is the concrete setup for store password in protected ci/cd secret store, and check job logs do not show credential values supplies a direct confirmation.
Incorrect Answers
B:Configure secret scanning and pre-commit detection. This concerns avoiding secrets in prs. Here, reference masked secret variable and limit pipeline scope.
C:Configure reference dacpac or project with SQLCMD variable. This is relevant when a project build fails because referenced object is in another database. Here, reference masked secret variable and limit pipeline scope.
D:Fail workflow on project build or dacpac validation error. This concerns stopping deployment on SQL model validation errors. Here, reference masked secret variable and limit pipeline scope.
Question 627
A deployment pipeline needs SQL authentication secret. After implementing the design, which check most directly validates the expected behavior?
- Check sample fake secret triggers a block
- Insert invalid reference and confirm stage blocks
- Rebuild with referenced model and check dependencies
- Check job logs do not show credential values
Explanation
Correct Answer
D:Check job logs do not show credential values. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that secret was hard-coded or echoed.
Incorrect Answers
A:Check sample fake secret triggers a block. This concerns avoiding secrets in prs. Instead, check job logs do not show credential values.
B:Insert invalid reference and confirm stage blocks. This concerns stopping deployment on SQL model validation errors. Instead, check job logs do not show credential values.
C:Rebuild with referenced model and check dependencies. This is relevant when a SQL project uses another team's shared database types. Instead, check job logs do not show credential values.
Question 628
A deployment pipeline needs SQL authentication secret. A test instead finds: Database password leaks in build output. Which underlying issue best explains this finding?
- Secret was hard-coded or echoed
- Pipeline rebuilt source differently per environment
- Potential data-loss gate was disabled
- Secret checks are missing or bypassed
Explanation
Correct Answer
A:Secret was hard-coded or echoed. It accounts for the specific observed failure: database password leaks in build output. The intended solution is store password in protected ci/cd secret store with the required setup.
Incorrect Answers
B:Pipeline rebuilt source differently per environment. This concerns production uses artifacts different from test. Here, secret was hard-coded or echoed.
C:Potential data-loss gate was disabled. This concerns deployment silently drops a populated column. Here, secret was hard-coded or echoed.
D:Secret checks are missing or bypassed. This concerns token appears in checked-in config. Here, secret was hard-coded or echoed.
Question 629
A team notices production schema does not match approved source. Which database design or engineering approach most directly meets this requirement?
- Use separate validated test and production deployment stages
- Add a database reference to the SQL Database Project
- Create a SQL Database Project with source-controlled schema
- Run SQL Database Project drift comparison
Explanation
Correct Answer
D:Run SQL Database Project drift comparison. The implementation is compare deployed database against expected dacpac model; success can be checked by record unexpected additions/deletions before release. The method addresses the stated data and workload constraint.
Incorrect Answers
A:Use separate validated test and production deployment stages. This concerns staged promotion of SQL schema changes. Instead, run SQL Database Project drift comparison.
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, run SQL Database Project drift comparison.
C:Create a SQL Database Project with source-controlled schema. This concerns table definitions versioned with application code. Instead, run SQL Database Project drift comparison.
Question 630
A team notices production schema does not match approved source. The team selects: Run SQL Database Project drift comparison. Which implementation action puts this design into practice?
- Compare deployed database against expected dacpac model
- Pin dependency reference and validate schema contract
- Ensure view and proc compile against latest schema
- Enable data-loss blocking and inspect deployment report
Explanation
Correct Answer
A:Compare deployed database against expected dacpac model. This is the concrete setup for run sql database project drift comparison, and record unexpected additions/deletions before release supplies a direct confirmation.
Incorrect Answers
B:Pin dependency reference and validate schema contract. This is relevant when a SQL project uses another team's shared database types. Instead, compare deployed database against expected dacpac model.
C:Ensure view and proc compile against latest schema. This concerns a team updates views and stored procedures in one change. Instead, compare deployed database against expected dacpac model.
D:Enable data-loss blocking and inspect deployment report. This concerns a deployment may delete production data through dacpac change. Instead, compare deployed database against expected dacpac model.
Developing AI-Enabled Database Solutions (DP-800) Practice Tests