Configure and manage automation of tasks →hardMultiple Choice

DP-300 Configure and manage automation of tasks Practice Question

Exhibit

Refer to the exhibit.

{
    "type": "Microsoft.Sql/servers/databases",
    "apiVersion": "2023-08-01-preview",
    "name": "[format('{0}/{1}', parameters('serverName'), parameters('databaseName'))]",
    "location": "[parameters('location')]",
    "properties": {
        "collation": "SQL_Latin1_General_CP1_CI_AS",
        "maxSizeBytes": 1073741824,
        "readScale": "Disabled",
        "zoneRedundant": false,
        "autoPauseDelay": 60
    },
    "sku": {
        "name": "GP_Gen5_2",
        "tier": "GeneralPurpose",
        "family": "Gen5",
        "capacity": 2
    }
}

Refer to the exhibit. You are deploying an Azure SQL Database using this ARM template. After deployment, you need to automate the scaling of the database to a higher service tier when DTU consumption exceeds 80% for 5 minutes. Which Azure service should you use to trigger the scaling?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Azure Monitor metric alert

Azure Monitor metric alerts can be configured to trigger an Azure Automation runbook that scales the Azure SQL Database when DTU consumption exceeds 80% for 5 minutes. This is a common pattern for autoscaling based on metrics. Option A (Azure SQL Analytics) is a monitoring solution that does not trigger actions. Option B (Azure Automation Update Management) is for managing updates on virtual machines, not for scaling databases. Option C (SQL Server Agent) is not available in Azure SQL Database; it is used for on-premises SQL Server instances.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Azure SQL Analytics
Why it's wrong here
Azure SQL Analytics is a monitoring solution that visualises DTU and query performance in Log Analytics; it raises no alerts and executes no scaling action. It would be the right choice for historical performance reporting, not for triggering an automated tier change.
✗
Azure Automation Update Management
Why it's wrong here
Update Management schedules patching and inventory on VMs, not metric-driven database scaling. It is tempting because Azure Automation runbooks can scale Azure SQL Database, but the trigger must be an alert on the DTU metric, which Update Management cannot raise.
✗
SQL Server Agent
Why it's wrong here
SQL Server Agent runs scheduled T-SQL jobs inside SQL Server or Managed Instance, and is unavailable in Azure SQL Database. It is tempting because agent jobs commonly automate maintenance, but scaling requires an alert rule reacting to the DTU metric, which the agent cannot observe.
✓
Azure Monitor metric alert
Why this is correct
Azure Monitor metric alerts evaluate the database's DTU percentage against an 80% threshold sustained over a five-minute window, then fire an action group. That action group can invoke automation to scale the service tier, giving the required metric-driven trigger.

Go deeper

DP-300 Configure and manage automation of tasks Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question