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 61

Question 600

An Azure SQL operations team investigates: A database mail alert says a job failed but the DBA needs the exact SQL error and step time to investigate. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. A controlled rerun identifies the previous failing step and completes after the specific cause is corrected.
  2. Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks.
  3. Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.
  4. Inspect SQL Server Agent job and step histories, failure output, schedules and retry settings before modifying dependent systems.
  5. A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs.

Explanation

Correct Answers

A:

The acceptance evidence for this incident (A database mail alert says a job failed but the DBA needs the exact SQL error and step time to investigate.) is: A controlled rerun identifies the previous failing step and completes after the specific cause is corrected. It directly tests whether the remediation (Inspect SQL Server Agent job and step histories, failure output, schedules and retry settings before modifying dependent systems.) solves the specified issue, instead of proving an unrelated database control works.

D:

The reported Azure SQL or SQL Server condition is: A database mail alert says a job failed but the DBA needs the exact SQL error and step time to investigate. The specific supported administrative response is: Inspect SQL Server Agent job and step histories, failure output, schedules and retry settings before modifying dependent systems. The technical risk is: A top-level job failure can conceal the precise failing step or a flawed retry sequence that repeats non-idempotent work. Confirm the correction with: A controlled rerun identifies the previous failing step and completes after the specific cause is corrected.

Incorrect Answers

B:

Azure automation SQL runbooks and managed identities (4.3) addresses another technical failure: Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk. This choice can be useful for that problem, but it does not establish the Troubleshooting job steps and retry behavior (4.1) control being assessed here.

C:

SQL server agent maintenance job schedules (4.1) addresses another technical failure: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. This case instead tests Troubleshooting job steps and retry behavior (4.1); the choice measures or changes another part of the system.

E:

Azure powershell database automation (4.2) would demonstrate or implement: A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs. The paired-answer requirement concerns Troubleshooting job steps and retry behavior (4.1); this alternative does not provide the matching intervention and separate acceptance evidence.

Question 601

An Azure database administrator observes: A database replica becomes writable after failover but its backup or maintenance job is missing. Which action best addresses the specific technical requirement?

  1. Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks.
  2. Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.
  3. Provision Azure SQL database resources with version-controlled Bicep definitions and environment parameters through approved deployment pipelines.
  4. Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.

Explanation

Correct Answer

D:

The reported Azure SQL or SQL Server condition is: A database replica becomes writable after failover but its backup or maintenance job is missing. The specific supported administrative response is: Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover. The technical risk is: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled. Confirm the correction with: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes.

Incorrect Answers

A:

Azure automation SQL runbooks and managed identities (4.3) addresses another technical failure: Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk. The case states: A database replica becomes writable after failover but its backup or maintenance job is missing. The most direct corrective action is: Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.

B:

SQL server agent maintenance job schedules (4.1) addresses another technical failure: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. This choice can be useful for that problem, but it does not establish the Maintaining job schedules across failover (4.1) control being assessed here.

C:

Azure SQL resource deployment using bicep (4.2) addresses another technical failure: Manual production configuration can drift from tested resource sizing, networking and backup settings. This case instead tests Maintaining job schedules across failover (4.1); the choice measures or changes another part of the system.

Question 602

During post-change validation, the team reports: A database replica becomes writable after failover but its backup or maintenance job is missing. Which observation best demonstrates that the appropriate correction worked?

  1. A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes.
  2. A scheduled runbook uses its managed identity, writes an auditable outcome and changes only authorized SQL resources.
  3. A repeatable deployment produces the approved Azure SQL resource configuration and its change is reviewable.
  4. Job history records successful scheduled execution and its effect on the intended target database.

Explanation

Correct Answer

A:

The acceptance evidence for this incident (A database replica becomes writable after failover but its backup or maintenance job is missing.) is: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes. It directly tests whether the remediation (Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

B:

Azure automation SQL runbooks and managed identities (4.3) would demonstrate or implement: A scheduled runbook uses its managed identity, writes an auditable outcome and changes only authorized SQL resources. This choice can be useful for that problem, but it does not establish the Maintaining job schedules across failover (4.1) control being assessed here.

C:

Azure SQL resource deployment using bicep (4.2) would demonstrate or implement: A repeatable deployment produces the approved Azure SQL resource configuration and its change is reviewable. This case instead tests Maintaining job schedules across failover (4.1); the choice measures or changes another part of the system.

D:

SQL server agent maintenance job schedules (4.1) would demonstrate or implement: Job history records successful scheduled execution and its effect on the intended target database. The required evidence concerns Maintaining job schedules across failover (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 603

An Azure database administrator observes: Two SQL Server replicas each run the same data-processing job and generate duplicate records. Which action best addresses the specific technical requirement?

  1. Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks.
  2. Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.
  3. Provision Azure SQL database resources with version-controlled Bicep definitions and environment parameters through approved deployment pipelines.
  4. Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: Two SQL Server replicas each run the same data-processing job and generate duplicate records. The specific supported administrative response is: Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover. The technical risk is: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled. Confirm the correction with: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes.

Incorrect Answers

A:

Azure automation SQL runbooks and managed identities (4.3) addresses another technical failure: Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk. The case states: Two SQL Server replicas each run the same data-processing job and generate duplicate records. The most direct corrective action is: Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.

C:

Azure SQL resource deployment using bicep (4.2) addresses another technical failure: Manual production configuration can drift from tested resource sizing, networking and backup settings. This case instead tests Maintaining job schedules across failover (4.1); the choice measures or changes another part of the system.

D:

SQL server agent maintenance job schedules (4.1) addresses another technical failure: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. The required corrective action concerns Maintaining job schedules across failover (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 604

In a database operations review, a team encounters: Two SQL Server replicas each run the same data-processing job and generate duplicate records. Which failure or exposure is most directly relevant?

  1. Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk.
  2. A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled.
  3. Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed.
  4. Manual production configuration can drift from tested resource sizing, networking and backup settings.

Explanation

Correct Answer

B:

The incident (Two SQL Server replicas each run the same data-processing job and generate duplicate records.) most directly exposes: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled. The resulting safe technical response is: Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover. Its verification is: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes.

Incorrect Answers

A:

Azure automation SQL runbooks and managed identities (4.3) would demonstrate or implement: Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk. The case states: Two SQL Server replicas each run the same data-processing job and generate duplicate records. The most direct risk is: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled.

C:

SQL server agent maintenance job schedules (4.1) would demonstrate or implement: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. This case instead tests Maintaining job schedules across failover (4.1); the choice measures or changes another part of the system.

D:

Azure SQL resource deployment using bicep (4.2) would demonstrate or implement: Manual production configuration can drift from tested resource sizing, networking and backup settings. The required risk concerns Maintaining job schedules across failover (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 605

An Azure database administrator observes: An operator assumes all msdb SQL Agent jobs automatically follow database geo-replication. Which action best addresses the specific technical requirement?

  1. Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks.
  2. Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.
  3. Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.
  4. Provision Azure SQL database resources with version-controlled Bicep definitions and environment parameters through approved deployment pipelines.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: An operator assumes all msdb SQL Agent jobs automatically follow database geo-replication. The specific supported administrative response is: Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover. The technical risk is: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled. Confirm the correction with: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes.

Incorrect Answers

A:

Azure automation SQL runbooks and managed identities (4.3) addresses another technical failure: Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk. The case states: An operator assumes all msdb SQL Agent jobs automatically follow database geo-replication. The most direct corrective action is: Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.

C:

SQL server agent maintenance job schedules (4.1) addresses another technical failure: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. This case instead tests Maintaining job schedules across failover (4.1); the choice measures or changes another part of the system.

D:

Azure SQL resource deployment using bicep (4.2) addresses another technical failure: Manual production configuration can drift from tested resource sizing, networking and backup settings. The required corrective action concerns Maintaining job schedules across failover (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 606

During post-change validation, the team reports: An operator assumes all msdb SQL Agent jobs automatically follow database geo-replication. 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. A scheduled runbook uses its managed identity, writes an auditable outcome and changes only authorized SQL resources.
  3. A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes.
  4. A repeatable deployment produces the approved Azure SQL resource configuration and its change is reviewable.

Explanation

Correct Answer

C:

The acceptance evidence for this incident (An operator assumes all msdb SQL Agent jobs automatically follow database geo-replication.) is: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes. It directly tests whether the remediation (Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

SQL server agent maintenance job schedules (4.1) would demonstrate or implement: Job history records successful scheduled execution and its effect on the intended target database. The case states: An operator assumes all msdb SQL Agent jobs automatically follow database geo-replication. The most direct evidence is: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes.

B:

Azure automation SQL runbooks and managed identities (4.3) would demonstrate or implement: A scheduled runbook uses its managed identity, writes an auditable outcome and changes only authorized SQL resources. This choice can be useful for that problem, but it does not establish the Maintaining job schedules across failover (4.1) control being assessed here.

D:

Azure SQL resource deployment using bicep (4.2) would demonstrate or implement: A repeatable deployment produces the approved Azure SQL resource configuration and its change is reviewable. The required evidence concerns Maintaining job schedules across failover (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 607

An Azure database administrator observes: A managed instance migration brings user databases online but scheduled operational tasks are not yet recreated. 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. Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.
  3. Provision Azure SQL database resources with version-controlled Bicep definitions and environment parameters through approved deployment pipelines.
  4. Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: A managed instance migration brings user databases online but scheduled operational tasks are not yet recreated. The specific supported administrative response is: Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover. The technical risk is: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled. Confirm the correction with: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes.

Incorrect Answers

A:

SQL server agent maintenance job schedules (4.1) addresses another technical failure: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. The case states: A managed instance migration brings user databases online but scheduled operational tasks are not yet recreated. The most direct corrective action is: Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.

C:

Azure SQL resource deployment using bicep (4.2) addresses another technical failure: Manual production configuration can drift from tested resource sizing, networking and backup settings. This case instead tests Maintaining job schedules across failover (4.1); the choice measures or changes another part of the system.

D:

Azure automation SQL runbooks and managed identities (4.3) addresses another technical failure: Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk. The required corrective action concerns Maintaining job schedules across failover (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 608

In a database operations review, a team encounters: A managed instance migration brings user databases online but scheduled operational tasks are not yet recreated. Which failure or exposure is most directly relevant?

  1. Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk.
  2. Manual production configuration can drift from tested resource sizing, networking and backup settings.
  3. Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed.
  4. A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled.

Explanation

Correct Answer

D:

The incident (A managed instance migration brings user databases online but scheduled operational tasks are not yet recreated.) most directly exposes: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled. The resulting safe technical response is: Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover. Its verification is: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes.

Incorrect Answers

A:

Azure automation SQL runbooks and managed identities (4.3) would demonstrate or implement: Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk. The case states: A managed instance migration brings user databases online but scheduled operational tasks are not yet recreated. The most direct risk is: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled.

B:

Azure SQL resource deployment using bicep (4.2) would demonstrate or implement: Manual production configuration can drift from tested resource sizing, networking and backup settings. This choice can be useful for that problem, but it does not establish the Maintaining job schedules across failover (4.1) control being assessed here.

C:

SQL server agent maintenance job schedules (4.1) would demonstrate or implement: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. This case instead tests Maintaining job schedules across failover (4.1); the choice measures or changes another part of the system.

Question 609

An Azure database administrator observes: A disaster-recovery plan includes the database connection string but omits job owners, notifications and schedules. Which action best addresses the specific technical requirement?

  1. Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks.
  2. Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.
  3. Provision Azure SQL database resources with version-controlled Bicep definitions and environment parameters through approved deployment pipelines.
  4. Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: A disaster-recovery plan includes the database connection string but omits job owners, notifications and schedules. The specific supported administrative response is: Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover. The technical risk is: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled. Confirm the correction with: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes.

Incorrect Answers

A:

Azure automation SQL runbooks and managed identities (4.3) addresses another technical failure: Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk. The case states: A disaster-recovery plan includes the database connection string but omits job owners, notifications and schedules. The most direct corrective action is: Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.

C:

Azure SQL resource deployment using bicep (4.2) addresses another technical failure: Manual production configuration can drift from tested resource sizing, networking and backup settings. This case instead tests Maintaining job schedules across failover (4.1); the choice measures or changes another part of the system.

D:

SQL server agent maintenance job schedules (4.1) addresses another technical failure: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. The required corrective action concerns Maintaining job schedules across failover (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 610

An Azure SQL operations team investigates: A disaster-recovery plan includes the database connection string but omits job owners, notifications and schedules. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks.
  2. A repeatable deployment produces the approved Azure SQL resource configuration and its change is reviewable.
  3. Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.
  4. A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes.
  5. Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.

Explanation

Correct Answers

D:

The acceptance evidence for this incident (A disaster-recovery plan includes the database connection string but omits job owners, notifications and schedules.) is: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes. It directly tests whether the remediation (Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.) solves the specified issue, instead of proving an unrelated database control works.

E:

The reported Azure SQL or SQL Server condition is: A disaster-recovery plan includes the database connection string but omits job owners, notifications and schedules. The specific supported administrative response is: Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover. The technical risk is: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled. Confirm the correction with: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes.

Incorrect Answers

A:

Azure automation SQL runbooks and managed identities (4.3) addresses another technical failure: Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes.

B:

Azure SQL resource deployment using bicep (4.2) would demonstrate or implement: A repeatable deployment produces the approved Azure SQL resource configuration and its change is reviewable. This choice can be useful for that problem, but it does not establish the Maintaining job schedules across failover (4.1) control being assessed here.

C:

SQL server agent maintenance job schedules (4.1) addresses another technical failure: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. This case instead tests Maintaining job schedules across failover (4.1); the choice measures or changes another part of the system.