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 40

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.

Question 391

Before implementation the team records this technical condition: An Agent job fails on an intermittent linked-service outage but succeeds when restarted manually. Which technical or administrative action most directly addresses this requirement?

  1. Review the job and step history before changing schedules or credentials
  2. Configure bounded retry behavior for the specific transient job step
  3. Use elastic jobs or a supported external scheduler instead of requiring SQL Agent in Azure SQL Database
  4. Assign an appropriate durable job owner and scoped execution permissions

Explanation

Correct Answer

B:

Configure bounded retry behavior for the specific transient job step directly resolves the reported requirement that an Agent job fails on an intermittent linked-service outage but succeeds when restarted manually. Known temporary failures can be retried within the schedule. The implementation must also respect this constraint: Retries should not hide permanent logic failures or duplicate nonidempotent writes.

Incorrect Answers

A:

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 an Agent job fails on an intermittent linked-service outage but succeeds when restarted manually.

C:

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 an Agent job fails on an intermittent linked-service outage but succeeds when restarted manually.

D:

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 an Agent job fails on an intermittent linked-service outage but succeeds when restarted manually.

Question 392

The DBA must resolve this concrete requirement: A broadly privileged Agent job owner is leaving the team and the job should continue with least privilege. Which technical or administrative action most directly addresses this requirement?

  1. Configure bounded retry behavior for the specific transient job step
  2. Assign an appropriate durable job owner and scoped execution permissions
  3. Use elastic jobs or a supported external scheduler instead of requiring SQL Agent in Azure SQL Database
  4. Review the job and step history before changing schedules or credentials

Explanation

Correct Answer

B:

Assign an appropriate durable job owner and scoped execution permissions directly resolves the reported requirement that a broadly privileged Agent job owner is leaving the team and the job should continue with least privilege. The scheduled job can run under a controlled service identity. The implementation must also respect this constraint: Changing ownership can alter security context and require retesting.

Incorrect Answers

A:

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 broadly privileged Agent job owner is leaving the team and the job should continue with least privilege.

C:

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 broadly privileged Agent job owner is leaving the team and the job should continue with least privilege.

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 broadly privileged Agent job owner is leaving the team and the job should continue with least privilege.

Question 393

A migration or configuration change request describes the following problem: A multi-step SQL Agent job is marked failed and administrators need the exact failed step and message. Which technical or administrative action most directly addresses this requirement?

  1. Assign an appropriate durable job owner and scoped execution permissions
  2. Configure an Agent operator and suitable failure notification integration
  3. Configure bounded retry behavior for the specific transient job step
  4. Review the job and step history before changing schedules or credentials

Explanation

Correct Answer

D:

Review the job and step history before changing schedules or credentials directly resolves the reported requirement that a multi-step SQL Agent job is marked failed and administrators need the exact failed step and message. Diagnosis identifies whether failure was in a step command security or dependencies. The implementation must also respect this constraint: The generic final job status alone does not identify its root cause.

Incorrect Answers

A:

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 multi-step SQL Agent job is marked failed and administrators need the exact failed step and message.

B:

Configure an Agent operator and suitable failure notification integration applies when a nightly SQL Agent ETL job fails but operators do not receive an alert until morning, not when a multi-step SQL Agent job is marked failed and administrators need the exact failed step and message.

C:

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 multi-step SQL Agent job is marked failed and administrators need the exact failed step and message.

Question 394

The team needs to anticipate the behavior of a correct solution for: A SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window. What operational outcome follows from implementing the appropriate solution?

  1. The scheduled job can run under a controlled service identity
  2. The maintenance procedure executes at the designated schedule
  3. Diagnosis identifies whether failure was in a step command security or dependencies
  4. Existing automation patterns can be retained with compatible changes

Explanation

Correct Answer

B:

The maintenance procedure executes at the designated schedule is the expected technical effect when the administrator chooses the relevant approach for a SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window. The needed action is to create an Agent job with a recurring scheduled T-SQL step.

Incorrect Answers

A:

The scheduled job can run under a controlled service identity 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.

C:

Diagnosis identifies whether failure was in a step command security or dependencies applies when a multi-step SQL Agent job is marked failed and administrators need the exact failed step and message, not when a SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window.

D:

Existing automation patterns can be retained with compatible changes applies when a migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance, not when a SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window.

Question 395

An operational planning meeting reviews this deployment condition: A migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance. What operational outcome follows from implementing the appropriate solution?

  1. Existing automation patterns can be retained with compatible changes
  2. Diagnosis identifies whether failure was in a step command security or dependencies
  3. Operators can receive messages when monitored scheduled jobs fail
  4. The scheduled job can run under a controlled service identity

Explanation

Correct Answer

A:

Existing automation patterns can be retained with compatible changes is the expected technical effect when the administrator chooses the relevant approach for a migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance. The needed action is to configure and test supported SQL Server Agent jobs on Azure SQL Managed Instance.

Incorrect Answers

B:

Diagnosis identifies whether failure was in a step command security or dependencies 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.

C:

Operators can receive messages when monitored scheduled jobs fail applies when a nightly SQL Agent ETL job fails but operators do not receive an alert until morning, not when a migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance.

D:

The scheduled job can run under a controlled service identity 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.

Question 396

A post-change impact assessment considers the requirement that: An Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service. What operational outcome follows from implementing the appropriate solution?

  1. Diagnosis identifies whether failure was in a step command security or dependencies
  2. Supported automation can run without an instance-resident Agent service
  3. Operators can receive messages when monitored scheduled jobs fail
  4. Known temporary failures can be retried within the schedule

