100% Latest & Updated Microsoft DP-300 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
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.
- Database-scoped execution identity and GRANT results for each target
- Per-target elastic job execution outcome and Azure monitoring alert signal
- Target group membership and server pool or database exclusions
- Fleet job agent settings and dynamic target enumeration results
- Azure Automation runbook identity job schedule and Az module logs
- 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.
Question 451
The DBA must resolve this concrete requirement: Hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly. Which technical or administrative action most directly addresses this requirement?
- Configure supported target authentication and least-privileged database permissions
- Create an Azure SQL elastic job for the targeted databases
- Configure supported Azure monitoring and notification for job failure outcomes
- Create a scheduled Azure Automation runbook with managed identity and required roles
Explanation
Correct Answer
B:Create an Azure SQL elastic job for the targeted databases directly resolves the reported requirement that hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly. One managed job can execute against many Azure SQL Database targets. The implementation must also respect this constraint: Elastic jobs require correct target credentials and are not SQL Server Agent.
Incorrect Answers
A:Configure supported target authentication and least-privileged database permissions 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.
C:Configure supported Azure monitoring and notification for job failure outcomes applies when a nightly elastic job fails only on one target and the on-call team requires actionable notification, not when hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly.
D:Create a scheduled Azure Automation runbook with managed identity and required roles 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.
Question 452
A migration or configuration change request describes the following problem: A team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions. Which technical or administrative action most directly addresses this requirement?
- Configure supported Azure monitoring and notification for job failure outcomes
- Create a scheduled Azure Automation runbook with managed identity and required roles
- Configure supported target authentication and least-privileged database permissions
- Create and configure an elastic job agent with its job database
Explanation
Correct Answer
D:Create and configure an elastic job agent with its job database directly resolves the reported requirement that a team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions. The service can persist job definitions and manage execution. The implementation must also respect this constraint: A normal SQL Database alone is not the elastic job scheduling agent.
Incorrect Answers
A:Configure supported Azure monitoring and notification for job failure outcomes applies when a nightly elastic job fails only on one target and the on-call team requires actionable notification, not when a team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions.
B:Create a scheduled Azure Automation runbook with managed identity and required roles 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.
C:Configure supported target authentication and least-privileged database permissions 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.
Question 453
Before implementation the team records this technical condition: An elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet. Which technical or administrative action most directly addresses this requirement?
- Configure supported target authentication and least-privileged database permissions
- Define and verify the elastic job target group explicitly
- Create a scheduled Azure Automation runbook with managed identity and required roles
- Configure supported Azure monitoring and notification for job failure outcomes
Explanation
Correct Answer
B:Define and verify the elastic job target group explicitly directly resolves the reported requirement that an elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet. Job execution scope can be limited to selected databases. The implementation must also respect this constraint: Dynamic target enumeration can include new databases if membership rules are too broad.
Incorrect Answers
A:Configure supported target authentication and least-privileged database permissions 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.
C:Create a scheduled Azure Automation runbook with managed identity and required roles applies when a resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM, not when an elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet.
D:Configure supported Azure monitoring and notification for job failure outcomes applies when a nightly elastic job fails only on one target and the on-call team requires actionable notification, not when an elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet.
Question 454
The DBA must resolve this concrete requirement: A centrally scheduled elastic job cannot execute its T-SQL on a protected target database. Which technical or administrative action most directly addresses this requirement?
- Define and verify the elastic job target group explicitly
- Create and configure an elastic job agent with its job database
- Configure supported target authentication and least-privileged database permissions
- Create a scheduled Azure Automation runbook with managed identity and required roles
Explanation
Correct Answer
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.
Incorrect Answers
A:Define and verify the elastic job target group explicitly 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.
B:Create and configure an elastic job agent with its job database 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:Create a scheduled Azure Automation runbook with managed identity and required roles applies when a resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM, not when a centrally scheduled elastic job cannot execute its T-SQL on a protected target database.
Question 455
A migration or configuration change request describes the following problem: An elastic job executes manually but has not been configured for the required nightly cadence. Which technical or administrative action most directly addresses this requirement?
- Create a scheduled Azure Automation runbook with managed identity and required roles
- Define and verify the elastic job target group explicitly
- Set a supported elastic job schedule and monitor job executions
- Configure supported target authentication and least-privileged database permissions
Explanation
Correct Answer
C:Set a supported elastic job schedule and monitor job executions directly resolves the reported requirement that 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. The implementation must also respect this constraint: Successful job submission does not mean every individual target succeeded.
Incorrect Answers
A:Create a scheduled Azure Automation runbook with managed identity and required roles 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.
B:Define and verify the elastic job target group explicitly 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.
D:Configure supported target authentication and least-privileged database permissions applies when a centrally scheduled elastic job cannot execute its T-SQL on a protected target database, not when an elastic job executes manually but has not been configured for the required nightly cadence.
Question 456
Before implementation the team records this technical condition: A resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM. Which technical or administrative action most directly addresses this requirement?
- Create a scheduled Azure Automation runbook with managed identity and required roles
- Create and configure an elastic job agent with its job database
- Define and verify the elastic job target group explicitly
- Configure supported target authentication and least-privileged database permissions
Explanation
Correct Answer
A: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
B:Create and configure an elastic job agent with its job database applies when a team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions, not when a resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM.
C:Define and verify the elastic job target group explicitly 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.
D:Configure supported target authentication and least-privileged database 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.
Question 457
The DBA must resolve this concrete requirement: A nightly elastic job fails only on one target and the on-call team requires actionable notification. Which technical or administrative action most directly addresses this requirement?
- Create an Azure SQL elastic job for the targeted databases
- Define and verify the elastic job target group explicitly
- Create and configure an elastic job agent with its job database
- Configure supported Azure monitoring and notification for job failure outcomes
Explanation
Correct Answer
D:Configure supported Azure monitoring and notification for job failure outcomes directly resolves the reported requirement that 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. The implementation must also respect this constraint: An alert does not repair failed target-specific SQL permissions or scripts.
Incorrect Answers
A:Create an Azure SQL elastic job for the targeted databases 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:Define and verify the elastic job target group explicitly 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.
C:Create and configure an elastic job agent with its job database applies when a team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions, not when a nightly elastic job fails only on one target and the on-call team requires actionable notification.
Question 458
A post-change impact assessment considers the requirement that: Hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly. What operational outcome follows from implementing the appropriate solution?
- One managed job can execute against many Azure SQL Database targets
- Maintenance runs on an expected cadence with inspectable execution history
- The service can persist job definitions and manage execution
- Resource administration can run under an Azure-hosted scheduler
Explanation
Correct Answer
A:One managed job can execute against many Azure SQL Database targets is the expected technical effect when the administrator chooses the relevant approach for hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly. The needed action is to create an Azure SQL elastic job for the targeted databases.
Incorrect Answers
B:Maintenance runs on an expected cadence with inspectable execution history applies when an elastic job executes manually but has not been configured for the required nightly cadence, not when hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly.
C:The service can persist job definitions and manage execution applies when a team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions, not when hundreds of separate Azure SQL Databases must execute the same controlled data-maintenance T-SQL nightly.
D:Resource administration can run under an Azure-hosted scheduler 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.
Question 459
Two independent Azure SQL administration tickets require separate actions. Case A: A team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions. Case B: An elastic job executes manually but has not been configured for the required nightly cadence. Select exactly TWO distinct implementation steps, one for each case.
- Configure supported Azure monitoring and notification for job failure outcomes
- Configure supported target authentication and least-privileged database permissions
- Set a supported elastic job schedule and monitor job executions
- Create a scheduled Azure Automation runbook with managed identity and required roles
- Create and configure an elastic job agent with its job database
Explanation
Correct Answers
C:Set a supported elastic job schedule and monitor job executions directly resolves the reported requirement that 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. The implementation must also respect this constraint: Successful job submission does not mean every individual target succeeded.
E:Create and configure an elastic job agent with its job database directly resolves the reported requirement that a team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions. The service can persist job definitions and manage execution. The implementation must also respect this constraint: A normal SQL Database alone is not the elastic job scheduling agent.
Incorrect Answers
A:Configure supported Azure monitoring and notification for job failure outcomes 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 2 cases are A: A team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions; B: An elastic job executes manually but has not been configured for the required nightly cadence. This option is not the specific implementation or corrective step for any of those stated cases.
B:Configure supported target authentication and least-privileged database permissions is appropriate for the separate condition that a centrally scheduled elastic job cannot execute its T-SQL on a protected target database. The actual 2 cases are A: A team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions; B: An elastic job executes manually but has not been configured for the required nightly cadence. This option is not the specific implementation or corrective step for any of those stated cases.
D:Create a scheduled Azure Automation runbook with managed identity and required roles is appropriate for the separate condition that a resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM. The actual 2 cases are A: A team tries to execute elastic jobs but has not provisioned the resource that stores their job definitions; B: An elastic job executes manually but has not been configured for the required nightly cadence. This option is not the specific implementation or corrective step for any of those stated cases.
Question 460
Three independently confirmed SQL platform issues require separate evidence checks. Case A: An elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet. Case B: A centrally scheduled elastic job cannot execute its T-SQL on a protected target database. Case C: A nightly elastic job fails only on one target and the on-call team requires actionable notification. Select exactly THREE distinct diagnostic checks, one for each case.
- Per-target elastic job execution outcome and Azure monitoring alert signal
- Database-scoped execution identity and GRANT results for each target
- Target group membership and server pool or database exclusions
- Fleet job agent settings and dynamic target enumeration results
- Elastic job agent configuration and backing job database metadata
- Azure Automation runbook identity job schedule and Az module logs
Explanation
Correct Answers
A: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.
B: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.
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
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: An elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet; B: A centrally scheduled elastic job cannot execute its T-SQL on a protected target database; C: A nightly elastic job fails only on one target and the on-call team requires actionable notification. This option is not the specific diagnostic evidence for any of those stated cases.
E: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: An elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet; B: A centrally scheduled elastic job cannot execute its T-SQL on a protected target database; C: A nightly elastic job fails only on one target and the on-call team requires actionable notification. This option is not the specific diagnostic evidence for any of those stated cases.
F:Azure Automation runbook identity job schedule and Az module logs is appropriate for the separate condition that a resource group requires periodically updating SQL resource settings using Azure PowerShell without a continuously running VM. The actual 3 cases are A: An elastic job accidentally ran against an unexpected database and must be constrained to an approved fleet; B: A centrally scheduled elastic job cannot execute its T-SQL on a protected target database; C: A nightly elastic job fails only on one target and the on-call team requires actionable notification. This option is not the specific diagnostic evidence for any of those stated cases.
Administering Microsoft Azure SQL Solutions (DP-300) Practice Tests