Microsoft DP-300 Exam Dumps, Practice Test Questions

100% Latest & Updated Microsoft DP-300 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!

Microsoft DP-300 Premium Bundle
$79.97
$59.98

DP-300 Premium Bundle

  • Premium File: 470 Questions & Answers. Last update: Nov 5, 2026
  • Training Course: 130 Video Lectures
  • Study Guide: 672 Pages
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

DP-300 Premium Bundle

Microsoft DP-300 Premium Bundle
  • Premium File: 470 Questions & Answers. Last update: Nov 5, 2026
  • Training Course: 130 Video Lectures
  • Study Guide: 672 Pages
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
$79.97
$59.98

Microsoft DP-300 Practice Test 13

Question 120

Three independently confirmed SQL platform issues require separate evidence checks. Case A: Several engineers need identical read-only data access without individually maintained GRANT statements. Case B: A stored procedure works for its owner but fails on a permission check for an ordinary application user. Case C: A developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. Select exactly THREE distinct diagnostic checks, one for each case.

  1. EXECUTE AS USER or effective permissions test and failed statement context
  2. Connection error identity claim database name and principal mapping
  3. Effective permission queries and role-membership hierarchy
  4. Microsoft Entra group membership mapped to database role membership
  5. sys.database_role_members and effective SELECT privileges on the reporting view
  6. SQL login usage inventory and secret rotation audit trail

Explanation

Correct Answers

A:

EXECUTE AS USER or effective permissions test and failed statement context directly tests the observation that a stored procedure works for its owner but fails on a permission check for an ordinary application user. It helps the team evaluate whether it should reproduce the statement under the calling principal's security context. The check has a boundary: Using the dbo context can hide access weaknesses seen by normal users.

C:

Effective permission queries and role-membership hierarchy directly tests the observation that a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. It helps the team evaluate whether it should inspect explicit GRANT DENY and role inheritance for the exact securable. The check has a boundary: A DENY can override a GRANT and exceptions depend on security context.

D:

Microsoft Entra group membership mapped to database role membership directly tests the observation that several engineers need identical read-only data access without individually maintained GRANT statements. It helps the team evaluate whether it should grant a least-privileged database role to an Entra group principal. The check has a boundary: Directory group membership changes and existing sessions may affect effective access timing.

Incorrect Answers

B:

Connection error identity claim database name and principal mapping is appropriate for the separate condition that a managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope. The actual 3 cases are A: Several engineers need identical read-only data access without individually maintained GRANT statements; B: A stored procedure works for its owner but fails on a permission check for an ordinary application user; C: A developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. This option is not the specific diagnostic evidence for any of those stated cases.

E:

sys.database_role_members and effective SELECT privileges on the reporting view is appropriate for the separate condition that a report service must read one approved view but currently has db_owner membership. The actual 3 cases are A: Several engineers need identical read-only data access without individually maintained GRANT statements; B: A stored procedure works for its owner but fails on a permission check for an ordinary application user; C: A developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. This option is not the specific diagnostic evidence for any of those stated cases.

F:

SQL login usage inventory and secret rotation audit trail is appropriate for the separate condition that a legacy SQL application uses password credentials that need controlled rotation and secure storage. The actual 3 cases are A: Several engineers need identical read-only data access without individually maintained GRANT statements; B: A stored procedure works for its owner but fails on a permission check for an ordinary application user; C: A developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. This option is not the specific diagnostic evidence for any of those stated cases.

Question 121

A production database review needs evidence of this condition: A report service must read one approved view but currently has db_owner membership. Which diagnostic artifact would most directly validate the stated condition?

  1. Connection error identity claim database name and principal mapping
  2. SQL login usage inventory and secret rotation audit trail
  3. Logical-server Microsoft Entra administrator configuration and successful token-based sign-in
  4. sys.database_role_members and effective SELECT privileges on the reporting view

Explanation

Correct Answer

D:

sys.database_role_members and effective SELECT privileges on the reporting view directly tests the observation that a report service must read one approved view but currently has db_owner membership. It helps the team evaluate whether it should replace broad db_owner membership with a narrowly scoped GRANT SELECT on the view. The check has a boundary: View ownership chaining and underlying security context should still be reviewed.

Incorrect Answers

A:

Connection error identity claim database name and principal mapping applies when a managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope, not when a report service must read one approved view but currently has db_owner membership.

B:

SQL login usage inventory and secret rotation audit trail applies when a legacy SQL application uses password credentials that need controlled rotation and secure storage, not when a report service must read one approved view but currently has db_owner membership.

C:

