mcAfee Secure Website
23

Microsoft DP-300 Bundle

Exam Code: DP-300

Exam Name Administering Microsoft Azure SQL Solutions

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Azure Database Administrator Associate

DP-300 Training Materials $44.99

Reliable & Actual Study Materials for DP-300 Exam Success

The Latest DP-300 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    DP-300 Questions & Answers

    470 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • 25
    DP-300 Video Course

    DP-300 Training Course

    130 Video Lectures

    Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.

  • exam =30
    Study Guide

    DP-300 Study Guide

    672 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

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

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Microsoft Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    470 Questions

    $124.99
    exam =35
  • exam =37
    DP-300 Video Course

    Training Course

    130 Video Lectures

    $39.99
  • exam =36
    Study Guide

    Study Guide

    672 PDF Pages

    $29.99

Microsoft DP-300 Practice Test 18

Question 170

An Azure SQL operations team investigates: A database team must review which directory account has authority to create Azure SQL Entra users. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. Configure a supported Microsoft Entra administrator and tenant identity prerequisites before enabling Entra-based SQL principals and sign-in.
  2. Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication.
  3. An authorized Entra identity can authenticate and create the intended supported contained database principal without a shared SQL password.
  4. Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.
  5. An approved SQL client validates the intended server certificate and rejects an untrusted endpoint during a controlled test.

Explanation

Correct Answers

A:

The reported Azure SQL or SQL Server condition is: A database team must review which directory account has authority to create Azure SQL Entra users. The specific supported administrative response is: Configure a supported Microsoft Entra administrator and tenant identity prerequisites before enabling Entra-based SQL principals and sign-in. The technical risk is: Without correct tenant mapping and directory administration, intended Entra accounts cannot be provisioned for database access. Confirm the correction with: An authorized Entra identity can authenticate and create the intended supported contained database principal without a shared SQL password.

C:

The acceptance evidence for this incident (A database team must review which directory account has authority to create Azure SQL Entra users.) is: An authorized Entra identity can authenticate and create the intended supported contained database principal without a shared SQL password. It directly tests whether the remediation (Configure a supported Microsoft Entra administrator and tenant identity prerequisites before enabling Entra-based SQL principals and sign-in.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

B:

Diagnosing login and token failures (2.1) addresses another technical failure: Treating every database error as a firewall block can conceal authentication and access-control faults. This choice can be useful for that problem, but it does not establish the Microsoft entra administrator for azure SQL (2.1) control being assessed here.

D:

Row-level security with session predicates (2.3) addresses another technical failure: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. The required paired action and test concerns Microsoft entra administrator for azure SQL (2.1); a passing result for this alternative could leave that requirement unresolved.

E:

SQL encrypted connections and TLS verification (2.2) would demonstrate or implement: An approved SQL client validates the intended server certificate and rejects an untrusted endpoint during a controlled test. The paired-answer requirement concerns Microsoft entra administrator for azure SQL (2.1); this alternative does not provide the matching intervention and separate acceptance evidence.

Question 171

An Azure database administrator observes: An application developer can sign in to Azure but receives a database principal not found error. Which action best addresses the specific technical requirement?

  1. Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.
  2. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.
  3. Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.
  4. Use supported dynamic data masking for low-privilege query-result obfuscation while enforcing true authorization separately.

Explanation

Correct Answer

A:

The reported Azure SQL or SQL Server condition is: An application developer can sign in to Azure but receives a database principal not found error. The specific supported administrative response is: Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions. The technical risk is: An Entra identity alone does not automatically confer SQL database authorization to the data it needs. Confirm the correction with: The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.

Incorrect Answers

B:

Managed identity database access (2.1) addresses another technical failure: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely. This choice can be useful for that problem, but it does not establish the Contained database users from entra identities (2.1) control being assessed here.

C:

SQL ledger tamper-evidence (2.3) addresses another technical failure: Audit logs alone or editable records cannot guarantee detection of all later data history alterations. This case instead tests Contained database users from entra identities (2.1); the choice measures or changes another part of the system.

D:

Dynamic data masking limitations (2.3) addresses another technical failure: Dynamic data masking is not encryption or a complete barrier against inference by a user able to query data. The required corrective action concerns Contained database users from entra identities (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 172

During post-change validation, the team reports: An application developer can sign in to Azure but receives a database principal not found error. Which observation best demonstrates that the appropriate correction worked?

  1. Authorized privileged users see expected values and restricted users receive masked output under tested permissions.
  2. The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.
  3. An external digest and ledger verification detect a controlled unauthorized alteration of historical records.
  4. The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.

Explanation

Correct Answer

D:

The acceptance evidence for this incident (An application developer can sign in to Azure but receives a database principal not found error.) is: The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions. It directly tests whether the remediation (Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

Dynamic data masking limitations (2.3) would demonstrate or implement: Authorized privileged users see expected values and restricted users receive masked output under tested permissions. The case states: An application developer can sign in to Azure but receives a database principal not found error. The most direct evidence is: The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.

B:

Managed identity database access (2.1) would demonstrate or implement: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source. This choice can be useful for that problem, but it does not establish the Contained database users from entra identities (2.1) control being assessed here.

C:

SQL ledger tamper-evidence (2.3) would demonstrate or implement: An external digest and ledger verification detect a controlled unauthorized alteration of historical records. This case instead tests Contained database users from entra identities (2.1); the choice measures or changes another part of the system.

Question 173

An Azure database administrator observes: A reporting Entra security group needs read access to one database without server-wide privileges. Which action best addresses the specific technical requirement?

  1. Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.
  2. Use supported dynamic data masking for low-privilege query-result obfuscation while enforcing true authorization separately.
  3. Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.
  4. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.

Explanation

Correct Answer

A:

The reported Azure SQL or SQL Server condition is: A reporting Entra security group needs read access to one database without server-wide privileges. The specific supported administrative response is: Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions. The technical risk is: An Entra identity alone does not automatically confer SQL database authorization to the data it needs. Confirm the correction with: The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.

Incorrect Answers

B:

Dynamic data masking limitations (2.3) addresses another technical failure: Dynamic data masking is not encryption or a complete barrier against inference by a user able to query data. This choice can be useful for that problem, but it does not establish the Contained database users from entra identities (2.1) control being assessed here.

C:

SQL ledger tamper-evidence (2.3) addresses another technical failure: Audit logs alone or editable records cannot guarantee detection of all later data history alterations. This case instead tests Contained database users from entra identities (2.1); the choice measures or changes another part of the system.

D:

Managed identity database access (2.1) addresses another technical failure: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely. The required corrective action concerns Contained database users from entra identities (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 174

In a database operations review, a team encounters: A reporting Entra security group needs read access to one database without server-wide privileges. Which failure or exposure is most directly relevant?

  1. An Entra identity alone does not automatically confer SQL database authorization to the data it needs.
  2. Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely.
  3. Audit logs alone or editable records cannot guarantee detection of all later data history alterations.
  4. Dynamic data masking is not encryption or a complete barrier against inference by a user able to query data.

Explanation

Correct Answer

A:

The incident (A reporting Entra security group needs read access to one database without server-wide privileges.) most directly exposes: An Entra identity alone does not automatically confer SQL database authorization to the data it needs. The resulting safe technical response is: Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions. Its verification is: The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.

Incorrect Answers

B:

Managed identity database access (2.1) would demonstrate or implement: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely. This choice can be useful for that problem, but it does not establish the Contained database users from entra identities (2.1) control being assessed here.

C:

SQL ledger tamper-evidence (2.3) would demonstrate or implement: Audit logs alone or editable records cannot guarantee detection of all later data history alterations. This case instead tests Contained database users from entra identities (2.1); the choice measures or changes another part of the system.

D:

Dynamic data masking limitations (2.3) would demonstrate or implement: Dynamic data masking is not encryption or a complete barrier against inference by a user able to query data. The required risk concerns Contained database users from entra identities (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 175

An Azure database administrator observes: An identity changes its SQL login context and unexpectedly has no contained user in the target database. Which action best addresses the specific technical requirement?

  1. Use supported dynamic data masking for low-privilege query-result obfuscation while enforcing true authorization separately.
  2. Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.
  3. Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.
  4. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.

Explanation

Correct Answer

C:

The reported Azure SQL or SQL Server condition is: An identity changes its SQL login context and unexpectedly has no contained user in the target database. The specific supported administrative response is: Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions. The technical risk is: An Entra identity alone does not automatically confer SQL database authorization to the data it needs. Confirm the correction with: The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.

Incorrect Answers

A:

Dynamic data masking limitations (2.3) addresses another technical failure: Dynamic data masking is not encryption or a complete barrier against inference by a user able to query data. The case states: An identity changes its SQL login context and unexpectedly has no contained user in the target database. The most direct corrective action is: Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.

B:

SQL ledger tamper-evidence (2.3) addresses another technical failure: Audit logs alone or editable records cannot guarantee detection of all later data history alterations. This choice can be useful for that problem, but it does not establish the Contained database users from entra identities (2.1) control being assessed here.

D:

Managed identity database access (2.1) addresses another technical failure: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely. The required corrective action concerns Contained database users from entra identities (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 176

During post-change validation, the team reports: An identity changes its SQL login context and unexpectedly has no contained user in the target database. Which observation best demonstrates that the appropriate correction worked?

  1. The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.
  2. An external digest and ledger verification detect a controlled unauthorized alteration of historical records.
  3. Authorized privileged users see expected values and restricted users receive masked output under tested permissions.
  4. The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.

Explanation

Correct Answer

D:

The acceptance evidence for this incident (An identity changes its SQL login context and unexpectedly has no contained user in the target database.) is: The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions. It directly tests whether the remediation (Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

Managed identity database access (2.1) would demonstrate or implement: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source. The case states: An identity changes its SQL login context and unexpectedly has no contained user in the target database. The most direct evidence is: The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.

B:

SQL ledger tamper-evidence (2.3) would demonstrate or implement: An external digest and ledger verification detect a controlled unauthorized alteration of historical records. This choice can be useful for that problem, but it does not establish the Contained database users from entra identities (2.1) control being assessed here.

C:

Dynamic data masking limitations (2.3) would demonstrate or implement: Authorized privileged users see expected values and restricted users receive masked output under tested permissions. This case instead tests Contained database users from entra identities (2.1); the choice measures or changes another part of the system.

Question 177

An Azure database administrator observes: A new analytics app receives an Entra access token but cannot select from authorized tables. Which action best addresses the specific technical requirement?

  1. Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.
  2. Use supported dynamic data masking for low-privilege query-result obfuscation while enforcing true authorization separately.
  3. Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.
  4. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.

Explanation

Correct Answer

A:

The reported Azure SQL or SQL Server condition is: A new analytics app receives an Entra access token but cannot select from authorized tables. The specific supported administrative response is: Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions. The technical risk is: An Entra identity alone does not automatically confer SQL database authorization to the data it needs. Confirm the correction with: The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.

Incorrect Answers

B:

Dynamic data masking limitations (2.3) addresses another technical failure: Dynamic data masking is not encryption or a complete barrier against inference by a user able to query data. This choice can be useful for that problem, but it does not establish the Contained database users from entra identities (2.1) control being assessed here.

C:

SQL ledger tamper-evidence (2.3) addresses another technical failure: Audit logs alone or editable records cannot guarantee detection of all later data history alterations. This case instead tests Contained database users from entra identities (2.1); the choice measures or changes another part of the system.

D:

Managed identity database access (2.1) addresses another technical failure: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely. The required corrective action concerns Contained database users from entra identities (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 178

In a database operations review, a team encounters: A new analytics app receives an Entra access token but cannot select from authorized tables. Which failure or exposure is most directly relevant?

  1. An Entra identity alone does not automatically confer SQL database authorization to the data it needs.
  2. Dynamic data masking is not encryption or a complete barrier against inference by a user able to query data.
  3. Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely.
  4. Audit logs alone or editable records cannot guarantee detection of all later data history alterations.

Explanation

Correct Answer

A:

The incident (A new analytics app receives an Entra access token but cannot select from authorized tables.) most directly exposes: An Entra identity alone does not automatically confer SQL database authorization to the data it needs. The resulting safe technical response is: Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions. Its verification is: The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.

Incorrect Answers

B:

Dynamic data masking limitations (2.3) would demonstrate or implement: Dynamic data masking is not encryption or a complete barrier against inference by a user able to query data. This choice can be useful for that problem, but it does not establish the Contained database users from entra identities (2.1) control being assessed here.

C:

Managed identity database access (2.1) would demonstrate or implement: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely. This case instead tests Contained database users from entra identities (2.1); the choice measures or changes another part of the system.

D:

SQL ledger tamper-evidence (2.3) would demonstrate or implement: Audit logs alone or editable records cannot guarantee detection of all later data history alterations. The required risk concerns Contained database users from entra identities (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 179

An Azure database administrator observes: A cloud DBA wants to grant one external group database role membership rather than maintain individual SQL passwords. Which action best addresses the specific technical requirement?

  1. Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.
  2. Use supported dynamic data masking for low-privilege query-result obfuscation while enforcing true authorization separately.
  3. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.
  4. Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.

Explanation

Correct Answer

A:

The reported Azure SQL or SQL Server condition is: A cloud DBA wants to grant one external group database role membership rather than maintain individual SQL passwords. The specific supported administrative response is: Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions. The technical risk is: An Entra identity alone does not automatically confer SQL database authorization to the data it needs. Confirm the correction with: The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.

Incorrect Answers

B:

Dynamic data masking limitations (2.3) addresses another technical failure: Dynamic data masking is not encryption or a complete barrier against inference by a user able to query data. This choice can be useful for that problem, but it does not establish the Contained database users from entra identities (2.1) control being assessed here.

C:

Managed identity database access (2.1) addresses another technical failure: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely. This case instead tests Contained database users from entra identities (2.1); the choice measures or changes another part of the system.

D:

SQL ledger tamper-evidence (2.3) addresses another technical failure: Audit logs alone or editable records cannot guarantee detection of all later data history alterations. The required corrective action concerns Contained database users from entra identities (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 180

An Azure SQL operations team investigates: A cloud DBA wants to grant one external group database role membership rather than maintain individual SQL passwords. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. An external digest and ledger verification detect a controlled unauthorized alteration of historical records.
  2. The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.
  3. Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.
  4. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.
  5. Use supported dynamic data masking for low-privilege query-result obfuscation while enforcing true authorization separately.

Explanation

Correct Answers

B:

The acceptance evidence for this incident (A cloud DBA wants to grant one external group database role membership rather than maintain individual SQL passwords.) is: The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions. It directly tests whether the remediation (Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.) solves the specified issue, instead of proving an unrelated database control works.

C:

The reported Azure SQL or SQL Server condition is: A cloud DBA wants to grant one external group database role membership rather than maintain individual SQL passwords. The specific supported administrative response is: Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions. The technical risk is: An Entra identity alone does not automatically confer SQL database authorization to the data it needs. Confirm the correction with: The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.

Incorrect Answers

A:

SQL ledger tamper-evidence (2.3) would demonstrate or implement: An external digest and ledger verification detect a controlled unauthorized alteration of historical records. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.

D:

Managed identity database access (2.1) addresses another technical failure: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely. The required paired action and test concerns Contained database users from entra identities (2.1); a passing result for this alternative could leave that requirement unresolved.

E:

Dynamic data masking limitations (2.3) addresses another technical failure: Dynamic data masking is not encryption or a complete barrier against inference by a user able to query data. The paired-answer requirement concerns Contained database users from entra identities (2.1); this alternative does not provide the matching intervention and separate acceptance evidence.