Explanation

Correct Answer

B:

Supported automation can run without an instance-resident Agent service is the expected technical effect when the administrator chooses the relevant approach for an Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service. The needed action is to use elastic jobs or a supported external scheduler instead of requiring SQL Agent in Azure SQL Database.

Incorrect Answers

A:

Diagnosis identifies whether failure was in a step command security or dependencies 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.

C:

Operators can receive messages when monitored scheduled jobs fail 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.

D:

Known temporary failures can be retried within the schedule applies when an Agent job fails on an intermittent linked-service outage but succeeds when restarted manually, not when an Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service.

Question 397

The team needs to anticipate the behavior of a correct solution for: A nightly SQL Agent ETL job fails but operators do not receive an alert until morning. What operational outcome follows from implementing the appropriate solution?

  1. Diagnosis identifies whether failure was in a step command security or dependencies
  2. Operators can receive messages when monitored scheduled jobs fail
  3. Supported automation can run without an instance-resident Agent service
  4. The scheduled job can run under a controlled service identity

Explanation

Correct Answer

B:

Operators can receive messages when monitored scheduled jobs fail is the expected technical effect when the administrator chooses the relevant approach for a nightly SQL Agent ETL job fails but operators do not receive an alert until morning. The needed action is to configure an Agent operator and suitable failure notification integration.

Incorrect Answers

A:

Diagnosis identifies whether failure was in a step command security or dependencies applies when a multi-step SQL Agent job is marked failed and administrators need the exact failed step and message, not when a nightly SQL Agent ETL job fails but operators do not receive an alert until morning.

C:

Supported automation can run without an instance-resident Agent service 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:

The scheduled job can run under a controlled service identity 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.

Question 398

An operational planning meeting reviews this deployment condition: An Agent job fails on an intermittent linked-service outage but succeeds when restarted manually. What operational outcome follows from implementing the appropriate solution?

  1. Diagnosis identifies whether failure was in a step command security or dependencies
  2. Supported automation can run without an instance-resident Agent service
  3. Known temporary failures can be retried within the schedule
  4. The scheduled job can run under a controlled service identity

Explanation

Correct Answer

C:

Known temporary failures can be retried within the schedule is the expected technical effect when the administrator chooses the relevant approach for an Agent job fails on an intermittent linked-service outage but succeeds when restarted manually. The needed action is to configure bounded retry behavior for the specific transient job step.

Incorrect Answers

A:

Diagnosis identifies whether failure was in a step command security or dependencies 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:

Supported automation can run without an instance-resident Agent service 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.

D:

The scheduled job can run under a controlled service identity 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 399

Two independent Azure SQL administration tickets require separate actions. Case A: A broadly privileged Agent job owner is leaving the team and the job should continue with least privilege. Case B: A SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window. 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 and test supported SQL Server Agent jobs on Azure SQL Managed Instance
  3. Create an Agent job with a recurring scheduled T-SQL step
  4. Assign an appropriate durable job owner and scoped execution permissions
  5. Configure bounded retry behavior for the specific transient job step

Explanation

Correct Answers

C:

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.

D:

Assign an appropriate durable job owner and scoped execution permissions directly resolves the reported requirement that a broadly privileged Agent job owner is leaving the team and the job should continue with least privilege. The scheduled job can run under a controlled service identity. The implementation must also respect this constraint: Changing ownership can alter security context and require retesting.

Incorrect Answers

A:

Use elastic jobs or a supported external scheduler instead of requiring SQL Agent in Azure SQL Database 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 2 cases are A: A broadly privileged Agent job owner is leaving the team and the job should continue with least privilege; B: A SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window. This option is not the specific implementation or corrective step for any of those stated cases.

B:

Configure and test supported SQL Server Agent jobs on Azure SQL Managed Instance is appropriate for the separate condition that a migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance. The actual 2 cases are A: A broadly privileged Agent job owner is leaving the team and the job should continue with least privilege; B: A SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window. This option is not the specific implementation or corrective step for any of those stated cases.

E:

Configure bounded retry behavior for the specific transient job step is appropriate for the separate condition that an Agent job fails on an intermittent linked-service outage but succeeds when restarted manually. The actual 2 cases are A: A broadly privileged Agent job owner is leaving the team and the job should continue with least privilege; B: A SQL Server on Azure VM needs an index-maintenance stored procedure to run every Sunday after its reporting window. This option is not the specific implementation or corrective step for any of those stated cases.

Question 400

Three independently confirmed SQL platform issues require separate evidence checks. Case A: A multi-step SQL Agent job is marked failed and administrators need the exact failed step and message. Case B: A migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance. Case C: An Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service. Select exactly THREE distinct diagnostic checks, one for each case.

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

Explanation

Correct Answers

A:

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.

B:

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.

C:

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

D:

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 multi-step SQL Agent job is marked failed and administrators need the exact failed step and message; B: A migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance; C: An Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service. This option is not the specific diagnostic evidence for any of those stated cases.

E:

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 multi-step SQL Agent job is marked failed and administrators need the exact failed step and message; B: A migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance; C: An Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service. This option is not the specific diagnostic evidence for any of those stated cases.

F:

SQL Server Agent job steps enabled schedule and recent execution history 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 3 cases are A: A multi-step SQL Agent job is marked failed and administrators need the exact failed step and message; B: A migrated workload uses SQL Server Agent jobs and the new target is Azure SQL Managed Instance; C: An Azure SQL Database administrator looks for SQL Server Agent under the single-database PaaS service. 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.