Microsoft DP-300 Exam Dumps, Practice Test Questions

100% Latest & Updated Microsoft DP-300 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!

Microsoft DP-300 Premium Bundle
$79.97
$59.98

DP-300 Premium Bundle

  • Premium File: 470 Questions & Answers. Last update: Nov 5, 2026
  • Training Course: 130 Video Lectures
  • Study Guide: 672 Pages
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

DP-300 Premium Bundle

Microsoft DP-300 Premium Bundle
  • Premium File: 470 Questions & Answers. Last update: Nov 5, 2026
  • Training Course: 130 Video Lectures
  • Study Guide: 672 Pages
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
$79.97
$59.98

Microsoft DP-300 Practice Test 45

Question 440

Three independently confirmed SQL platform issues require separate evidence checks. Case A: A centrally scheduled elastic job cannot execute its T-SQL on a protected target database. Case B: Hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly. Case C: A resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM. Select exactly THREE distinct diagnostic checks, one for each case.

  1. Job schedule and execution history including per-target outcomes
  2. Target group membership and server pool or database exclusions
  3. Database-scoped execution identity and GRANT results for each target
  4. Per-target elastic job execution outcome and Azure monitoring alert signal
  5. Fleet job agent settings and dynamic target enumeration results
  6. Azure Automation runbook identity job schedule and Az module logs

Explanation

Correct Answers

C:

Database-scoped execution identity and GRANT results for each target directly tests the observation that a centrally scheduled elastic job cannot execute its T-SQL on a protected target database. It helps the team evaluate whether it should configure supported target authentication and least-privileged database permissions. The check has a boundary: A job credential must never be shared broadly or overprivileged.

E:

Fleet job agent settings and dynamic target enumeration results directly tests the observation that hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly. It helps the team evaluate whether it should create an Azure SQL elastic job for the targeted databases. The check has a boundary: Elastic jobs require correct target credentials and are not SQL Server Agent.

F:

Azure Automation runbook identity job schedule and Az module logs directly tests the observation that a resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM. It helps the team evaluate whether it should create a scheduled Azure Automation runbook with managed identity and required roles. The check has a boundary: An Automation runbook is not the same as executing T-SQL SQL Server Agent steps.

Incorrect Answers

A:

Job schedule and execution history including per-target outcomes is appropriate for the separate condition that an elastic job executes manually but has not been configured for the required nightly cadence. The actual 3 cases are A: A centrally scheduled elastic job cannot execute its T-SQL on a protected target database; B: Hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly; C: A resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM. This option is not the specific diagnostic evidence for any of those stated cases.

B:

Target group membership and server pool or database exclusions is appropriate for the separate condition that an elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet. The actual 3 cases are A: A centrally scheduled elastic job cannot execute its T-SQL on a protected target database; B: Hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly; C: A resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM. This option is not the specific diagnostic evidence for any of those stated cases.

D:

Per-target elastic job execution outcome and Azure monitoring alert signal is appropriate for the separate condition that a nightly elastic job fails only on one target and the on-call team requires actionable notification. The actual 3 cases are A: A centrally scheduled elastic job cannot execute its T-SQL on a protected target database; B: Hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly; C: A resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM. This option is not the specific diagnostic evidence for any of those stated cases.

Question 441

The data platform team is assessing this situation: An elastic job executes manually but has not been configured for the required nightly cadence. Which Azure SQL service or administration concept most precisely fits this situation?

  1. Dynamic target membership scope
  2. Scheduled execution outcome tracking
  3. Agent registration and metadata store
  4. Alerts for failed database jobs

Explanation

Correct Answer

B:

Scheduled execution outcome tracking matches the precise requirement: an elastic job executes manually but has not been configured for the required nightly cadence. Maintenance runs on an expected cadence with inspectable execution history. Important scope limit: Successful job submission does not mean every individual target succeeded.

Incorrect Answers

A:

Dynamic target membership scope applies when an elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet, not when an elastic job executes manually but has not been configured for the required nightly cadence.

C:

Agent registration and metadata store applies when a team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions, not when an elastic job executes manually but has not been configured for the required nightly cadence.

D:

Alerts for failed database jobs applies when a nightly elastic job fails only on one target and the on-call team requires actionable notification, not when an elastic job executes manually but has not been configured for the required nightly cadence.

