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 31

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.

Question 301

An Azure database administrator observes: A regulated database has no retained record of privileged schema changes. 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. Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.
  3. Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.
  4. Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.

Explanation

Correct Answer

D:

The reported Azure SQL or SQL Server condition is: A regulated database has no retained record of privileged schema changes. The specific supported administrative response is: Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls. The technical risk is: Audit events written only to a disposable or broadly writable destination may be lost or tampered with. Confirm the correction with: A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp.

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 regulated database has no retained record of privileged schema changes. The most direct corrective action is: Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.

B:

Row-level security with session predicates (2.3) addresses another technical failure: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. This choice can be useful for that problem, but it does not establish the SQL database auditing and audit storage (2.3) control being assessed here.

C:

Contained database users from entra identities (2.1) addresses another technical failure: An Entra identity alone does not automatically confer SQL database authorization to the data it needs. This case instead tests SQL database auditing and audit storage (2.3); the choice measures or changes another part of the system.

Question 302

During post-change validation, the team reports: A regulated database has no retained record of privileged schema changes. Which observation best demonstrates that the appropriate correction worked?

  1. The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.
  2. A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp.
  3. Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records.
  4. The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.

Explanation

Correct Answer

B:

The acceptance evidence for this incident (A regulated database has no retained record of privileged schema changes.) is: A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp. It directly tests whether the remediation (Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

Managed identity database access (2.1) would demonstrate or implement: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source. The case states: A regulated database has no retained record of privileged schema changes. The most direct evidence is: A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp.

C:

Row-level security with session predicates (2.3) would demonstrate or implement: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records. This case instead tests SQL database auditing and audit storage (2.3); the choice measures or changes another part of the system.

D:

Contained database users from entra identities (2.1) would demonstrate or implement: The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions. The required evidence concerns SQL database auditing and audit storage (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 303

An Azure database administrator observes: An Azure SQL audit policy is configured but its storage destination has inaccessible permissions. Which action best addresses the specific technical requirement?

  1. Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.
  2. Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.
  3. Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.
  4. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: An Azure SQL audit policy is configured but its storage destination has inaccessible permissions. The specific supported administrative response is: Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls. The technical risk is: Audit events written only to a disposable or broadly writable destination may be lost or tampered with. Confirm the correction with: A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp.

Incorrect Answers

A:

Contained database users from entra identities (2.1) addresses another technical failure: An Entra identity alone does not automatically confer SQL database authorization to the data it needs. The case states: An Azure SQL audit policy is configured but its storage destination has inaccessible permissions. The most direct corrective action is: Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.

C:

Row-level security with session predicates (2.3) addresses another technical failure: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. This case instead tests SQL database auditing and audit storage (2.3); the choice measures or changes another part of the system.

D:

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

Question 304

In a database operations review, a team encounters: An Azure SQL audit policy is configured but its storage destination has inaccessible permissions. Which failure or exposure is most directly relevant?

  1. Audit events written only to a disposable or broadly writable destination may be lost or tampered with.
  2. An Entra identity alone does not automatically confer SQL database authorization to the data it needs.
  3. Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely.
  4. Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools.

Explanation

Correct Answer

A:

The incident (An Azure SQL audit policy is configured but its storage destination has inaccessible permissions.) most directly exposes: Audit events written only to a disposable or broadly writable destination may be lost or tampered with. The resulting safe technical response is: Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls. Its verification is: A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp.

Incorrect Answers

B:

Contained database users from entra identities (2.1) would demonstrate or implement: An Entra identity alone does not automatically confer SQL database authorization to the data it needs. This choice can be useful for that problem, but it does not establish the SQL database auditing and audit storage (2.3) control being assessed here.

C:

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

D:

Row-level security with session predicates (2.3) would demonstrate or implement: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. The required risk concerns SQL database auditing and audit storage (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 305

An Azure database administrator observes: A compliance reviewer needs proof of which principal queried a sensitive table under an approved audit specification. 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. Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.
  3. Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.
  4. Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.

Explanation

Correct Answer

D:

The reported Azure SQL or SQL Server condition is: A compliance reviewer needs proof of which principal queried a sensitive table under an approved audit specification. The specific supported administrative response is: Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls. The technical risk is: Audit events written only to a disposable or broadly writable destination may be lost or tampered with. Confirm the correction with: A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp.

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 compliance reviewer needs proof of which principal queried a sensitive table under an approved audit specification. The most direct evidence is: Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.

B:

Row-level security with session predicates (2.3) addresses another technical failure: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. This choice can be useful for that problem, but it does not establish the SQL database auditing and audit storage (2.3) control being assessed here.

C:

Contained database users from entra identities (2.1) addresses another technical failure: An Entra identity alone does not automatically confer SQL database authorization to the data it needs. This case instead tests SQL database auditing and audit storage (2.3); the choice measures or changes another part of the system.

Question 306

During post-change validation, the team reports: A compliance reviewer needs proof of which principal queried a sensitive table under an approved audit specification. Which observation best demonstrates that the appropriate correction worked?

  1. A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp.
  2. The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.
  3. Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records.
  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 compliance reviewer needs proof of which principal queried a sensitive table under an approved audit specification.) is: A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp. It directly tests whether the remediation (Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

B:

Contained database users from entra identities (2.1) would demonstrate or implement: The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions. This choice can be useful for that problem, but it does not establish the SQL database auditing and audit storage (2.3) control being assessed here.

C:

Row-level security with session predicates (2.3) would demonstrate or implement: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records. This case instead tests SQL database auditing and audit storage (2.3); 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 SQL database auditing and audit storage (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 307

An Azure database administrator observes: An administrator enables auditing but leaves logs in a location broadly deletable by application developers. Which action best addresses the specific technical requirement?

  1. Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.
  2. Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.
  3. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.
  4. Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.

Explanation

Correct Answer

A:

The reported Azure SQL or SQL Server condition is: An administrator enables auditing but leaves logs in a location broadly deletable by application developers. The specific supported administrative response is: Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls. The technical risk is: Audit events written only to a disposable or broadly writable destination may be lost or tampered with. Confirm the correction with: A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp.

Incorrect Answers

B:

Contained database users from entra identities (2.1) addresses another technical failure: An Entra identity alone does not automatically confer SQL database authorization to the data it needs. This choice can be useful for that problem, but it does not establish the SQL database auditing and audit storage (2.3) control being assessed here.

C:

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

D:

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

Question 308

In a database operations review, a team encounters: An administrator enables auditing but leaves logs in a location broadly deletable by application developers. Which failure or exposure is most directly relevant?

  1. Audit events written only to a disposable or broadly writable destination may be lost or tampered with.
  2. Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely.
  3. Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools.
  4. An Entra identity alone does not automatically confer SQL database authorization to the data it needs.

Explanation

Correct Answer

A:

The incident (An administrator enables auditing but leaves logs in a location broadly deletable by application developers.) most directly exposes: Audit events written only to a disposable or broadly writable destination may be lost or tampered with. The resulting safe technical response is: Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls. Its verification is: A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp.

Incorrect Answers

B:

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

C:

Row-level security with session predicates (2.3) would demonstrate or implement: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. This case instead tests SQL database auditing and audit storage (2.3); the choice measures or changes another part of the system.

D:

Contained database users from entra identities (2.1) would demonstrate or implement: An Entra identity alone does not automatically confer SQL database authorization to the data it needs. The required risk concerns SQL database auditing and audit storage (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 309

An Azure database administrator observes: A test SQL connection is denied and the monitoring team needs to verify whether the approved audit events were captured. 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. Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.
  3. Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.
  4. Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: A test SQL connection is denied and the monitoring team needs to verify whether the approved audit events were captured. The specific supported administrative response is: Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls. The technical risk is: Audit events written only to a disposable or broadly writable destination may be lost or tampered with. Confirm the correction with: A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp.

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 test SQL connection is denied and the monitoring team needs to verify whether the approved audit events were captured. The most direct evidence is: Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.

C:

Contained database users from entra identities (2.1) addresses another technical failure: An Entra identity alone does not automatically confer SQL database authorization to the data it needs. This case instead tests SQL database auditing and audit storage (2.3); the choice measures or changes another part of the system.

D:

Row-level security with session predicates (2.3) addresses another technical failure: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. The required evidence concerns SQL database auditing and audit storage (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 310

An Azure SQL operations team investigates: A test SQL connection is denied and the monitoring team needs to verify whether the approved audit events were captured. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.
  2. A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp.
  3. The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.
  4. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.
  5. Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.

Explanation

Correct Answers

A:

The reported Azure SQL or SQL Server condition is: A test SQL connection is denied and the monitoring team needs to verify whether the approved audit events were captured. The specific supported administrative response is: Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls. The technical risk is: Audit events written only to a disposable or broadly writable destination may be lost or tampered with. Confirm the correction with: A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp.

B:

The acceptance evidence for this incident (A test SQL connection is denied and the monitoring team needs to verify whether the approved audit events were captured.) is: A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp. It directly tests whether the remediation (Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

C:

Contained database users from entra identities (2.1) would demonstrate or implement: The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions. This case instead tests SQL database auditing and audit storage (2.3); the choice measures or changes another part of the system.

D:

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

E:

Row-level security with session predicates (2.3) addresses another technical failure: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. The paired-answer requirement concerns SQL database auditing and audit storage (2.3); this alternative does not provide the matching intervention and separate acceptance evidence.