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 39

Question 380

Three independently confirmed SQL platform issues require separate evidence checks. Case A: A SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window. Case B: An Agent job fails on an intermittent linked-service outage but succeeds when restarted manually. Case C: A broadly privileged Agent job owner is leaving the team and the job should continue with least privilege. Select exactly THREE distinct diagnostic checks, one for each case.

  1. Feature support matrix listing SQL Agent versus elastic jobs
  2. SQL Server Agent job steps enabled schedule and recent execution history
  3. Job notification configuration operator email profile and job failure history
  4. Agent step retry interval count and failing step history
  5. msdb job owner metadata and SQL Agent security roles
  6. SQL Agent job execution history with step_id error output and timestamps

Explanation

Correct Answers

B:

SQL Server Agent job steps enabled schedule and recent execution history directly tests the observation that a SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window. It helps the team evaluate whether it should create an Agent job with a recurring scheduled T-SQL step. The check has a boundary: A schedule alone is insufficient if SQL Server Agent service is stopped.

D:

Agent step retry interval count and failing step history directly tests the observation that an Agent job fails on an intermittent linked-service outage but succeeds when restarted manually. It helps the team evaluate whether it should configure bounded retry behavior for the specific transient job step. The check has a boundary: Retries should not hide permanent logic failures or duplicate nonidempotent writes.

E:

msdb job owner metadata and SQL Agent security roles directly tests the observation that a broadly privileged Agent job owner is leaving the team and the job should continue with least privilege. It helps the team evaluate whether it should assign an appropriate durable job owner and scoped execution permissions. The check has a boundary: Changing ownership can alter security context and require retesting.

Incorrect Answers

A:

Feature support matrix listing SQL Agent versus elastic jobs is appropriate for the separate condition that an Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service. The actual 3 cases are A: A SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window; B: An Agent job fails on an intermittent linked-service outage but succeeds when restarted manually; C: A broadly privileged Agent job owner is leaving the team and the job should continue with least privilege. This option is not the specific diagnostic evidence for any of those stated cases.

C:

Job notification configuration operator email profile and job failure history is appropriate for the separate condition that a nightly SQL Agent ETL job fails but operators do not receive an alert until morning. The actual 3 cases are A: A SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window; B: An Agent job fails on an intermittent linked-service outage but succeeds when restarted manually; C: A broadly privileged Agent job owner is leaving the team and the job should continue with least privilege. This option is not the specific diagnostic evidence for any of those stated cases.

F:

SQL Agent job execution history with step_id error output and timestamps is appropriate for the separate condition that a multi-step SQL Agent job is marked failed and administrators need the exact failed step and message. The actual 3 cases are A: A SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window; B: An Agent job fails on an intermittent linked-service outage but succeeds when restarted manually; C: A broadly privileged Agent job owner is leaving the team and the job should continue with least privilege. This option is not the specific diagnostic evidence for any of those stated cases.

Question 381

A production database review needs evidence of this condition: A migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance. Which diagnostic artifact would most directly validate the stated condition?

  1. Managed Instance SQL Server Agent feature availability and job history
  2. msdb job owner metadata and SQL Agent security roles
  3. SQL Agent job execution history with step_id error output and timestamps
  4. Feature support matrix listing SQL Agent versus elastic jobs

Explanation

Correct Answer

A:

Managed Instance SQL Server Agent feature availability and job history directly tests the observation that a migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance. It helps the team evaluate whether it should configure and test supported SQL Server Agent jobs on Azure SQL Managed Instance. The check has a boundary: Not every on-premises Agent subsystem is supported on Managed Instance.

Incorrect Answers

B:

Msdb job owner metadata and SQL Agent security roles applies when a broadly privileged Agent job owner is leaving the team and the job should continue with least privilege, not when a migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance.

C:

SQL Agent job execution history with step_id error output and timestamps applies when a multi-step SQL Agent job is marked failed and administrators need the exact failed step and message, not when a migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance.

D:

Feature support matrix listing SQL Agent versus elastic jobs applies when an Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service, not when a migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance.

Question 382

An operator is collecting proof for the following observation: An Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service. Which diagnostic artifact would most directly validate the stated condition?

  1. Job notification configuration operator email profile and job failure history
  2. Feature support matrix listing SQL Agent versus elastic jobs
  3. SQL Agent job execution history with step_id error output and timestamps
  4. SQL Server Agent job steps enabled schedule and recent execution history

Explanation

Correct Answer

B:

Feature support matrix listing SQL Agent versus elastic jobs directly tests the observation that an Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service. It helps the team evaluate whether it should use elastic jobs or a supported external scheduler instead of requiring SQL Agent in Azure SQL Database. The check has a boundary: Database-level Azure SQL Database does not expose ordinary SQL Server Agent.

Incorrect Answers

A:

Job notification configuration operator email profile and job failure history applies when a nightly SQL Agent ETL job fails but operators do not receive an alert until morning, not when an Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service.

C:

SQL Agent job execution history with step_id error output and timestamps applies when a multi-step SQL Agent job is marked failed and administrators need the exact failed step and message, not when an Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service.

D:

SQL Server Agent job steps enabled schedule and recent execution history applies when a SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window, not when an Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service.

Question 383

During SQL troubleshooting the team must test this hypothesis: A nightly SQL Agent ETL job fails but operators do not receive an alert until morning. Which diagnostic artifact would most directly validate the stated condition?

  1. msdb job owner metadata and SQL Agent security roles
  2. Job notification configuration operator email profile and job failure history
  3. Feature support matrix listing SQL Agent versus elastic jobs
  4. SQL Server Agent job steps enabled schedule and recent execution history

Explanation

Correct Answer

B:

Job notification configuration operator email profile and job failure history directly tests the observation that a nightly SQL Agent ETL job fails but operators do not receive an alert until morning. It helps the team evaluate whether it should configure an Agent operator and suitable failure notification integration. The check has a boundary: Notifications require correctly configured mail or external alert delivery.

Incorrect Answers

A:

Msdb job owner metadata and SQL Agent security roles applies when a broadly privileged Agent job owner is leaving the team and the job should continue with least privilege, not when a nightly SQL Agent ETL job fails but operators do not receive an alert until morning.

C:

Feature support matrix listing SQL Agent versus elastic jobs applies when an Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service, not when a nightly SQL Agent ETL job fails but operators do not receive an alert until morning.

D:

SQL Server Agent job steps enabled schedule and recent execution history applies when a SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window, not when a nightly SQL Agent ETL job fails but operators do not receive an alert until morning.

Question 384

A production database review needs evidence of this condition: An Agent job fails on an intermittent linked-service outage but succeeds when restarted manually. Which diagnostic artifact would most directly validate the stated condition?

  1. SQL Agent job execution history with step_id error output and timestamps
  2. Feature support matrix listing SQL Agent versus elastic jobs
  3. msdb job owner metadata and SQL Agent security roles
  4. Agent step retry interval count and failing step history

Explanation

Correct Answer

D:

Agent step retry interval count and failing step history directly tests the observation that an Agent job fails on an intermittent linked-service outage but succeeds when restarted manually. It helps the team evaluate whether it should configure bounded retry behavior for the specific transient job step. The check has a boundary: Retries should not hide permanent logic failures or duplicate nonidempotent writes.

Incorrect Answers

A:

SQL Agent job execution history with step_id error output and timestamps applies when a multi-step SQL Agent job is marked failed and administrators need the exact failed step and message, not when an Agent job fails on an intermittent linked-service outage but succeeds when restarted manually.

B:

Feature support matrix listing SQL Agent versus elastic jobs applies when an Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service, not when an Agent job fails on an intermittent linked-service outage but succeeds when restarted manually.

C:

Msdb job owner metadata and SQL Agent security roles applies when a broadly privileged Agent job owner is leaving the team and the job should continue with least privilege, not when an Agent job fails on an intermittent linked-service outage but succeeds when restarted manually.

Question 385

An operator is collecting proof for the following observation: A broadly privileged Agent job owner is leaving the team and the job should continue with least privilege. Which diagnostic artifact would most directly validate the stated condition?

  1. Agent step retry interval count and failing step history
  2. msdb job owner metadata and SQL Agent security roles
  3. SQL Agent job execution history with step_id error output and timestamps
  4. Job notification configuration operator email profile and job failure history

Explanation

Correct Answer

B:

msdb job owner metadata and SQL Agent security roles directly tests the observation that a broadly privileged Agent job owner is leaving the team and the job should continue with least privilege. It helps the team evaluate whether it should assign an appropriate durable job owner and scoped execution permissions. The check has a boundary: Changing ownership can alter security context and require retesting.

Incorrect Answers

A:

Agent step retry interval count and failing step history applies when an Agent job fails on an intermittent linked-service outage but succeeds when restarted manually, not when a broadly privileged Agent job owner is leaving the team and the job should continue with least privilege.

C:

SQL Agent job execution history with step_id error output and timestamps applies when a multi-step SQL Agent job is marked failed and administrators need the exact failed step and message, not when a broadly privileged Agent job owner is leaving the team and the job should continue with least privilege.

