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 21

Question 200

An Azure SQL operations team investigates: An administrator tries to use an unsupported server-host SQL login management pattern for Azure SQL single database. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. Approved users authenticate with expected policies while disabled credentials fail and access is logged.
  2. Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication.
  3. Maintain SQL login configuration and password policy appropriately on SQL Server installations that support SQL authentication and coordinate with directory alternatives.
  4. Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.
  5. Encryption state and database availability checks confirm files are encrypted while ordinary authorized queries continue.

Explanation

Correct Answers

A:

The acceptance evidence for this incident (An administrator tries to use an unsupported server-host SQL login management pattern for Azure SQL single database.) is: Approved users authenticate with expected policies while disabled credentials fail and access is logged. It directly tests whether the remediation (Maintain SQL login configuration and password policy appropriately on SQL Server installations that support SQL authentication and coordinate with directory alternatives.) solves the specified issue, instead of proving an unrelated database control works.

C:

The reported Azure SQL or SQL Server condition is: An administrator tries to use an unsupported server-host SQL login management pattern for Azure SQL single database. The specific supported administrative response is: Maintain SQL login configuration and password policy appropriately on SQL Server installations that support SQL authentication and coordinate with directory alternatives. The technical risk is: Poorly governed shared SQL logins are hard to rotate and can bypass centralized identity lifecycle management. Confirm the correction with: Approved users authenticate with expected policies while disabled credentials fail and access is logged.

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 SQL authentication management on SQL server vms (2.1) control being assessed here.

D:

Sensitive data classification and discovery (2.3) addresses another technical failure: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. The required paired action and test concerns SQL authentication management on SQL server vms (2.1); a passing result for this alternative could leave that requirement unresolved.

E:

Transparent data encryption at rest (2.2) would demonstrate or implement: Encryption state and database availability checks confirm files are encrypted while ordinary authorized queries continue. The paired-answer requirement concerns SQL authentication management on SQL server vms (2.1); this alternative does not provide the matching intervention and separate acceptance evidence.

Question 201

An Azure database administrator observes: An Azure App Service currently stores a SQL password in its public deployment configuration. Which action best addresses the specific technical requirement?

  1. Configure a supported Microsoft Entra administrator and tenant identity prerequisites before enabling Entra-based SQL principals and sign-in.
  2. Require supported TLS encryption, valid certificates and client hostname validation for database network connections.
  3. Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.
  4. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.

Explanation

Correct Answer

D:

The reported Azure SQL or SQL Server condition is: An Azure App Service currently stores a SQL password in its public deployment configuration. The specific supported administrative response is: Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions. The technical risk is: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely. Confirm the correction with: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.

Incorrect Answers

A:

Microsoft entra administrator for azure SQL (2.1) addresses another technical failure: Without correct tenant mapping and directory administration, intended Entra accounts cannot be provisioned for database access. The case states: An Azure App Service currently stores a SQL password in its public deployment configuration. The most direct corrective action is: Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.

B:

SQL encrypted connections and TLS verification (2.2) addresses another technical failure: Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation. This choice can be useful for that problem, but it does not establish the Managed identity database access (2.1) control being assessed here.

C:

Sensitive data classification and discovery (2.3) addresses another technical failure: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. This case instead tests Managed identity database access (2.1); the choice measures or changes another part of the system.

Question 202

During post-change validation, the team reports: An Azure App Service currently stores a SQL password in its public deployment configuration. Which observation best demonstrates that the appropriate correction worked?

  1. An approved SQL client validates the intended server certificate and rejects an untrusted endpoint during a controlled test.
  2. The classification inventory identifies sensitive columns and its labels match approved data handling requirements.
  3. An authorized Entra identity can authenticate and create the intended supported contained database principal without a shared SQL password.
  4. The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.

Explanation

Correct Answer

D:

The acceptance evidence for this incident (An Azure App Service currently stores a SQL password in its public deployment configuration.) is: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source. It directly tests whether the remediation (Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

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 case states: An Azure App Service currently stores a SQL password in its public deployment configuration. The most direct evidence is: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.

B:

Sensitive data classification and discovery (2.3) would demonstrate or implement: The classification inventory identifies sensitive columns and its labels match approved data handling requirements. This choice can be useful for that problem, but it does not establish the Managed identity database access (2.1) control being assessed here.

C:

Microsoft entra administrator for azure SQL (2.1) would demonstrate or implement: An authorized Entra identity can authenticate and create the intended supported contained database principal without a shared SQL password. This case instead tests Managed identity database access (2.1); the choice measures or changes another part of the system.

Question 203

An Azure database administrator observes: An Azure Function needs database access without storing an Entra application client secret. Which action best addresses the specific technical requirement?

  1. Require supported TLS encryption, valid certificates and client hostname validation for database network connections.
  2. Configure a supported Microsoft Entra administrator and tenant identity prerequisites before enabling Entra-based SQL principals and sign-in.
  3. Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.
  4. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.

Explanation

Correct Answer

D:

The reported Azure SQL or SQL Server condition is: An Azure Function needs database access without storing an Entra application client secret. The specific supported administrative response is: Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions. The technical risk is: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely. Confirm the correction with: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.

Incorrect Answers

A:

SQL encrypted connections and TLS verification (2.2) addresses another technical failure: Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation. The case states: An Azure Function needs database access without storing an Entra application client secret. The most direct corrective action is: Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.

B:

Microsoft entra administrator for azure SQL (2.1) addresses another technical failure: Without correct tenant mapping and directory administration, intended Entra accounts cannot be provisioned for database access. This choice can be useful for that problem, but it does not establish the Managed identity database access (2.1) control being assessed here.

C:

Sensitive data classification and discovery (2.3) addresses another technical failure: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. This case instead tests Managed identity database access (2.1); the choice measures or changes another part of the system.

Question 204

In a database operations review, a team encounters: An Azure Function needs database access without storing an Entra application client secret. Which failure or exposure is most directly relevant?

  1. Without correct tenant mapping and directory administration, intended Entra accounts cannot be provisioned for database access.
  2. Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions.
  3. Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely.
  4. Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation.

Explanation

Correct Answer

C:

The incident (An Azure Function needs database access without storing an Entra application client secret.) most directly exposes: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely. The resulting safe technical response is: Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions. Its verification is: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.

Incorrect Answers

A:

Microsoft entra administrator for azure SQL (2.1) would demonstrate or implement: Without correct tenant mapping and directory administration, intended Entra accounts cannot be provisioned for database access. The case states: An Azure Function needs database access without storing an Entra application client secret. The most direct risk is: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely.

B:

Sensitive data classification and discovery (2.3) would demonstrate or implement: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. This choice can be useful for that problem, but it does not establish the Managed identity database access (2.1) control being assessed here.

D:

SQL encrypted connections and TLS verification (2.2) would demonstrate or implement: Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation. The required risk concerns Managed identity database access (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 205

An Azure database administrator observes: A developer creates a managed identity but forgets to create the matching contained database user. Which action best addresses the specific technical requirement?

  1. Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.
  2. Configure a supported Microsoft Entra administrator and tenant identity prerequisites before enabling Entra-based SQL principals and sign-in.
  3. Require supported TLS encryption, valid certificates and client hostname validation for database network connections.
  4. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.

Explanation

Correct Answer

D:

The reported Azure SQL or SQL Server condition is: A developer creates a managed identity but forgets to create the matching contained database user. The specific supported administrative response is: Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions. The technical risk is: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely. Confirm the correction with: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.

Incorrect Answers

A:

Sensitive data classification and discovery (2.3) addresses another technical failure: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. The case states: A developer creates a managed identity but forgets to create the matching contained database user. The most direct corrective action is: Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.

B:

Microsoft entra administrator for azure SQL (2.1) addresses another technical failure: Without correct tenant mapping and directory administration, intended Entra accounts cannot be provisioned for database access. This choice can be useful for that problem, but it does not establish the Managed identity database access (2.1) control being assessed here.

C:

SQL encrypted connections and TLS verification (2.2) addresses another technical failure: Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation. This case instead tests Managed identity database access (2.1); the choice measures or changes another part of the system.

Question 206

During post-change validation, the team reports: A developer creates a managed identity but forgets to create the matching contained database user. Which observation best demonstrates that the appropriate correction worked?

  1. An approved SQL client validates the intended server certificate and rejects an untrusted endpoint during a controlled test.
  2. The classification inventory identifies sensitive columns and its labels match approved data handling requirements.
  3. The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.
  4. An authorized Entra identity can authenticate and create the intended supported contained database principal without a shared SQL password.

Explanation

Correct Answer

C:

The acceptance evidence for this incident (A developer creates a managed identity but forgets to create the matching contained database user.) is: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source. It directly tests whether the remediation (Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

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 case states: A developer creates a managed identity but forgets to create the matching contained database user. The most direct evidence is: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.

B:

Sensitive data classification and discovery (2.3) would demonstrate or implement: The classification inventory identifies sensitive columns and its labels match approved data handling requirements. This choice can be useful for that problem, but it does not establish the Managed identity database access (2.1) control being assessed here.

D:

Microsoft entra administrator for azure SQL (2.1) would demonstrate or implement: An authorized Entra identity can authenticate and create the intended supported contained database principal without a shared SQL password. The required evidence concerns Managed identity database access (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 207

An Azure database administrator observes: An application token authenticates yet cannot insert because its database permissions are insufficient. Which action best addresses the specific technical requirement?

  1. Configure a supported Microsoft Entra administrator and tenant identity prerequisites before enabling Entra-based SQL principals and sign-in.
  2. Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.
  3. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.
  4. Require supported TLS encryption, valid certificates and client hostname validation for database network connections.

Explanation

Correct Answer

C:

The reported Azure SQL or SQL Server condition is: An application token authenticates yet cannot insert because its database permissions are insufficient. The specific supported administrative response is: Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions. The technical risk is: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely. Confirm the correction with: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.

Incorrect Answers

A:

Microsoft entra administrator for azure SQL (2.1) addresses another technical failure: Without correct tenant mapping and directory administration, intended Entra accounts cannot be provisioned for database access. The case states: An application token authenticates yet cannot insert because its database permissions are insufficient. The most direct corrective action is: Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.

B:

Sensitive data classification and discovery (2.3) addresses another technical failure: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. This choice can be useful for that problem, but it does not establish the Managed identity database access (2.1) control being assessed here.

D:

SQL encrypted connections and TLS verification (2.2) addresses another technical failure: Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation. The required corrective action concerns Managed identity database access (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 208

In a database operations review, a team encounters: An application token authenticates yet cannot insert because its database permissions are insufficient. Which failure or exposure is most directly relevant?

  1. Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions.
  2. Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely.
  3. Without correct tenant mapping and directory administration, intended Entra accounts cannot be provisioned for database access.
  4. Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation.

Explanation

Correct Answer

B:

The incident (An application token authenticates yet cannot insert because its database permissions are insufficient.) most directly exposes: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely. The resulting safe technical response is: Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions. Its verification is: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.

Incorrect Answers

A:

Sensitive data classification and discovery (2.3) would demonstrate or implement: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. The case states: An application token authenticates yet cannot insert because its database permissions are insufficient. The most direct risk is: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely.

C:

Microsoft entra administrator for azure SQL (2.1) would demonstrate or implement: Without correct tenant mapping and directory administration, intended Entra accounts cannot be provisioned for database access. This case instead tests Managed identity database access (2.1); the choice measures or changes another part of the system.

D:

SQL encrypted connections and TLS verification (2.2) would demonstrate or implement: Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation. The required risk concerns Managed identity database access (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 209

An Azure database administrator observes: A platform team rotates a shared SQL credential and inadvertently breaks dozens of instances that could use managed identities. Which action best addresses the specific technical requirement?

  1. Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.
  2. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.
  3. Require supported TLS encryption, valid certificates and client hostname validation for database network connections.
  4. Configure a supported Microsoft Entra administrator and tenant identity prerequisites before enabling Entra-based SQL principals and sign-in.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: A platform team rotates a shared SQL credential and inadvertently breaks dozens of instances that could use managed identities. The specific supported administrative response is: Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions. The technical risk is: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely. Confirm the correction with: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.

Incorrect Answers

A:

Sensitive data classification and discovery (2.3) addresses another technical failure: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. The case states: A platform team rotates a shared SQL credential and inadvertently breaks dozens of instances that could use managed identities. The most direct corrective action is: Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.

C:

SQL encrypted connections and TLS verification (2.2) addresses another technical failure: Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation. This case instead tests Managed identity database access (2.1); the choice measures or changes another part of the system.

D:

Microsoft entra administrator for azure SQL (2.1) addresses another technical failure: Without correct tenant mapping and directory administration, intended Entra accounts cannot be provisioned for database access. The required corrective action concerns Managed identity database access (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 210

An Azure SQL operations team investigates: A platform team rotates a shared SQL credential and inadvertently breaks dozens of instances that could use managed identities. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.
  2. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.
  3. The classification inventory identifies sensitive columns and its labels match approved data handling requirements.
  4. Configure a supported Microsoft Entra administrator and tenant identity prerequisites before enabling Entra-based SQL principals and sign-in.
  5. Require supported TLS encryption, valid certificates and client hostname validation for database network connections.

Explanation

Correct Answers

A:

The acceptance evidence for this incident (A platform team rotates a shared SQL credential and inadvertently breaks dozens of instances that could use managed identities.) is: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source. It directly tests whether the remediation (Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.) solves the specified issue, instead of proving an unrelated database control works.

B:

The reported Azure SQL or SQL Server condition is: A platform team rotates a shared SQL credential and inadvertently breaks dozens of instances that could use managed identities. The specific supported administrative response is: Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions. The technical risk is: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely. Confirm the correction with: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.

Incorrect Answers

C:

Sensitive data classification and discovery (2.3) would demonstrate or implement: The classification inventory identifies sensitive columns and its labels match approved data handling requirements. This case instead tests Managed identity database access (2.1); the choice measures or changes another part of the system.

D:

Microsoft entra administrator for azure SQL (2.1) addresses another technical failure: Without correct tenant mapping and directory administration, intended Entra accounts cannot be provisioned for database access. The required paired action and test concerns Managed identity database access (2.1); a passing result for this alternative could leave that requirement unresolved.

E:

SQL encrypted connections and TLS verification (2.2) addresses another technical failure: Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation. The paired-answer requirement concerns Managed identity database access (2.1); this alternative does not provide the matching intervention and separate acceptance evidence.