Logical-server Microsoft Entra administrator configuration and successful token-based sign-in applies when an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned, not when a report service must read one approved view but currently has db_owner membership.

Question 122

An operator is collecting proof for the following observation: An Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins. Which diagnostic artifact would most directly validate the stated condition?

  1. sys.database_principals and relevant server-level principal inventory
  2. EXECUTE AS USER or effective permissions test and failed statement context
  3. Logical-server Microsoft Entra administrator configuration and successful token-based sign-in
  4. Microsoft Entra group membership mapped to database role membership

Explanation

Correct Answer

A:

sys.database_principals and relevant server-level principal inventory directly tests the observation that an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins. It helps the team evaluate whether it should manage the contained user in its database rather than assuming a matching master login. The check has a boundary: Database contained users are not portable to every SQL Server instance configuration unchanged.

Incorrect Answers

B:

EXECUTE AS USER or effective permissions test and failed statement context applies when a stored procedure works for its owner but fails on a permission check for an ordinary application user, not when an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins.

C:

Logical-server Microsoft Entra administrator configuration and successful token-based sign-in applies when an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned, not when an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins.

D:

Microsoft Entra group membership mapped to database role membership applies when several engineers need identical read-only data access without individually maintained GRANT statements, not when an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins.

Question 123

During SQL troubleshooting the team must test this hypothesis: A managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope. Which diagnostic artifact would most directly validate the stated condition?

  1. sys.database_role_members and effective SELECT privileges on the reporting view
  2. Logical-server Microsoft Entra administrator configuration and successful token-based sign-in
  3. Connection error identity claim database name and principal mapping
  4. Effective permission queries and role-membership hierarchy

Explanation

Correct Answer

C:

Connection error identity claim database name and principal mapping directly tests the observation that a managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope. It helps the team evaluate whether it should validate the acquired token's resource and mapped database user privileges. The check has a boundary: Adding firewall access does not repair an incorrect database principal mapping.

Incorrect Answers

A:

Sys.database_role_members and effective SELECT privileges on the reporting view applies when a report service must read one approved view but currently has db_owner membership, not when a managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope.

B:

Logical-server Microsoft Entra administrator configuration and successful token-based sign-in applies when an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned, not when a managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope.

D:

Effective permission queries and role-membership hierarchy applies when a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission, not when a managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope.

Question 124

A production database review needs evidence of this condition: A developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. Which diagnostic artifact would most directly validate the stated condition?

  1. Effective permission queries and role-membership hierarchy
  2. Logical-server Microsoft Entra administrator configuration and successful token-based sign-in
  3. SQL login usage inventory and secret rotation audit trail
  4. sys.database_principals plus the authenticated identity and database context

Explanation

Correct Answer

A:

Effective permission queries and role-membership hierarchy directly tests the observation that a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. It helps the team evaluate whether it should inspect explicit GRANT DENY and role inheritance for the exact securable. The check has a boundary: A DENY can override a GRANT and exceptions depend on security context.

Incorrect Answers

B:

Logical-server Microsoft Entra administrator configuration and successful token-based sign-in applies when an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned, not when a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission.

C:

SQL login usage inventory and secret rotation audit trail applies when a legacy SQL application uses password credentials that need controlled rotation and secure storage, not when a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission.

D:

Sys.database_principals plus the authenticated identity and database context applies when a service principal successfully obtains an Entra token but receives a database user-not-found error, not when a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission.

Question 125

An operator is collecting proof for the following observation: A legacy SQL application uses password credentials that need controlled rotation and secure storage. Which diagnostic artifact would most directly validate the stated condition?

  1. Microsoft Entra group membership mapped to database role membership
  2. SQL login usage inventory and secret rotation audit trail
  3. sys.database_principals and relevant server-level principal inventory
  4. Effective permission queries and role-membership hierarchy

Explanation

Correct Answer

B:

SQL login usage inventory and secret rotation audit trail directly tests the observation that a legacy SQL application uses password credentials that need controlled rotation and secure storage. It helps the team evaluate whether it should apply least-privileged SQL credentials with managed secret rotation where required. The check has a boundary: Password-only SQL authentication does not supply Microsoft Entra conditional access.

Incorrect Answers

A:

Microsoft Entra group membership mapped to database role membership applies when several engineers need identical read-only data access without individually maintained GRANT statements, not when a legacy SQL application uses password credentials that need controlled rotation and secure storage.

C:

Sys.database_principals and relevant server-level principal inventory applies when an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins, not when a legacy SQL application uses password credentials that need controlled rotation and secure storage.