D:

Job notification configuration operator email profile and job failure history applies when a nightly SQL Agent ETL job fails but operators do not receive an alert until morning, not when a broadly privileged Agent job owner is leaving the team and the job should continue with least privilege.

Question 386

During SQL troubleshooting the team must test this hypothesis: A multi-step SQL Agent job is marked failed and administrators need the exact failed step and message. Which diagnostic artifact would most directly validate the stated condition?

  1. SQL Agent job execution history with step_id error output and timestamps
  2. Managed Instance SQL Server Agent feature availability and job history
  3. Feature support matrix listing SQL Agent versus elastic jobs
  4. msdb job owner metadata and SQL Agent security roles

Explanation

Correct Answer

A:

SQL Agent job execution history with step_id error output and timestamps directly tests the observation that a multi-step SQL Agent job is marked failed and administrators need the exact failed step and message. It helps the team evaluate whether it should review the job and step history before changing schedules or credentials. The check has a boundary: The generic final job status alone does not identify its root cause.

Incorrect Answers

B:

Managed Instance SQL Server Agent feature availability and job history applies when a migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance, not when a multi-step SQL Agent job is marked failed and administrators need the exact failed step and message.

C:

Feature support matrix listing SQL Agent versus elastic jobs applies when an Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service, not when a multi-step SQL Agent job is marked failed and administrators need the exact failed step and message.

D:

Msdb job owner metadata and SQL Agent security roles applies when a broadly privileged Agent job owner is leaving the team and the job should continue with least privilege, not when a multi-step SQL Agent job is marked failed and administrators need the exact failed step and message.

Question 387

A migration or configuration change request describes the following problem: A SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window. Which technical or administrative action most directly addresses this requirement?

  1. Create an Agent job with a recurring scheduled T-SQL step
  2. Use elastic jobs or a supported external scheduler instead of requiring SQL Agent in Azure SQL Database
  3. Assign an appropriate durable job owner and scoped execution permissions
  4. Configure bounded retry behavior for the specific transient job step

Explanation

Correct Answer

A:

Create an Agent job with a recurring scheduled T-SQL step directly resolves the reported requirement that a SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window. The maintenance procedure executes at the designated schedule. The implementation must also respect this constraint: A schedule alone is insufficient if SQL Server Agent service is stopped.

Incorrect Answers

B:

Use elastic jobs or a supported external scheduler instead of requiring SQL Agent in Azure SQL Database applies when an Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service, not when a SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window.

C:

Assign an appropriate durable job owner and scoped execution permissions applies when a broadly privileged Agent job owner is leaving the team and the job should continue with least privilege, not when a SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window.

D:

Configure bounded retry behavior for the specific transient job step applies when an Agent job fails on an intermittent linked-service outage but succeeds when restarted manually, not when a SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window.

Question 388

Before implementation the team records this technical condition: A migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance. Which technical or administrative action most directly addresses this requirement?

  1. Create an Agent job with a recurring scheduled T-SQL step
  2. Assign an appropriate durable job owner and scoped execution permissions
  3. Configure and test supported SQL Server Agent jobs on Azure SQL Managed Instance
  4. Review the job and step history before changing schedules or credentials

Explanation

Correct Answer

C:

Configure and test supported SQL Server Agent jobs on Azure SQL Managed Instance directly resolves the reported requirement that a migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance. Existing automation patterns can be retained with compatible changes. The implementation must also respect this constraint: Not every on-premises Agent subsystem is supported on Managed Instance.

Incorrect Answers

A:

Create an Agent job with a recurring scheduled T-SQL step applies when a SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window, not when a migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance.

B:

Assign an appropriate durable job owner and scoped execution permissions applies when a broadly privileged Agent job owner is leaving the team and the job should continue with least privilege, not when a migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance.

D:

Review the job and step history before changing schedules or credentials applies when a multi-step SQL Agent job is marked failed and administrators need the exact failed step and message, not when a migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance.

Question 389

Two independent Azure SQL administration tickets require separate actions. Case A: An Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service. Case B: A nightly SQL Agent ETL job fails but operators do not receive an alert until morning. Select exactly TWO distinct implementation steps, one for each case.

  1. Use elastic jobs or a supported external scheduler instead of requiring SQL Agent in Azure SQL Database
  2. Configure an Agent operator and suitable failure notification integration
  3. Review the job and step history before changing schedules or credentials
  4. Create an Agent job with a recurring scheduled T-SQL step
  5. Assign an appropriate durable job owner and scoped execution permissions