Question 442

A database architecture review reports the following requirement: A resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM. Which Azure SQL service or administration concept most precisely fits this situation?

  1. Fleet-wide T-SQL job automation
  2. Target database execution permissions
  3. Dynamic target membership scope
  4. Automation runbook for SQL tasks

Explanation

Correct Answer

D:

Automation runbook for SQL tasks matches the precise requirement: a resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM. Resource administration can run under an Azure-hosted scheduler. Important scope limit: An Automation runbook is not the same as executing T-SQL SQL Server Agent steps.

Incorrect Answers

A:

Fleet-wide T-SQL job automation applies when hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly, not when a resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM.

B:

Target database execution permissions applies when a centrally scheduled elastic job cannot execute its T-SQL on a protected target database, not when a resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM.

C:

Dynamic target membership scope applies when an elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet, not when a resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM.

Question 443

A Microsoft Azure SQL solution proposal begins with this condition: A nightly elastic job fails only on one target and the on-call team requires actionable notification. Which Azure SQL service or administration concept most precisely fits this situation?

  1. Fleet-wide T-SQL job automation
  2. Scheduled execution outcome tracking
  3. Dynamic target membership scope
  4. Alerts for failed database jobs

Explanation

Correct Answer

D:

Alerts for failed database jobs matches the precise requirement: a nightly elastic job fails only on one target and the on-call team requires actionable notification. Operators can identify and respond to failed scheduled database tasks. Important scope limit: An alert does not repair failed target-specific SQL permissions or scripts.

Incorrect Answers

A:

Fleet-wide T-SQL job automation applies when hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly, not when a nightly elastic job fails only on one target and the on-call team requires actionable notification.

B:

Scheduled execution outcome tracking applies when an elastic job executes manually but has not been configured for the required nightly cadence, not when a nightly elastic job fails only on one target and the on-call team requires actionable notification.

C:

Dynamic target membership scope applies when an elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet, not when a nightly elastic job fails only on one target and the on-call team requires actionable notification.

Question 444

An operator is collecting proof for the following observation: Hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly. Which diagnostic artifact would most directly validate the stated condition?

  1. Fleet job agent settings and dynamic target enumeration results
  2. Azure Automation runbook identity job schedule and Az module logs
  3. Target group membership and server pool or database exclusions
  4. Database-scoped execution identity and GRANT results for each target

Explanation

Correct Answer

A:

Fleet job agent settings and dynamic target enumeration results directly tests the observation that hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly. It helps the team evaluate whether it should create an Azure SQL elastic job for the targeted databases. The check has a boundary: Elastic jobs require correct target credentials and are not SQL Server Agent.

Incorrect Answers

B:

Azure Automation runbook identity job schedule and Az module logs applies when a resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM, not when hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly.

C:

Target group membership and server pool or database exclusions applies when an elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet, not when hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly.

D:

Database-scoped execution identity and GRANT results for each target applies when a centrally scheduled elastic job cannot execute its T-SQL on a protected target database, not when hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly.

Question 445

During SQL troubleshooting the team must test this hypothesis: A team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions. Which diagnostic artifact would most directly validate the stated condition?

  1. Job schedule and execution history including per-target outcomes
  2. Database-scoped execution identity and GRANT results for each target
  3. Azure Automation runbook identity job schedule and Az module logs
  4. Elastic job agent configuration and backing job database metadata

Explanation

Correct Answer

D:

Elastic job agent configuration and backing job database metadata directly tests the observation that a team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions. It helps the team evaluate whether it should create and configure an elastic job agent with its job database. The check has a boundary: A normal SQL Database alone is not the elastic job scheduling agent.

Incorrect Answers

A:

Job schedule and execution history including per-target outcomes applies when an elastic job executes manually but has not been configured for the required nightly cadence, not when a team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions.

B:

Database-scoped execution identity and GRANT results for each target applies when a centrally scheduled elastic job cannot execute its T-SQL on a protected target database, not when a team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions.

C:

Azure Automation runbook identity job schedule and Az module logs applies when a resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM, not when a team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions.

Question 446

