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 32

Question 310

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

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

Explanation

Correct Answers

A:

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

B:

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

Incorrect Answers

C:

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

D:

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

E:

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

Question 311

An Azure database administrator observes: A customer database has credit card fields with no recorded sensitivity classification. Which action best addresses the specific technical requirement?

  1. Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.
  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. 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

B:

The reported Azure SQL or SQL Server condition is: A customer database has credit card fields with no recorded sensitivity classification. The specific supported administrative response is: Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners. The technical risk is: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. Confirm the correction with: The classification inventory identifies sensitive columns and its labels match approved data handling requirements.

Incorrect Answers

A:

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 case states: A customer database has credit card fields with no recorded sensitivity classification. The most direct corrective action is: Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.

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 Sensitive data classification and discovery (2.3); the choice measures or changes another part of the system.

D:

Always encrypted column confidentiality (2.2) addresses another technical failure: TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support. The required corrective action concerns Sensitive data classification and discovery (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 312

During post-change validation, the team reports: A customer database has credit card fields with no recorded sensitivity classification. Which observation best demonstrates that the appropriate correction worked?

  1. Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records.
  2. Client-side encryption tests show protected fields are not revealed as plaintext to unauthorized database administrators while approved clients can use them.
  3. The classification inventory identifies sensitive columns and its labels match approved data handling requirements.
  4. Approved source clients can connect through expected network paths and unauthorized test addresses are rejected.

Explanation

Correct Answer

C:

The acceptance evidence for this incident (A customer database has credit card fields with no recorded sensitivity classification.) is: The classification inventory identifies sensitive columns and its labels match approved data handling requirements. It directly tests whether the remediation (Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

Row-level security with session predicates (2.3) would demonstrate or implement: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records. The case states: A customer database has credit card fields with no recorded sensitivity classification. The most direct evidence is: The classification inventory identifies sensitive columns and its labels match approved data handling requirements.

B:

Always encrypted column confidentiality (2.2) would demonstrate or implement: Client-side encryption tests show protected fields are not revealed as plaintext to unauthorized database administrators while approved clients can use them. This choice can be useful for that problem, but it does not establish the Sensitive data classification and discovery (2.3) control being assessed here.

D:

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 required evidence concerns Sensitive data classification and discovery (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 313

An Azure database administrator observes: An operations team relies only on table names to infer which columns contain personal data. 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. Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: An operations team relies only on table names to infer which columns contain personal data. The specific supported administrative response is: Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners. The technical risk is: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. Confirm the correction with: The classification inventory identifies sensitive columns and its labels match approved data handling requirements.

Incorrect Answers

A:

Always encrypted column confidentiality (2.2) addresses another technical failure: TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support. The case states: An operations team relies only on table names to infer which columns contain personal data. The most direct corrective action is: Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.

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 Sensitive data classification and discovery (2.3); the choice measures or changes another part of the system.

D:

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

Question 314

In a database operations review, a team encounters: An operations team relies only on table names to infer which columns contain personal data. Which failure or exposure is most directly relevant?

  1. Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools.
  2. Allowing every public Azure IP or all internet clients to connect widens access to the SQL endpoint unnecessarily.
  3. Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions.
  4. TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support.

Explanation

Correct Answer

C:

The incident (An operations team relies only on table names to infer which columns contain personal data.) most directly exposes: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. The resulting safe technical response is: Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners. Its verification is: The classification inventory identifies sensitive columns and its labels match approved data handling requirements.

Incorrect Answers

A:

Row-level security with session predicates (2.3) would demonstrate or implement: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. The case states: An operations team relies only on table names to infer which columns contain personal data. The most direct risk is: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions.

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 Sensitive data classification and discovery (2.3) control being assessed here.

D:

Always encrypted column confidentiality (2.2) would demonstrate or implement: TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support. The required risk concerns Sensitive data classification and discovery (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 315

An Azure database administrator observes: A DBA wants to document the business owner and sensitivity of a national identifier column. 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. Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.
  3. Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.
  4. Use 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

A:

The reported Azure SQL or SQL Server condition is: A DBA wants to document the business owner and sensitivity of a national identifier column. The specific supported administrative response is: Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners. The technical risk is: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. Confirm the correction with: The classification inventory identifies sensitive columns and its labels match approved data handling requirements.

Incorrect Answers

B:

Row-level security with session predicates (2.3) addresses another technical failure: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. This choice can be useful for that problem, but it does not establish the Sensitive data classification and discovery (2.3) 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 Sensitive data classification and discovery (2.3); the choice measures or changes another part of the system.

D:

Always encrypted column confidentiality (2.2) addresses another technical failure: TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support. The required corrective action concerns Sensitive data classification and discovery (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 316

During post-change validation, the team reports: A DBA wants to document the business owner and sensitivity of a national identifier column. Which observation best demonstrates that the appropriate correction worked?

  1. Client-side encryption tests show protected fields are not revealed as plaintext to unauthorized database administrators while approved clients can use them.
  2. The classification inventory identifies sensitive columns and its labels match approved data handling requirements.
  3. Approved source clients can connect through expected network paths and unauthorized test addresses are rejected.
  4. Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records.

Explanation

Correct Answer

B:

The acceptance evidence for this incident (A DBA wants to document the business owner and sensitivity of a national identifier column.) is: The classification inventory identifies sensitive columns and its labels match approved data handling requirements. It directly tests whether the remediation (Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

Always encrypted column confidentiality (2.2) would demonstrate or implement: Client-side encryption tests show protected fields are not revealed as plaintext to unauthorized database administrators while approved clients can use them. The case states: A DBA wants to document the business owner and sensitivity of a national identifier column. The most direct evidence is: The classification inventory identifies sensitive columns and its labels match approved data handling requirements.

C:

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 case instead tests Sensitive data classification and discovery (2.3); the choice measures or changes another part of the system.

D:

Row-level security with session predicates (2.3) would demonstrate or implement: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records. The required evidence concerns Sensitive data classification and discovery (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 317

An Azure database administrator observes: A security dashboard flags newly added sensitive fields that have not been reviewed. 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. Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.
  3. Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.
  4. Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.

Explanation

Correct Answer

D:

The reported Azure SQL or SQL Server condition is: A security dashboard flags newly added sensitive fields that have not been reviewed. The specific supported administrative response is: Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners. The technical risk is: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. Confirm the correction with: The classification inventory identifies sensitive columns and its labels match approved data handling requirements.

Incorrect Answers

A:

Always encrypted column confidentiality (2.2) addresses another technical failure: TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support. The case states: A security dashboard flags newly added sensitive fields that have not been reviewed. The most direct corrective action is: Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.

B:

Row-level security with session predicates (2.3) addresses another technical failure: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. This choice can be useful for that problem, but it does not establish the Sensitive data classification and discovery (2.3) 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 Sensitive data classification and discovery (2.3); the choice measures or changes another part of the system.

Question 318

In a database operations review, a team encounters: A security dashboard flags newly added sensitive fields that have not been reviewed. Which failure or exposure is most directly relevant?

  1. Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools.
  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. Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions.

Explanation

Correct Answer

D:

The incident (A security dashboard flags newly added sensitive fields that have not been reviewed.) most directly exposes: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. The resulting safe technical response is: Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners. Its verification is: The classification inventory identifies sensitive columns and its labels match approved data handling requirements.

Incorrect Answers

A:

Row-level security with session predicates (2.3) would demonstrate or implement: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. The case states: A security dashboard flags newly added sensitive fields that have not been reviewed. The most direct risk is: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions.

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 Sensitive data classification and discovery (2.3) control being assessed here.

C:

Always encrypted column confidentiality (2.2) would demonstrate or implement: TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support. This case instead tests Sensitive data classification and discovery (2.3); the choice measures or changes another part of the system.

Question 319

An Azure database administrator observes: An audit needs consistent data labels before configuring role-based masking and export restrictions. 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. 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. Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.
  4. Apply Azure SQL server-level or database-level firewall controls with least-privilege source ranges and verify interaction with network access policy.

Explanation

Correct Answer

A:

The reported Azure SQL or SQL Server condition is: An audit needs consistent data labels before configuring role-based masking and export restrictions. The specific supported administrative response is: Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners. The technical risk is: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. Confirm the correction with: The classification inventory identifies sensitive columns and its labels match approved data handling requirements.

Incorrect Answers

B:

Always encrypted column confidentiality (2.2) addresses another technical failure: TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support. This choice can be useful for that problem, but it does not establish the Sensitive data classification and discovery (2.3) control being assessed here.

C:

Row-level security with session predicates (2.3) addresses another technical failure: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. This case instead tests Sensitive data classification and discovery (2.3); 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 corrective action concerns Sensitive data classification and discovery (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 320

An Azure SQL operations team investigates: An audit needs consistent data labels before configuring role-based masking and export restrictions. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. Approved source clients can connect through expected network paths and unauthorized test addresses are rejected.
  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. Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.
  5. The classification inventory identifies sensitive columns and its labels match approved data handling requirements.

Explanation

Correct Answers

C:

The reported Azure SQL or SQL Server condition is: An audit needs consistent data labels before configuring role-based masking and export restrictions. The specific supported administrative response is: Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners. The technical risk is: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. Confirm the correction with: The classification inventory identifies sensitive columns and its labels match approved data handling requirements.

E:

The acceptance evidence for this incident (An audit needs consistent data labels before configuring role-based masking and export restrictions.) is: The classification inventory identifies sensitive columns and its labels match approved data handling requirements. It directly tests whether the remediation (Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.) 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: An audit needs consistent data labels before configuring role-based masking and export restrictions. The most direct paired action and test is: Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.

B:

Always encrypted column confidentiality (2.2) addresses another technical failure: TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support. This choice can be useful for that problem, but it does not establish the Sensitive data classification and discovery (2.3) control being assessed here.

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 Sensitive data classification and discovery (2.3); a passing result for this alternative could leave that requirement unresolved.