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 30

Question 290

An Azure SQL operations team investigates: A remote on-premises application uses a private route but cannot resolve the SQL server to its private link address. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. Inside-VNet DNS resolves the intended private endpoint, allowed clients connect and prohibited public access fails.
  2. Approved users authenticate with expected policies while disabled credentials fail and access is logged.
  3. Use Always Encrypted with supported clients and key storage for sensitive column data that should remain protected from the database engine where the workload requires it.
  4. Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication.
  5. Use supported private endpoints and private DNS configuration for Azure SQL Database and restrict public network access when private connectivity is required.

Explanation

Correct Answers

A:

The acceptance evidence for this incident (A remote on-premises application uses a private route but cannot resolve the SQL server to its private link address.) is: Inside-VNet DNS resolves the intended private endpoint, allowed clients connect and prohibited public access fails. It directly tests whether the remediation (Use supported private endpoints and private DNS configuration for Azure SQL Database and restrict public network access when private connectivity is required.) solves the specified issue, instead of proving an unrelated database control works.

E:

The reported Azure SQL or SQL Server condition is: A remote on-premises application uses a private route but cannot resolve the SQL server to its private link address. The specific supported administrative response is: Use supported private endpoints and private DNS configuration for Azure SQL Database and restrict public network access when private connectivity is required. The technical risk is: A created private endpoint without correct DNS resolution or network controls can still leave clients using public endpoints or unable to connect. Confirm the correction with: Inside-VNet DNS resolves the intended private endpoint, allowed clients connect and prohibited public access fails.

Incorrect Answers

B:

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. This choice can be useful for that problem, but it does not establish the Azure SQL private endpoints and public exposure (2.2) control being assessed here.

C:

Always encrypted column confidentiality (2.2) addresses another technical failure: TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support. This case instead tests Azure SQL private endpoints and public exposure (2.2); the choice measures or changes another part of the system.

