DP-300日本語 無料問題集「Microsoft Administering Relational Databases on Microsoft Azure (DP-300日本語版)」

Explanation:
Box 1: sys.resource_stats
sys.resource_stats returns CPU usage and storage data for an Azure SQL Database. It has database_name and start_time columns.
Box 2: DateAdd
The following example returns all databases that are averaging at least 80% of compute utilization over the last one week.
DECLARE @s datetime;
DECLARE @e datetime;
SET @s= DateAdd(d,-7,GetUTCDate());
SET @e= GETUTCDATE();
SELECT database_name, AVG(avg_cpu_percent) AS Average_Compute_Utilization FROM sys.resource_stats WHERE start_time BETWEEN @s AND @e GROUP BY database_name HAVING AVG(avg_cpu_percent) >= 80 Incorrect Answers:
sys.dm_exec_requests:
sys.dm_exec_requests returns information about each request that is executing in SQL Server. It does not have a column named database_name.
sys.dm_db_resource_stats:
sys.dm_db_resource_stats does not have any start_time column.
Note: sys.dm_db_resource_stats returns CPU, I/O, and memory consumption for an Azure SQL Database database. One row exists for every 15 seconds, even if there is no activity in the database. Historical data is maintained for approximately one hour.
Sys.dm_user_db_resource_governance returns actual configuration and capacity settings used by resource governance mechanisms in the current database or elastic pool. It does not have any start_time column.
Reference:
https://docs.microsoft.com/en-us/sql/relational-databases/system-catalog-views/sys-resource- stats-azure-sql-database

To classify your SQL Server database:
Step 1: In SQL Server Management Studio (SSMS), connect to the SQL Server.
Step 2: In the SSMS Object Explorer, select the database [Here db1] that you would like to classify and choose Tasks > Data Discovery and Classification > Classify Data....

Step 3: The classification engine scans your database for columns containing potentially sensitive data and provides a list of recommended column classifications:


Step 4: You can change the recommended Information Type and Sensitivity Label using the drop- down boxes.

Step 5: Select columns StandardCost and ListPrice. Unselect other columns if necessary. For StandardCost and ListPrice columns select information type of Financial, and sensitivity label of Confidential.
Step 6: To apply the selected recommendations, select the Save selected recommendations button.

Step 7: To display the classified columns, select appropriate schema and corresponding table from the drop-down, then select Load Columns.

Step 8: You can also manually classify columns as an alternative, or in addition, to the recommendation-based classification:
Select Add classification in the top menu of the window.

Step 9: If you want to add classification for all the unclassified columns for a specific table in a single attempt, then select All Unclassified in the Column drop down of Add Classification page.

Step 10: To complete your classification and persistently label (tag) the database columns with the new classification metadata, select the Save button on the top menu of the window.

Reference:
https://learn.microsoft.com/en-us/sql/relational-databases/security/sql-data-discovery-and- classification

Explanation:
To query the data in your Hadoop data source, you must define an external table to use in Transact-SQL queries. The following steps describe how to configure the external table.
Step 1: Create a master key on database.
1. Create a master key on the database. The master key is required to encrypt the credential secret.
(Create a database scoped credential for Azure blob storage.)
Step 2: Create an external data source for Azure Blob storage.
2. Create an external data source with CREATE EXTERNAL DATA SOURCE..
Step 3: Create an external file format to map the parquet files.
3. Create an external file format with CREATE EXTERNAL FILE FORMAT.
Step 4. Create an external table FactSalesOrderDetails
4. Create an external table pointing to data stored in Azure storage with CREATE EXTERNAL TABLE.
Reference:
https://docs.microsoft.com/en-us/sql/relational-databases/polybase/polybase-configure-azure- blob-storage

Explanation:
https://learn.microsoft.com/en-
us/azure/templates/microsoft.sql/servers/firewallrules?pivots=deployment-language-bicep The start IP address of the firewall rule. Must be IPv4 format. Use value '0.0.0.0' for all Azure- internal IP addresses.

解説: (JPNTest メンバーにのみ表示されます)

解説: (JPNTest メンバーにのみ表示されます)

解説: (JPNTest メンバーにのみ表示されます)

Explanation:
Box 1: TO URL = 'https://storage1.blob.core.windows.net/blob1/Sales.bak' Native database backup in Azure SQL Managed Instance.
You can backup any database using standard BACKUP T-SQL command:
BACKUP DATABASE tpcc2501
TO URL = 'https://myacc.blob.core.windows.net/testcontainer/tpcc2501.bak' WITH COPY_ONLY Box 2: WITH COPY_ONLY SQLMI has "managed" everything, includes backup chain, so user can not break it's chain by using different method than COPY_ONLY.
Reference:
https://techcommunity.microsoft.com/t5/azure-sql-database/native-database-backup-in-azure-sql- managed-instance/ba-p/386154

解説: (JPNTest メンバーにのみ表示されます)

解説: (JPNTest メンバーにのみ表示されます)

解説: (JPNTest メンバーにのみ表示されます)

解説: (JPNTest メンバーにのみ表示されます)

解説: (JPNTest メンバーにのみ表示されます)