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 14

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.

Question 131

A migration or configuration change request describes the following problem: An Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins. Which technical or administrative action most directly addresses this requirement?

  1. Replace broad db_owner membership with a narrowly scoped GRANT SELECT on the view
  2. Apply least-privileged SQL credentials with managed secret rotation where required
  3. Configure an appropriate Microsoft Entra administrator for the Azure SQL resource
  4. Manage the contained user in its database rather than assuming a matching master login

Explanation

Correct Answer

D:

Manage the contained user in its database rather than assuming a matching master login directly resolves the reported requirement that an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins. Database identity management can occur independently of classic instance login mappings. The implementation must also respect this constraint: Database contained users are not portable to every SQL Server instance configuration unchanged.

Incorrect Answers

A:

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 Database connection uses a contained database user and administrators expect it to appear in server-level logins.

B:

Apply least-privileged SQL credentials with managed secret rotation where required applies when a legacy SQL application uses password credentials that need controlled rotation and secure storage, not when an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins.

C:

Configure an appropriate Microsoft Entra administrator for the Azure SQL resource 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.

Question 132

Before implementation the team records this technical condition: A managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope. Which technical or administrative action most directly addresses this requirement?

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

Explanation

Correct Answer

D:

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.

Incorrect Answers

A:

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 managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope.

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 managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope.

C:

Configure an appropriate Microsoft Entra administrator for the Azure SQL resource 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.

Question 133

The DBA must resolve this concrete requirement: A developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. Which technical or administrative action most directly addresses this requirement?

  1. Replace broad db_owner membership with a narrowly scoped GRANT SELECT on the view
  2. Inspect explicit GRANT DENY and role inheritance for the exact securable
  3. Reproduce the statement under the calling principal's security context
  4. Manage the contained user in its database rather than assuming a matching master login

Explanation

Correct Answer

B:

Inspect explicit GRANT DENY and role inheritance for the exact securable directly resolves the reported requirement that a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. Conflicting privileges can be explained without guessing from one role name. The implementation must also respect this constraint: A DENY can override a GRANT and exceptions depend on security context.

Incorrect Answers

A:

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 developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission.

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 developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission.

D:

Manage the contained user in its database rather than assuming a matching master login 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 developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission.

Question 134

A migration or configuration change request describes the following problem: A legacy SQL application uses password credentials that need controlled rotation and secure storage. Which technical or administrative action most directly addresses this requirement?

  1. Manage the contained user in its database rather than assuming a matching master login
  2. Validate the acquired token's resource and mapped database user privileges
  3. Reproduce the statement under the calling principal's security context
  4. Apply least-privileged SQL credentials with managed secret rotation where required

Explanation

Correct Answer

D:

Apply least-privileged SQL credentials with managed secret rotation where required directly resolves the reported requirement that a legacy SQL application uses password credentials that need controlled rotation and secure storage. Credential exposure risk can be reduced while the legacy application remains supported. The implementation must also respect this constraint: Password-only SQL authentication does not supply Microsoft Entra conditional access.

Incorrect Answers

A:

Manage the contained user in its database rather than assuming a matching master login 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.

B:

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 a legacy SQL application uses password credentials that need controlled rotation and secure storage.

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 legacy SQL application uses password credentials that need controlled rotation and secure storage.

Question 135

Before implementation the team records this technical condition: A stored procedure works for its owner but fails on a permission check for an ordinary application user. Which technical or administrative action most directly addresses this requirement?

  1. Apply least-privileged SQL credentials with managed secret rotation where required
  2. Validate the acquired token's resource and mapped database user privileges
  3. Create a suitable contained database user FROM EXTERNAL PROVIDER with required privileges
  4. Reproduce the statement under the calling principal's security context

Explanation

Correct Answer

D:

Reproduce the statement under the calling principal's security context directly resolves the reported requirement that a stored procedure works for its owner but fails on a permission check for an ordinary application user. The DBA isolates object permission differences behind the failure. The implementation must also respect this constraint: Using the dbo context can hide access weaknesses seen by normal users.

Incorrect Answers

A:

Apply least-privileged SQL credentials with managed secret rotation where required applies when a legacy SQL application uses password credentials that need controlled rotation and secure storage, not when a stored procedure works for its owner but fails on a permission check for an ordinary application user.

B:

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 a stored procedure works for its owner but fails on a permission check for an ordinary application user.

C:

Create a suitable contained database user FROM EXTERNAL PROVIDER with required privileges applies when a service principal successfully obtains an Entra token but receives a database user-not-found error, not when a stored procedure works for its owner but fails on a permission check for an ordinary application user.

Question 136

The team needs to anticipate the behavior of a correct solution for: An Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned. What operational outcome follows from implementing the appropriate solution?

  1. Role-based grants simplify controlled shared access
  2. The server has a trusted identity bootstrap path for Entra database principals
  3. The DBA isolates object permission differences behind the failure
  4. Conflicting privileges can be explained without guessing from one role name

Explanation

Correct Answer

B:

The server has a trusted identity bootstrap path for Entra database principals is the expected technical effect when the administrator chooses the relevant approach for an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned. The needed action is to configure an appropriate Microsoft Entra administrator for the Azure SQL resource.

Incorrect Answers

A:

Role-based grants simplify controlled shared access 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:

The DBA isolates object permission differences behind the failure 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 logical server requires central identity administration before Microsoft Entra database accounts can be provisioned.

D:

Conflicting privileges can be explained without guessing from one role name applies when a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission, not when an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned.

Question 137

An operational planning meeting reviews this deployment condition: A service principal successfully obtains an Entra token but receives a database user-not-found error. What operational outcome follows from implementing the appropriate solution?

  1. The Entra identity can be mapped to an authorized database principal
  2. Role-based grants simplify controlled shared access
  3. Conflicting privileges can be explained without guessing from one role name
  4. The DBA isolates object permission differences behind the failure

Explanation

Correct Answer

A:

The Entra identity can be mapped to an authorized database principal is the expected technical effect when the administrator chooses the relevant approach for a service principal successfully obtains an Entra token but receives a database user-not-found error. The needed action is to create a suitable contained database user FROM EXTERNAL PROVIDER with required privileges.

Incorrect Answers

B:

Role-based grants simplify controlled shared access applies when several engineers need identical read-only data access without individually maintained GRANT statements, not when a service principal successfully obtains an Entra token but receives a database user-not-found error.

C:

Conflicting privileges can be explained without guessing from one role name 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.

D:

The DBA isolates object permission differences behind the failure 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.

Question 138

A post-change impact assessment considers the requirement that: Several engineers need identical read-only data access without individually maintained GRANT statements. What operational outcome follows from implementing the appropriate solution?

  1. Database identity management can occur independently of classic instance login mappings
  2. Role-based grants simplify controlled shared access
  3. The failure is isolated to token audience authentication or authorization
  4. Credential exposure risk can be reduced while the legacy application remains supported

Explanation

Correct Answer

B:

Role-based grants simplify controlled shared access is the expected technical effect when the administrator chooses the relevant approach for several engineers need identical read-only data access without individually maintained GRANT statements. The needed action is to grant a least-privileged database role to an Entra group principal.

Incorrect Answers

A:

Database identity management can occur independently of classic instance login mappings applies when an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins, not when several engineers need identical read-only data access without individually maintained GRANT statements.

C:

The failure is isolated to token audience authentication or authorization applies when a managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope, not when several engineers need identical read-only data access without individually maintained GRANT statements.

D:

Credential exposure risk can be reduced while the legacy application remains supported applies when a legacy SQL application uses password credentials that need controlled rotation and secure storage, not when several engineers need identical read-only data access without individually maintained GRANT statements.

Question 139

Two independent Azure SQL administration tickets require separate actions. Case A: A report service must read one approved view but currently has db_owner membership. Case B: An Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned. Select exactly TWO distinct implementation steps, one for each case.

  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. Manage the contained user in its database rather than assuming a matching master login
  4. Validate the acquired token's resource and mapped database user privileges
  5. Replace broad db_owner membership with a narrowly scoped GRANT SELECT on the view

Explanation

Correct Answers

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.

E:

Replace broad db_owner membership with a narrowly scoped GRANT SELECT on the view directly resolves the reported requirement that a report service must read one approved view but currently has db_owner membership. The report can read intended data without unrelated schema control. The implementation must also respect this constraint: View ownership chaining and underlying security context should still be reviewed.

Incorrect Answers

B:

Grant a least-privileged database role to an Entra group principal is appropriate for the separate condition that several engineers need identical read-only data access without individually maintained GRANT statements. The actual 2 cases are A: A report service must read one approved view but currently has db_owner membership; B: An Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned. This option is not the specific implementation or corrective step for any of those stated cases.

C:

Manage the contained user in its database rather than assuming a matching master login is appropriate for the separate condition that an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins. The actual 2 cases are A: A report service must read one approved view but currently has db_owner membership; B: An Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned. This option is not the specific implementation or corrective step for any of those stated cases.

D:

Validate the acquired token's resource and mapped database user privileges 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 2 cases are A: A report service must read one approved view but currently has db_owner membership; B: An Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned. This option is not the specific implementation or corrective step for any of those stated cases.

Question 140

Three independently confirmed SQL platform issues require separate evidence checks. Case A: An Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins. Case B: A managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope. Case C: Several engineers need identical read-only data access without individually maintained GRANT statements. Select exactly THREE distinct diagnostic checks, one for each case.

  1. Connection error identity claim database name and principal mapping
  2. EXECUTE AS USER or effective permissions test and failed statement context
  3. SQL login usage inventory and secret rotation audit trail
  4. Microsoft Entra group membership mapped to database role membership
  5. Logical-server Microsoft Entra administrator configuration and successful token-based sign-in
  6. sys.database_principals and relevant server-level principal inventory

Explanation

Correct Answers

A:

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.

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.

F:

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 is appropriate for the separate condition that a stored procedure works for its owner but fails on a permission check for an ordinary application user. The actual 3 cases are A: An Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins; B: A managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope; C: Several engineers need identical read-only data access without individually maintained GRANT statements. This option is not the specific diagnostic evidence for any of those stated cases.

C:

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: An Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins; B: A managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope; C: Several engineers need identical read-only data access without individually maintained GRANT statements. This option is not the specific diagnostic evidence for any of those stated cases.

E:

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: An Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins; B: A managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope; C: Several engineers need identical read-only data access without individually maintained GRANT statements. 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.