Exam DP-300 topic 3 question 5 discussion

Alerts cannot be set at the resource group or Logical SQL server level, So it has to be "SQL Database"

I have checked in Lab. In SQL Database we can create CPU percentage alert rule.

At server level , if you set database level it does not affect the frequency that Query Store writes in the server disk

B - SQL Servers - in this case, since you want to cover all current and future databases on a particular SQL Server, you would configure the alert at the SQL Server level, not at the individual SQL Database level.

SQL Database

I think it should be B since in a question the key is "You must be alerted when CPU usage exceeds 80 percent for any database"

If the scope is changed in Azure Monitor to SQL managed instance, then an alert based on the log search (using KQL) of CPU utilization above 95% (might be a custom query) is supported. Otherwise, SQL VM might be the right answer as this ref https://docs.microsoft.com/en-us/azure/azure-monitor/alerts/alerts-metric-overview indicates that the rule is applied at the VM level.

Tested on Azure SQL. CPU percentage signal returns an error -- "alert rule that uses an Activity Log signal type" -- when scope is specified as the SQL database from the Azure Monitor alert workflow window. This window supports signals at the SQL server scope level, but does not cover CPU percentage, as noted by another person on this discussion. The supported signals include admin tasks at the server level -- create, delete, update SQL server.

C. SQL Databases

The given answer is correct You can specify the scope of monitoring by a single metric alert rule in one of three ways. For example, with virtual machines you can specify the scope as: a list of virtual machines (in one Azure region) within a subscription all virtual machines (in one Azure region) in one or more resource groups in a subscription all virtual machines (in one Azure region) in a subscription Note The scope of a multi-resource metric alert rule must contain at least one resource of the selected resource type. Creating metric alert rules that monitor multiple resources is like creating any other metric alert that monitors a single resource. Only difference is that you would select all the resources you want to monitor. You can also create these rules through Azure Resource Manager templates. You will receive individual notifications for each monitored resource. Note In a metric alert rule that monitors multiple resources, only one condition is allowed.

I think the correct answer is A, https://docs.microsoft.com/en-us/azure/azure-monitor/alerts/alerts-activity-log

The correct Answer is "A". Just make sure to review carefully, "The solution must apply to any additional databases that are created on the Azure SQL server." statement! Then, RG (Resource group) would be the correct Answer.

So, what is the correct answer here?

It should be Azure SQL database server .

answer is correct. you can monitor all database on a specific resouregroup or many resourceg group for sql database type.

Many times, you might want the same alert rule applied to many resources. Azure Monitor also supports monitoring multiple resources (of the same type) with one metric alert rule, for resources that exist in the same Azure region. https://docs.microsoft.com/en-us/azure/azure-monitor/alerts/alerts-metric-overview