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 27

Question 260

An Azure SQL operations team investigates: A team enables TDE and incorrectly claims that queried sensitive columns can no longer be seen by SQL privileged users. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. 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.
  2. The classification inventory identifies sensitive columns and its labels match approved data handling requirements.
  3. Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.
  4. Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.
  5. Client-side encryption tests show protected fields are not revealed as plaintext to unauthorized database administrators while approved clients can use them.

Explanation

Correct Answers

A:

The reported Azure SQL or SQL Server condition is: A team enables TDE and incorrectly claims that queried sensitive columns can no longer be seen by SQL privileged users. The specific supported administrative response is: 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. The technical risk is: TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support. Confirm the correction with: Client-side encryption tests show protected fields are not revealed as plaintext to unauthorized database administrators while approved clients can use them.

E:

The acceptance evidence for this incident (A team enables TDE and incorrectly claims that queried sensitive columns can no longer be seen by SQL privileged users.) is: Client-side encryption tests show protected fields are not revealed as plaintext to unauthorized database administrators while approved clients can use them. It directly tests whether the remediation (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.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

B:

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

C:

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 case instead tests Always encrypted column confidentiality (2.2); the choice measures or changes another part of the system.

D:

Azure SQL firewall rule scoping (2.2) addresses another technical failure: Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily. The required paired action and test concerns Always encrypted column confidentiality (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 261

An Azure database administrator observes: A protected HR table requires supported richer comparisons on encrypted columns. Which action best addresses the specific technical requirement?

  1. Require supported TLS encryption, valid certificates and client hostname validation for database network connections.
  2. Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.
  3. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.
  4. Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: A protected HR table requires supported richer comparisons on encrypted columns. The specific supported administrative response is: Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration. The technical risk is: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior. Confirm the correction with: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.

Incorrect Answers

A:

SQL encrypted connections and TLS verification (2.2) addresses another technical failure: Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation. The case states: A protected HR table requires supported richer comparisons on encrypted columns. The most direct corrective action is: Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.

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 Always encrypted secure enclave workloads (2.2); the choice measures or changes another part of the system.

D:

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 required corrective action concerns Always encrypted secure enclave workloads (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 262

During post-change validation, the team reports: A protected HR table requires supported richer comparisons on encrypted columns. Which observation best demonstrates that the appropriate correction worked?

  1. The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.
  2. Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.
  3. The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.
  4. An approved SQL client validates the intended server certificate and rejects an untrusted endpoint during a controlled test.

Explanation

Correct Answer

B:

The acceptance evidence for this incident (A protected HR table requires supported richer comparisons on encrypted columns.) is: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked. It directly tests whether the remediation (Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

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 case states: A protected HR table requires supported richer comparisons on encrypted columns. The most direct evidence is: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.

C:

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 case instead tests Always encrypted secure enclave workloads (2.2); the choice measures or changes another part of the system.

D:

SQL encrypted connections and TLS verification (2.2) would demonstrate or implement: An approved SQL client validates the intended server certificate and rejects an untrusted endpoint during a controlled test. The required evidence concerns Always encrypted secure enclave workloads (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 263

An Azure database administrator observes: An architect expects ordinary Always Encrypted randomized ciphertext to allow any wildcard search. 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. Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.
  3. Require supported TLS encryption, valid certificates and client hostname validation for database network connections.
  4. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.

Explanation

Correct Answer

A:

The reported Azure SQL or SQL Server condition is: An architect expects ordinary Always Encrypted randomized ciphertext to allow any wildcard search. The specific supported administrative response is: Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration. The technical risk is: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior. Confirm the correction with: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.

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 Always encrypted secure enclave workloads (2.2) control being assessed here.

C:

SQL encrypted connections and TLS verification (2.2) addresses another technical failure: Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation. This case instead tests Always encrypted secure enclave workloads (2.2); 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 Always encrypted secure enclave workloads (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 264

In a database operations review, a team encounters: An architect expects ordinary Always Encrypted randomized ciphertext to allow any wildcard search. Which failure or exposure is most directly relevant?

  1. Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely.
  2. Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation.
  3. An Entra identity alone does not automatically confer SQL database authorization to the data it needs.
  4. Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior.

Explanation

Correct Answer

D:

The incident (An architect expects ordinary Always Encrypted randomized ciphertext to allow any wildcard search.) most directly exposes: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior. The resulting safe technical response is: Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration. Its verification is: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.

Incorrect Answers

A:

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 case states: An architect expects ordinary Always Encrypted randomized ciphertext to allow any wildcard search. The most direct risk is: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior.

B:

SQL encrypted connections and TLS verification (2.2) would demonstrate or implement: Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation. This choice can be useful for that problem, but it does not establish the Always encrypted secure enclave workloads (2.2) control being assessed here.

C:

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 case instead tests Always encrypted secure enclave workloads (2.2); the choice measures or changes another part of the system.

Question 265

An Azure database administrator observes: A secure-enclave configuration is introduced without verifying driver support or attestation prerequisites. 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. Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.
  3. Require supported TLS encryption, valid certificates and client hostname validation for database network connections.
  4. Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: A secure-enclave configuration is introduced without verifying driver support or attestation prerequisites. The specific supported administrative response is: Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration. The technical risk is: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior. Confirm the correction with: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.

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 secure-enclave configuration is introduced without verifying driver support or attestation prerequisites. The most direct evidence is: Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.

C:

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

D:

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 required evidence concerns Always encrypted secure enclave workloads (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 266

During post-change validation, the team reports: A secure-enclave configuration is introduced without verifying driver support or attestation prerequisites. Which observation best demonstrates that the appropriate correction worked?

  1. Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.
  2. The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.
  3. An approved SQL client validates the intended server certificate and rejects an untrusted endpoint during a controlled test.
  4. The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.

Explanation

Correct Answer

A:

The acceptance evidence for this incident (A secure-enclave configuration is introduced without verifying driver support or attestation prerequisites.) is: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked. It directly tests whether the remediation (Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.) 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 Always encrypted secure enclave workloads (2.2) control being assessed here.

C:

SQL encrypted connections and TLS verification (2.2) would demonstrate or implement: An approved SQL client validates the intended server certificate and rejects an untrusted endpoint during a controlled test. This case instead tests Always encrypted secure enclave workloads (2.2); 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 Always encrypted secure enclave workloads (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 267

An Azure database administrator observes: A developer wants enclave-enabled operations while keeping sensitive field values inaccessible to the normal SQL engine. 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. Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.
  3. Require supported TLS encryption, valid certificates and client hostname validation for database network connections.
  4. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: A developer wants enclave-enabled operations while keeping sensitive field values inaccessible to the normal SQL engine. The specific supported administrative response is: Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration. The technical risk is: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior. Confirm the correction with: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.

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: A developer wants enclave-enabled operations while keeping sensitive field values inaccessible to the normal SQL engine. The most direct corrective action is: Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.

C:

SQL encrypted connections and TLS verification (2.2) addresses another technical failure: Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation. This case instead tests Always encrypted secure enclave workloads (2.2); 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 Always encrypted secure enclave workloads (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 268

In a database operations review, a team encounters: A developer wants enclave-enabled operations while keeping sensitive field values inaccessible to the normal SQL engine. Which failure or exposure is most directly relevant?

  1. Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation.
  2. Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely.
  3. Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior.
  4. An Entra identity alone does not automatically confer SQL database authorization to the data it needs.

Explanation

Correct Answer

C:

The incident (A developer wants enclave-enabled operations while keeping sensitive field values inaccessible to the normal SQL engine.) most directly exposes: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior. The resulting safe technical response is: Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration. Its verification is: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.

Incorrect Answers

A:

SQL encrypted connections and TLS verification (2.2) would demonstrate or implement: Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation. The case states: A developer wants enclave-enabled operations while keeping sensitive field values inaccessible to the normal SQL engine. The most direct risk is: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior.

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 Always encrypted secure enclave workloads (2.2) control being assessed here.

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 Always encrypted secure enclave workloads (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 269

An Azure database administrator observes: A database team enables encrypted columns but fails to validate whether its planned query functions are supported. Which action best addresses the specific technical requirement?

  1. Require supported TLS encryption, valid certificates and client hostname validation for database network connections.
  2. Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.
  3. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.
  4. Create contained database users mapped to supported Microsoft Entra identities and grant only the required database roles or permissions.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: A database team enables encrypted columns but fails to validate whether its planned query functions are supported. The specific supported administrative response is: Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration. The technical risk is: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior. Confirm the correction with: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.

Incorrect Answers

A:

SQL encrypted connections and TLS verification (2.2) addresses another technical failure: Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation. The case states: A database team enables encrypted columns but fails to validate whether its planned query functions are supported. The most direct evidence is: Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.

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 Always encrypted secure enclave workloads (2.2); the choice measures or changes another part of the system.

D:

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 required evidence concerns Always encrypted secure enclave workloads (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 270

An Azure SQL operations team investigates: A database team enables encrypted columns but fails to validate whether its planned query functions are supported. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. The signed-in user can perform the assigned database operations and is denied unrelated schema or data actions.
  2. Require supported TLS encryption, valid certificates and client hostname validation for database network connections.
  3. Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.
  4. Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.
  5. Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.

Explanation

Correct Answers

C:

The acceptance evidence for this incident (A database team enables encrypted columns but fails to validate whether its planned query functions are supported.) is: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked. It directly tests whether the remediation (Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration.) solves the specified issue, instead of proving an unrelated database control works.

D:

The reported Azure SQL or SQL Server condition is: A database team enables encrypted columns but fails to validate whether its planned query functions are supported. The specific supported administrative response is: Evaluate Always Encrypted with secure enclaves for supported encrypted-column operations that require enclave-supported computations and key configuration. The technical risk is: Assuming all encrypted-column operations work without enclave support can cause unsupported queries or unexpected decryption behavior. Confirm the correction with: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.

Incorrect Answers

A:

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 case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked.

B:

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

E:

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 paired-answer requirement concerns Always encrypted secure enclave workloads (2.2); this alternative does not provide the matching intervention and separate acceptance evidence.