最新的Microsoft Administering Relational Databases on Microsoft Azure (DP-300 Korean Version) - DP-300 Korean免費考試真題

說明：（僅 PDFExamDumps 成員可見）

Explanation:

Box 1: SET AUTOMATIC_TUNING = AUTO
To enable automatic tuning on a single database via T-SQL, connect to the database and execute the following query:
ALTER DATABASE current SET AUTOMATIC_TUNING = AUTO
Setting automatic tuning to AUTO will apply Azure Defaults.
Box 2: SET AUTOMATIC_TUNING (FORCE_LAST_GOOD_PLAN = ON)
To configure individual automatic tuning options via T-SQL, connect to the database and execute the query such as this one:
ALTER DATABASE current SET AUTOMATIC_TUNING (FORCE_LAST_GOOD_PLAN = ON) Setting the individual tuning option to ON will override any setting that database inherited and enable the tuning option. Setting it to OFF will also override any setting that database inherited and disable the tuning option.
Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/automatic-tuning-enable

Explanation:

Basic Concept: This question tests high availability and disaster recovery design for Azure SQL, SQL Server on Azure VMs, and regional failure scenarios.
Why the selected answer is Correct: The selected values fit this scenario because they apply the required Azure SQL configuration at the correct scope and sequence: You configure a long-term retention policy for an Azure SQL database as shown in the exhibit.
Why the alternate choices are Wrong: The alternate selections apply to different administrative stages or different scopes. In a hotspot or drag-drop task, order and scope are part of the answer, so a technically valid Azure feature can still be wrong if it is placed in the wrong step.

說明：（僅 PDFExamDumps 成員可見）

說明：（僅 PDFExamDumps 成員可見）

說明：（僅 PDFExamDumps 成員可見）

說明：（僅 PDFExamDumps 成員可見）

說明：（僅 PDFExamDumps 成員可見）

Explanation:
" Assigned Identity " and " Key id " https://learn.microsoft.com/en-us/powershell/module/az.sql/new- azsqlserver?view=azps-10.2.0#code-try-3 Basic Concept: This question tests identity and authentication for Azure SQL and SQL Server workloads, including when to use contained users, directory identities, certificate validation, or authentication profiles.
Why the selected answer is Correct: The selected values fit this scenario because they apply the required Azure SQL configuration at the correct scope and sequence: You need to deploy a logical SQL server by using PowerShell.
Why the alternate choices are Wrong: The alternate actions fail because Entra authentication must be established at the server/administrator level first, then mapped to contained database users, and finally used by the client connection.

說明：（僅 PDFExamDumps 成員可見）

說明：（僅 PDFExamDumps 成員可見）

說明：（僅 PDFExamDumps 成員可見）

Explanation:

Box 1: Move to cool storage
The cool access tier has lower storage costs and higher access costs compared to hot storage. This tier is intended for data that will remain in the cool tier for at least 30 days. Example usage scenarios for the cool access tier include:
Short-term backup and disaster recovery
Older data not used frequently but expected to be available immediately when accessed Large data sets that need to be stored cost effectively, while more data is being gathered for future processing Note: Hot - Optimized for storing data that is accessed frequently.
Cool - Optimized for storing data that is infrequently accessed and stored for at least 30 days.
Archive - Optimized for storing data that is rarely accessed and stored for at least 180 days with flexible latency requirements, on the order of hours.
Box 2: Move to archive storage
Example usage scenarios for the archive access tier include:
Long-term backup, secondary backup, and archival datasets
Original (raw) data that must be preserved, even after it has been processed into final usable form Compliance and archival data that needs to be stored for a long time and is hardly ever accessed Reference:
https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-storage-tiers

說明：（僅 PDFExamDumps 成員可見）