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 70

Question 690

An Azure SQL operations team investigates: An organization needs a repeatable Azure SQL automation task that produces protected execution history. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. A drift check identifies a test manual change and a reviewed pipeline restores the approved state.
  2. A scheduled runbook uses its managed identity, writes an auditable outcome and changes only authorized SQL resources.
  3. Use Azure SQL Database elastic jobs with an agent, job database, target groups and schedule for T-SQL tasks across one or many databases.
  4. Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources.
  5. Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks.

Explanation

Correct Answers

B:

The acceptance evidence for this incident (An organization needs a repeatable Azure SQL automation task that produces protected execution history.) is: A scheduled runbook uses its managed identity, writes an auditable outcome and changes only authorized SQL resources. It directly tests whether the remediation (Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks.) solves the specified issue, instead of proving an unrelated database control works.

E:

The reported Azure SQL or SQL Server condition is: An organization needs a repeatable Azure SQL automation task that produces protected execution history. The specific supported administrative response is: Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks. The technical risk is: Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk. Confirm the correction with: A scheduled runbook uses its managed identity, writes an auditable outcome and changes only authorized SQL resources.

Incorrect Answers

A:

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 case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: A scheduled runbook uses its managed identity, writes an auditable outcome and changes only authorized SQL resources.

C:

Elastic jobs across azure SQL databases (4.3) addresses another technical failure: SQL Server Agent is not a feature of Azure SQL Database, and per-database ad hoc scripts can be hard to govern at scale. This case instead tests Azure automation SQL runbooks and managed identities (4.3); the choice measures or changes another part of the system.

D:

SQL agent execution context and proxy permissions (4.1) addresses another technical failure: Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures. The required paired action and test concerns Azure automation SQL runbooks and managed identities (4.3); a passing result for this alternative could leave that requirement unresolved.

Question 691

An Azure database administrator observes: An elastic job runs across many tenant databases but individual target failures are never reported. Which action best addresses the specific technical requirement?

  1. Use Azure SQL Database elastic jobs with an agent, job database, target groups and schedule for T-SQL tasks across one or many databases.
  2. Provision Azure SQL database resources with version-controlled Bicep definitions and environment parameters through approved deployment pipelines.
  3. Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts.
  4. Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations.

Explanation

Correct Answer

C:

The reported Azure SQL or SQL Server condition is: An elastic job runs across many tenant databases but individual target failures are never reported. The specific supported administrative response is: Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts. The technical risk is: A schedule existing in configuration does not prove its SQL operation executed or completed successfully. Confirm the correction with: A simulated failure triggers the expected alert with actionable job identity, step and owner context.

Incorrect Answers

A:

Elastic jobs across azure SQL databases (4.3) addresses another technical failure: SQL Server Agent is not a feature of Azure SQL Database, and per-database ad hoc scripts can be hard to govern at scale. The case states: An elastic job runs across many tenant databases but individual target failures are never reported. The most direct corrective action is: Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts.

B:

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 choice can be useful for that problem, but it does not establish the Database task alerts and outcome monitoring (4.3) control being assessed here.

D:

Azure powershell database automation (4.2) addresses another technical failure: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment. The required corrective action concerns Database task alerts and outcome monitoring (4.3); a passing result for this alternative could leave that requirement unresolved.

Question 692

During post-change validation, the team reports: An elastic job runs across many tenant databases but individual target failures are never reported. Which observation best demonstrates that the appropriate correction worked?

  1. A repeatable deployment produces the approved Azure SQL resource configuration and its change is reviewable.
  2. A simulated failure triggers the expected alert with actionable job identity, step and owner context.
  3. A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs.
  4. Elastic job execution history shows the approved step ran on all selected target databases and excluded unrelated tenants.

Explanation

Correct Answer

B:

The acceptance evidence for this incident (An elastic job runs across many tenant databases but individual target failures are never reported.) is: A simulated failure triggers the expected alert with actionable job identity, step and owner context. It directly tests whether the remediation (Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

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 case states: An elastic job runs across many tenant databases but individual target failures are never reported. The most direct evidence is: A simulated failure triggers the expected alert with actionable job identity, step and owner context.

C:

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. This case instead tests Database task alerts and outcome monitoring (4.3); the choice measures or changes another part of the system.

D:

Elastic jobs across azure SQL databases (4.3) would demonstrate or implement: Elastic job execution history shows the approved step ran on all selected target databases and excluded unrelated tenants. The required evidence concerns Database task alerts and outcome monitoring (4.3); a passing result for this alternative could leave that requirement unresolved.

Question 693

An Azure database administrator observes: A DBA sees that an Azure Automation schedule fired but the SQL action failed silently. 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. Use Azure SQL Database elastic jobs with an agent, job database, target groups and schedule for T-SQL tasks across one or many databases.
  3. Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts.
  4. Provision Azure SQL database resources with version-controlled Bicep definitions and environment parameters through approved deployment pipelines.

Explanation

Correct Answer

C:

The reported Azure SQL or SQL Server condition is: A DBA sees that an Azure Automation schedule fired but the SQL action failed silently. The specific supported administrative response is: Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts. The technical risk is: A schedule existing in configuration does not prove its SQL operation executed or completed successfully. Confirm the correction with: A simulated failure triggers the expected alert with actionable job identity, step and owner context.

Incorrect Answers

A:

Azure powershell database automation (4.2) addresses another technical failure: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment. The case states: A DBA sees that an Azure Automation schedule fired but the SQL action failed silently. The most direct corrective action is: Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts.

B:

Elastic jobs across azure SQL databases (4.3) addresses another technical failure: SQL Server Agent is not a feature of Azure SQL Database, and per-database ad hoc scripts can be hard to govern at scale. This choice can be useful for that problem, but it does not establish the Database task alerts and outcome monitoring (4.3) control being assessed here.

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 Database task alerts and outcome monitoring (4.3); a passing result for this alternative could leave that requirement unresolved.

Question 694

In a database operations review, a team encounters: A DBA sees that an Azure Automation schedule fired but the SQL action failed silently. Which failure or exposure is most directly relevant?

  1. A schedule existing in configuration does not prove its SQL operation executed or completed successfully.
  2. Manual production configuration can drift from tested resource sizing, networking and backup settings.
  3. SQL Server Agent is not a feature of Azure SQL Database, and per-database ad hoc scripts can be hard to govern at scale.
  4. Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment.

Explanation

Correct Answer

A:

The incident (A DBA sees that an Azure Automation schedule fired but the SQL action failed silently.) most directly exposes: A schedule existing in configuration does not prove its SQL operation executed or completed successfully. The resulting safe technical response is: Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts. Its verification is: A simulated failure triggers the expected alert with actionable job identity, step and owner context.

Incorrect Answers

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 Database task alerts and outcome monitoring (4.3) control being assessed here.

C:

Elastic jobs across azure SQL databases (4.3) would demonstrate or implement: SQL Server Agent is not a feature of Azure SQL Database, and per-database ad hoc scripts can be hard to govern at scale. This case instead tests Database task alerts and outcome monitoring (4.3); the choice measures or changes another part of the system.

D:

Azure powershell database automation (4.2) would demonstrate or implement: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment. The required risk concerns Database task alerts and outcome monitoring (4.3); a passing result for this alternative could leave that requirement unresolved.

Question 695

An Azure database administrator observes: An operations team wants an escalation when a nightly database task exceeds its agreed duration. Which action best addresses the specific technical requirement?

  1. Provision Azure SQL database resources with version-controlled Bicep definitions and environment parameters through approved deployment pipelines.
  2. Use Azure SQL Database elastic jobs with an agent, job database, target groups and schedule for T-SQL tasks across one or many databases.
  3. Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts.
  4. Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations.

Explanation

Correct Answer

C:

The reported Azure SQL or SQL Server condition is: An operations team wants an escalation when a nightly database task exceeds its agreed duration. The specific supported administrative response is: Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts. The technical risk is: A schedule existing in configuration does not prove its SQL operation executed or completed successfully. Confirm the correction with: A simulated failure triggers the expected alert with actionable job identity, step and owner context.

Incorrect Answers

A:

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 case states: An operations team wants an escalation when a nightly database task exceeds its agreed duration. The most direct corrective action is: Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts.

B:

Elastic jobs across azure SQL databases (4.3) addresses another technical failure: SQL Server Agent is not a feature of Azure SQL Database, and per-database ad hoc scripts can be hard to govern at scale. This choice can be useful for that problem, but it does not establish the Database task alerts and outcome monitoring (4.3) control being assessed here.

D:

Azure powershell database automation (4.2) addresses another technical failure: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment. The required corrective action concerns Database task alerts and outcome monitoring (4.3); a passing result for this alternative could leave that requirement unresolved.

Question 696

During post-change validation, the team reports: An operations team wants an escalation when a nightly database task exceeds its agreed duration. Which observation best demonstrates that the appropriate correction worked?

  1. Elastic job execution history shows the approved step ran on all selected target databases and excluded unrelated tenants.
  2. A repeatable deployment produces the approved Azure SQL resource configuration and its change is reviewable.
  3. A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs.
  4. A simulated failure triggers the expected alert with actionable job identity, step and owner context.

Explanation

Correct Answer

D:

The acceptance evidence for this incident (An operations team wants an escalation when a nightly database task exceeds its agreed duration.) is: A simulated failure triggers the expected alert with actionable job identity, step and owner context. It directly tests whether the remediation (Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

Elastic jobs across azure SQL databases (4.3) would demonstrate or implement: Elastic job execution history shows the approved step ran on all selected target databases and excluded unrelated tenants. The case states: An operations team wants an escalation when a nightly database task exceeds its agreed duration. The most direct evidence is: A simulated failure triggers the expected alert with actionable job identity, step and owner context.

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 Database task alerts and outcome monitoring (4.3) control being assessed here.

C:

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. This case instead tests Database task alerts and outcome monitoring (4.3); the choice measures or changes another part of the system.

Question 697

An Azure database administrator observes: A scheduled database cleanup job completes without any retained execution output. 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. Use Azure SQL Database elastic jobs with an agent, job database, target groups and schedule for T-SQL tasks across one or many databases.
  3. Provision Azure SQL database resources with version-controlled Bicep definitions and environment parameters through approved deployment pipelines.
  4. Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts.

Explanation

Correct Answer

D:

The reported Azure SQL or SQL Server condition is: A scheduled database cleanup job completes without any retained execution output. The specific supported administrative response is: Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts. The technical risk is: A schedule existing in configuration does not prove its SQL operation executed or completed successfully. Confirm the correction with: A simulated failure triggers the expected alert with actionable job identity, step and owner context.

Incorrect Answers

A:

Azure powershell database automation (4.2) addresses another technical failure: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment. The case states: A scheduled database cleanup job completes without any retained execution output. The most direct corrective action is: Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts.

B:

Elastic jobs across azure SQL databases (4.3) addresses another technical failure: SQL Server Agent is not a feature of Azure SQL Database, and per-database ad hoc scripts can be hard to govern at scale. This choice can be useful for that problem, but it does not establish the Database task alerts and outcome monitoring (4.3) 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 Database task alerts and outcome monitoring (4.3); the choice measures or changes another part of the system.

Question 698

In a database operations review, a team encounters: A scheduled database cleanup job completes without any retained execution output. Which failure or exposure is most directly relevant?

  1. SQL Server Agent is not a feature of Azure SQL Database, and per-database ad hoc scripts can be hard to govern at scale.
  2. Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment.
  3. Manual production configuration can drift from tested resource sizing, networking and backup settings.
  4. A schedule existing in configuration does not prove its SQL operation executed or completed successfully.

Explanation

Correct Answer

D:

The incident (A scheduled database cleanup job completes without any retained execution output.) most directly exposes: A schedule existing in configuration does not prove its SQL operation executed or completed successfully. The resulting safe technical response is: Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts. Its verification is: A simulated failure triggers the expected alert with actionable job identity, step and owner context.

Incorrect Answers

A:

Elastic jobs across azure SQL databases (4.3) would demonstrate or implement: SQL Server Agent is not a feature of Azure SQL Database, and per-database ad hoc scripts can be hard to govern at scale. The case states: A scheduled database cleanup job completes without any retained execution output. The most direct risk is: A schedule existing in configuration does not prove its SQL operation executed or completed successfully.

B:

Azure powershell database automation (4.2) would demonstrate or implement: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment. This choice can be useful for that problem, but it does not establish the Database task alerts and outcome monitoring (4.3) control being assessed here.

C:

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 case instead tests Database task alerts and outcome monitoring (4.3); the choice measures or changes another part of the system.

Question 699

An Azure database administrator observes: An auditor requests evidence of the last successful maintenance run and any unresolved failure alerts. Which action best addresses the specific technical requirement?

  1. Use Azure SQL Database elastic jobs with an agent, job database, target groups and schedule for T-SQL tasks across one or many databases.
  2. Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations.
  3. Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts.
  4. Provision Azure SQL database resources with version-controlled Bicep definitions and environment parameters through approved deployment pipelines.

Explanation

Correct Answer

C:

The reported Azure SQL or SQL Server condition is: An auditor requests evidence of the last successful maintenance run and any unresolved failure alerts. The specific supported administrative response is: Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts. The technical risk is: A schedule existing in configuration does not prove its SQL operation executed or completed successfully. Confirm the correction with: A simulated failure triggers the expected alert with actionable job identity, step and owner context.

Incorrect Answers

A:

Elastic jobs across azure SQL databases (4.3) addresses another technical failure: SQL Server Agent is not a feature of Azure SQL Database, and per-database ad hoc scripts can be hard to govern at scale. The case states: An auditor requests evidence of the last successful maintenance run and any unresolved failure alerts. The most direct corrective action is: Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts.

B:

Azure powershell database automation (4.2) addresses another technical failure: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment. This choice can be useful for that problem, but it does not establish the Database task alerts and outcome monitoring (4.3) control being assessed here.

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 Database task alerts and outcome monitoring (4.3); a passing result for this alternative could leave that requirement unresolved.

Question 700

An Azure SQL operations team investigates: An auditor requests evidence of the last successful maintenance run and any unresolved failure alerts. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. A repeatable deployment produces the approved Azure SQL resource configuration and its change is reviewable.
  2. Use Azure SQL Database elastic jobs with an agent, job database, target groups and schedule for T-SQL tasks across one or many databases.
  3. Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts.
  4. Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations.
  5. A simulated failure triggers the expected alert with actionable job identity, step and owner context.

Explanation

Correct Answers

C:

The reported Azure SQL or SQL Server condition is: An auditor requests evidence of the last successful maintenance run and any unresolved failure alerts. The specific supported administrative response is: Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts. The technical risk is: A schedule existing in configuration does not prove its SQL operation executed or completed successfully. Confirm the correction with: A simulated failure triggers the expected alert with actionable job identity, step and owner context.

E:

The acceptance evidence for this incident (An auditor requests evidence of the last successful maintenance run and any unresolved failure alerts.) is: A simulated failure triggers the expected alert with actionable job identity, step and owner context. It directly tests whether the remediation (Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

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 case states: An auditor requests evidence of the last successful maintenance run and any unresolved failure alerts. The most direct paired action and test is: Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts.

B:

Elastic jobs across azure SQL databases (4.3) addresses another technical failure: SQL Server Agent is not a feature of Azure SQL Database, and per-database ad hoc scripts can be hard to govern at scale. This choice can be useful for that problem, but it does not establish the Database task alerts and outcome monitoring (4.3) control being assessed here.

D:

Azure powershell database automation (4.2) addresses another technical failure: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment. The required paired action and test concerns Database task alerts and outcome monitoring (4.3); a passing result for this alternative could leave that requirement unresolved.