Explanation

Correct Answers

A:

Use elastic jobs or a supported external scheduler instead of requiring SQL Agent in Azure SQL Database directly resolves the reported requirement that an Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service. Supported automation can run without an instance-resident Agent service. The implementation must also respect this constraint: Database-level Azure SQL Database does not expose ordinary SQL Server Agent.

B:

Configure an Agent operator and suitable failure notification integration directly resolves the reported requirement that a nightly SQL Agent ETL job fails but operators do not receive an alert until morning. Operators can receive messages when monitored scheduled jobs fail. The implementation must also respect this constraint: Notifications require correctly configured mail or external alert delivery.

Incorrect Answers

C:

Review the job and step history before changing schedules or credentials is appropriate for the separate condition that a multi-step SQL Agent job is marked failed and administrators need the exact failed step and message. The actual 2 cases are A: An Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service; B: A nightly SQL Agent ETL job fails but operators do not receive an alert until morning. This option is not the specific implementation or corrective step for any of those stated cases.

D:

Create an Agent job with a recurring scheduled T-SQL step is appropriate for the separate condition that a SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window. The actual 2 cases are A: An Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service; B: A nightly SQL Agent ETL job fails but operators do not receive an alert until morning. This option is not the specific implementation or corrective step for any of those stated cases.

E:

Assign an appropriate durable job owner and scoped execution permissions is appropriate for the separate condition that a broadly privileged Agent job owner is leaving the team and the job should continue with least privilege. The actual 2 cases are A: An Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service; B: A nightly SQL Agent ETL job fails but operators do not receive an alert until morning. This option is not the specific implementation or corrective step for any of those stated cases.

Question 390

Three independently confirmed SQL platform issues require separate evidence checks. Case A: A nightly SQL Agent ETL job fails but operators do not receive an alert until morning. Case B: A migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance. Case C: An Agent job fails on an intermittent linked-service outage but succeeds when restarted manually. Select exactly THREE distinct diagnostic checks, one for each case.

  1. Agent step retry interval count and failing step history
  2. msdb job owner metadata and SQL Agent security roles
  3. SQL Agent job execution history with step_id error output and timestamps
  4. Managed Instance SQL Server Agent feature availability and job history
  5. Feature support matrix listing SQL Agent versus elastic jobs
  6. Job notification configuration operator email profile and job failure history

Explanation

Correct Answers

A:

Agent step retry interval count and failing step history directly tests the observation that an Agent job fails on an intermittent linked-service outage but succeeds when restarted manually. It helps the team evaluate whether it should configure bounded retry behavior for the specific transient job step. The check has a boundary: Retries should not hide permanent logic failures or duplicate nonidempotent writes.

D:

Managed Instance SQL Server Agent feature availability and job history directly tests the observation that a migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance. It helps the team evaluate whether it should configure and test supported SQL Server Agent jobs on Azure SQL Managed Instance. The check has a boundary: Not every on-premises Agent subsystem is supported on Managed Instance.

F:

Job notification configuration operator email profile and job failure history directly tests the observation that a nightly SQL Agent ETL job fails but operators do not receive an alert until morning. It helps the team evaluate whether it should configure an Agent operator and suitable failure notification integration. The check has a boundary: Notifications require correctly configured mail or external alert delivery.

Incorrect Answers

B:

msdb job owner metadata and SQL Agent security roles is appropriate for the separate condition that a broadly privileged Agent job owner is leaving the team and the job should continue with least privilege. The actual 3 cases are A: A nightly SQL Agent ETL job fails but operators do not receive an alert until morning; B: A migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance; C: An Agent job fails on an intermittent linked-service outage but succeeds when restarted manually. This option is not the specific diagnostic evidence for any of those stated cases.

C:

SQL Agent job execution history with step_id error output and timestamps is appropriate for the separate condition that a multi-step SQL Agent job is marked failed and administrators need the exact failed step and message. The actual 3 cases are A: A nightly SQL Agent ETL job fails but operators do not receive an alert until morning; B: A migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance; C: An Agent job fails on an intermittent linked-service outage but succeeds when restarted manually. This option is not the specific diagnostic evidence for any of those stated cases.

E:

Feature support matrix listing SQL Agent versus elastic jobs is appropriate for the separate condition that an Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service. The actual 3 cases are A: A nightly SQL Agent ETL job fails but operators do not receive an alert until morning; B: A migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance; C: An Agent job fails on an intermittent linked-service outage but succeeds when restarted manually. 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.