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 57

Question 560

An Azure SQL operations team investigates: A service owner needs to validate the cost and performance trade-offs of a higher Azure SQL service objective. 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. The revised plan and measured reads show the intended operator change with correct query results.
  3. Use Query Store runtime history and plan records to identify regressed queries and consider supported plan forcing when justified.
  4. Before-and-after workload metrics, capacity headroom and connection behavior confirm that the change meets its objective.
  5. Maintain optimizer statistics with appropriate auto-update settings or targeted updates when actual data distribution changes warrant it.

Explanation

Correct Answers

A:

The reported Azure SQL or SQL Server condition is: A service owner needs to validate the cost and performance trade-offs of a higher Azure SQL service objective. The specific supported administrative response is: Resize supported Azure SQL compute and storage service objectives based on sustained utilization, latency and downtime considerations. The technical risk is: Increasing vCores blindly may not solve throttled log IO or storage bottlenecks and scaling can cause transient failovers. Confirm the correction with: Before-and-after workload metrics, capacity headroom and connection behavior confirm that the change meets its objective.

D:

The acceptance evidence for this incident (A service owner needs to validate the cost and performance trade-offs of a higher Azure SQL service objective.) is: Before-and-after workload metrics, capacity headroom and connection behavior confirm that the change meets its objective. It directly tests whether the remediation (Resize supported Azure SQL compute and storage service objectives based on sustained utilization, latency and downtime considerations.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

B:

Execution plan scans and cardinality estimation (3.2) would demonstrate or implement: The revised plan and measured reads show the intended operator change with correct query results. This choice can be useful for that problem, but it does not establish the Azure SQL compute and storage scaling (3.3) control being assessed here.

C:

Query store performance regressions (3.2) addresses another technical failure: Changing server compute before checking a new inefficient execution plan can mask a query-level regression. This case instead tests Azure SQL compute and storage scaling (3.3); the choice measures or changes another part of the system.

E:

Statistics maintenance and cardinality accuracy (3.3) addresses another technical failure: Stale histograms can lead to poor row estimates and inefficient plan choices even with appropriate indexes. The paired-answer requirement concerns Azure SQL compute and storage scaling (3.3); this alternative does not provide the matching intervention and separate acceptance evidence.

Question 561

An Azure database administrator observes: A SQL Server VM runs weekly index maintenance manually and the DBA wants a reliable schedule. Which action best addresses the specific technical requirement?

  1. Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.
  2. For SQL database in Microsoft Fabric, use supported Fabric pipelines, notebooks or recurring orchestration rather than assuming a traditional SQL Server Agent service.
  3. Configure supported SQL Server Agent alerts, operators and notification mechanisms for important job failures or database conditions.
  4. Use Azure CLI with explicit account, subscription, resource-group and SQL database parameters to automate approved SQL deployments.

Explanation

Correct Answer

A:

The reported Azure SQL or SQL Server condition is: A SQL Server VM runs weekly index maintenance manually and the DBA wants a reliable schedule. The specific supported administrative response is: Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance. The technical risk is: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. Confirm the correction with: Job history records successful scheduled execution and its effect on the intended target database.

Incorrect Answers

B:

Fabric SQL database pipelines and recurring tasks (4.3) addresses another technical failure: Moving automation from SQL Server to a Fabric-managed SQL database without adapting its scheduling mechanism can leave tasks unexecuted. This choice can be useful for that problem, but it does not establish the SQL server agent maintenance job schedules (4.1) control being assessed here.

C:

SQL agent job alerts and operator notifications (4.1) addresses another technical failure: A job can fail repeatedly without incident response if its failure status is not routed to a responsible operator. This case instead tests SQL server agent maintenance job schedules (4.1); the choice measures or changes another part of the system.

D:

Azure cli SQL resource provisioning (4.2) addresses another technical failure: A command without correct scope can deploy resources to the wrong region or subscription despite succeeding. The required corrective action concerns SQL server agent maintenance job schedules (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 562

During post-change validation, the team reports: A SQL Server VM runs weekly index maintenance manually and the DBA wants a reliable schedule. Which observation best demonstrates that the appropriate correction worked?

  1. Job history records successful scheduled execution and its effect on the intended target database.
  2. The Fabric pipeline or scheduled task runs against the intended database and its status is visible in the Fabric monitoring experience.
  3. A controlled failed job sends the expected notification and records the error in job history.
  4. CLI output and an independent resource readback confirm the database was created with intended settings.

Explanation

Correct Answer

A:

The acceptance evidence for this incident (A SQL Server VM runs weekly index maintenance manually and the DBA wants a reliable schedule.) is: Job history records successful scheduled execution and its effect on the intended target database. It directly tests whether the remediation (Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

B:

Fabric SQL database pipelines and recurring tasks (4.3) would demonstrate or implement: The Fabric pipeline or scheduled task runs against the intended database and its status is visible in the Fabric monitoring experience. This choice can be useful for that problem, but it does not establish the SQL server agent maintenance job schedules (4.1) control being assessed here.

C:

SQL agent job alerts and operator notifications (4.1) would demonstrate or implement: A controlled failed job sends the expected notification and records the error in job history. This case instead tests SQL server agent maintenance job schedules (4.1); the choice measures or changes another part of the system.

D:

Azure cli SQL resource provisioning (4.2) would demonstrate or implement: CLI output and an independent resource readback confirm the database was created with intended settings. The required evidence concerns SQL server agent maintenance job schedules (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 563

An Azure database administrator observes: An administrator creates a SQL Agent job on an Azure SQL Database logical server and cannot find the agent. Which action best addresses the specific technical requirement?

  1. Use Azure CLI with explicit account, subscription, resource-group and SQL database parameters to automate approved SQL deployments.
  2. Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.
  3. Configure supported SQL Server Agent alerts, operators and notification mechanisms for important job failures or database conditions.
  4. For SQL database in Microsoft Fabric, use supported Fabric pipelines, notebooks or recurring orchestration rather than assuming a traditional SQL Server Agent service.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: An administrator creates a SQL Agent job on an Azure SQL Database logical server and cannot find the agent. The specific supported administrative response is: Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance. The technical risk is: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. Confirm the correction with: Job history records successful scheduled execution and its effect on the intended target database.

Incorrect Answers

A:

Azure cli SQL resource provisioning (4.2) addresses another technical failure: A command without correct scope can deploy resources to the wrong region or subscription despite succeeding. The case states: An administrator creates a SQL Agent job on an Azure SQL Database logical server and cannot find the agent. The most direct corrective action is: Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.

C:

SQL agent job alerts and operator notifications (4.1) addresses another technical failure: A job can fail repeatedly without incident response if its failure status is not routed to a responsible operator. This case instead tests SQL server agent maintenance job schedules (4.1); the choice measures or changes another part of the system.

D:

Fabric SQL database pipelines and recurring tasks (4.3) addresses another technical failure: Moving automation from SQL Server to a Fabric-managed SQL database without adapting its scheduling mechanism can leave tasks unexecuted. The required corrective action concerns SQL server agent maintenance job schedules (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 564

In a database operations review, a team encounters: An administrator creates a SQL Agent job on an Azure SQL Database logical server and cannot find the agent. Which failure or exposure is most directly relevant?

  1. Moving automation from SQL Server to a Fabric-managed SQL database without adapting its scheduling mechanism can leave tasks unexecuted.
  2. A job can fail repeatedly without incident response if its failure status is not routed to a responsible operator.
  3. Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed.
  4. A command without correct scope can deploy resources to the wrong region or subscription despite succeeding.

Explanation

Correct Answer

C:

The incident (An administrator creates a SQL Agent job on an Azure SQL Database logical server and cannot find the agent.) most directly exposes: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. The resulting safe technical response is: Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance. Its verification is: Job history records successful scheduled execution and its effect on the intended target database.

Incorrect Answers

A:

Fabric SQL database pipelines and recurring tasks (4.3) would demonstrate or implement: Moving automation from SQL Server to a Fabric-managed SQL database without adapting its scheduling mechanism can leave tasks unexecuted. The case states: An administrator creates a SQL Agent job on an Azure SQL Database logical server and cannot find the agent. The most direct risk is: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed.

B:

SQL agent job alerts and operator notifications (4.1) would demonstrate or implement: A job can fail repeatedly without incident response if its failure status is not routed to a responsible operator. This choice can be useful for that problem, but it does not establish the SQL server agent maintenance job schedules (4.1) control being assessed here.

D:

Azure cli SQL resource provisioning (4.2) would demonstrate or implement: A command without correct scope can deploy resources to the wrong region or subscription despite succeeding. The required risk concerns SQL server agent maintenance job schedules (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 565

An Azure database administrator observes: A managed instance needs a recurring T-SQL stored procedure call with job schedule tracking. Which action best addresses the specific technical requirement?

  1. Use Azure CLI with explicit account, subscription, resource-group and SQL database parameters to automate approved SQL deployments.
  2. For SQL database in Microsoft Fabric, use supported Fabric pipelines, notebooks or recurring orchestration rather than assuming a traditional SQL Server Agent service.
  3. Configure supported SQL Server Agent alerts, operators and notification mechanisms for important job failures or database conditions.
  4. Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.

Explanation

Correct Answer

D:

The reported Azure SQL or SQL Server condition is: A managed instance needs a recurring T-SQL stored procedure call with job schedule tracking. The specific supported administrative response is: Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance. The technical risk is: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. Confirm the correction with: Job history records successful scheduled execution and its effect on the intended target database.

Incorrect Answers

A:

Azure cli SQL resource provisioning (4.2) addresses another technical failure: A command without correct scope can deploy resources to the wrong region or subscription despite succeeding. The case states: A managed instance needs a recurring T-SQL stored procedure call with job schedule tracking. The most direct corrective action is: Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.

B:

Fabric SQL database pipelines and recurring tasks (4.3) addresses another technical failure: Moving automation from SQL Server to a Fabric-managed SQL database without adapting its scheduling mechanism can leave tasks unexecuted. This choice can be useful for that problem, but it does not establish the SQL server agent maintenance job schedules (4.1) control being assessed here.

C:

SQL agent job alerts and operator notifications (4.1) addresses another technical failure: A job can fail repeatedly without incident response if its failure status is not routed to a responsible operator. This case instead tests SQL server agent maintenance job schedules (4.1); the choice measures or changes another part of the system.

Question 566

During post-change validation, the team reports: A managed instance needs a recurring T-SQL stored procedure call with job schedule tracking. Which observation best demonstrates that the appropriate correction worked?

  1. Job history records successful scheduled execution and its effect on the intended target database.
  2. CLI output and an independent resource readback confirm the database was created with intended settings.
  3. The Fabric pipeline or scheduled task runs against the intended database and its status is visible in the Fabric monitoring experience.
  4. A controlled failed job sends the expected notification and records the error in job history.

Explanation

Correct Answer

A:

The acceptance evidence for this incident (A managed instance needs a recurring T-SQL stored procedure call with job schedule tracking.) is: Job history records successful scheduled execution and its effect on the intended target database. It directly tests whether the remediation (Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

B:

Azure cli SQL resource provisioning (4.2) would demonstrate or implement: CLI output and an independent resource readback confirm the database was created with intended settings. This choice can be useful for that problem, but it does not establish the SQL server agent maintenance job schedules (4.1) control being assessed here.

C:

Fabric SQL database pipelines and recurring tasks (4.3) would demonstrate or implement: The Fabric pipeline or scheduled task runs against the intended database and its status is visible in the Fabric monitoring experience. This case instead tests SQL server agent maintenance job schedules (4.1); the choice measures or changes another part of the system.

D:

SQL agent job alerts and operator notifications (4.1) would demonstrate or implement: A controlled failed job sends the expected notification and records the error in job history. The required evidence concerns SQL server agent maintenance job schedules (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 567

An Azure database administrator observes: A maintenance task fires in the wrong local time zone after a daylight-saving change. Which action best addresses the specific technical requirement?

  1. For SQL database in Microsoft Fabric, use supported Fabric pipelines, notebooks or recurring orchestration rather than assuming a traditional SQL Server Agent service.
  2. Use Azure CLI with explicit account, subscription, resource-group and SQL database parameters to automate approved SQL deployments.
  3. Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.
  4. Configure supported SQL Server Agent alerts, operators and notification mechanisms for important job failures or database conditions.

Explanation

Correct Answer

C:

The reported Azure SQL or SQL Server condition is: A maintenance task fires in the wrong local time zone after a daylight-saving change. The specific supported administrative response is: Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance. The technical risk is: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. Confirm the correction with: Job history records successful scheduled execution and its effect on the intended target database.

Incorrect Answers

A:

Fabric SQL database pipelines and recurring tasks (4.3) addresses another technical failure: Moving automation from SQL Server to a Fabric-managed SQL database without adapting its scheduling mechanism can leave tasks unexecuted. The case states: A maintenance task fires in the wrong local time zone after a daylight-saving change. The most direct corrective action is: Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.

B:

Azure cli SQL resource provisioning (4.2) addresses another technical failure: A command without correct scope can deploy resources to the wrong region or subscription despite succeeding. This choice can be useful for that problem, but it does not establish the SQL server agent maintenance job schedules (4.1) control being assessed here.

D:

SQL agent job alerts and operator notifications (4.1) addresses another technical failure: A job can fail repeatedly without incident response if its failure status is not routed to a responsible operator. The required corrective action concerns SQL server agent maintenance job schedules (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 568

In a database operations review, a team encounters: A maintenance task fires in the wrong local time zone after a daylight-saving change. Which failure or exposure is most directly relevant?

  1. A job can fail repeatedly without incident response if its failure status is not routed to a responsible operator.
  2. Moving automation from SQL Server to a Fabric-managed SQL database without adapting its scheduling mechanism can leave tasks unexecuted.
  3. A command without correct scope can deploy resources to the wrong region or subscription despite succeeding.
  4. Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed.

Explanation

Correct Answer

D:

The incident (A maintenance task fires in the wrong local time zone after a daylight-saving change.) most directly exposes: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. The resulting safe technical response is: Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance. Its verification is: Job history records successful scheduled execution and its effect on the intended target database.

Incorrect Answers

A:

SQL agent job alerts and operator notifications (4.1) would demonstrate or implement: A job can fail repeatedly without incident response if its failure status is not routed to a responsible operator. The case states: A maintenance task fires in the wrong local time zone after a daylight-saving change. The most direct risk is: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed.

B:

Fabric SQL database pipelines and recurring tasks (4.3) would demonstrate or implement: Moving automation from SQL Server to a Fabric-managed SQL database without adapting its scheduling mechanism can leave tasks unexecuted. This choice can be useful for that problem, but it does not establish the SQL server agent maintenance job schedules (4.1) control being assessed here.

C:

Azure cli SQL resource provisioning (4.2) would demonstrate or implement: A command without correct scope can deploy resources to the wrong region or subscription despite succeeding. This case instead tests SQL server agent maintenance job schedules (4.1); the choice measures or changes another part of the system.

Question 569

An Azure database administrator observes: A DBA designs a recurring integrity check but never enables the SQL Agent schedule that should trigger it. Which action best addresses the specific technical requirement?

  1. Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.
  2. Use Azure CLI with explicit account, subscription, resource-group and SQL database parameters to automate approved SQL deployments.
  3. Configure supported SQL Server Agent alerts, operators and notification mechanisms for important job failures or database conditions.
  4. For SQL database in Microsoft Fabric, use supported Fabric pipelines, notebooks or recurring orchestration rather than assuming a traditional SQL Server Agent service.

Explanation

Correct Answer

A:

The reported Azure SQL or SQL Server condition is: A DBA designs a recurring integrity check but never enables the SQL Agent schedule that should trigger it. The specific supported administrative response is: Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance. The technical risk is: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. Confirm the correction with: Job history records successful scheduled execution and its effect on the intended target database.

Incorrect Answers

B:

Azure cli SQL resource provisioning (4.2) addresses another technical failure: A command without correct scope can deploy resources to the wrong region or subscription despite succeeding. This choice can be useful for that problem, but it does not establish the SQL server agent maintenance job schedules (4.1) control being assessed here.

C:

SQL agent job alerts and operator notifications (4.1) addresses another technical failure: A job can fail repeatedly without incident response if its failure status is not routed to a responsible operator. This case instead tests SQL server agent maintenance job schedules (4.1); the choice measures or changes another part of the system.

D:

Fabric SQL database pipelines and recurring tasks (4.3) addresses another technical failure: Moving automation from SQL Server to a Fabric-managed SQL database without adapting its scheduling mechanism can leave tasks unexecuted. The required corrective action concerns SQL server agent maintenance job schedules (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 570

An Azure SQL operations team investigates: A DBA designs a recurring integrity check but never enables the SQL Agent schedule that should trigger it. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. Configure supported SQL Server Agent alerts, operators and notification mechanisms for important job failures or database conditions.
  2. Use Azure CLI with explicit account, subscription, resource-group and SQL database parameters to automate approved SQL deployments.
  3. Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.
  4. Job history records successful scheduled execution and its effect on the intended target database.
  5. The Fabric pipeline or scheduled task runs against the intended database and its status is visible in the Fabric monitoring experience.

Explanation

Correct Answers

C:

The reported Azure SQL or SQL Server condition is: A DBA designs a recurring integrity check but never enables the SQL Agent schedule that should trigger it. The specific supported administrative response is: Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance. The technical risk is: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. Confirm the correction with: Job history records successful scheduled execution and its effect on the intended target database.

D:

The acceptance evidence for this incident (A DBA designs a recurring integrity check but never enables the SQL Agent schedule that should trigger it.) is: Job history records successful scheduled execution and its effect on the intended target database. It directly tests whether the remediation (Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

SQL agent job alerts and operator notifications (4.1) addresses another technical failure: A job can fail repeatedly without incident response if its failure status is not routed to a responsible operator. The case states: A DBA designs a recurring integrity check but never enables the SQL Agent schedule that should trigger it. The most direct paired action and test is: Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.

B:

Azure cli SQL resource provisioning (4.2) addresses another technical failure: A command without correct scope can deploy resources to the wrong region or subscription despite succeeding. This choice can be useful for that problem, but it does not establish the SQL server agent maintenance job schedules (4.1) control being assessed here.

E:

Fabric SQL database pipelines and recurring tasks (4.3) would demonstrate or implement: The Fabric pipeline or scheduled task runs against the intended database and its status is visible in the Fabric monitoring experience. The paired-answer requirement concerns SQL server agent maintenance job schedules (4.1); this alternative does not provide the matching intervention and separate acceptance evidence.