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 69

Question 680

An Azure SQL operations team investigates: A multi-tenant application needs target credentials scoped to approved maintenance procedures only. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. CLI output and an independent resource readback confirm the database was created with intended settings.
  2. For SQL database in Microsoft Fabric, use supported Fabric pipelines, notebooks or recurring orchestration rather than assuming a traditional SQL Server Agent service.
  3. Configure appropriate authentication and least-privilege target permissions for Azure SQL elastic job steps, then validate target connections.
  4. Provision Azure SQL database resources with version-controlled Bicep definitions and environment parameters through approved deployment pipelines.
  5. A controlled job connects only to intended target databases, completes allowed statements and is denied unapproved objects.

Explanation

Correct Answers

C:

The reported Azure SQL or SQL Server condition is: A multi-tenant application needs target credentials scoped to approved maintenance procedures only. The specific supported administrative response is: Configure appropriate authentication and least-privilege target permissions for Azure SQL elastic job steps, then validate target connections. The technical risk is: A job agent with excessive access or invalid credentials can expose other tenants or fail across all targets. Confirm the correction with: A controlled job connects only to intended target databases, completes allowed statements and is denied unapproved objects.

E:

The acceptance evidence for this incident (A multi-tenant application needs target credentials scoped to approved maintenance procedures only.) is: A controlled job connects only to intended target databases, completes allowed statements and is denied unapproved objects. It directly tests whether the remediation (Configure appropriate authentication and least-privilege target permissions for Azure SQL elastic job steps, then validate target connections.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

Azure cli SQL resource provisioning (4.2) would demonstrate or implement: CLI output and an independent resource readback confirm the database was created with intended settings. The case states: A multi-tenant application needs target credentials scoped to approved maintenance procedures only. The most direct paired action and test is: Configure appropriate authentication and least-privilege target permissions for Azure SQL elastic job steps, then validate target connections.

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 Elastic job credential and target security (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 paired action and test concerns Elastic job credential and target security (4.3); a passing result for this alternative could leave that requirement unresolved.

Question 681

An Azure database administrator observes: An operations team schedules database configuration updates using a script that stores the administrator password in plaintext. 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. Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources.
  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.

Explanation

Correct Answer

C:

The reported Azure SQL or SQL Server condition is: An operations team schedules database configuration updates using a script that stores the administrator password in plaintext. 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:

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 operations team schedules database configuration updates using a script that stores the administrator password in plaintext. The most direct corrective action is: Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks.

B:

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. This choice can be useful for that problem, but it does not establish the Azure automation SQL runbooks and managed identities (4.3) 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 automation SQL runbooks and managed identities (4.3); a passing result for this alternative could leave that requirement unresolved.

Question 682

During post-change validation, the team reports: An operations team schedules database configuration updates using a script that stores the administrator password in plaintext. Which observation best demonstrates that the appropriate correction worked?

  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. The job completes using a least-privilege execution principal while attempts to access unapproved paths fail.
  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 operations team schedules database configuration updates using a script that stores the administrator password in plaintext.) 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.

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: An operations team schedules database configuration updates using a script that stores the administrator password in plaintext. The most direct evidence is: A scheduled runbook uses its managed identity, writes an auditable outcome and changes only authorized SQL resources.

C:

SQL agent execution context and proxy permissions (4.1) would demonstrate or implement: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail. This case instead tests Azure automation SQL runbooks and managed identities (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 Azure automation SQL runbooks and managed identities (4.3); a passing result for this alternative could leave that requirement unresolved.

Question 683

An Azure database administrator observes: An old Azure Automation Run As account is still referenced by a SQL management runbook. 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 Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks.
  3. Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources.
  4. Compare deployed Azure SQL resources with approved IaC definitions and reconcile changes through controlled pipeline updates.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: An old Azure Automation Run As account is still referenced by a SQL management runbook. 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:

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 old Azure Automation Run As account is still referenced by a SQL management runbook. The most direct corrective action is: Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks.

C:

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. This case instead tests Azure automation SQL runbooks and managed identities (4.3); 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 corrective action concerns Azure automation SQL runbooks and managed identities (4.3); a passing result for this alternative could leave that requirement unresolved.

Question 684

In a database operations review, a team encounters: An old Azure Automation Run As account is still referenced by a SQL management runbook. Which failure or exposure is most directly relevant?

  1. Untracked manual overrides can break reproducibility and cause security configuration drift between environments.
  2. SQL Server Agent is not a feature of Azure SQL Database, and per-database ad hoc scripts can be hard to govern at scale.
  3. Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures.
  4. Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk.

Explanation

Correct Answer

D:

The incident (An old Azure Automation Run As account is still referenced by a SQL management runbook.) most directly exposes: Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk. The resulting safe technical response is: Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks. Its verification is: 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: Untracked manual overrides can break reproducibility and cause security configuration drift between environments. The case states: An old Azure Automation Run As account is still referenced by a SQL management runbook. The most direct risk is: Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk.

B:

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 choice can be useful for that problem, but it does not establish the Azure automation SQL runbooks and managed identities (4.3) control being assessed here.

C:

SQL agent execution context and proxy permissions (4.1) would demonstrate or implement: Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures. This case instead tests Azure automation SQL runbooks and managed identities (4.3); the choice measures or changes another part of the system.

Question 685

An Azure database administrator observes: A runbook starts successfully but its managed identity lacks SQL resource role assignments. 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. Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources.
  3. Compare deployed Azure SQL resources with approved IaC definitions and reconcile changes through controlled pipeline updates.
  4. Use Azure SQL Database elastic jobs with an agent, job database, target groups and schedule for T-SQL tasks across one or many databases.

Explanation

Correct Answer

A:

The reported Azure SQL or SQL Server condition is: A runbook starts successfully but its managed identity lacks SQL resource role assignments. 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

B:

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. This choice can be useful for that problem, but it does not establish the Azure automation SQL runbooks and managed identities (4.3) 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 automation SQL runbooks and managed identities (4.3); the choice measures or changes another part of the system.

D:

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 required corrective action concerns Azure automation SQL runbooks and managed identities (4.3); a passing result for this alternative could leave that requirement unresolved.

Question 686

During post-change validation, the team reports: A runbook starts successfully but its managed identity lacks SQL resource role assignments. Which observation best demonstrates that the appropriate correction worked?

  1. A drift check identifies a test manual change and a reviewed pipeline restores the approved state.
  2. The job completes using a least-privilege execution principal while attempts to access unapproved paths fail.
  3. A scheduled runbook uses its managed identity, writes an auditable outcome and changes only authorized SQL resources.
  4. Elastic job execution history shows the approved step ran on all selected target databases and excluded unrelated tenants.

Explanation

Correct Answer

C:

The acceptance evidence for this incident (A runbook starts successfully but its managed identity lacks SQL resource role assignments.) 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.

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: A runbook starts successfully but its managed identity lacks SQL resource role assignments. The most direct evidence is: A scheduled runbook uses its managed identity, writes an auditable outcome and changes only authorized SQL resources.

B:

SQL agent execution context and proxy permissions (4.1) would demonstrate or implement: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail. This choice can be useful for that problem, but it does not establish the Azure automation SQL runbooks and managed identities (4.3) control being assessed here.

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 Azure automation SQL runbooks and managed identities (4.3); a passing result for this alternative could leave that requirement unresolved.

Question 687

An Azure database administrator observes: A cloud administrator wants recurring SQL configuration checks without managing VM scheduled tasks. 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. Compare deployed Azure SQL resources with approved IaC definitions and reconcile changes through controlled pipeline updates.
  3. Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks.
  4. Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources.

Explanation

Correct Answer

C:

The reported Azure SQL or SQL Server condition is: A cloud administrator wants recurring SQL configuration checks without managing VM scheduled tasks. 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:

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: A cloud administrator wants recurring SQL configuration checks without managing VM scheduled tasks. The most direct corrective action is: Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks.

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 automation SQL runbooks and managed identities (4.3) control being assessed here.

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 corrective action concerns Azure automation SQL runbooks and managed identities (4.3); a passing result for this alternative could leave that requirement unresolved.

Question 688

In a database operations review, a team encounters: A cloud administrator wants recurring SQL configuration checks without managing VM scheduled tasks. Which failure or exposure is most directly relevant?

  1. Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures.
  2. SQL Server Agent is not a feature of Azure SQL Database, and per-database ad hoc scripts can be hard to govern at scale.
  3. Untracked manual overrides can break reproducibility and cause security configuration drift between environments.
  4. Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk.

Explanation

Correct Answer

D:

The incident (A cloud administrator wants recurring SQL configuration checks without managing VM scheduled tasks.) most directly exposes: Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk. The resulting safe technical response is: Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks. Its verification is: A scheduled runbook uses its managed identity, writes an auditable outcome and changes only authorized SQL resources.

Incorrect Answers

A:

SQL agent execution context and proxy permissions (4.1) would demonstrate or implement: Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures. The case states: A cloud administrator wants recurring SQL configuration checks without managing VM scheduled tasks. The most direct risk is: Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk.

B:

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 choice can be useful for that problem, but it does not establish the Azure automation SQL runbooks and managed identities (4.3) control being assessed here.

C:

Infrastructure drift and declarative reconciliation (4.2) would demonstrate or implement: Untracked manual overrides can break reproducibility and cause security configuration drift between environments. This case instead tests Azure automation SQL runbooks and managed identities (4.3); the choice measures or changes another part of the system.

Question 689

An Azure database administrator observes: An organization needs a repeatable Azure SQL automation task that produces protected execution history. Which action best addresses the specific technical requirement?

  1. Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources.
  2. Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks.
  3. Compare deployed Azure SQL resources with approved IaC definitions and reconcile changes through controlled pipeline updates.
  4. Use Azure SQL Database elastic jobs with an agent, job database, target groups and schedule for T-SQL tasks across one or many databases.

Explanation

Correct Answer

B:

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:

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 case states: An organization needs a repeatable Azure SQL automation task that produces protected execution history. The most direct corrective action is: Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks.

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 automation SQL runbooks and managed identities (4.3); the choice measures or changes another part of the system.

D:

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 required corrective action concerns Azure automation SQL runbooks and managed identities (4.3); a passing result for this alternative could leave that requirement unresolved.

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.