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 63

Question 620

An Azure SQL operations team investigates: An Azure SQL server is created successfully but the associated private endpoint deployment is absent. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. Provision Azure SQL database resources with version-controlled Bicep definitions and environment parameters through approved deployment pipelines.
  2. A repeatable deployment produces the approved Azure SQL resource configuration and its change is reviewable.
  3. Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks.
  4. Compare deployed Azure SQL resources with approved IaC definitions and reconcile changes through controlled pipeline updates.
  5. A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes.

Explanation

Correct Answers

A:

The reported Azure SQL or SQL Server condition is: An Azure SQL server is created successfully but the associated private endpoint deployment is absent. The specific supported administrative response is: Provision Azure SQL database resources with version-controlled Bicep definitions and environment parameters through approved deployment pipelines. The technical risk is: Manual production configuration can drift from tested resource sizing, networking and backup settings. Confirm the correction with: A repeatable deployment produces the approved Azure SQL resource configuration and its change is reviewable.

B:

The acceptance evidence for this incident (An Azure SQL server is created successfully but the associated private endpoint deployment is absent.) is: A repeatable deployment produces the approved Azure SQL resource configuration and its change is reviewable. It directly tests whether the remediation (Provision Azure SQL database resources with version-controlled Bicep definitions and environment parameters through approved deployment pipelines.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

C:

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 case instead tests Azure SQL resource deployment using bicep (4.2); the choice measures or changes another part of the system.

D:

Infrastructure drift and declarative reconciliation (4.2) addresses another technical failure: Untracked manual overrides can break reproducibility and cause security configuration drift between environments. The required paired action and test concerns Azure SQL resource deployment using bicep (4.2); a passing result for this alternative could leave that requirement unresolved.

E:

Maintaining job schedules across failover (4.1) would demonstrate or implement: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes. The paired-answer requirement concerns Azure SQL resource deployment using bicep (4.2); this alternative does not provide the matching intervention and separate acceptance evidence.

Question 621

An Azure database administrator observes: A DBA needs to update backup retention policy consistently across several Azure SQL servers. Which action best addresses the specific technical requirement?

  1. Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.
  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. Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations.
  4. Compare deployed Azure SQL resources with approved IaC definitions and reconcile changes through controlled pipeline updates.

Explanation

Correct Answer

C:

The reported Azure SQL or SQL Server condition is: A DBA needs to update backup retention policy consistently across several Azure SQL servers. The specific supported administrative response is: Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations. The technical risk is: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment. Confirm the correction with: A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs.

Incorrect Answers

A:

Maintaining job schedules across failover (4.1) addresses another technical failure: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled. The case states: A DBA needs to update backup retention policy consistently across several Azure SQL servers. The most direct corrective action is: Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations.

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 Azure powershell database automation (4.2) control being assessed here.

D:

Infrastructure drift and declarative reconciliation (4.2) addresses another technical failure: Untracked manual overrides can break reproducibility and cause security configuration drift between environments. The required corrective action concerns Azure powershell database automation (4.2); a passing result for this alternative could leave that requirement unresolved.

Question 622

During post-change validation, the team reports: A DBA needs to update backup retention policy consistently across several Azure SQL servers. Which observation best demonstrates that the appropriate correction worked?

  1. The Fabric pipeline or scheduled task runs against the intended database and its status is visible in the Fabric monitoring experience.
  2. A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes.
  3. A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs.
  4. A drift check identifies a test manual change and a reviewed pipeline restores the approved state.

Explanation

Correct Answer

C:

The acceptance evidence for this incident (A DBA needs to update backup retention policy consistently across several Azure SQL servers.) is: A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs. It directly tests whether the remediation (Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

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 case states: A DBA needs to update backup retention policy consistently across several Azure SQL servers. The most direct evidence is: A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs.

B:

Maintaining job schedules across failover (4.1) would demonstrate or implement: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes. This choice can be useful for that problem, but it does not establish the Azure powershell database automation (4.2) control being assessed here.

D:

Infrastructure drift and declarative reconciliation (4.2) would demonstrate or implement: A drift check identifies a test manual change and a reviewed pipeline restores the approved state. The required evidence concerns Azure powershell database automation (4.2); a passing result for this alternative could leave that requirement unresolved.

Question 623

An Azure database administrator observes: A PowerShell script works on a laptop but fails in automation because the operator's personal login expired. Which action best addresses the specific technical requirement?

  1. Compare deployed Azure SQL resources with approved IaC definitions and reconcile changes through controlled pipeline updates.
  2. Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.
  3. Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations.
  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

C:

The reported Azure SQL or SQL Server condition is: A PowerShell script works on a laptop but fails in automation because the operator's personal login expired. The specific supported administrative response is: Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations. The technical risk is: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment. Confirm the correction with: A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs.

Incorrect Answers

A:

Infrastructure drift and declarative reconciliation (4.2) addresses another technical failure: Untracked manual overrides can break reproducibility and cause security configuration drift between environments. The case states: A PowerShell script works on a laptop but fails in automation because the operator's personal login expired. The most direct corrective action is: Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations.

B:

Maintaining job schedules across failover (4.1) addresses another technical failure: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled. This choice can be useful for that problem, but it does not establish the Azure powershell database automation (4.2) control being assessed here.

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 Azure powershell database automation (4.2); a passing result for this alternative could leave that requirement unresolved.

Question 624

In a database operations review, a team encounters: A PowerShell script works on a laptop but fails in automation because the operator's personal login expired. Which failure or exposure is most directly relevant?

  1. Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment.
  2. A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled.
  3. Moving automation from SQL Server to a Fabric-managed SQL database without adapting its scheduling mechanism can leave tasks unexecuted.
  4. Untracked manual overrides can break reproducibility and cause security configuration drift between environments.

Explanation

Correct Answer

A:

The incident (A PowerShell script works on a laptop but fails in automation because the operator's personal login expired.) most directly exposes: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment. The resulting safe technical response is: Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations. Its verification is: A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs.

Incorrect Answers

B:

Maintaining job schedules across failover (4.1) would demonstrate or implement: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled. This choice can be useful for that problem, but it does not establish the Azure powershell database automation (4.2) control being assessed here.

C:

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 case instead tests Azure powershell database automation (4.2); the choice measures or changes another part of the system.

D:

Infrastructure drift and declarative reconciliation (4.2) would demonstrate or implement: Untracked manual overrides can break reproducibility and cause security configuration drift between environments. The required risk concerns Azure powershell database automation (4.2); a passing result for this alternative could leave that requirement unresolved.

Question 625

An Azure database administrator observes: A production script selects the wrong subscription and begins scaling a test database. Which action best addresses the specific technical requirement?

  1. Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations.
  2. Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.
  3. Compare deployed Azure SQL resources with approved IaC definitions and reconcile changes through controlled pipeline updates.
  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 production script selects the wrong subscription and begins scaling a test database. The specific supported administrative response is: Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations. The technical risk is: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment. Confirm the correction with: A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs.

Incorrect Answers

B:

Maintaining job schedules across failover (4.1) addresses another technical failure: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled. This choice can be useful for that problem, but it does not establish the Azure powershell database automation (4.2) control being assessed here.

C:

Infrastructure drift and declarative reconciliation (4.2) addresses another technical failure: Untracked manual overrides can break reproducibility and cause security configuration drift between environments. This case instead tests Azure powershell database automation (4.2); 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 Azure powershell database automation (4.2); a passing result for this alternative could leave that requirement unresolved.

Question 626

During post-change validation, the team reports: A production script selects the wrong subscription and begins scaling a test database. Which observation best demonstrates that the appropriate correction worked?

  1. A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs.
  2. A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes.
  3. A drift check identifies a test manual change and a reviewed pipeline restores the approved state.
  4. The Fabric pipeline or scheduled task runs against the intended database and its status is visible in the Fabric monitoring experience.

Explanation

Correct Answer

A:

The acceptance evidence for this incident (A production script selects the wrong subscription and begins scaling a test database.) is: A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs. It directly tests whether the remediation (Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

B:

Maintaining job schedules across failover (4.1) would demonstrate or implement: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes. This choice can be useful for that problem, but it does not establish the Azure powershell database automation (4.2) control being assessed here.

C:

Infrastructure drift and declarative reconciliation (4.2) would demonstrate or implement: A drift check identifies a test manual change and a reviewed pipeline restores the approved state. This case instead tests Azure powershell database automation (4.2); the choice measures or changes another part of the system.

D:

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 required evidence concerns Azure powershell database automation (4.2); a passing result for this alternative could leave that requirement unresolved.

Question 627

An Azure database administrator observes: An engineer wants to list Azure SQL database service objectives through authenticated PowerShell. Which action best addresses the specific technical requirement?

  1. Compare deployed Azure SQL resources with approved IaC definitions and reconcile changes through controlled pipeline updates.
  2. Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations.
  3. Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.
  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 engineer wants to list Azure SQL database service objectives through authenticated PowerShell. The specific supported administrative response is: Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations. The technical risk is: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment. Confirm the correction with: A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs.

Incorrect Answers

A:

Infrastructure drift and declarative reconciliation (4.2) addresses another technical failure: Untracked manual overrides can break reproducibility and cause security configuration drift between environments. The case states: An engineer wants to list Azure SQL database service objectives through authenticated PowerShell. The most direct corrective action is: Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations.

C:

Maintaining job schedules across failover (4.1) addresses another technical failure: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled. This case instead tests Azure powershell database automation (4.2); 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 Azure powershell database automation (4.2); a passing result for this alternative could leave that requirement unresolved.

Question 628

In a database operations review, a team encounters: An engineer wants to list Azure SQL database service objectives through authenticated PowerShell. Which failure or exposure is most directly relevant?

  1. Untracked manual overrides can break reproducibility and cause security configuration drift between environments.
  2. Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment.
  3. A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled.
  4. Moving automation from SQL Server to a Fabric-managed SQL database without adapting its scheduling mechanism can leave tasks unexecuted.

Explanation

Correct Answer

B:

The incident (An engineer wants to list Azure SQL database service objectives through authenticated PowerShell.) most directly exposes: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment. The resulting safe technical response is: Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations. Its verification is: A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs.

Incorrect Answers

A:

Infrastructure drift and declarative reconciliation (4.2) would demonstrate or implement: Untracked manual overrides can break reproducibility and cause security configuration drift between environments. The case states: An engineer wants to list Azure SQL database service objectives through authenticated PowerShell. The most direct risk is: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment.

C:

Maintaining job schedules across failover (4.1) would demonstrate or implement: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled. This case instead tests Azure powershell database automation (4.2); the choice measures or changes another part of the system.

D:

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 required risk concerns Azure powershell database automation (4.2); a passing result for this alternative could leave that requirement unresolved.

Question 629

An Azure database administrator observes: A compliance team requires logged configuration changes instead of unaudited manual portal edits. Which action best addresses the specific technical requirement?

  1. Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations.
  2. Compare deployed Azure SQL resources with approved IaC definitions and reconcile changes through controlled pipeline updates.
  3. Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.
  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 compliance team requires logged configuration changes instead of unaudited manual portal edits. The specific supported administrative response is: Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations. The technical risk is: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment. Confirm the correction with: A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs.

Incorrect Answers

B:

Infrastructure drift and declarative reconciliation (4.2) addresses another technical failure: Untracked manual overrides can break reproducibility and cause security configuration drift between environments. This choice can be useful for that problem, but it does not establish the Azure powershell database automation (4.2) control being assessed here.

C:

Maintaining job schedules across failover (4.1) addresses another technical failure: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled. This case instead tests Azure powershell database automation (4.2); 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 Azure powershell database automation (4.2); a passing result for this alternative could leave that requirement unresolved.

Question 630

An Azure SQL operations team investigates: A compliance team requires logged configuration changes instead of unaudited manual portal edits. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. The Fabric pipeline or scheduled task runs against the intended database and its status is visible in the Fabric monitoring experience.
  2. Compare deployed Azure SQL resources with approved IaC definitions and reconcile changes through controlled pipeline updates.
  3. Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.
  4. A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs.
  5. Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations.

Explanation

Correct Answers

D:

The acceptance evidence for this incident (A compliance team requires logged configuration changes instead of unaudited manual portal edits.) is: A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs. It directly tests whether the remediation (Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations.) solves the specified issue, instead of proving an unrelated database control works.

E:

The reported Azure SQL or SQL Server condition is: A compliance team requires logged configuration changes instead of unaudited manual portal edits. The specific supported administrative response is: Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations. The technical risk is: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment. Confirm the correction with: A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs.

Incorrect Answers

A:

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 case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs.

B:

Infrastructure drift and declarative reconciliation (4.2) addresses another technical failure: Untracked manual overrides can break reproducibility and cause security configuration drift between environments. This choice can be useful for that problem, but it does not establish the Azure powershell database automation (4.2) control being assessed here.

C:

Maintaining job schedules across failover (4.1) addresses another technical failure: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled. This case instead tests Azure powershell database automation (4.2); the choice measures or changes another part of the system.