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 22

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.

Question 211

An Azure database administrator observes: A client reaches TCP 1433 but gets a SQL login failed message after an identity change. Which action best addresses the specific technical requirement?

  1. Use supported private endpoints and private DNS configuration for Azure SQL Database and restrict public network access when private connectivity is required.
  2. Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication.
  3. Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.
  4. Maintain SQL login configuration and password policy appropriately on SQL Server installations that support SQL authentication and coordinate with directory alternatives.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: A client reaches TCP 1433 but gets a SQL login failed message after an identity change. The specific supported administrative response is: Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication. The technical risk is: Treating every database error as a firewall block can conceal authentication and access-control faults. Confirm the correction with: Connection logs and controlled tests identify whether the failure occurs at network, authentication or authorization stage.

Incorrect Answers

A:

Azure SQL private endpoints and public exposure (2.2) addresses another technical failure: A created private endpoint without correct DNS resolution or network controls can still leave clients using public endpoints or unable to connect. The case states: A client reaches TCP 1433 but gets a SQL login failed message after an identity change. The most direct corrective action is: Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication.

C:

Always encrypted secure enclave workloads (2.2) addresses another technical failure: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior. This case instead tests Diagnosing login and token failures (2.1); the choice measures or changes another part of the system.

D:

SQL authentication management on SQL server vms (2.1) addresses another technical failure: Poorly governed shared SQL logins are hard to rotate and can bypass centralized identity lifecycle management. The required corrective action concerns Diagnosing login and token failures (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 212

During post-change validation, the team reports: A client reaches TCP 1433 but gets a SQL login failed message after an identity change. Which observation best demonstrates that the appropriate correction worked?

  1. Connection logs and controlled tests identify whether the failure occurs at network, authentication or authorization stage.
  2. Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.
  3. Inside-VNet DNS resolves the intended private endpoint, allowed clients connect and prohibited public access fails.
  4. Approved users authenticate with expected policies while disabled credentials fail and access is logged.

Explanation

Correct Answer

A:

The acceptance evidence for this incident (A client reaches TCP 1433 but gets a SQL login failed message after an identity change.) is: Connection logs and controlled tests identify whether the failure occurs at network, authentication or authorization stage. It directly tests whether the remediation (Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

B:

Always encrypted secure enclave workloads (2.2) would demonstrate or implement: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked. This choice can be useful for that problem, but it does not establish the Diagnosing login and token failures (2.1) control being assessed here.

C:

Azure SQL private endpoints and public exposure (2.2) would demonstrate or implement: Inside-VNet DNS resolves the intended private endpoint, allowed clients connect and prohibited public access fails. This case instead tests Diagnosing login and token failures (2.1); the choice measures or changes another part of the system.

D:

SQL authentication management on SQL server vms (2.1) would demonstrate or implement: Approved users authenticate with expected policies while disabled credentials fail and access is logged. The required evidence concerns Diagnosing login and token failures (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 213

An Azure database administrator observes: A managed identity token uses the wrong resource audience and the driver refuses connection. Which action best addresses the specific technical requirement?

  1. Maintain SQL login configuration and password policy appropriately on SQL Server installations that support SQL authentication and coordinate with directory alternatives.
  2. Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.
  3. Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication.
  4. Use supported private endpoints and private DNS configuration for Azure SQL Database and restrict public network access when private connectivity is required.

Explanation

Correct Answer

C:

The reported Azure SQL or SQL Server condition is: A managed identity token uses the wrong resource audience and the driver refuses connection. The specific supported administrative response is: Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication. The technical risk is: Treating every database error as a firewall block can conceal authentication and access-control faults. Confirm the correction with: Connection logs and controlled tests identify whether the failure occurs at network, authentication or authorization stage.

Incorrect Answers

A:

SQL authentication management on SQL server vms (2.1) addresses another technical failure: Poorly governed shared SQL logins are hard to rotate and can bypass centralized identity lifecycle management. The case states: A managed identity token uses the wrong resource audience and the driver refuses connection. The most direct corrective action is: Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication.

B:

Always encrypted secure enclave workloads (2.2) addresses another technical failure: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior. This choice can be useful for that problem, but it does not establish the Diagnosing login and token failures (2.1) control being assessed here.

D:

Azure SQL private endpoints and public exposure (2.2) addresses another technical failure: A created private endpoint without correct DNS resolution or network controls can still leave clients using public endpoints or unable to connect. The required corrective action concerns Diagnosing login and token failures (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 214

In a database operations review, a team encounters: A managed identity token uses the wrong resource audience and the driver refuses connection. Which failure or exposure is most directly relevant?

  1. Treating every database error as a firewall block can conceal authentication and access-control faults.
  2. Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior.
  3. A created private endpoint without correct DNS resolution or network controls can still leave clients using public endpoints or unable to connect.
  4. Poorly governed shared SQL logins are hard to rotate and can bypass centralized identity lifecycle management.

Explanation

Correct Answer

A:

The incident (A managed identity token uses the wrong resource audience and the driver refuses connection.) most directly exposes: Treating every database error as a firewall block can conceal authentication and access-control faults. The resulting safe technical response is: Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication. Its verification is: Connection logs and controlled tests identify whether the failure occurs at network, authentication or authorization stage.

Incorrect Answers

B:

Always encrypted secure enclave workloads (2.2) would demonstrate or implement: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior. This choice can be useful for that problem, but it does not establish the Diagnosing login and token failures (2.1) control being assessed here.

C:

Azure SQL private endpoints and public exposure (2.2) would demonstrate or implement: A created private endpoint without correct DNS resolution or network controls can still leave clients using public endpoints or unable to connect. This case instead tests Diagnosing login and token failures (2.1); the choice measures or changes another part of the system.

D:

SQL authentication management on SQL server vms (2.1) would demonstrate or implement: Poorly governed shared SQL logins are hard to rotate and can bypass centralized identity lifecycle management. The required risk concerns Diagnosing login and token failures (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 215

An Azure database administrator observes: A user can authenticate to master but gets permission denied reading a table in a different database. Which action best addresses the specific technical requirement?

  1. Maintain SQL login configuration and password policy appropriately on SQL Server installations that support SQL authentication and coordinate with directory alternatives.
  2. Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.
  3. Use supported private endpoints and private DNS configuration for Azure SQL Database and restrict public network access when private connectivity is required.
  4. Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication.

Explanation

Correct Answer

D:

The reported Azure SQL or SQL Server condition is: A user can authenticate to master but gets permission denied reading a table in a different database. The specific supported administrative response is: Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication. The technical risk is: Treating every database error as a firewall block can conceal authentication and access-control faults. Confirm the correction with: Connection logs and controlled tests identify whether the failure occurs at network, authentication or authorization stage.

Incorrect Answers

A:

SQL authentication management on SQL server vms (2.1) addresses another technical failure: Poorly governed shared SQL logins are hard to rotate and can bypass centralized identity lifecycle management. The case states: A user can authenticate to master but gets permission denied reading a table in a different database. The most direct corrective action is: Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication.

B:

Always encrypted secure enclave workloads (2.2) addresses another technical failure: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior. This choice can be useful for that problem, but it does not establish the Diagnosing login and token failures (2.1) control being assessed here.

C:

Azure SQL private endpoints and public exposure (2.2) addresses another technical failure: A created private endpoint without correct DNS resolution or network controls can still leave clients using public endpoints or unable to connect. This case instead tests Diagnosing login and token failures (2.1); the choice measures or changes another part of the system.

Question 216

During post-change validation, the team reports: A user can authenticate to master but gets permission denied reading a table in a different database. Which observation best demonstrates that the appropriate correction worked?

  1. Approved users authenticate with expected policies while disabled credentials fail and access is logged.
  2. Connection logs and controlled tests identify whether the failure occurs at network, authentication or authorization stage.
  3. Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.
  4. Inside-VNet DNS resolves the intended private endpoint, allowed clients connect and prohibited public access fails.

Explanation

Correct Answer

B:

The acceptance evidence for this incident (A user can authenticate to master but gets permission denied reading a table in a different database.) is: Connection logs and controlled tests identify whether the failure occurs at network, authentication or authorization stage. It directly tests whether the remediation (Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

SQL authentication management on SQL server vms (2.1) would demonstrate or implement: Approved users authenticate with expected policies while disabled credentials fail and access is logged. The case states: A user can authenticate to master but gets permission denied reading a table in a different database. The most direct evidence is: Connection logs and controlled tests identify whether the failure occurs at network, authentication or authorization stage.

C:

Always encrypted secure enclave workloads (2.2) would demonstrate or implement: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked. This case instead tests Diagnosing login and token failures (2.1); the choice measures or changes another part of the system.

D:

Azure SQL private endpoints and public exposure (2.2) would demonstrate or implement: Inside-VNet DNS resolves the intended private endpoint, allowed clients connect and prohibited public access fails. The required evidence concerns Diagnosing login and token failures (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 217

An Azure database administrator observes: An application cannot connect after an Entra group assignment because the database principal was never created. Which action best addresses the specific technical requirement?

  1. Maintain SQL login configuration and password policy appropriately on SQL Server installations that support SQL authentication and coordinate with directory alternatives.
  2. Use supported private endpoints and private DNS configuration for Azure SQL Database and restrict public network access when private connectivity is required.
  3. Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication.
  4. Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.

Explanation

Correct Answer

C:

The reported Azure SQL or SQL Server condition is: An application cannot connect after an Entra group assignment because the database principal was never created. The specific supported administrative response is: Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication. The technical risk is: Treating every database error as a firewall block can conceal authentication and access-control faults. Confirm the correction with: Connection logs and controlled tests identify whether the failure occurs at network, authentication or authorization stage.

Incorrect Answers

A:

SQL authentication management on SQL server vms (2.1) addresses another technical failure: Poorly governed shared SQL logins are hard to rotate and can bypass centralized identity lifecycle management. The case states: An application cannot connect after an Entra group assignment because the database principal was never created. The most direct corrective action is: Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication.

B:

Azure SQL private endpoints and public exposure (2.2) addresses another technical failure: A created private endpoint without correct DNS resolution or network controls can still leave clients using public endpoints or unable to connect. This choice can be useful for that problem, but it does not establish the Diagnosing login and token failures (2.1) control being assessed here.

D:

Always encrypted secure enclave workloads (2.2) addresses another technical failure: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior. The required corrective action concerns Diagnosing login and token failures (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 218

In a database operations review, a team encounters: An application cannot connect after an Entra group assignment because the database principal was never created. Which failure or exposure is most directly relevant?

  1. Treating every database error as a firewall block can conceal authentication and access-control faults.
  2. A created private endpoint without correct DNS resolution or network controls can still leave clients using public endpoints or unable to connect.
  3. Poorly governed shared SQL logins are hard to rotate and can bypass centralized identity lifecycle management.
  4. Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior.

Explanation

Correct Answer

A:

The incident (An application cannot connect after an Entra group assignment because the database principal was never created.) most directly exposes: Treating every database error as a firewall block can conceal authentication and access-control faults. The resulting safe technical response is: Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication. Its verification is: Connection logs and controlled tests identify whether the failure occurs at network, authentication or authorization stage.

Incorrect Answers

B:

Azure SQL private endpoints and public exposure (2.2) would demonstrate or implement: A created private endpoint without correct DNS resolution or network controls can still leave clients using public endpoints or unable to connect. This choice can be useful for that problem, but it does not establish the Diagnosing login and token failures (2.1) control being assessed here.

C:

SQL authentication management on SQL server vms (2.1) would demonstrate or implement: Poorly governed shared SQL logins are hard to rotate and can bypass centralized identity lifecycle management. This case instead tests Diagnosing login and token failures (2.1); the choice measures or changes another part of the system.

D:

Always encrypted secure enclave workloads (2.2) would demonstrate or implement: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior. The required risk concerns Diagnosing login and token failures (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 219

An Azure database administrator observes: A network engineer opens broad public firewall rules in response to a database permission-denied error. Which action best addresses the specific technical requirement?

  1. Use supported private endpoints and private DNS configuration for Azure SQL Database and restrict public network access when private connectivity is required.
  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. Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: A network engineer opens broad public firewall rules in response to a database permission-denied error. The specific supported administrative response is: Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication. The technical risk is: Treating every database error as a firewall block can conceal authentication and access-control faults. Confirm the correction with: Connection logs and controlled tests identify whether the failure occurs at network, authentication or authorization stage.

Incorrect Answers

A:

Azure SQL private endpoints and public exposure (2.2) addresses another technical failure: A created private endpoint without correct DNS resolution or network controls can still leave clients using public endpoints or unable to connect. The case states: A network engineer opens broad public firewall rules in response to a database permission-denied error. The most direct corrective action is: Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication.

C:

SQL authentication management on SQL server vms (2.1) addresses another technical failure: Poorly governed shared SQL logins are hard to rotate and can bypass centralized identity lifecycle management. This case instead tests Diagnosing login and token failures (2.1); the choice measures or changes another part of the system.

D:

Always encrypted secure enclave workloads (2.2) addresses another technical failure: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior. The required corrective action concerns Diagnosing login and token failures (2.1); a passing result for this alternative could leave that requirement unresolved.

Question 220

An Azure SQL operations team investigates: A network engineer opens broad public firewall rules in response to a database permission-denied error. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication.
  2. Inside-VNet DNS resolves the intended private endpoint, allowed clients connect and prohibited public access fails.
  3. Connection logs and controlled tests identify whether the failure occurs at network, authentication or authorization stage.
  4. Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.
  5. Maintain SQL login configuration and password policy appropriately on SQL Server installations that support SQL authentication and coordinate with directory alternatives.

Explanation

Correct Answers

A:

The reported Azure SQL or SQL Server condition is: A network engineer opens broad public firewall rules in response to a database permission-denied error. The specific supported administrative response is: Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication. The technical risk is: Treating every database error as a firewall block can conceal authentication and access-control faults. Confirm the correction with: Connection logs and controlled tests identify whether the failure occurs at network, authentication or authorization stage.

C:

The acceptance evidence for this incident (A network engineer opens broad public firewall rules in response to a database permission-denied error.) is: Connection logs and controlled tests identify whether the failure occurs at network, authentication or authorization stage. It directly tests whether the remediation (Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

B:

Azure SQL private endpoints and public exposure (2.2) would demonstrate or implement: Inside-VNet DNS resolves the intended private endpoint, allowed clients connect and prohibited public access fails. This choice can be useful for that problem, but it does not establish the Diagnosing login and token failures (2.1) control being assessed here.

D:

Always encrypted secure enclave workloads (2.2) addresses another technical failure: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior. The required paired action and test concerns Diagnosing login and token failures (2.1); a passing result for this alternative could leave that requirement unresolved.

E:

SQL authentication management on SQL server vms (2.1) addresses another technical failure: Poorly governed shared SQL logins are hard to rotate and can bypass centralized identity lifecycle management. The paired-answer requirement concerns Diagnosing login and token failures (2.1); this alternative does not provide the matching intervention and separate acceptance evidence.