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 36

Question 350

An Azure SQL operations team investigates: A DBA must evaluate whether the target Azure SQL service supports the specific capture feature and required retention. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. Choose SQL change tracking or supported change data capture according to whether an integration needs row-change identification or detailed changed-data history.
  2. Separate network reachability, token validity, tenant identity, database mapping and SQL permission problems when troubleshooting failed authentication.
  3. A permission check proves only the intended schema or table actions succeed for the dedicated workload identity.
  4. Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.
  5. A controlled INSERT UPDATE and DELETE sequence produces the required tracking metadata or captured changes for the chosen design.

Explanation

Correct Answers

A:

The reported Azure SQL or SQL Server condition is: A DBA must evaluate whether the target Azure SQL service supports the specific capture feature and required retention. The specific supported administrative response is: Choose SQL change tracking or supported change data capture according to whether an integration needs row-change identification or detailed changed-data history. The technical risk is: Confusing lightweight change identifiers with historical before-and-after data can produce incomplete downstream synchronization. Confirm the correction with: A controlled INSERT UPDATE and DELETE sequence produces the required tracking metadata or captured changes for the chosen design.

E:

The acceptance evidence for this incident (A DBA must evaluate whether the target Azure SQL service supports the specific capture feature and required retention.) is: A controlled INSERT UPDATE and DELETE sequence produces the required tracking metadata or captured changes for the chosen design. It directly tests whether the remediation (Choose SQL change tracking or supported change data capture according to whether an integration needs row-change identification or detailed changed-data history.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

B:

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

C:

Least-privilege database roles and grants (2.1) would demonstrate or implement: A permission check proves only the intended schema or table actions succeed for the dedicated workload identity. This case instead tests Change tracking and change data capture (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 paired action and test concerns Change tracking and change data capture (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 351

An Azure database administrator observes: A financial workflow must prove later modifications to its ledger history have not gone unnoticed. Which action best addresses the specific technical requirement?

  1. Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.
  2. Configure a supported Microsoft Entra administrator and tenant identity prerequisites before enabling Entra-based SQL principals and sign-in.
  3. Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.
  4. Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.

Explanation

Correct Answer

A:

The reported Azure SQL or SQL Server condition is: A financial workflow must prove later modifications to its ledger history have not gone unnoticed. The specific supported administrative response is: Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage. The technical risk is: Audit logs alone or editable records cannot guarantee detection of all later data history alterations. Confirm the correction with: An external digest and ledger verification detect a controlled unauthorized alteration of historical records.

Incorrect Answers

B:

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

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 SQL ledger tamper-evidence (2.3); the choice measures or changes another part of the system.

D:

SQL database auditing and audit storage (2.3) addresses another technical failure: Audit events written only to a disposable or broadly writable destination may be lost or tampered with. The required evidence concerns SQL ledger tamper-evidence (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 352

During post-change validation, the team reports: A financial workflow must prove later modifications to its ledger history have not gone unnoticed. Which observation best demonstrates that the appropriate correction worked?

  1. An authorized Entra identity can authenticate and create the intended supported contained database principal without a shared SQL password.
  2. A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp.
  3. An external digest and ledger verification detect a controlled unauthorized alteration of historical records.
  4. Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.

Explanation

Correct Answer

C:

The acceptance evidence for this incident (A financial workflow must prove later modifications to its ledger history have not gone unnoticed.) is: An external digest and ledger verification detect a controlled unauthorized alteration of historical records. It directly tests whether the remediation (Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

Microsoft entra administrator for azure SQL (2.1) would demonstrate or implement: An authorized Entra identity can authenticate and create the intended supported contained database principal without a shared SQL password. The case states: A financial workflow must prove later modifications to its ledger history have not gone unnoticed. The most direct evidence is: An external digest and ledger verification detect a controlled unauthorized alteration of historical records.

B:

SQL database auditing and audit storage (2.3) would demonstrate or implement: A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp. This choice can be useful for that problem, but it does not establish the SQL ledger tamper-evidence (2.3) control being assessed here.

D:

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. The required evidence concerns SQL ledger tamper-evidence (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 353

An Azure database administrator observes: A DBA creates an ordinary audit trigger and labels it cryptographically tamper-evident ledger storage. Which action best addresses the specific technical requirement?

  1. Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.
  2. Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.
  3. Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.
  4. Configure a supported Microsoft Entra administrator and tenant identity prerequisites before enabling Entra-based SQL principals and sign-in.

Explanation

Correct Answer

C:

The reported Azure SQL or SQL Server condition is: A DBA creates an ordinary audit trigger and labels it cryptographically tamper-evident ledger storage. The specific supported administrative response is: Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage. The technical risk is: Audit logs alone or editable records cannot guarantee detection of all later data history alterations. Confirm the correction with: An external digest and ledger verification detect a controlled unauthorized alteration of historical records.

Incorrect Answers

A:

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 case states: A DBA creates an ordinary audit trigger and labels it cryptographically tamper-evident ledger storage. The most direct corrective action is: Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.

B:

SQL database auditing and audit storage (2.3) addresses another technical failure: Audit events written only to a disposable or broadly writable destination may be lost or tampered with. This choice can be useful for that problem, but it does not establish the SQL ledger tamper-evidence (2.3) control being assessed here.

D:

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

Question 354

In a database operations review, a team encounters: A DBA creates an ordinary audit trigger and labels it cryptographically tamper-evident ledger storage. Which failure or exposure is most directly relevant?

  1. Audit logs alone or editable records cannot guarantee detection of all later data history alterations.
  2. Without correct tenant mapping and directory administration, intended Entra accounts cannot be provisioned for database access.
  3. Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior.
  4. Audit events written only to a disposable or broadly writable destination may be lost or tampered with.

Explanation

Correct Answer

A:

The incident (A DBA creates an ordinary audit trigger and labels it cryptographically tamper-evident ledger storage.) most directly exposes: Audit logs alone or editable records cannot guarantee detection of all later data history alterations. The resulting safe technical response is: Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage. Its verification is: An external digest and ledger verification detect a controlled unauthorized alteration of historical records.

Incorrect Answers

B:

Microsoft entra administrator for azure SQL (2.1) would demonstrate or implement: Without correct tenant mapping and directory administration, intended Entra accounts cannot be provisioned for database access. This choice can be useful for that problem, but it does not establish the SQL ledger tamper-evidence (2.3) control being assessed here.

C:

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 case instead tests SQL ledger tamper-evidence (2.3); the choice measures or changes another part of the system.

D:

SQL database auditing and audit storage (2.3) would demonstrate or implement: Audit events written only to a disposable or broadly writable destination may be lost or tampered with. The required risk concerns SQL ledger tamper-evidence (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 355

An Azure database administrator observes: A compliance reviewer wants independently verifiable historical integrity for important SQL records. 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. Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.
  3. Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.
  4. Configure a supported Microsoft Entra administrator and tenant identity prerequisites before enabling Entra-based SQL principals and sign-in.

Explanation

Correct Answer

C:

The reported Azure SQL or SQL Server condition is: A compliance reviewer wants independently verifiable historical integrity for important SQL records. The specific supported administrative response is: Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage. The technical risk is: Audit logs alone or editable records cannot guarantee detection of all later data history alterations. Confirm the correction with: An external digest and ledger verification detect a controlled unauthorized alteration of historical records.

Incorrect Answers

A:

SQL database auditing and audit storage (2.3) addresses another technical failure: Audit events written only to a disposable or broadly writable destination may be lost or tampered with. The case states: A compliance reviewer wants independently verifiable historical integrity for important SQL records. The most direct corrective action is: Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.

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 SQL ledger tamper-evidence (2.3) control being assessed here.

D:

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

Question 356

During post-change validation, the team reports: A compliance reviewer wants independently verifiable historical integrity for important SQL records. 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. An external digest and ledger verification detect a controlled unauthorized alteration of historical records.
  3. Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.
  4. An authorized Entra identity can authenticate and create the intended supported contained database principal without a shared SQL password.

Explanation

Correct Answer

B:

The acceptance evidence for this incident (A compliance reviewer wants independently verifiable historical integrity for important SQL records.) is: An external digest and ledger verification detect a controlled unauthorized alteration of historical records. It directly tests whether the remediation (Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

SQL database auditing and audit storage (2.3) would demonstrate or implement: A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp. The case states: A compliance reviewer wants independently verifiable historical integrity for important SQL records. The most direct evidence is: An external digest and ledger verification detect a controlled unauthorized alteration of historical records.

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 SQL ledger tamper-evidence (2.3); the choice measures or changes another part of the system.

D:

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

Question 357

An Azure database administrator observes: A ledger verification test is run but digest material is stored only in the database controlled by the same admins. 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. Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.
  3. Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.
  4. Configure a supported Microsoft Entra administrator and tenant identity prerequisites before enabling Entra-based SQL principals and sign-in.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: A ledger verification test is run but digest material is stored only in the database controlled by the same admins. The specific supported administrative response is: Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage. The technical risk is: Audit logs alone or editable records cannot guarantee detection of all later data history alterations. Confirm the correction with: An external digest and ledger verification detect a controlled unauthorized alteration of historical records.

Incorrect Answers

A:

SQL database auditing and audit storage (2.3) addresses another technical failure: Audit events written only to a disposable or broadly writable destination may be lost or tampered with. The case states: A ledger verification test is run but digest material is stored only in the database controlled by the same admins. The most direct corrective action is: Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.

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 SQL ledger tamper-evidence (2.3); the choice measures or changes another part of the system.

D:

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

Question 358

In a database operations review, a team encounters: A ledger verification test is run but digest material is stored only in the database controlled by the same admins. 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. Audit logs alone or editable records cannot guarantee detection of all later data history alterations.
  3. Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior.
  4. Without correct tenant mapping and directory administration, intended Entra accounts cannot be provisioned for database access.

Explanation

Correct Answer

B:

The incident (A ledger verification test is run but digest material is stored only in the database controlled by the same admins.) most directly exposes: Audit logs alone or editable records cannot guarantee detection of all later data history alterations. The resulting safe technical response is: Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage. Its verification is: An external digest and ledger verification detect a controlled unauthorized alteration of historical records.

Incorrect Answers

A:

SQL database auditing and audit storage (2.3) would demonstrate or implement: Audit events written only to a disposable or broadly writable destination may be lost or tampered with. The case states: A ledger verification test is run but digest material is stored only in the database controlled by the same admins. The most direct risk is: Audit logs alone or editable records cannot guarantee detection of all later data history alterations.

C:

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 case instead tests SQL ledger tamper-evidence (2.3); the choice measures or changes another part of the system.

D:

Microsoft entra administrator for azure SQL (2.1) would demonstrate or implement: Without correct tenant mapping and directory administration, intended Entra accounts cannot be provisioned for database access. The required risk concerns SQL ledger tamper-evidence (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 359

An Azure database administrator observes: An organization needs to decide when built-in ledger features suit audit evidence requirements. 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. Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.
  3. Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.
  4. Configure a supported Microsoft Entra administrator and tenant identity prerequisites before enabling Entra-based SQL principals and sign-in.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: An organization needs to decide when built-in ledger features suit audit evidence requirements. The specific supported administrative response is: Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage. The technical risk is: Audit logs alone or editable records cannot guarantee detection of all later data history alterations. Confirm the correction with: An external digest and ledger verification detect a controlled unauthorized alteration of historical records.

Incorrect Answers

A:

SQL database auditing and audit storage (2.3) addresses another technical failure: Audit events written only to a disposable or broadly writable destination may be lost or tampered with. The case states: An organization needs to decide when built-in ledger features suit audit evidence requirements. The most direct corrective action is: Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.

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 SQL ledger tamper-evidence (2.3); the choice measures or changes another part of the system.

D:

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

Question 360

An Azure SQL operations team investigates: An organization needs to decide when built-in ledger features suit audit evidence requirements. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. Configure a supported Microsoft Entra administrator and tenant identity prerequisites before enabling Entra-based SQL principals and sign-in.
  2. Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.
  3. Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.
  4. An external digest and ledger verification detect a controlled unauthorized alteration of historical records.
  5. Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.

Explanation

Correct Answers

D:

The acceptance evidence for this incident (An organization needs to decide when built-in ledger features suit audit evidence requirements.) is: An external digest and ledger verification detect a controlled unauthorized alteration of historical records. It directly tests whether the remediation (Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.) solves the specified issue, instead of proving an unrelated database control works.

E:

The reported Azure SQL or SQL Server condition is: An organization needs to decide when built-in ledger features suit audit evidence requirements. The specific supported administrative response is: Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage. The technical risk is: Audit logs alone or editable records cannot guarantee detection of all later data history alterations. Confirm the correction with: An external digest and ledger verification detect a controlled unauthorized alteration of historical records.

Incorrect Answers

A:

Microsoft entra administrator for azure SQL (2.1) addresses another technical failure: Without correct tenant mapping and directory administration, intended Entra accounts cannot be provisioned for database access. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: An external digest and ledger verification detect a controlled unauthorized alteration of historical records.

B:

SQL database auditing and audit storage (2.3) addresses another technical failure: Audit events written only to a disposable or broadly writable destination may be lost or tampered with. This choice can be useful for that problem, but it does not establish the SQL ledger tamper-evidence (2.3) control being assessed here.

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 SQL ledger tamper-evidence (2.3); the choice measures or changes another part of the system.