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 26

Question 250

An Azure SQL operations team investigates: An auditor wants evidence that a customer-managed encryption key can be rotated without losing database accessibility. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. Maintain SQL login configuration and password policy appropriately on SQL Server installations that support SQL authentication and coordinate with directory alternatives.
  2. Use supported private endpoints and private DNS configuration for Azure SQL Database and restrict public network access when private connectivity is required.
  3. Authorized privileged users see expected values and restricted users receive masked output under tested permissions.
  4. Configure supported customer-managed TDE protector keys in Azure Key Vault or Managed HSM with required identity permissions and key availability safeguards.
  5. A rotation rehearsal validates the supported key version and the SQL resource retains access after planned key changes.

Explanation

Correct Answers

D:

The reported Azure SQL or SQL Server condition is: An auditor wants evidence that a customer-managed encryption key can be rotated without losing database accessibility. The specific supported administrative response is: Configure supported customer-managed TDE protector keys in Azure Key Vault or Managed HSM with required identity permissions and key availability safeguards. The technical risk is: Key deletion or disabled access can render encrypted databases unavailable despite healthy compute and storage. Confirm the correction with: A rotation rehearsal validates the supported key version and the SQL resource retains access after planned key changes.

E:

The acceptance evidence for this incident (An auditor wants evidence that a customer-managed encryption key can be rotated without losing database accessibility.) is: A rotation rehearsal validates the supported key version and the SQL resource retains access after planned key changes. It directly tests whether the remediation (Configure supported customer-managed TDE protector keys in Azure Key Vault or Managed HSM with required identity permissions and key availability safeguards.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

SQL authentication management on SQL server vms (2.1) addresses another technical failure: Poorly governed shared SQL logins are hard to rotate and can bypass centralized identity lifecycle management. The case states: An auditor wants evidence that a customer-managed encryption key can be rotated without losing database accessibility. The most direct paired action and test is: Configure supported customer-managed TDE protector keys in Azure Key Vault or Managed HSM with required identity permissions and key availability safeguards.

B:

Azure SQL private endpoints and public exposure (2.2) addresses another technical failure: A created private endpoint without correct DNS resolution or network controls can still leave clients using public endpoints or unable to connect. This choice can be useful for that problem, but it does not establish the Customer-managed tde keys in azure key vault (2.2) control being assessed here.

C:

Dynamic data masking limitations (2.3) would demonstrate or implement: Authorized privileged users see expected values and restricted users receive masked output under tested permissions. This case instead tests Customer-managed tde keys in azure key vault (2.2); the choice measures or changes another part of the system.

Question 251

An Azure database administrator observes: A hospital wants selected patient identifiers inaccessible to server-side database administrators. Which action best addresses the specific technical requirement?

  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. Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.
  3. Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.
  4. Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.

Explanation

Correct Answer

A:

The reported Azure SQL or SQL Server condition is: A hospital wants selected patient identifiers inaccessible to server-side database administrators. 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.

Incorrect Answers

B:

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. 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:

Sensitive data classification and discovery (2.3) addresses another technical failure: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. The required corrective action concerns Always encrypted column confidentiality (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 252

During post-change validation, the team reports: A hospital wants selected patient identifiers inaccessible to server-side database administrators. Which observation best demonstrates that the appropriate correction worked?

  1. The classification inventory identifies sensitive columns and its labels match approved data handling requirements.
  2. Approved source clients can connect through expected network paths and unauthorized test addresses are rejected.
  3. A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp.
  4. Client-side encryption tests show protected fields are not revealed as plaintext to unauthorized database administrators while approved clients can use them.

Explanation

Correct Answer

D:

The acceptance evidence for this incident (A hospital wants selected patient identifiers inaccessible to server-side database administrators.) 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

A:

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. The case states: A hospital wants selected patient identifiers inaccessible to server-side database administrators. The most direct evidence is: Client-side encryption tests show protected fields are not revealed as plaintext to unauthorized database administrators while approved clients can use them.

B:

Azure SQL firewall rule scoping (2.2) would demonstrate or implement: Approved source clients can connect through expected network paths and unauthorized test addresses are rejected. 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) would demonstrate or implement: A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp. This case instead tests Always encrypted column confidentiality (2.2); the choice measures or changes another part of the system.

Question 253

An Azure database administrator observes: A payroll application needs column protection beyond database file encryption. Which action best addresses the specific technical requirement?

  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. Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.
  3. Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.
  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 payroll application needs column protection beyond database file encryption. 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.

Incorrect Answers

B:

Sensitive data classification and discovery (2.3) addresses another technical failure: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. 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:

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. This case instead tests Always encrypted column confidentiality (2.2); 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 corrective action concerns Always encrypted column confidentiality (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 254

In a database operations review, a team encounters: A payroll application needs column protection beyond database file encryption. Which failure or exposure is most directly relevant?

  1. Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions.
  2. Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily.
  3. Audit events written only to a disposable or broadly writable destination may be lost or tampered with.
  4. TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support.

Explanation

Correct Answer

D:

The incident (A payroll application needs column protection beyond database file encryption.) most directly exposes: TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support. The resulting safe technical 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. Its verification is: Client-side encryption tests show protected fields are not revealed as plaintext to unauthorized database administrators while approved clients can use them.

Incorrect Answers

A:

Sensitive data classification and discovery (2.3) would demonstrate or implement: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. The case states: A payroll application needs column protection beyond database file encryption. The most direct risk is: TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support.

B:

Azure SQL firewall rule scoping (2.2) would demonstrate or implement: Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily. 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) would demonstrate or implement: 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.

Question 255

An Azure database administrator observes: A driver lacks Always Encrypted support and begins returning ciphertext instead of usable values. Which action best addresses the specific technical requirement?

  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. Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.
  3. Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.
  4. Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.

Explanation

Correct Answer

A:

The reported Azure SQL or SQL Server condition is: A driver lacks Always Encrypted support and begins returning ciphertext instead of usable values. 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.

Incorrect Answers

B:

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. 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:

Sensitive data classification and discovery (2.3) addresses another technical failure: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. The required corrective action concerns Always encrypted column confidentiality (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 256

During post-change validation, the team reports: A driver lacks Always Encrypted support and begins returning ciphertext instead of usable values. Which observation best demonstrates that the appropriate correction worked?

  1. Approved source clients can connect through expected network paths and unauthorized test addresses are rejected.
  2. A controlled access or schema-change event appears in the approved audit store with expected principal and timestamp.
  3. The classification inventory identifies sensitive columns and its labels match approved data handling requirements.
  4. Client-side encryption tests show protected fields are not revealed as plaintext to unauthorized database administrators while approved clients can use them.

Explanation

Correct Answer

D:

The acceptance evidence for this incident (A driver lacks Always Encrypted support and begins returning ciphertext instead of usable values.) 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

A:

Azure SQL firewall rule scoping (2.2) would demonstrate or implement: Approved source clients can connect through expected network paths and unauthorized test addresses are rejected. The case states: A driver lacks Always Encrypted support and begins returning ciphertext instead of usable values. The most direct evidence is: Client-side encryption tests show protected fields are not revealed as plaintext to unauthorized database administrators while approved clients can use them.

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 Always encrypted column confidentiality (2.2) control being assessed here.

C:

Sensitive data classification and discovery (2.3) would demonstrate or implement: The classification inventory identifies sensitive columns and its labels match approved data handling requirements. This case instead tests Always encrypted column confidentiality (2.2); the choice measures or changes another part of the system.

Question 257

An Azure database administrator observes: A schema migration moves encrypted column master keys to a location clients cannot access. Which action best addresses the specific technical requirement?

  1. Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.
  2. Use 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.
  3. Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.
  4. Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: A schema migration moves encrypted column master keys to a location clients cannot access. 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.

Incorrect Answers

A:

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 case states: A schema migration moves encrypted column master keys to a location clients cannot access. The most direct corrective action 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.

C:

Sensitive data classification and discovery (2.3) addresses another technical failure: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. This case instead tests Always encrypted column confidentiality (2.2); 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 corrective action concerns Always encrypted column confidentiality (2.2); a passing result for this alternative could leave that requirement unresolved.

Question 258

In a database operations review, a team encounters: A schema migration moves encrypted column master keys to a location clients cannot access. Which failure or exposure is most directly relevant?

  1. Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions.
  2. Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily.
  3. TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support.
  4. Audit events written only to a disposable or broadly writable destination may be lost or tampered with.

Explanation

Correct Answer

C:

The incident (A schema migration moves encrypted column master keys to a location clients cannot access.) most directly exposes: TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support. The resulting safe technical 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. Its verification is: Client-side encryption tests show protected fields are not revealed as plaintext to unauthorized database administrators while approved clients can use them.

Incorrect Answers

A:

Sensitive data classification and discovery (2.3) would demonstrate or implement: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. The case states: A schema migration moves encrypted column master keys to a location clients cannot access. The most direct risk is: TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support.

B:

Azure SQL firewall rule scoping (2.2) would demonstrate or implement: Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily. This choice can be useful for that problem, but it does not establish the Always encrypted column confidentiality (2.2) control being assessed here.

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

Question 259

An Azure database administrator observes: A team enables TDE and incorrectly claims that queried sensitive columns can no longer be seen by SQL privileged users. Which action best addresses the specific technical requirement?

  1. Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.
  2. Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.
  3. Configure Azure SQL or SQL Server auditing to collect relevant database events into appropriately restricted log destinations with retention controls.
  4. 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.

Explanation

Correct Answer

D:

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.

Incorrect Answers

A:

Sensitive data classification and discovery (2.3) addresses another technical failure: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. The case states: A team enables TDE and incorrectly claims that queried sensitive columns can no longer be seen by SQL privileged users. The most direct corrective action 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.

B:

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. 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.

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.