D:

Effective permission queries and role-membership hierarchy applies when a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission, not when a legacy SQL application uses password credentials that need controlled rotation and secure storage.

Question 126

During SQL troubleshooting the team must test this hypothesis: A stored procedure works for its owner but fails on a permission check for an ordinary application user. Which diagnostic artifact would most directly validate the stated condition?

  1. sys.database_principals and relevant server-level principal inventory
  2. Logical-server Microsoft Entra administrator configuration and successful token-based sign-in
  3. Microsoft Entra group membership mapped to database role membership
  4. EXECUTE AS USER or effective permissions test and failed statement context

Explanation

Correct Answer

D:

EXECUTE AS USER or effective permissions test and failed statement context directly tests the observation that a stored procedure works for its owner but fails on a permission check for an ordinary application user. It helps the team evaluate whether it should reproduce the statement under the calling principal's security context. The check has a boundary: Using the dbo context can hide access weaknesses seen by normal users.

Incorrect Answers

A:

Sys.database_principals and relevant server-level principal inventory applies when an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins, not when a stored procedure works for its owner but fails on a permission check for an ordinary application user.

B:

Logical-server Microsoft Entra administrator configuration and successful token-based sign-in applies when an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned, not when a stored procedure works for its owner but fails on a permission check for an ordinary application user.

C:

Microsoft Entra group membership mapped to database role membership applies when several engineers need identical read-only data access without individually maintained GRANT statements, not when a stored procedure works for its owner but fails on a permission check for an ordinary application user.

Question 127

The DBA must resolve this concrete requirement: An Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned. Which technical or administrative action most directly addresses this requirement?

  1. Configure an appropriate Microsoft Entra administrator for the Azure SQL resource
  2. Grant a least-privileged database role to an Entra group principal
  3. Replace broad db_owner membership with a narrowly scoped GRANT SELECT on the view
  4. Validate the acquired token's resource and mapped database user privileges

Explanation

Correct Answer

A:

Configure an appropriate Microsoft Entra administrator for the Azure SQL resource directly resolves the reported requirement that an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned. The server has a trusted identity bootstrap path for Entra database principals. The implementation must also respect this constraint: An Entra administrator does not make every directory user a database reader automatically.

Incorrect Answers

B:

Grant a least-privileged database role to an Entra group principal applies when several engineers need identical read-only data access without individually maintained GRANT statements, not when an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned.

C:

Replace broad db_owner membership with a narrowly scoped GRANT SELECT on the view applies when a report service must read one approved view but currently has db_owner membership, not when an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned.

D:

Validate the acquired token's resource and mapped database user privileges applies when a managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope, not when an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned.

Question 128

A migration or configuration change request describes the following problem: A service principal successfully obtains an Entra token but receives a database user-not-found error. Which technical or administrative action most directly addresses this requirement?

  1. Create a suitable contained database user FROM EXTERNAL PROVIDER with required privileges
  2. Inspect explicit GRANT DENY and role inheritance for the exact securable
  3. Reproduce the statement under the calling principal's security context
  4. Replace broad db_owner membership with a narrowly scoped GRANT SELECT on the view

Explanation

Correct Answer

A:

Create a suitable contained database user FROM EXTERNAL PROVIDER with required privileges directly resolves the reported requirement that a service principal successfully obtains an Entra token but receives a database user-not-found error. The Entra identity can be mapped to an authorized database principal. The implementation must also respect this constraint: Authentication alone does not convey table permissions.

Incorrect Answers

B:

Inspect explicit GRANT DENY and role inheritance for the exact securable applies when a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission, not when a service principal successfully obtains an Entra token but receives a database user-not-found error.

C:

Reproduce the statement under the calling principal's security context applies when a stored procedure works for its owner but fails on a permission check for an ordinary application user, not when a service principal successfully obtains an Entra token but receives a database user-not-found error.

D:

Replace broad db_owner membership with a narrowly scoped GRANT SELECT on the view applies when a report service must read one approved view but currently has db_owner membership, not when a service principal successfully obtains an Entra token but receives a database user-not-found error.

Question 129

Two independent Azure SQL administration tickets require separate actions. Case A: Several engineers need identical read-only data access without individually maintained GRANT statements. Case B: A managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope. Select exactly TWO distinct implementation steps, one for each case.

  1. Validate the acquired token's resource and mapped database user privileges
  2. Grant a least-privileged database role to an Entra group principal
  3. Inspect explicit GRANT DENY and role inheritance for the exact securable
  4. Replace broad db_owner membership with a narrowly scoped GRANT SELECT on the view
  5. Configure an appropriate Microsoft Entra administrator for the Azure SQL resource