A production database review needs evidence of this condition: An elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet. Which diagnostic artifact would most directly validate the stated condition?

  1. Database-scoped execution identity and GRANT results for each target
  2. Fleet job agent settings and dynamic target enumeration results
  3. Target group membership and server pool or database exclusions
  4. Job schedule and execution history including per-target outcomes

Explanation

Correct Answer

C:

Target group membership and server pool or database exclusions directly tests the observation that an elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet. It helps the team evaluate whether it should define and verify the elastic job target group explicitly. The check has a boundary: Dynamic target enumeration can include new databases if membership rules are too broad.

Incorrect Answers

A:

Database-scoped execution identity and GRANT results for each target applies when a centrally scheduled elastic job cannot execute its T-SQL on a protected target database, not when an elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet.

B:

Fleet job agent settings and dynamic target enumeration results applies when hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly, not when an elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet.

D:

Job schedule and execution history including per-target outcomes applies when an elastic job executes manually but has not been configured for the required nightly cadence, not when an elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet.

Question 447

An operator is collecting proof for the following observation: A centrally scheduled elastic job cannot execute its T-SQL on a protected target database. Which diagnostic artifact would most directly validate the stated condition?

  1. Database-scoped execution identity and GRANT results for each target
  2. Fleet job agent settings and dynamic target enumeration results
  3. Elastic job agent configuration and backing job database metadata
  4. Target group membership and server pool or database exclusions

Explanation

Correct Answer

A:

Database-scoped execution identity and GRANT results for each target directly tests the observation that a centrally scheduled elastic job cannot execute its T-SQL on a protected target database. It helps the team evaluate whether it should configure supported target authentication and least-privileged database permissions. The check has a boundary: A job credential must never be shared broadly or overprivileged.

Incorrect Answers

B:

Fleet job agent settings and dynamic target enumeration results applies when hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly, not when a centrally scheduled elastic job cannot execute its T-SQL on a protected target database.

C:

Elastic job agent configuration and backing job database metadata applies when a team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions, not when a centrally scheduled elastic job cannot execute its T-SQL on a protected target database.

D:

Target group membership and server pool or database exclusions applies when an elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet, not when a centrally scheduled elastic job cannot execute its T-SQL on a protected target database.

Question 448

During SQL troubleshooting the team must test this hypothesis: An elastic job executes manually but has not been configured for the required nightly cadence. Which diagnostic artifact would most directly validate the stated condition?

  1. Elastic job agent configuration and backing job database metadata
  2. Target group membership and server pool or database exclusions
  3. Azure Automation runbook identity job schedule and Az module logs
  4. Job schedule and execution history including per-target outcomes

Explanation

Correct Answer

D:

Job schedule and execution history including per-target outcomes directly tests the observation that an elastic job executes manually but has not been configured for the required nightly cadence. It helps the team evaluate whether it should set a supported elastic job schedule and monitor job executions. The check has a boundary: Successful job submission does not mean every individual target succeeded.

Incorrect Answers

A:

Elastic job agent configuration and backing job database metadata applies when a team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions, not when an elastic job executes manually but has not been configured for the required nightly cadence.

B:

Target group membership and server pool or database exclusions applies when an elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet, not when an elastic job executes manually but has not been configured for the required nightly cadence.

C:

Azure Automation runbook identity job schedule and Az module logs applies when a resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM, not when an elastic job executes manually but has not been configured for the required nightly cadence.

Question 449

Two independent Azure SQL administration tickets require separate actions. Case A: A resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM. Case B: A centrally scheduled elastic job cannot execute its T-SQL on a protected target database. Select exactly TWO distinct implementation steps, one for each case.

  1. Define and verify the elastic job target group explicitly
  2. Create and configure an elastic job agent with its job database
  3. Configure supported target authentication and least-privileged database permissions
  4. Set a supported elastic job schedule and monitor job executions
  5. Create a scheduled Azure Automation runbook with managed identity and required roles

Explanation

Correct Answers

C:

Configure supported target authentication and least-privileged database permissions directly resolves the reported requirement that a centrally scheduled elastic job cannot execute its T-SQL on a protected target database. The agent can execute planned steps on authorized targets. The implementation must also respect this constraint: A job credential must never be shared broadly or overprivileged.

E:

Create a scheduled Azure Automation runbook with managed identity and required roles directly resolves the reported requirement that a resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM. Resource administration can run under an Azure-hosted scheduler. The implementation must also respect this constraint: An Automation runbook is not the same as executing T-SQL SQL Server Agent steps.

