DP-300 Korean試験無料問題集「Microsoft Administering Relational Databases on Microsoft Azure (DP-300 Korean Version) 認定」

Explanation:

Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/managed-instance/create-template-quickstart?tabs=azure- powershell

Explanation:

Box 1: Hash
Scenario:
Ensure that queries joining and filtering sales transaction records based on product ID complete as quickly as possible.
A hash distributed table can deliver the highest query performance for joins and aggregations on large tables.
Box 2: Round-robin
Scenario:
You plan to create a promotional table that will contain a promotion ID. The promotion ID will be associated to a specific product. The product will be identified by a product ID. The table will be approximately 5 GB.
A round-robin table is the most straightforward table to create and delivers fast performance when used as a staging table for loads. These are some scenarios where you should choose Round robin distribution:
* When you cannot identify a single key to distribute your data.
* If your data doesn't frequently join with data from other tables.
* When there are no obvious keys to join.
Reference:
https://rajanieshkaushikk.com/2020/09/09/how-to-choose-right-data-distribution-strategy-for-azure-synapse/

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

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

See the explanation part for the complete Solution.
Explanation:
SQL injection attacks are a type of cyberattack that exploit a vulnerability in the application code that interacts with the database. An attacker can inject malicious SQL statements into the user input, such as a form field or a URL parameter, and execute them on the database server, resulting in data theft, corruption, or unauthorized access1.
To protect all the databases on sql37006S95 from SQL injection attacks, you need to follow some best practices for securing your application and database layers. Here are some of the recommended steps:
* Use parameterized queries or stored procedures to separate the SQL code from the user input. This will prevent the user input from being interpreted as part of the SQL statement and avoid SQL injection23.
* Validate and sanitize the user input before passing it to the database. This will ensure that the input conforms to the expected format and type, and remove any potentially harmful characters or keywords4.
* Implement least privilege access for the database users and roles. This will limit the permissions and actions that the application can perform on the database, and reduce the impact of a successful SQL injection attack5.
* Enable Advanced Threat Protection for Azure SQL Database. This is a feature that detects and alerts you of anomalous activities and potential threats on your database, such as SQL injection, brute force attacks, or unusual access patterns. You can configure the alert settings and notifications using the Azure portal or PowerShell.
These are some of the steps to protect all the databases on sql37006S95 from SQL injection attacks.

See the explanation part for the complete Solution.
Explanation:
To configure high availability for dbl, you can use the failover groups feature of Azure SQL Database. Failover groups allow you to manage the replication and failover of a group of databases across different regions with the same connection strings1. You can choose all, or a subset of, user databases in a logical server to be replicated to another logical server in a different region. You can also specify the failover policy, such as manual or automatic, and the grace period for data loss.
Here are the steps to create a failover group for dbl:
* Using the Azure portal:
* Go to the Azure portal and select your Azure SQL Database server that hosts dbl.
* Select Failover groups in the left menu and click on Add group.
* Enter a name for the failover group and select a secondary region that is different from the primary region.
* Click on Create a new server and enter the details for the secondary server, such as server name, admin login, password, and subscription.
* Click on Select existing database(s) and choose dbl from the list of databases on the primary server.
* Click on Configure failover policy and select the failover mode, grace period, and read-write failover endpoint mode according to your preferences.
* Click on Create to create the failover group and start the replication of dbl to the secondary server.
* Using PowerShell commands:
* Install the Azure PowerShell module and log in with your Azure account.
* Run the following command to create a new server in the secondary region: New-AzSqlServer - ResourceGroupName <your-resource-group-name> -ServerName <your-secondary-server-name>
-Location "<secondary-region-name>" -SqlAdministratorCredentials $(New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList "<your-admin-login>",
$(ConvertTo-SecureString -String "<your-password>" -AsPlainText -Force))
* Run the following command to create a new failover group with dbl: New- AzSqlDatabaseFailoverGroup -ResourceGroupName <your-resource-group-name> -ServerName
<your-primary-server-name> -PartnerResourceGroupName <your-resource-group-name> - PartnerServerName <your-secondary-server-name> -FailoverGroupName <your-failover-group- name> -Database dbl -FailoverPolicy <manual-or-automatic> -GracePeriodWithDataLossHours
<grace-period-in-hours> -ReadWriteFailoverEndpoint "<enabled-or-disabled>"
* You can modify the parameters of the command according to your preferences, such as the failover policy, grace period, and read-write failover endpoint mode.
These are the steps to create a failover group for dbl

Explanation:

Azure Database Migration service
Box 1: Premium 4-VCore
Scenario: Migrate the SERVER1 databases to the Azure SQL Database platform.
* Minimize downtime during the migration of the SERVER1 databases.
Premimum 4-vCore is for large or business critical workloads. It supports online migrations, offline migrations, and faster migration speeds.
Reference:
https://azure.microsoft.com/pricing/details/database-migration/
https://docs.microsoft.com/en-us/azure/dms/tutorial-sql-server-azure-sql-online

Explanation:

Box 1: HASH
Box 2: OrderDateKey
In most cases, table partitions are created on a date column.
A way to eliminate rollbacks is to use Metadata Only operations like partition switching for data management.
For example, rather than execute a DELETE statement to delete all rows in a table where the order_date was in October of 2001, you could partition your data early. Then you can switch out the partition with data for an empty partition from another table.
Reference:
https://docs.microsoft.com/en-us/sql/t-sql/statements/create-table-azure-sql-data-warehouse
https://docs.microsoft.com/en-us/azure/synapse-analytics/sql/best-practices-dedicated-sql-pool

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