Explanation

Correct Answers

A:

Validate the acquired token's resource and mapped database user privileges directly resolves the reported requirement that a managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope. The failure is isolated to token audience authentication or authorization. The implementation must also respect this constraint: Adding firewall access does not repair an incorrect database principal mapping.

B:

Grant a least-privileged database role to an Entra group principal directly resolves the reported requirement that several engineers need identical read-only data access without individually maintained GRANT statements. Role-based grants simplify controlled shared access. The implementation must also respect this constraint: Directory group membership changes and existing sessions may affect effective access timing.

Incorrect Answers

C:

Inspect explicit GRANT DENY and role inheritance for the exact securable is appropriate for the separate condition that a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. The actual 2 cases are A: Several engineers need identical read-only data access without individually maintained GRANT statements; B: A managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope. This option is not the specific implementation or corrective step for any of those stated cases.

D:

Replace broad db_owner membership with a narrowly scoped GRANT SELECT on the view is appropriate for the separate condition that a report service must read one approved view but currently has db_owner membership. The actual 2 cases are A: Several engineers need identical read-only data access without individually maintained GRANT statements; B: A managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope. This option is not the specific implementation or corrective step for any of those stated cases.

E:

Configure an appropriate Microsoft Entra administrator for the Azure SQL resource is appropriate for the separate condition that an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned. The actual 2 cases are A: Several engineers need identical read-only data access without individually maintained GRANT statements; B: A managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope. This option is not the specific implementation or corrective step for any of those stated cases.

Question 130

Three independently confirmed SQL platform issues require separate evidence checks. Case A: A report service must read one approved view but currently has db_owner membership. Case B: A developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. Case C: An Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins. Select exactly THREE distinct diagnostic checks, one for each case.

  1. SQL login usage inventory and secret rotation audit trail
  2. Effective permission queries and role-membership hierarchy
  3. sys.database_principals and relevant server-level principal inventory
  4. Logical-server Microsoft Entra administrator configuration and successful token-based sign-in
  5. Connection error identity claim database name and principal mapping
  6. sys.database_role_members and effective SELECT privileges on the reporting view

Explanation

Correct Answers

B:

Effective permission queries and role-membership hierarchy directly tests the observation that a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. It helps the team evaluate whether it should inspect explicit GRANT DENY and role inheritance for the exact securable. The check has a boundary: A DENY can override a GRANT and exceptions depend on security context.

C:

sys.database_principals and relevant server-level principal inventory directly tests the observation that an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins. It helps the team evaluate whether it should manage the contained user in its database rather than assuming a matching master login. The check has a boundary: Database contained users are not portable to every SQL Server instance configuration unchanged.

F:

sys.database_role_members and effective SELECT privileges on the reporting view directly tests the observation that a report service must read one approved view but currently has db_owner membership. It helps the team evaluate whether it should replace broad db_owner membership with a narrowly scoped GRANT SELECT on the view. The check has a boundary: View ownership chaining and underlying security context should still be reviewed.

Incorrect Answers

A:

SQL login usage inventory and secret rotation audit trail is appropriate for the separate condition that a legacy SQL application uses password credentials that need controlled rotation and secure storage. The actual 3 cases are A: A report service must read one approved view but currently has db_owner membership; B: A developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission; C: An Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins. This option is not the specific diagnostic evidence for any of those stated cases.

D:

Logical-server Microsoft Entra administrator configuration and successful token-based sign-in is appropriate for the separate condition that an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned. The actual 3 cases are A: A report service must read one approved view but currently has db_owner membership; B: A developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission; C: An Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins. This option is not the specific diagnostic evidence for any of those stated cases.

E:

Connection error identity claim database name and principal mapping is appropriate for the separate condition that a managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope. The actual 3 cases are A: A report service must read one approved view but currently has db_owner membership; B: A developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission; C: An Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins. This option is not the specific diagnostic evidence for any of those stated cases.

Administering Microsoft Azure SQL Solutions (DP-300) Practice Tests

UP

SPECIAL OFFER: GET 10% OFF

This is ONE TIME OFFER

ExamSnap Discount Offer
Enter Your Email Address to Receive Your 10% Off Discount Code

A confirmation link will be sent to this email address to verify your login. *We value your privacy. We will not rent or sell your email address.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your e-mail address below to get started with our interactive software demo of your free trial.

Free Demo Limits: In the demo version you will be able to access only first 5 questions from exam.