[Reference:, https://community.idera.com/database-tools/blog/b/community_blog/posts/why-use-a-date-dimension-table-ina-data-warehouse, , , , , , , , Basic Concept: This question tests monitor, configure, and optimize database resources in the DP-300 exam context. The correct choice is determined by the exact service boundary and operational requirement stated in the scenario., Why B and D is Correct: Create a date dimension table that has an integer key in the format of YYYYMMDD. matches the expected DP-300 administration action. Create a date dimension table that has an integer key in the format of YYYYMMDD. 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: You need to ensure that the design provides the fastest query times of the records when querying for arbitrary date ranges and aggregating by fiscal calendar attributes. Use integer columns for the date fields. matches the expected DP-300 administration action. Use integer columns for the date fields. 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: You need to ensure that the design provides the fastest query times of the records when querying for arbitrary date ranges and aggregating by fiscal calendar attributes., Why A is Wrong: Create a date dimension table that has a DateTime key. 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 does not expose the required metric, query history, wait/blocking signal, or tuning mechanism; using it would not give the administrator the evidence requested., Why C is Wrong: Use built-in SQL functions to extract date attributes. 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 E is Wrong: Use DateTime columns for the date fields. 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., ]