D:

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. The required paired action and test concerns Azure SQL private endpoints and public exposure (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 291

An Azure database administrator observes: A DBA adds 0.0.0.0 style broad Azure-services access without reviewing tenant risks. 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 a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.
  3. Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.
  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 DBA adds 0.0.0.0 style broad Azure-services access without reviewing tenant risks. The specific supported administrative response is: Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy. The technical risk is: Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily. Confirm the correction with: Approved source clients can connect through expected network paths and unauthorized test addresses are rejected.

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 DBA adds 0.0.0.0 style broad Azure-services access without reviewing tenant risks. The most direct corrective action is: Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.

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 Azure SQL firewall rule scoping (2.2) 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 Azure SQL firewall rule scoping (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 292

During post-change validation, the team reports: A DBA adds 0.0.0.0 style broad Azure-services access without reviewing tenant risks. Which observation best demonstrates that the appropriate correction worked?

  1. Approved source clients can connect through expected network paths and unauthorized test addresses are rejected.
  2. Approved users authenticate with expected policies while disabled credentials fail and access is logged.
  3. Inside-VNet DNS resolves the intended private endpoint, allowed clients connect and prohibited public access fails.
  4. The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.

Explanation

Correct Answer

A:

The acceptance evidence for this incident (A DBA adds 0.0.0.0 style broad Azure-services access without reviewing tenant risks.) is: Approved source clients can connect through expected network paths and unauthorized test addresses are rejected. It directly tests whether the remediation (Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

B:

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. This choice can be useful for that problem, but it does not establish the Azure SQL firewall rule scoping (2.2) 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 Azure SQL firewall rule scoping (2.2); the choice measures or changes another part of the system.

D:

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 required evidence concerns Azure SQL firewall rule scoping (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 293

An Azure database administrator observes: A SQL logical server firewall denies an approved office IP after a WAN address change. Which action best addresses the specific technical requirement?

  1. Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.
  2. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.
  3. Maintain SQL login configuration and password policy appropriately on SQL Server installations that support SQL authentication and coordinate with directory alternatives.
  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

A:

The reported Azure SQL or SQL Server condition is: A SQL logical server firewall denies an approved office IP after a WAN address change. The specific supported administrative response is: Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy. The technical risk is: Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily. Confirm the correction with: Approved source clients can connect through expected network paths and unauthorized test addresses are rejected.

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 Azure SQL firewall rule scoping (2.2) control being assessed here.

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 Azure SQL firewall rule scoping (2.2); the choice measures or changes another part of the system.

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 evidence concerns Azure SQL firewall rule scoping (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 294

In a database operations review, a team encounters: A SQL logical server firewall denies an approved office IP after a WAN address change. Which failure or exposure is most directly relevant?

  1. A created private endpoint without correct DNS resolution or network controls can still leave clients using public endpoints or unable to connect.
  2. Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily.
  3. Poorly governed shared SQL logins are hard to rotate and can bypass centralized identity lifecycle management.
  4. Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely.

Explanation

Correct Answer

B:

The incident (A SQL logical server firewall denies an approved office IP after a WAN address change.) most directly exposes: Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily. The resulting safe technical response is: Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy. Its verification is: Approved source clients can connect through expected network paths and unauthorized test addresses are rejected.

Incorrect Answers

A:

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. The case states: A SQL logical server firewall denies an approved office IP after a WAN address change. The most direct evidence is: Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily.

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 Azure SQL firewall rule scoping (2.2); the choice measures or changes another part of the system.

D:

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. The required evidence concerns Azure SQL firewall rule scoping (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 295

An Azure database administrator observes: A security auditor discovers a server-level allow rule broader than the intended development range. Which action best addresses the specific technical requirement?

  1. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.
  2. Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.
  3. Maintain SQL login configuration and password policy appropriately on SQL Server installations that support SQL authentication and coordinate with directory alternatives.
  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

B:

The reported Azure SQL or SQL Server condition is: A security auditor discovers a server-level allow rule broader than the intended development range. The specific supported administrative response is: Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy. The technical risk is: Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily. Confirm the correction with: Approved source clients can connect through expected network paths and unauthorized test addresses are rejected.

Incorrect Answers

A:

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 case states: A security auditor discovers a server-level allow rule broader than the intended development range. The most direct corrective action is: Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.

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 Azure SQL firewall rule scoping (2.2); the choice measures or changes another part of the system.

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 Azure SQL firewall rule scoping (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 296

During post-change validation, the team reports: A security auditor discovers a server-level allow rule broader than the intended development range. 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. The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.
  3. Approved source clients can connect through expected network paths and unauthorized test addresses are rejected.
  4. Inside-VNet DNS resolves the intended private endpoint, allowed clients connect and prohibited public access fails.

Explanation

Correct Answer

C:

The acceptance evidence for this incident (A security auditor discovers a server-level allow rule broader than the intended development range.) is: Approved source clients can connect through expected network paths and unauthorized test addresses are rejected. It directly tests whether the remediation (Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.) 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 security auditor discovers a server-level allow rule broader than the intended development range. The most direct evidence is: Approved source clients can connect through expected network paths and unauthorized test addresses are rejected.

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 Azure SQL firewall rule scoping (2.2) control being assessed here.

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 Azure SQL firewall rule scoping (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 297

An Azure database administrator observes: An application network team opens all source addresses to fix an unresolved database login error. 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 a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.
  3. Use supported private endpoints and private DNS configuration for Azure SQL Database and restrict public network access when private connectivity is required.
  4. Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.

Explanation

Correct Answer

D:

The reported Azure SQL or SQL Server condition is: An application network team opens all source addresses to fix an unresolved database login error. The specific supported administrative response is: Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy. The technical risk is: Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily. Confirm the correction with: Approved source clients can connect through expected network paths and unauthorized test addresses are rejected.

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 network team opens all source addresses to fix an unresolved database login error. The most direct corrective action is: Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.

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 Azure SQL firewall rule scoping (2.2) 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 Azure SQL firewall rule scoping (2.2); the choice measures or changes another part of the system.

Question 298

In a database operations review, a team encounters: An application network team opens all source addresses to fix an unresolved database login error. Which failure or exposure is most directly relevant?

  1. A created private endpoint without correct DNS resolution or network controls can still leave clients using public endpoints or unable to connect.
  2. Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily.
  3. Poorly governed shared SQL logins are hard to rotate and can bypass centralized identity lifecycle management.
  4. Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely.

Explanation

Correct Answer

B:

The incident (An application network team opens all source addresses to fix an unresolved database login error.) most directly exposes: Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily. The resulting safe technical response is: Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy. Its verification is: Approved source clients can connect through expected network paths and unauthorized test addresses are rejected.

Incorrect Answers

A:

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. The case states: An application network team opens all source addresses to fix an unresolved database login error. The most direct risk is: Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily.

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 Azure SQL firewall rule scoping (2.2); the choice measures or changes another part of the system.

D:

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. The required risk concerns Azure SQL firewall rule scoping (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 299

An Azure database administrator observes: A database-level firewall exception must be documented without bypassing the organization's public endpoint policy. Which action best addresses the specific technical requirement?

  1. Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.
  2. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.
  3. Use supported private endpoints and private DNS configuration for Azure SQL Database and restrict public network access when private connectivity is required.
  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

A:

The reported Azure SQL or SQL Server condition is: A database-level firewall exception must be documented without bypassing the organization's public endpoint policy. The specific supported administrative response is: Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy. The technical risk is: Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily. Confirm the correction with: Approved source clients can connect through expected network paths and unauthorized test addresses are rejected.

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 Azure SQL firewall rule scoping (2.2) 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 Azure SQL firewall rule scoping (2.2); 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 Azure SQL firewall rule scoping (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 300

An Azure SQL operations team investigates: A database-level firewall exception must be documented without bypassing the organization's public endpoint policy. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.
  2. The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.
  3. Approved source clients can connect through expected network paths and unauthorized test addresses are rejected.
  4. Maintain SQL login configuration and password policy appropriately on SQL Server installations that support SQL authentication and coordinate with directory alternatives.
  5. Use supported private endpoints and private DNS configuration for Azure SQL Database and restrict public network access when private connectivity is required.

Explanation

Correct Answers

A:

The reported Azure SQL or SQL Server condition is: A database-level firewall exception must be documented without bypassing the organization's public endpoint policy. The specific supported administrative response is: Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy. The technical risk is: Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily. Confirm the correction with: Approved source clients can connect through expected network paths and unauthorized test addresses are rejected.

C:

The acceptance evidence for this incident (A database-level firewall exception must be documented without bypassing the organization's public endpoint policy.) is: Approved source clients can connect through expected network paths and unauthorized test addresses are rejected. It directly tests whether the remediation (Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

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 Azure SQL firewall rule scoping (2.2) control being assessed here.

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 paired action and test concerns Azure SQL firewall rule scoping (2.2); a passing result for this alternative could leave that requirement unresolved.

E:

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 paired-answer requirement concerns Azure SQL firewall rule scoping (2.2); this alternative does not provide the matching intervention and separate acceptance evidence.