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 34

Question 330

An Azure SQL operations team investigates: A database team needs to demonstrate which roles see masked results without assuming it prevents all data inference. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. Use supported dynamic data masking for low-privilege query-result obfuscation while enforcing true authorization separately.
  2. An approved SQL client validates the intended server certificate and rejects an untrusted endpoint during a controlled test.
  3. Authorized privileged users see expected values and restricted users receive masked output under tested permissions.
  4. Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.
  5. Maintain SQL login configuration and password policy appropriately on SQL Server installations that support SQL authentication and coordinate with directory alternatives.

Explanation

Correct Answers

A:

The reported Azure SQL or SQL Server condition is: A database team needs to demonstrate which roles see masked results without assuming it prevents all data inference. The specific supported administrative response is: Use supported dynamic data masking for low-privilege query-result obfuscation while enforcing true authorization separately. The technical risk is: Dynamic data masking is not encryption or a complete barrier against inference by a user able to query data. Confirm the correction with: Authorized privileged users see expected values and restricted users receive masked output under tested permissions.

C:

The acceptance evidence for this incident (A database team needs to demonstrate which roles see masked results without assuming it prevents all data inference.) is: Authorized privileged users see expected values and restricted users receive masked output under tested permissions. It directly tests whether the remediation (Use supported dynamic data masking for low-privilege query-result obfuscation while enforcing true authorization separately.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

B:

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 choice can be useful for that problem, but it does not establish the Dynamic data masking limitations (2.3) control being assessed here.

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 paired action and test concerns Dynamic data masking limitations (2.3); a passing result for this alternative could leave that requirement unresolved.

E:

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 paired-answer requirement concerns Dynamic data masking limitations (2.3); this alternative does not provide the matching intervention and separate acceptance evidence.

Question 331

An Azure database administrator observes: A multi-tenant orders table allows users from one tenant to retrieve another tenant's invoices. Which action best addresses the specific technical requirement?

  1. Use schema ownership, object-level GRANT, DENY and appropriate role membership to control SQL access consistently.
  2. Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.
  3. Use custom database roles and targeted GRANT or REVOKE permissions instead of broad administrative memberships.
  4. Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.

Explanation

Correct Answer

D:

The reported Azure SQL or SQL Server condition is: A multi-tenant orders table allows users from one tenant to retrieve another tenant's invoices. The specific supported administrative response is: Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context. The technical risk is: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. Confirm the correction with: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records.

Incorrect Answers

A:

Database object ownership and schema authorization (2.1) addresses another technical failure: Granting broad table permissions for a narrow reporting requirement can expose unrelated sensitive objects. The case states: A multi-tenant orders table allows users from one tenant to retrieve another tenant's invoices. The most direct corrective action is: Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.

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 Row-level security with session predicates (2.3) control being assessed here.

C:

Least-privilege database roles and grants (2.1) addresses another technical failure: Giving every application db_owner or server-wide authority expands the blast radius of compromised credentials. This case instead tests Row-level security with session predicates (2.3); the choice measures or changes another part of the system.

Question 332

During post-change validation, the team reports: A multi-tenant orders table allows users from one tenant to retrieve another tenant's invoices. Which observation best demonstrates that the appropriate correction worked?

  1. A permission check proves only the intended schema or table actions succeed for the dedicated workload identity.
  2. Database effective-permission tests confirm view and procedure access while disallowed base-table operations fail.
  3. The classification inventory identifies sensitive columns and its labels match approved data handling requirements.
  4. Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records.

Explanation

Correct Answer

D:

The acceptance evidence for this incident (A multi-tenant orders table allows users from one tenant to retrieve another tenant's invoices.) is: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records. It directly tests whether the remediation (Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

Least-privilege database roles and grants (2.1) would demonstrate or implement: A permission check proves only the intended schema or table actions succeed for the dedicated workload identity. The case states: A multi-tenant orders table allows users from one tenant to retrieve another tenant's invoices. The most direct evidence is: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records.

B:

Database object ownership and schema authorization (2.1) would demonstrate or implement: Database effective-permission tests confirm view and procedure access while disallowed base-table operations fail. This choice can be useful for that problem, but it does not establish the Row-level security with session predicates (2.3) 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 Row-level security with session predicates (2.3); the choice measures or changes another part of the system.

Question 333

An Azure database administrator observes: A developer filters account IDs in the web API but an export job queries the same table directly. Which action best addresses the specific technical requirement?

  1. Use schema ownership, object-level GRANT, DENY and appropriate role membership to control SQL access consistently.
  2. Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.
  3. Use custom database roles and targeted GRANT or REVOKE permissions instead of broad administrative memberships.
  4. Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.

Explanation

Correct Answer

D:

The reported Azure SQL or SQL Server condition is: A developer filters account IDs in the web API but an export job queries the same table directly. The specific supported administrative response is: Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context. The technical risk is: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. Confirm the correction with: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records.

Incorrect Answers

A:

Database object ownership and schema authorization (2.1) addresses another technical failure: Granting broad table permissions for a narrow reporting requirement can expose unrelated sensitive objects. The case states: A developer filters account IDs in the web API but an export job queries the same table directly. The most direct corrective action is: Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.

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 Row-level security with session predicates (2.3) control being assessed here.

C:

Least-privilege database roles and grants (2.1) addresses another technical failure: Giving every application db_owner or server-wide authority expands the blast radius of compromised credentials. This case instead tests Row-level security with session predicates (2.3); the choice measures or changes another part of the system.

Question 334

In a database operations review, a team encounters: A developer filters account IDs in the web API but an export job queries the same table directly. Which failure or exposure is most directly relevant?

  1. Granting broad table permissions for a narrow reporting requirement can expose unrelated sensitive objects.
  2. Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools.
  3. Giving every application db_owner or server-wide authority expands the blast radius of compromised credentials.
  4. Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions.

Explanation

Correct Answer

B:

The incident (A developer filters account IDs in the web API but an export job queries the same table directly.) most directly exposes: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. The resulting safe technical response is: Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context. Its verification is: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records.

Incorrect Answers

A:

Database object ownership and schema authorization (2.1) would demonstrate or implement: Granting broad table permissions for a narrow reporting requirement can expose unrelated sensitive objects. The case states: A developer filters account IDs in the web API but an export job queries the same table directly. The most direct risk is: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools.

C:

Least-privilege database roles and grants (2.1) would demonstrate or implement: Giving every application db_owner or server-wide authority expands the blast radius of compromised credentials. This case instead tests Row-level security with session predicates (2.3); the choice measures or changes another part of the system.

D:

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 required risk concerns Row-level security with session predicates (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 335

An Azure database administrator observes: A row-level security predicate accidentally grants access when the session tenant context is missing. Which action best addresses the specific technical requirement?

  1. Use schema ownership, object-level GRANT, DENY and appropriate role membership to control SQL access consistently.
  2. Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.
  3. Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.
  4. Use custom database roles and targeted GRANT or REVOKE permissions instead of broad administrative memberships.

Explanation

Correct Answer

C:

The reported Azure SQL or SQL Server condition is: A row-level security predicate accidentally grants access when the session tenant context is missing. The specific supported administrative response is: Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context. The technical risk is: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. Confirm the correction with: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records.

Incorrect Answers

A:

Database object ownership and schema authorization (2.1) addresses another technical failure: Granting broad table permissions for a narrow reporting requirement can expose unrelated sensitive objects. The case states: A row-level security predicate accidentally grants access when the session tenant context is missing. The most direct corrective action is: Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.

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 Row-level security with session predicates (2.3) control being assessed here.

D:

Least-privilege database roles and grants (2.1) addresses another technical failure: Giving every application db_owner or server-wide authority expands the blast radius of compromised credentials. The required corrective action concerns Row-level security with session predicates (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 336

During post-change validation, the team reports: A row-level security predicate accidentally grants access when the session tenant context is missing. Which observation best demonstrates that the appropriate correction worked?

  1. A permission check proves only the intended schema or table actions succeed for the dedicated workload identity.
  2. Database effective-permission tests confirm view and procedure access while disallowed base-table operations fail.
  3. The classification inventory identifies sensitive columns and its labels match approved data handling requirements.
  4. Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records.

Explanation

Correct Answer

D:

The acceptance evidence for this incident (A row-level security predicate accidentally grants access when the session tenant context is missing.) is: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records. It directly tests whether the remediation (Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

Least-privilege database roles and grants (2.1) would demonstrate or implement: A permission check proves only the intended schema or table actions succeed for the dedicated workload identity. The case states: A row-level security predicate accidentally grants access when the session tenant context is missing. The most direct evidence is: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records.

B:

Database object ownership and schema authorization (2.1) would demonstrate or implement: Database effective-permission tests confirm view and procedure access while disallowed base-table operations fail. This choice can be useful for that problem, but it does not establish the Row-level security with session predicates (2.3) 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 Row-level security with session predicates (2.3); the choice measures or changes another part of the system.

Question 337

An Azure database administrator observes: An administrator wants a database-enforced policy for tenant separation independent of UI filters. 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. Use custom database roles and targeted GRANT or REVOKE permissions instead of broad administrative memberships.
  4. Use schema ownership, object-level GRANT, DENY and appropriate role membership to control SQL access consistently.

Explanation

Correct Answer

A:

The reported Azure SQL or SQL Server condition is: An administrator wants a database-enforced policy for tenant separation independent of UI filters. The specific supported administrative response is: Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context. The technical risk is: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. Confirm the correction with: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records.

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 Row-level security with session predicates (2.3) control being assessed here.

C:

Least-privilege database roles and grants (2.1) addresses another technical failure: Giving every application db_owner or server-wide authority expands the blast radius of compromised credentials. This case instead tests Row-level security with session predicates (2.3); the choice measures or changes another part of the system.

D:

Database object ownership and schema authorization (2.1) addresses another technical failure: Granting broad table permissions for a narrow reporting requirement can expose unrelated sensitive objects. The required corrective action concerns Row-level security with session predicates (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 338

In a database operations review, a team encounters: An administrator wants a database-enforced policy for tenant separation independent of UI filters. 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. Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools.
  3. Giving every application db_owner or server-wide authority expands the blast radius of compromised credentials.
  4. Granting broad table permissions for a narrow reporting requirement can expose unrelated sensitive objects.

Explanation

Correct Answer

B:

The incident (An administrator wants a database-enforced policy for tenant separation independent of UI filters.) most directly exposes: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. The resulting safe technical response is: Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context. Its verification is: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records.

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: An administrator wants a database-enforced policy for tenant separation independent of UI filters. The most direct risk is: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools.

C:

Least-privilege database roles and grants (2.1) would demonstrate or implement: Giving every application db_owner or server-wide authority expands the blast radius of compromised credentials. This case instead tests Row-level security with session predicates (2.3); the choice measures or changes another part of the system.

D:

Database object ownership and schema authorization (2.1) would demonstrate or implement: Granting broad table permissions for a narrow reporting requirement can expose unrelated sensitive objects. The required risk concerns Row-level security with session predicates (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 339

An Azure database administrator observes: A reporting identity changes session context and unexpectedly sees rows from an unrelated tenant. 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. Use custom database roles and targeted GRANT or REVOKE permissions instead of broad administrative memberships.
  3. Use schema ownership, object-level GRANT, DENY and appropriate role membership to control SQL access consistently.
  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 reporting identity changes session context and unexpectedly sees rows from an unrelated tenant. The specific supported administrative response is: Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context. The technical risk is: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. Confirm the correction with: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records.

Incorrect Answers

B:

Least-privilege database roles and grants (2.1) addresses another technical failure: Giving every application db_owner or server-wide authority expands the blast radius of compromised credentials. This choice can be useful for that problem, but it does not establish the Row-level security with session predicates (2.3) control being assessed here.

C:

Database object ownership and schema authorization (2.1) addresses another technical failure: Granting broad table permissions for a narrow reporting requirement can expose unrelated sensitive objects. This case instead tests Row-level security with session predicates (2.3); 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 Row-level security with session predicates (2.3); a passing result for this alternative could leave that requirement unresolved.

Question 340

An Azure SQL operations team investigates: A reporting identity changes session context and unexpectedly sees rows from an unrelated tenant. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records.
  2. Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.
  3. Use schema ownership, object-level GRANT, DENY and appropriate role membership to control SQL access consistently.
  4. Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.
  5. A permission check proves only the intended schema or table actions succeed for the dedicated workload identity.

Explanation

Correct Answers

A:

The acceptance evidence for this incident (A reporting identity changes session context and unexpectedly sees rows from an unrelated tenant.) is: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records. It directly tests whether the remediation (Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.) solves the specified issue, instead of proving an unrelated database control works.

B:

The reported Azure SQL or SQL Server condition is: A reporting identity changes session context and unexpectedly sees rows from an unrelated tenant. The specific supported administrative response is: Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context. The technical risk is: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. Confirm the correction with: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records.

Incorrect Answers

C:

Database object ownership and schema authorization (2.1) addresses another technical failure: Granting broad table permissions for a narrow reporting requirement can expose unrelated sensitive objects. This case instead tests Row-level security with session predicates (2.3); 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 paired action and test concerns Row-level security with session predicates (2.3); a passing result for this alternative could leave that requirement unresolved.

E:

Least-privilege database roles and grants (2.1) would demonstrate or implement: A permission check proves only the intended schema or table actions succeed for the dedicated workload identity. The paired-answer requirement concerns Row-level security with session predicates (2.3); this alternative does not provide the matching intervention and separate acceptance evidence.