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 59

Question 580

An Azure SQL operations team investigates: An operations review needs evidence that an alert is both generated and acknowledged when a scheduled task fails. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. A controlled failed job sends the expected notification and records the error in job history.
  2. Configure supported SQL Server Agent alerts, operators and notification mechanisms for important job failures or database conditions.
  3. Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.
  4. Provision Azure SQL database resources with version-controlled Bicep definitions and environment parameters through approved deployment pipelines.
  5. CLI output and an independent resource readback confirm the database was created with intended settings.

Explanation

Correct Answers

A:

The acceptance evidence for this incident (An operations review needs evidence that an alert is both generated and acknowledged when a scheduled task fails.) is: A controlled failed job sends the expected notification and records the error in job history. It directly tests whether the remediation (Configure supported SQL Server Agent alerts, operators and notification mechanisms for important job failures or database conditions.) solves the specified issue, instead of proving an unrelated database control works.

B:

The reported Azure SQL or SQL Server condition is: An operations review needs evidence that an alert is both generated and acknowledged when a scheduled task fails. The specific supported administrative response is: Configure supported SQL Server Agent alerts, operators and notification mechanisms for important job failures or database conditions. The technical risk is: A job can fail repeatedly without incident response if its failure status is not routed to a responsible operator. Confirm the correction with: A controlled failed job sends the expected notification and records the error in job history.

Incorrect Answers

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 SQL agent job alerts and operator notifications (4.1); the choice measures or changes another part of the system.

D:

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

E:

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 paired-answer requirement concerns SQL agent job alerts and operator notifications (4.1); this alternative does not provide the matching intervention and separate acceptance evidence.

Question 581

An Azure database administrator observes: A PowerShell job step writes to a network share but the Agent service identity lacks permission. 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. Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.
  3. Configure appropriate authentication and least-privilege target permissions for Azure SQL elastic job steps, then validate target connections.
  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 PowerShell job step writes to a network share but the Agent service identity lacks permission. The specific supported administrative response is: Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources. The technical risk is: Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures. Confirm the correction with: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail.

Incorrect Answers

B:

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

C:

Elastic job credential and target security (4.3) addresses another technical failure: A job agent with excessive access or invalid credentials can expose other tenants or fail across all targets. This case instead tests SQL agent execution context and proxy permissions (4.1); 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 SQL agent execution context and proxy permissions (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 582

During post-change validation, the team reports: A PowerShell job step writes to a network share but the Agent service identity lacks permission. Which observation best demonstrates that the appropriate correction worked?

  1. The job completes using a least-privilege execution principal while attempts to access unapproved paths fail.
  2. Elastic job execution history shows the approved step ran on all selected target databases and excluded unrelated tenants.
  3. A controlled job connects only to intended target databases, completes allowed statements and is denied unapproved objects.
  4. Job history records successful scheduled execution and its effect on the intended target database.

Explanation

Correct Answer

A:

The acceptance evidence for this incident (A PowerShell job step writes to a network share but the Agent service identity lacks permission.) is: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail. It directly tests whether the remediation (Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

B:

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. This choice can be useful for that problem, but it does not establish the SQL agent execution context and proxy permissions (4.1) control being assessed here.

C:

Elastic job credential and target security (4.3) would demonstrate or implement: A controlled job connects only to intended target databases, completes allowed statements and is denied unapproved objects. This case instead tests SQL agent execution context and proxy permissions (4.1); the choice measures or changes another part of the system.

D:

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

Question 583

An Azure database administrator observes: A vendor maintenance job runs as an administrative account although it updates one staging table. 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. Configure appropriate authentication and least-privilege target permissions for Azure SQL elastic job steps, then validate target connections.
  3. Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.
  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 vendor maintenance job runs as an administrative account although it updates one staging table. The specific supported administrative response is: Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources. The technical risk is: Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures. Confirm the correction with: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail.

Incorrect Answers

B:

Elastic job credential and target security (4.3) addresses another technical failure: A job agent with excessive access or invalid credentials can expose other tenants or fail across all targets. This choice can be useful for that problem, but it does not establish the SQL agent execution context and proxy permissions (4.1) control being assessed here.

C:

SQL server agent maintenance job schedules (4.1) addresses another technical failure: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. This case instead tests SQL agent execution context and proxy permissions (4.1); 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 SQL agent execution context and proxy permissions (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 584

In a database operations review, a team encounters: A vendor maintenance job runs as an administrative account although it updates one staging table. Which failure or exposure is most directly relevant?

  1. Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed.
  2. Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures.
  3. A job agent with excessive access or invalid credentials can expose other tenants or fail across all targets.
  4. SQL Server Agent is not a feature of Azure SQL Database, and per-database ad hoc scripts can be hard to govern at scale.

Explanation

Correct Answer

B:

The incident (A vendor maintenance job runs as an administrative account although it updates one staging table.) most directly exposes: Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures. The resulting safe technical response is: Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources. Its verification is: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail.

Incorrect Answers

A:

SQL server agent maintenance job schedules (4.1) would demonstrate or implement: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. The case states: A vendor maintenance job runs as an administrative account although it updates one staging table. The most direct risk is: Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures.

C:

Elastic job credential and target security (4.3) would demonstrate or implement: A job agent with excessive access or invalid credentials can expose other tenants or fail across all targets. This case instead tests SQL agent execution context and proxy permissions (4.1); the choice measures or changes another part of the system.

D:

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 required risk concerns SQL agent execution context and proxy permissions (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 585

An Azure database administrator observes: An SSIS job step requires an appropriate proxy credential rather than default SQL Agent service rights. 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. Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.
  4. Configure appropriate authentication and least-privilege target permissions for Azure SQL elastic job steps, then validate target connections.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: An SSIS job step requires an appropriate proxy credential rather than default SQL Agent service rights. The specific supported administrative response is: Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources. The technical risk is: Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures. Confirm the correction with: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail.

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 SSIS job step requires an appropriate proxy credential rather than default SQL Agent service rights. The most direct corrective action is: Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources.

C:

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

D:

Elastic job credential and target security (4.3) addresses another technical failure: A job agent with excessive access or invalid credentials can expose other tenants or fail across all targets. The required corrective action concerns SQL agent execution context and proxy permissions (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 586

During post-change validation, the team reports: An SSIS job step requires an appropriate proxy credential rather than default SQL Agent service rights. Which observation best demonstrates that the appropriate correction worked?

  1. A controlled job connects only to intended target databases, completes allowed statements and is denied unapproved objects.
  2. Elastic job execution history shows the approved step ran on all selected target databases and excluded unrelated tenants.
  3. Job history records successful scheduled execution and its effect on the intended target database.
  4. The job completes using a least-privilege execution principal while attempts to access unapproved paths fail.

Explanation

Correct Answer

D:

The acceptance evidence for this incident (An SSIS job step requires an appropriate proxy credential rather than default SQL Agent service rights.) is: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail. It directly tests whether the remediation (Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

Elastic job credential and target security (4.3) would demonstrate or implement: A controlled job connects only to intended target databases, completes allowed statements and is denied unapproved objects. The case states: An SSIS job step requires an appropriate proxy credential rather than default SQL Agent service rights. The most direct evidence is: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail.

B:

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. This choice can be useful for that problem, but it does not establish the SQL agent execution context and proxy permissions (4.1) control being assessed here.

C:

SQL server agent maintenance job schedules (4.1) would demonstrate or implement: Job history records successful scheduled execution and its effect on the intended target database. This case instead tests SQL agent execution context and proxy permissions (4.1); the choice measures or changes another part of the system.

Question 587

An Azure database administrator observes: A newly created job succeeds interactively but fails under the scheduled execution context. 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. Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.
  3. Configure appropriate authentication and least-privilege target permissions for Azure SQL elastic job steps, then validate target connections.
  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 newly created job succeeds interactively but fails under the scheduled execution context. The specific supported administrative response is: Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources. The technical risk is: Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures. Confirm the correction with: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail.

Incorrect Answers

B:

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

C:

Elastic job credential and target security (4.3) addresses another technical failure: A job agent with excessive access or invalid credentials can expose other tenants or fail across all targets. This case instead tests SQL agent execution context and proxy permissions (4.1); 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 SQL agent execution context and proxy permissions (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 588

In a database operations review, a team encounters: A newly created job succeeds interactively but fails under the scheduled execution context. 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. Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures.
  3. Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed.
  4. A job agent with excessive access or invalid credentials can expose other tenants or fail across all targets.

Explanation

Correct Answer

B:

The incident (A newly created job succeeds interactively but fails under the scheduled execution context.) most directly exposes: Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures. The resulting safe technical response is: Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources. Its verification is: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail.

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 newly created job succeeds interactively but fails under the scheduled execution context. The most direct risk is: Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures.

C:

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

D:

Elastic job credential and target security (4.3) would demonstrate or implement: A job agent with excessive access or invalid credentials can expose other tenants or fail across all targets. The required risk concerns SQL agent execution context and proxy permissions (4.1); a passing result for this alternative could leave that requirement unresolved.

Question 589

An Azure database administrator observes: A compliance team wants to prove automated SQL tasks do not inherit unnecessary server-wide permissions. 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. Configure appropriate authentication and least-privilege target permissions for Azure SQL elastic job steps, then validate target connections.
  3. Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.
  4. Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources.

Explanation

Correct Answer

D:

The reported Azure SQL or SQL Server condition is: A compliance team wants to prove automated SQL tasks do not inherit unnecessary server-wide permissions. The specific supported administrative response is: Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources. The technical risk is: Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures. Confirm the correction with: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail.

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 compliance team wants to prove automated SQL tasks do not inherit unnecessary server-wide permissions. The most direct evidence is: Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources.

B:

Elastic job credential and target security (4.3) addresses another technical failure: A job agent with excessive access or invalid credentials can expose other tenants or fail across all targets. This choice can be useful for that problem, but it does not establish the SQL agent execution context and proxy permissions (4.1) control being assessed here.

C:

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

Question 590

An Azure SQL operations team investigates: A compliance team wants to prove automated SQL tasks do not inherit unnecessary server-wide permissions. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  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. Create SQL Server Agent jobs and schedules on supported SQL Server or Azure SQL Managed Instance targets for repeatable maintenance.
  3. The job completes using a least-privilege execution principal while attempts to access unapproved paths fail.
  4. A controlled job connects only to intended target databases, completes allowed statements and is denied unapproved objects.
  5. Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources.

Explanation

Correct Answers

C:

The acceptance evidence for this incident (A compliance team wants to prove automated SQL tasks do not inherit unnecessary server-wide permissions.) is: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail. It directly tests whether the remediation (Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources.) 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 wants to prove automated SQL tasks do not inherit unnecessary server-wide permissions. The specific supported administrative response is: Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources. The technical risk is: Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures. Confirm the correction with: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail.

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: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail.

B:

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

D:

Elastic job credential and target security (4.3) would demonstrate or implement: A controlled job connects only to intended target databases, completes allowed statements and is denied unapproved objects. The required paired action and test concerns SQL agent execution context and proxy permissions (4.1); a passing result for this alternative could leave that requirement unresolved.