100% Latest & Updated Microsoft DP-800 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 360
A developer must explain generated SQL before approving deployment. A test instead finds: Unreviewed DDL drops a dependent object. Which underlying issue best explains this finding?
- Tenant or workspace feature prerequisites are not enabled
- AI output bypassed the normal code-review gate
- Generated SQL was trusted without privilege checks
- The AI tool connection used a write-capable principal
Explanation
Correct Answer
B:AI output bypassed the normal code-review gate. It accounts for the specific observed failure: unreviewed ddl drops a dependent object. The intended solution is keep human review of ai-generated ddl and its data impact with the required setup.
Incorrect Answers
A:Tenant or workspace feature prerequisites are not enabled. This concerns assistant is inaccessible in a permitted workspace. The relevant SQL or system operation is AI output bypassed the normal code-review gate.
C:Generated SQL was trusted without privilege checks. This concerns copilot-generated query reads a restricted table. The relevant SQL or system operation is AI output bypassed the normal code-review gate.
D:The AI tool connection used a write-capable principal. This concerns agent accidentally changes production rows. The relevant SQL or system operation is AI output bypassed the normal code-review gate.
Question 361
A team wants Copilot in Fabric for SQL development assistance. Which TWO listed actions form the most appropriate database design and its concrete implementation? (Choose TWO.)
- Enable it under tenant-approved Fabric governance
- Define repository instructions for schema and test conventions
- Restrict MCP tools and endpoints to trusted approved servers
- Use the documented Fabric MCP server endpoint
- Check tenant settings, capacity and access prerequisites
Explanation
Correct Answers
A:Enable it under tenant-approved Fabric governance. The implementation is check tenant settings, capacity and access prerequisites; success can be checked by verify approved users can invoke assistant in the intended workspace. The method addresses the stated data and workload constraint.
E:This is the concrete configuration of the specified design: check tenant settings, capacity and access prerequisites. The choice makes the implementation testable in the given workload.
Incorrect Answers
B:Define repository instructions for schema and test conventions. This is relevant when a team uses github copilot across its SQL database project repository. Instead, enable it under tenant-approved Fabric governance.
C:Restrict MCP tools and endpoints to trusted approved servers. This concerns a developer invokes a third-party mcp server from the SQL code assistant. Instead, enable it under tenant-approved Fabric governance.
D:Use the documented Fabric MCP server endpoint. This concerns connection to a fabric lakehouse through mcp. Instead, enable it under tenant-approved Fabric governance.
Question 362
A team wants Copilot in Fabric for SQL development assistance. The team selects: Enable it under tenant-approved Fabric governance. Which implementation action puts this design into practice?
- Check tenant settings, capacity and access prerequisites
- Require a pull request with explain plans, tests and reviewers
- Review permissions and parameterize generated queries
- Create .github/copilot-instructions.md with approved coding policy
Explanation
Correct Answer
A:Check tenant settings, capacity and access prerequisites. This is the concrete setup for enable it under tenant-approved fabric governance, and verify approved users can invoke assistant in the intended workspace supplies a direct confirmation.
Incorrect Answers
B:Require a pull request with explain plans, tests and reviewers. This concerns explain generated SQL before approving deployment. Instead, check tenant settings, capacity and access prerequisites.
C:Review permissions and parameterize generated queries. This concerns a code assistant proposes SQL access beyond the developer's privileges. Instead, check tenant settings, capacity and access prerequisites.
D:Create .github/copilot-instructions.md with approved coding policy. This is relevant when a team uses github copilot across its SQL database project repository. Instead, check tenant settings, capacity and access prerequisites.
Question 363
A team wants Copilot in Fabric for SQL development assistance. After implementing the design, which check most directly validates the expected behavior?
- Validate access to allowed lakehouse metadata only
- Verify approved users can invoke assistant in the intended workspace
- Verify new pull requests fail on leaked secret patterns
- Assess suggested migrations against the repository rules
Explanation
Correct Answer
B:Verify approved users can invoke assistant in the intended workspace. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that tenant or workspace feature prerequisites are not enabled.
Incorrect Answers
A:Validate access to allowed lakehouse metadata only. This concerns connection to a fabric lakehouse through mcp. Instead, verify approved users can invoke assistant in the intended workspace.
C:Verify new pull requests fail on leaked secret patterns. This concerns a repository contains examples that copilot may use in suggestions. Instead, verify approved users can invoke assistant in the intended workspace.
D:Assess suggested migrations against the repository rules. This is relevant when a team uses github copilot across its SQL database project repository. Instead, verify approved users can invoke assistant in the intended workspace.
Question 364
A team wants Copilot in Fabric for SQL development assistance. A test instead finds: Assistant is inaccessible in a permitted workspace. Which underlying issue best explains this finding?
- Instructions file is absent or not applied
- Generated SQL was trusted without privilege checks
- MCP connection scope is overly broad
- Tenant or workspace feature prerequisites are not enabled
Explanation
Correct Answer
D:Tenant or workspace feature prerequisites are not enabled. It accounts for the specific observed failure: assistant is inaccessible in a permitted workspace. The intended solution is enable it under tenant-approved fabric governance with the required setup.
Incorrect Answers
A:Instructions file is absent or not applied. This concerns suggestions ignore established SQL code conventions. Here, tenant or workspace feature prerequisites are not enabled.
B:Generated SQL was trusted without privilege checks. This concerns copilot-generated query reads a restricted table. Here, tenant or workspace feature prerequisites are not enabled.
C:MCP connection scope is overly broad. This concerns agent can query an unintended workspace. Here, tenant or workspace feature prerequisites are not enabled.
Question 365
A SQL agent needs connection to a Fabric lakehouse through MCP. Which database design or engineering approach most directly meets this requirement?
- Use the documented Fabric MCP server endpoint
- Remove sensitive data and constrain repository access
- Restrict MCP tools and endpoints to trusted approved servers
- Enable it under tenant-approved Fabric governance
Explanation
Correct Answer
A:Use the documented Fabric MCP server endpoint. The implementation is configure approved lakehouse connector with scoped auth; success can be checked by validate access to allowed lakehouse metadata only. The method addresses the stated data and workload constraint.
Incorrect Answers
B:Remove sensitive data and constrain repository access. This concerns a repository contains examples that copilot may use in suggestions. Instead, use the documented Fabric MCP server endpoint.
C:Restrict MCP tools and endpoints to trusted approved servers. This concerns a developer invokes a third-party mcp server from the SQL code assistant. Instead, use the documented Fabric MCP server endpoint.
D:Enable it under tenant-approved Fabric governance. This concerns copilot in fabric for SQL development assistance. Instead, use the documented Fabric MCP server endpoint.
Question 366
A SQL agent needs connection to a Fabric lakehouse through MCP. The team selects: Use the documented Fabric MCP server endpoint. Which implementation action puts this design into practice?
- Configure approved lakehouse connector with scoped auth
- Review permissions and parameterize generated queries
- Check tenant settings, capacity and access prerequisites
- Allowlist endpoints, scope credentials and tool permissions
Explanation
Correct Answer
A:Configure approved lakehouse connector with scoped auth. This is the concrete setup for use the documented fabric mcp server endpoint, and validate access to allowed lakehouse metadata only supplies a direct confirmation.
Incorrect Answers
B:Review permissions and parameterize generated queries. This concerns a code assistant proposes SQL access beyond the developer's privileges. Instead, configure approved lakehouse connector with scoped auth.
C:Check tenant settings, capacity and access prerequisites. This concerns copilot in fabric for SQL development assistance. Instead, configure approved lakehouse connector with scoped auth.
D:Allowlist endpoints, scope credentials and tool permissions. This concerns a developer invokes a third-party mcp server from the SQL code assistant. Instead, configure approved lakehouse connector with scoped auth.
Question 367
A SQL agent needs connection to a Fabric lakehouse through MCP. After implementing the design, which check most directly validates the expected behavior?
- Assess suggested migrations against the repository rules
- Review invoked tool calls and returned resources
- Validate access to allowed lakehouse metadata only
- Run with a restricted test principal and inspect access
Explanation
Correct Answer
C:Validate access to allowed lakehouse metadata only. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that mcp connection scope is overly broad.
Incorrect Answers
A:Assess suggested migrations against the repository rules. This is relevant when a team uses github copilot across its SQL database project repository. Here, validate access to allowed lakehouse metadata only.
B:Review invoked tool calls and returned resources. This concerns a developer invokes a third-party mcp server from the SQL code assistant. Here, validate access to allowed lakehouse metadata only.
D:Run with a restricted test principal and inspect access. This concerns a code assistant proposes SQL access beyond the developer's privileges. Here, validate access to allowed lakehouse metadata only.
Question 368
A SQL agent needs connection to a Fabric lakehouse through MCP. A test instead finds: Agent can query an unintended workspace. Which underlying issue best explains this finding?
- Tenant or workspace feature prerequisites are not enabled
- Untrusted MCP endpoint was enabled with broad access
- The AI tool connection used a write-capable principal
- MCP connection scope is overly broad
Explanation
Correct Answer
D:MCP connection scope is overly broad. It accounts for the specific observed failure: agent can query an unintended workspace. The intended solution is use the documented fabric mcp server endpoint with the required setup.
Incorrect Answers
A:Tenant or workspace feature prerequisites are not enabled. This concerns assistant is inaccessible in a permitted workspace. The relevant SQL or system operation is MCP connection scope is overly broad.
B:Untrusted MCP endpoint was enabled with broad access. This concerns an unexpected tool exfiltrates schema information. The relevant SQL or system operation is MCP connection scope is overly broad.
C:The AI tool connection used a write-capable principal. This concerns agent accidentally changes production rows. The relevant SQL or system operation is MCP connection scope is overly broad.
Question 369
An AI assistant uses a database connection during debugging. Which database design or engineering approach most directly meets this requirement?
- Supply read-only credentials for exploratory AI tool calls
- Apply least-privilege security review to AI-assisted output
- Never provide secrets in the assistant prompt context
- Define repository instructions for schema and test conventions
Explanation
Correct Answer
A:Supply read-only credentials for exploratory AI tool calls. The implementation is create dedicated least-privileged database principal for tool; success can be checked by try prohibited write query and confirm denial. The method addresses the stated data and workload constraint.
Incorrect Answers
B:Apply least-privilege security review to AI-assisted output. This concerns a code assistant proposes SQL access beyond the developer's privileges. Instead, supply read-only credentials for exploratory AI tool calls.
C:Never provide secrets in the assistant prompt context. This concerns a prompt asks an assistant to print database passwords for troubleshooting. Instead, supply read-only credentials for exploratory AI tool calls.
D:Define repository instructions for schema and test conventions. This is relevant when a team uses github copilot across its SQL database project repository. Instead, supply read-only credentials for exploratory AI tool calls.
Question 370
An AI assistant uses a database connection during debugging. The team selects: Supply read-only credentials for exploratory AI tool calls. Which implementation action puts this design into practice?
- Use secret store and redacted placeholders in instructions
- Create dedicated least-privileged database principal for tool
- Configure approved lakehouse connector with scoped auth
- Create .github/copilot-instructions.md with approved coding policy
Explanation
Correct Answer
B:Create dedicated least-privileged database principal for tool. This is the concrete setup for supply read-only credentials for exploratory ai tool calls, and try prohibited write query and confirm denial supplies a direct confirmation.
Incorrect Answers
A:Use secret store and redacted placeholders in instructions. This concerns a prompt asks an assistant to print database passwords for troubleshooting. Instead, create dedicated least-privileged database principal for tool.
C:Configure approved lakehouse connector with scoped auth. This concerns connection to a fabric lakehouse through mcp. Instead, create dedicated least-privileged database principal for tool.
D:Create .github/copilot-instructions.md with approved coding policy. This is relevant when a team uses github copilot across its SQL database project repository. Instead, create dedicated least-privileged database principal for tool.
Developing AI-Enabled Database Solutions (DP-800) Practice Tests