You need to configure a runbook to execute when a Microsoft Azure SQL database uses more than 80 percent of the Database Throughput Unit (DTU) resources. What should you configure in the runbook?

While a runbook has triggers (like a webhook or schedule), 'a trigger' is too generic and not the specific mechanism configured within the runbook to receive external HTTP requests.

A connection asset stores authentication information for accessing other services but does not initiate runbook execution.

A webhook provides an HTTP endpoint that can be used by external services, such as an Azure Monitor alert's action group, to start an Azure Automation runbook. When the DTU utilization alert fires, it can invoke the runbook's webhook, initiating its execution to perform remedial or notification actions.

A job is an instance of a runbook execution, not the configuration that initiates the runbook based on an external event like a DTU threshold breach.