Incorrect Answers

A:

Define and verify the elastic job target group explicitly is appropriate for the separate condition that an elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet. The actual 2 cases are A: A resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM; B: A centrally scheduled elastic job cannot execute its T-SQL on a protected target database. This option is not the specific implementation or corrective step for any of those stated cases.

B:

Create and configure an elastic job agent with its job database is appropriate for the separate condition that a team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions. The actual 2 cases are A: A resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM; B: A centrally scheduled elastic job cannot execute its T-SQL on a protected target database. This option is not the specific implementation or corrective step for any of those stated cases.

D:

Set a supported elastic job schedule and monitor job executions is appropriate for the separate condition that an elastic job executes manually but has not been configured for the required nightly cadence. The actual 2 cases are A: A resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM; B: A centrally scheduled elastic job cannot execute its T-SQL on a protected target database. This option is not the specific implementation or corrective step for any of those stated cases.

Question 450

Three independently confirmed SQL platform issues require separate evidence checks. Case A: A nightly elastic job fails only on one target and the on-call team requires actionable notification. Case B: A resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM. Case C: A centrally scheduled elastic job cannot execute its T-SQL on a protected target database. Select exactly THREE distinct diagnostic checks, one for each case.

  1. Database-scoped execution identity and GRANT results for each target
  2. Per-target elastic job execution outcome and Azure monitoring alert signal
  3. Target group membership and server pool or database exclusions
  4. Fleet job agent settings and dynamic target enumeration results
  5. Azure Automation runbook identity job schedule and Az module logs
  6. Elastic job agent configuration and backing job database metadata

Explanation

Correct Answers

A:

Database-scoped execution identity and GRANT results for each target directly tests the observation that a centrally scheduled elastic job cannot execute its T-SQL on a protected target database. It helps the team evaluate whether it should configure supported target authentication and least-privileged database permissions. The check has a boundary: A job credential must never be shared broadly or overprivileged.

B:

Per-target elastic job execution outcome and Azure monitoring alert signal directly tests the observation that a nightly elastic job fails only on one target and the on-call team requires actionable notification. It helps the team evaluate whether it should configure supported Azure monitoring and notification for job failure outcomes. The check has a boundary: An alert does not repair failed target-specific SQL permissions or scripts.

E:

Azure Automation runbook identity job schedule and Az module logs directly tests the observation that a resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM. It helps the team evaluate whether it should create a scheduled Azure Automation runbook with managed identity and required roles. The check has a boundary: An Automation runbook is not the same as executing T-SQL SQL Server Agent steps.

Incorrect Answers

C:

Target group membership and server pool or database exclusions is appropriate for the separate condition that an elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet. The actual 3 cases are A: A nightly elastic job fails only on one target and the on-call team requires actionable notification; B: A resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM; C: A centrally scheduled elastic job cannot execute its T-SQL on a protected target database. This option is not the specific diagnostic evidence for any of those stated cases.

D:

Fleet job agent settings and dynamic target enumeration results is appropriate for the separate condition that hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly. The actual 3 cases are A: A nightly elastic job fails only on one target and the on-call team requires actionable notification; B: A resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM; C: A centrally scheduled elastic job cannot execute its T-SQL on a protected target database. This option is not the specific diagnostic evidence for any of those stated cases.

F:

Elastic job agent configuration and backing job database metadata is appropriate for the separate condition that a team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions. The actual 3 cases are A: A nightly elastic job fails only on one target and the on-call team requires actionable notification; B: A resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM; C: A centrally scheduled elastic job cannot execute its T-SQL on a protected target database. This option is not the specific diagnostic evidence for any of those stated cases.

Administering Microsoft Azure SQL Solutions (DP-300) Practice Tests

UP

SPECIAL OFFER: GET 10% OFF

This is ONE TIME OFFER

ExamSnap Discount Offer
Enter Your Email Address to Receive Your 10% Off Discount Code

A confirmation link will be sent to this email address to verify your login. *We value your privacy. We will not rent or sell your email address.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your e-mail address below to get started with our interactive software demo of your free trial.

Free Demo Limits: In the demo version you will be able to access only first 5 questions from exam.