For rowstore tables and indexes, use the data compression feature to help reduce the size of the database. In addition to saving space, data compression can help improve performance of I/O intensive workloads because the data is stored in fewer pages and queries need to read fewer pages from disk.
Use columnstore archival compression to further reduce the data size for situations when you can afford extra time and CPU resources to store and retrieve the data.
Basic Concept: This question tests Azure monitoring and performance management, including which metric, log destination, or alerting behavior fits the operational requirement.
Why B and E is Correct: Queries that use the index will retrieve fewer data pages. matches the expected DP-
300 administration action. Queries that use the index will retrieve fewer data pages. is related to operational monitoring or tuning, but it must match the exact signal needed: query history, resource utilization, wait
/blocking detail, or automatic remediation. The question is not asking for a general Azure capability; it is asking for the feature that produces this result: Each correct answer presents a complete solution. CPU percentage is important for database compute monitoring, but it is not the Stream Analytics sizing metric when the question is about streaming units. The scenario asks for: Each correct answer presents a complete solution. That makes Queries that use the index will consume more CPU resources. the option that satisfies the required Azure SQL layer and operational outcome.
Why A is Wrong: Queries that use the index will consume more disk I/O. is related to operational monitoring or tuning, but it must match the exact signal needed: query history, resource utilization, wait/blocking detail, or automatic remediation. It would produce a different operational signal than the one needed to investigate, alert, or tune the workload in this question.
Why C is Wrong: The index will consume more disk space. is related to operational monitoring or tuning, but it must match the exact signal needed: query history, resource utilization, wait/blocking detail, or automatic remediation. It is useful in other troubleshooting paths, but this scenario requires a more specific monitoring or optimization feature.
Why D is Wrong: The index will consume more memory. is related to operational monitoring or tuning, but it must match the exact signal needed: query history, resource utilization, wait/blocking detail, or automatic remediation. It would produce a different operational signal than the one needed to investigate, alert, or tune the workload in this question.