Exam DP-300 topic 18 question 1 discussion

A: Elastic pool and databases B: Log Analytics Streaming to log analytics is possible: https://learn.microsoft.com/en-us/azure/azure-sql/database/metrics-diagnostic-telemetry-logging-streaming-export-configure?view=azuresql&tabs=azure-portal You can stream metrics and resource logs to a Log Analytics workspace in Azure Monitor. Data streamed here can be consumed by SQL Analytics (preview), which is a cloud only monitoring solution that provides intelligent monitoring of your databases that includes performance reports, alerts, and mitigation recommendations. Data streamed to a Log Analytics workspace can be analyzed with other monitoring data collected and also enables you to leverage other Azure Monitor features such as alerts and visualizations. https://learn.microsoft.com/en-us/azure/azure-sql/database/monitor-tune-overview?view=azuresql Collecting server metrics is not an option: https://learn.microsoft.com/en-us/azure/azure-sql/database/elastic-pool-resource-management?view=azuresql

Further to my previous comment the below is in the scenario: All SQL Server and Azure SQL Database metrics related to CPU and storage usage and limits must be analyzed by using Azure built-in functionality.

To implement the monitoring of SalesSQLDb1 and meet the technical requirements, here's how you should configure the options: Collect metrics from: The server, the elastic pool, and the database - This option will collect metrics at every layer, including the SQL Server instance, the elastic pool, and individual databases. This provides comprehensive coverage of all possible metrics across different levels. Stream metrics to: Azure Log Analytics - This option allows you to stream metrics to a centralized service where you can analyze them in real time, create dashboards, and set up alerts. It is well-suited for in-depth analysis and is integrated into Azure Monitor, which aligns with the requirement to monitor SQL Server and Azure SQL Database metrics related to CPU and storage usage.

Elastic pool and databases. Log Analytics. Allows the use of a single dashboard to monitor all metrics from Azure resources; and SalesSQLDB1 is in an Azure Elastic Pool.

Because you need to collect and stream data, it has to go the destination of Azure Event Hub.

Given answer is correct. We can set alerts on both elastic pool and database level, plus company has dbs on Azure VMs

Server does not have metrics, So its only "Elastic pool and Database"

IMO, collecting 'basic' metric from the Elastic pool and the database to a Log Analytics Workspace is enough to meet the tech requirements.

It is to 'Implement the monitoring of SalesSQLDb1', in which the SalesSQLDb1 is elastic pool, and can use cloud solution to monitor.

Why not the server, the pool and the database?

Database only and Log Analytics