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 37

Question 360

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

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

Explanation

Correct Answers

D:

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

E:

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

Incorrect Answers

A:

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

B:

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

C:

Always encrypted secure enclave workloads (2.2) would demonstrate or implement: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked. This case instead tests SQL ledger tamper-evidence (2.3); the choice measures or changes another part of the system.

Question 361

An Azure database administrator observes: A database owner reports slow checkout queries but no historical performance measurements exist. Which action best addresses the specific technical requirement?

  1. Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service.
  2. Use Resource Governor where supported on SQL Server or eligible managed configurations to isolate competing workload resources after verifying availability.
  3. Resize supported Azure SQL compute and storage service objectives based on sustained utilization, latency and downtime considerations.
  4. Use Azure Monitor metrics, suitable diagnostic settings, log destinations and alerts to observe Azure SQL resource health and capacity.

Explanation

Correct Answer

A:

The reported Azure SQL or SQL Server condition is: A database owner reports slow checkout queries but no historical performance measurements exist. The specific supported administrative response is: Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service. The technical risk is: Without a baseline, a slow-query complaint cannot be separated reliably from normal variability or a new regression. Confirm the correction with: Before-and-after metrics for a comparable workload window show a measured effect on the requirement.

Incorrect Answers

B:

Resource governor workload classification (3.3) addresses another technical failure: Applying an instance feature to an unsupported Azure SQL database tier or using incorrect classifiers can fail or throttle critical users. This choice can be useful for that problem, but it does not establish the SQL workload performance baselining (3.1) control being assessed here.

C:

Azure SQL compute and storage scaling (3.3) addresses another technical failure: Increasing vCores blindly may not solve throttled log IO or storage bottlenecks and scaling can cause transient failovers. This case instead tests SQL workload performance baselining (3.1); the choice measures or changes another part of the system.

D:

Azure monitor metrics and diagnostic settings (3.1) addresses another technical failure: Platform metrics alone may miss a query-level root cause while unconfigured diagnostics leave gaps in incident history. The required corrective action concerns SQL workload performance baselining (3.1); a passing result for this alternative could leave that requirement unresolved.

Question 362

During post-change validation, the team reports: A database owner reports slow checkout queries but no historical performance measurements exist. Which observation best demonstrates that the appropriate correction worked?

  1. Before-and-after metrics for a comparable workload window show a measured effect on the stated objective.
  2. Before-and-after workload metrics, capacity headroom and connection behavior confirm that the change meets its objective.
  3. A workload classification test shows intended resource limits without starving high-priority connections.
  4. A reproducible resource event appears in the chosen metric or log destination and its threshold generates the intended alert.

Explanation

Correct Answer

A:

The acceptance evidence for this incident (A database owner reports slow checkout queries but no historical performance measurements exist.) is: Before-and-after metrics for a comparable workload window show a measured effect on the requirement. It directly tests whether the remediation (Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

B:

Azure SQL compute and storage scaling (3.3) would demonstrate or implement: Before-and-after workload metrics, capacity headroom and connection behavior confirm that the change meets its objective. This choice can be useful for that problem, but it does not establish the SQL workload performance baselining (3.1) control being assessed here.

C:

Resource governor workload classification (3.3) would demonstrate or implement: A workload classification test shows intended resource limits without starving high-priority connections. This case instead tests SQL workload performance baselining (3.1); the choice measures or changes another part of the system.

D:

Azure monitor metrics and diagnostic settings (3.1) would demonstrate or implement: A reproducible resource event appears in the chosen metric or log destination and its threshold generates the intended alert. The required evidence concerns SQL workload performance baselining (3.1); a passing result for this alternative could leave that requirement unresolved.

Question 363

An Azure database administrator observes: An application receives unpredictable traffic peaks and a DBA needs to establish normal CPU and log-write rates. Which action best addresses the specific technical requirement?

  1. Use Azure Monitor metrics, suitable diagnostic settings, log destinations and alerts to observe Azure SQL resource health and capacity.
  2. Use Resource Governor where supported on SQL Server or eligible managed configurations to isolate competing workload resources after verifying availability.
  3. Resize supported Azure SQL compute and storage service objectives based on sustained utilization, latency and downtime considerations.
  4. Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service.

Explanation

Correct Answer

D:

The reported Azure SQL or SQL Server condition is: An application receives unpredictable traffic peaks and a DBA needs to establish normal CPU and log-write rates. The specific supported administrative response is: Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service. The technical risk is: Without a baseline, a slow-query complaint cannot be separated reliably from normal variability or a new regression. Confirm the correction with: Before-and-after metrics for a comparable workload window show a measured effect on the requirement.

Incorrect Answers

A:

Azure monitor metrics and diagnostic settings (3.1) addresses another technical failure: Platform metrics alone may miss a query-level root cause while unconfigured diagnostics leave gaps in incident history. The case states: An application receives unpredictable traffic peaks and a DBA needs to establish normal CPU and log-write rates. The most direct corrective action is: Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service.

B:

Resource governor workload classification (3.3) addresses another technical failure: Applying an instance feature to an unsupported Azure SQL database tier or using incorrect classifiers can fail or throttle critical users. This choice can be useful for that problem, but it does not establish the SQL workload performance baselining (3.1) control being assessed here.

C:

Azure SQL compute and storage scaling (3.3) addresses another technical failure: Increasing vCores blindly may not solve throttled log IO or storage bottlenecks and scaling can cause transient failovers. This case instead tests SQL workload performance baselining (3.1); the choice measures or changes another part of the system.

Question 364

In a database operations review, a team encounters: An application receives unpredictable traffic peaks and a DBA needs to establish normal CPU and log-write rates. Which failure or exposure is most directly relevant?

  1. Applying an instance feature to an unsupported Azure SQL database tier or using incorrect classifiers can fail or throttle critical users.
  2. Increasing vCores blindly may not solve throttled log IO or storage bottlenecks and scaling can cause transient failovers.
  3. Without a baseline, a slow-query complaint cannot be separated reliably from normal variability or a new regression.
  4. Platform metrics alone may miss a query-level root cause while unconfigured diagnostics leave gaps in incident history.

Explanation

Correct Answer

C:

The incident (An application receives unpredictable traffic peaks and a DBA needs to establish normal CPU and log-write rates.) most directly exposes: Without a baseline, a slow-query complaint cannot be separated reliably from normal variability or a new regression. The resulting safe technical response is: Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service. Its verification is: Before-and-after metrics for a comparable workload window show a measured effect on the requirement.

Incorrect Answers

A:

Resource governor workload classification (3.3) would demonstrate or implement: Applying an instance feature to an unsupported Azure SQL database tier or using incorrect classifiers can fail or throttle critical users. The case states: An application receives unpredictable traffic peaks and a DBA needs to establish normal CPU and log-write rates. The most direct risk is: Without a baseline, a slow-query complaint cannot be separated reliably from normal variability or a new regression.

B:

Azure SQL compute and storage scaling (3.3) would demonstrate or implement: Increasing vCores blindly may not solve throttled log IO or storage bottlenecks and scaling can cause transient failovers. This choice can be useful for that problem, but it does not establish the SQL workload performance baselining (3.1) control being assessed here.

D:

Azure monitor metrics and diagnostic settings (3.1) would demonstrate or implement: Platform metrics alone may miss a query-level root cause while unconfigured diagnostics leave gaps in incident history. The required risk concerns SQL workload performance baselining (3.1); a passing result for this alternative could leave that requirement unresolved.

Question 365

An Azure database administrator observes: An upgrade is planned without collecting transaction latency or throughput baselines. Which action best addresses the specific technical requirement?

  1. Resize supported Azure SQL compute and storage service objectives based on sustained utilization, latency and downtime considerations.
  2. Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service.
  3. Use Azure Monitor metrics, suitable diagnostic settings, log destinations and alerts to observe Azure SQL resource health and capacity.
  4. Use Resource Governor where supported on SQL Server or eligible managed configurations to isolate competing workload resources after verifying availability.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: An upgrade is planned without collecting transaction latency or throughput baselines. The specific supported administrative response is: Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service. The technical risk is: Without a baseline, a slow-query complaint cannot be separated reliably from normal variability or a new regression. Confirm the correction with: Before-and-after metrics for a comparable workload window show a measured effect on the requirement.

Incorrect Answers

A:

Azure SQL compute and storage scaling (3.3) addresses another technical failure: Increasing vCores blindly may not solve throttled log IO or storage bottlenecks and scaling can cause transient failovers. The case states: An upgrade is planned without collecting transaction latency or throughput baselines. The most direct corrective action is: Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service.

C:

Azure monitor metrics and diagnostic settings (3.1) addresses another technical failure: Platform metrics alone may miss a query-level root cause while unconfigured diagnostics leave gaps in incident history. This case instead tests SQL workload performance baselining (3.1); the choice measures or changes another part of the system.

D:

Resource governor workload classification (3.3) addresses another technical failure: Applying an instance feature to an unsupported Azure SQL database tier or using incorrect classifiers can fail or throttle critical users. The required corrective action concerns SQL workload performance baselining (3.1); a passing result for this alternative could leave that requirement unresolved.

Question 366

During post-change validation, the team reports: An upgrade is planned without collecting transaction latency or throughput baselines. Which observation best demonstrates that the appropriate correction worked?

  1. Before-and-after metrics for a comparable workload window show a measured effect on the stated objective.
  2. A reproducible resource event appears in the chosen metric or log destination and its threshold generates the intended alert.
  3. A workload classification test shows intended resource limits without starving high-priority connections.
  4. Before-and-after workload metrics, capacity headroom and connection behavior confirm that the change meets its objective.

Explanation

Correct Answer

A:

The acceptance evidence for this incident (An upgrade is planned without collecting transaction latency or throughput baselines.) is: Before-and-after metrics for a comparable workload window show a measured effect on the requirement. It directly tests whether the remediation (Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

B:

Azure monitor metrics and diagnostic settings (3.1) would demonstrate or implement: A reproducible resource event appears in the chosen metric or log destination and its threshold generates the intended alert. This choice can be useful for that problem, but it does not establish the SQL workload performance baselining (3.1) control being assessed here.

C:

Resource governor workload classification (3.3) would demonstrate or implement: A workload classification test shows intended resource limits without starving high-priority connections. This case instead tests SQL workload performance baselining (3.1); the choice measures or changes another part of the system.

D:

Azure SQL compute and storage scaling (3.3) would demonstrate or implement: Before-and-after workload metrics, capacity headroom and connection behavior confirm that the change meets its objective. The required evidence concerns SQL workload performance baselining (3.1); a passing result for this alternative could leave that requirement unresolved.

Question 367

An Azure database administrator observes: A support team compares weekend idle performance with peak-month-end performance and draws the wrong conclusion. Which action best addresses the specific technical requirement?

  1. Use Resource Governor where supported on SQL Server or eligible managed configurations to isolate competing workload resources after verifying availability.
  2. Use Azure Monitor metrics, suitable diagnostic settings, log destinations and alerts to observe Azure SQL resource health and capacity.
  3. Resize supported Azure SQL compute and storage service objectives based on sustained utilization, latency and downtime considerations.
  4. Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service.

Explanation

Correct Answer

D:

The reported Azure SQL or SQL Server condition is: A support team compares weekend idle performance with peak-month-end performance and draws the wrong conclusion. The specific supported administrative response is: Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service. The technical risk is: Without a baseline, a slow-query complaint cannot be separated reliably from normal variability or a new regression. Confirm the correction with: Before-and-after metrics for a comparable workload window show a measured effect on the requirement.

Incorrect Answers

A:

Resource governor workload classification (3.3) addresses another technical failure: Applying an instance feature to an unsupported Azure SQL database tier or using incorrect classifiers can fail or throttle critical users. The case states: A support team compares weekend idle performance with peak-month-end performance and draws the wrong conclusion. The most direct corrective action is: Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service.

B:

Azure monitor metrics and diagnostic settings (3.1) addresses another technical failure: Platform metrics alone may miss a query-level root cause while unconfigured diagnostics leave gaps in incident history. This choice can be useful for that problem, but it does not establish the SQL workload performance baselining (3.1) control being assessed here.

C:

Azure SQL compute and storage scaling (3.3) addresses another technical failure: Increasing vCores blindly may not solve throttled log IO or storage bottlenecks and scaling can cause transient failovers. This case instead tests SQL workload performance baselining (3.1); the choice measures or changes another part of the system.

Question 368

In a database operations review, a team encounters: A support team compares weekend idle performance with peak-month-end performance and draws the wrong conclusion. Which failure or exposure is most directly relevant?

  1. Without a baseline, a slow-query complaint cannot be separated reliably from normal variability or a new regression.
  2. Increasing vCores blindly may not solve throttled log IO or storage bottlenecks and scaling can cause transient failovers.
  3. Applying an instance feature to an unsupported Azure SQL database tier or using incorrect classifiers can fail or throttle critical users.
  4. Platform metrics alone may miss a query-level root cause while unconfigured diagnostics leave gaps in incident history.

Explanation

Correct Answer

A:

The incident (A support team compares weekend idle performance with peak-month-end performance and draws the wrong conclusion.) most directly exposes: Without a baseline, a slow-query complaint cannot be separated reliably from normal variability or a new regression. The resulting safe technical response is: Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service. Its verification is: Before-and-after metrics for a comparable workload window show a measured effect on the requirement.

Incorrect Answers

B:

Azure SQL compute and storage scaling (3.3) would demonstrate or implement: Increasing vCores blindly may not solve throttled log IO or storage bottlenecks and scaling can cause transient failovers. This choice can be useful for that problem, but it does not establish the SQL workload performance baselining (3.1) control being assessed here.

C:

Resource governor workload classification (3.3) would demonstrate or implement: Applying an instance feature to an unsupported Azure SQL database tier or using incorrect classifiers can fail or throttle critical users. This case instead tests SQL workload performance baselining (3.1); the choice measures or changes another part of the system.

D:

Azure monitor metrics and diagnostic settings (3.1) would demonstrate or implement: Platform metrics alone may miss a query-level root cause while unconfigured diagnostics leave gaps in incident history. The required risk concerns SQL workload performance baselining (3.1); a passing result for this alternative could leave that requirement unresolved.

Question 369

An Azure database administrator observes: A migration to Azure SQL needs a baseline for validating post-cutover query response times. Which action best addresses the specific technical requirement?

  1. Use Azure Monitor metrics, suitable diagnostic settings, log destinations and alerts to observe Azure SQL resource health and capacity.
  2. Resize supported Azure SQL compute and storage service objectives based on sustained utilization, latency and downtime considerations.
  3. Use Resource Governor where supported on SQL Server or eligible managed configurations to isolate competing workload resources after verifying availability.
  4. Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service.

Explanation

Correct Answer

D:

The reported Azure SQL or SQL Server condition is: A migration to Azure SQL needs a baseline for validating post-cutover query response times. The specific supported administrative response is: Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service. The technical risk is: Without a baseline, a slow-query complaint cannot be separated reliably from normal variability or a new regression. Confirm the correction with: Before-and-after metrics for a comparable workload window show a measured effect on the requirement.

Incorrect Answers

A:

Azure monitor metrics and diagnostic settings (3.1) addresses another technical failure: Platform metrics alone may miss a query-level root cause while unconfigured diagnostics leave gaps in incident history. The case states: A migration to Azure SQL needs a baseline for validating post-cutover query response times. The most direct evidence is: Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service.

B:

Azure SQL compute and storage scaling (3.3) addresses another technical failure: Increasing vCores blindly may not solve throttled log IO or storage bottlenecks and scaling can cause transient failovers. This choice can be useful for that problem, but it does not establish the SQL workload performance baselining (3.1) control being assessed here.

C:

Resource governor workload classification (3.3) addresses another technical failure: Applying an instance feature to an unsupported Azure SQL database tier or using incorrect classifiers can fail or throttle critical users. This case instead tests SQL workload performance baselining (3.1); the choice measures or changes another part of the system.

Question 370

An Azure SQL operations team investigates: A migration to Azure SQL needs a baseline for validating post-cutover query response times. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. Resize supported Azure SQL compute and storage service objectives based on sustained utilization, latency and downtime considerations.
  2. Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service.
  3. A workload classification test shows intended resource limits without starving high-priority connections.
  4. Use Azure Monitor metrics, suitable diagnostic settings, log destinations and alerts to observe Azure SQL resource health and capacity.
  5. Before-and-after metrics for a comparable workload window show a measured effect on the stated objective.

Explanation

Correct Answers

B:

The reported Azure SQL or SQL Server condition is: A migration to Azure SQL needs a baseline for validating post-cutover query response times. The specific supported administrative response is: Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service. The technical risk is: Without a baseline, a slow-query complaint cannot be separated reliably from normal variability or a new regression. Confirm the correction with: Before-and-after metrics for a comparable workload window show a measured effect on the requirement.

E:

The acceptance evidence for this incident (A migration to Azure SQL needs a baseline for validating post-cutover query response times.) is: Before-and-after metrics for a comparable workload window show a measured effect on the requirement. It directly tests whether the remediation (Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

Azure SQL compute and storage scaling (3.3) addresses another technical failure: Increasing vCores blindly may not solve throttled log IO or storage bottlenecks and scaling can cause transient failovers. The case states: A migration to Azure SQL needs a baseline for validating post-cutover query response times. The most direct paired action and test is: Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service.

C:

Resource governor workload classification (3.3) would demonstrate or implement: A workload classification test shows intended resource limits without starving high-priority connections. This case instead tests SQL workload performance baselining (3.1); the choice measures or changes another part of the system.

D:

Azure monitor metrics and diagnostic settings (3.1) addresses another technical failure: Platform metrics alone may miss a query-level root cause while unconfigured diagnostics leave gaps in incident history. The required paired action and test concerns SQL workload performance baselining (3.1); a passing result for this alternative could leave that requirement unresolved.