C.

lifecycle management

The lifecycle management policy lets you:
Delete blobs, blob versions, and blob snapshots at the end of their lifecycles
Reference:
https://docs.microsoft.com/en-us/azure/storage/blobs/storage-lifecycle-managementconcepts

C.

Modify the automatic tuning settings for db1.

Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/automatic-tuning-overview

D.

READ_COMMITTED_SNAPSHOT to ON

Explanation:
In SQL Server, you can also minimize locking contention while protecting transactions from
dirty reads of uncommitted data modifications using either:
The READ COMMITTED isolation level with the
READ_COMMITTED_SNAPSHOT database option set to ON.
The SNAPSHOT isolation level.
If READ_COMMITTED_SNAPSHOT is set to ON (the default on SQL Azure Database),
the Database Engine uses row versioning to present each statement with a transactionally
consistent snapshot of the data as it existed at the start of the statement. Locks are not
used to protect the data from updates by other transactions.
Reference:
https://docs.microsoft.com/en-us/sql/t-sql/statements/set-transaction-isolation-leveltransact-
sql

B.

Set the Alert logic threshold to Dynamic

D.

Set Threshold Sensitivity to Low

B: Dynamic Thresholds continuously learns the data of the metric series and tries to model
it using a set of algorithms and methods. It detects patterns in the data such as seasonality
(Hourly / Daily / Weekly), and is able to handle noisy metrics (such as machine CPU or
memory) as well as metrics with low dispersion (such as availability and error rate).
D: Alert threshold sensitivity is a high-level concept that controls the amount of deviation
from metric behavior required to trigger an alert.
Low – The thresholds will be loose with more distance from metric series pattern. An alert
rule will only trigger on large deviations, resulting in fewer alerts.
Reference:
https://docs.microsoft.com/en-us/azure/azure-monitor/platform/alerts-dynamic-thresh

B.

CPU% utilization

Scenario: Real-time processing must be monitored to ensure that workloads are sized
properly based on actual usage patterns.
To monitor the performance of a database in Azure SQL Database and Azure SQL
Managed Instance, start by monitoring the CPU and IO resources used by your workload
relative to the level of database performance you chose in selecting a particular service tier
and performance level.
Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/monitor-tune-overview

D.

Azure Database Migration Service

https://www.techtarget.com/searchitoperations/tip/Easily-transfer-VMs-to-thecloud-
with-Microsoft-Azure-Migrate