SIMULATIONYou need to encrypt the LastName column of the SalesLT.Customer table in db1 by using Always Encrypted.You must use the Windows Certificate Store.You may need to use SQL Server Management Studio and the Azure portal.
Answer(s): A
Solution 1 [Less complex]Configure column encryption using Always Encrypted WizardThe Always Encrypted Wizard is a powerful tool that allows you to set the desired Always Encrypted configuration for selected database columns. Depending on the current configuration and the desired target configuration, the wizard can encrypt a column, decrypt it (remove encryption), or re-encrypt it (for example, using a new column encryption key or an encryption type that is different from the current type, configured for the column). Multiple columns can be configured in a single run of the wizard.Step 1: Open the Always Encrypted WizardYou can launch the wizard at three different levels:At a database level - if you want to encrypt multiple columns located in different tables. At a table level - if you want to encrypt multiple columns located in the same table. *-> At a column level - if you want to encrypt one specific column. [This option here]Step 2: Connect to your SQL Server with the Object Explorer component of SQL Server Management Studio.Step 3: To encrypt an individual column, navigate to the column, right-click on it, and then select Encrypt Columns. [Select the LastName column of the SalesLT.Customer table in db1]Step 4: Column Selection pageIn this page, you select columns you want to encrypt, re-encrypt, or decrypt, and you define the target encryption configuration for the selected columns.Step 5: If you want the wizard to encrypt or re-encrypt one or more columns using a new column encryption key, pick a key containing (New) in its name. The wizard will generate the key.Step 6: Master Key Configuration pageIf you have selected an autogenerated column encryption key for any column on the previous page, in this page you need to either select an existing column master key or configure a new column master key that will encrypt the column encryption key.When configuring a new column master key, you can either pick an existing key in Windows Certificate Store or in Azure Key Vault and have the wizard to create just a metadata object for the key in the database, or you can choose to generate both the key and the metadata object describing the key in the database.Step 7: Click "Next" and follow the wizard's instructions to complete the process.Solution 2 [A bit more complex. Use for reference]To encrypt a specific column using Always Encrypted with a Windows Certificate Store, you'll first need to set up a Column Master Key (CMK) [Task 1] and a Column Encryption Key (CEK) [Task 2]. The CMK will be protected by a certificate in the Windows Certificate Store, and the CEK will then be used to encrypt the data in your chosen column.Task 1: Set up a Column Master Key (CMK)Create a self-signed certificate using SQL Server Management Studio (SSMS)Provision Column Master Keys with the New Column Master Key Dialog The New Column Master Key dialog allows you to generate a column master key or pick an existing key in a key store, and create column master key metadata for the created or selected key in the database.Step 1: Using Object Explorer, navigate to the Security -> Always Encrypted Keys node under your database.Step 2: Right-click on the Column Master Keys node and select New Column Master Key....Step 3: In the New Column Master Key dialog, enter the name of the column master key metadata object.Step 4: Select a key store:*-> Certificate Store - Current User - indicates the Current User certificate store location in the Windows Certificate Store, which is your personal store. [Select this one]Certificate Store - Local computerAzure Key VaultEtc.Step 5: If you're using SQL Server 2019 (15.x) and your SQL Server instance is configured with a secure enclave, you can select the Allow enclave computations checkbox to make the master key enclave-enabled.[Skip]Step 6: Pick an existing key in your key store, or click the Generate Key or Generate Certificate button, to create a key in the key store. [Pick existing]Step 7: Click OK and the new key appears in the list.Task 2: Create a Column Encryption Key (CEK)1. In SSMS, navigate to "Always Encrypted Keys" -> "Column Encryption Keys".2. Right-click and select "New Column Encryption Key".3. Give the CEK a name.4. Select the CMK you just created. [Created in Stage 1]5. Click "OK".Task 3: Encrypt the data in your chosen column.1. Right-click on the specific column you want to encrypt in Object Explorer. [Select the LastName column of the SalesLT.Customer table in db1]2. Select "Tasks" -> "Encrypt Columns".3. The Always Encrypted Wizard will guide you through the process:4. Select the column you want to encrypt. [Select the LastName column of the SalesLT.Customer table in db1]5. Choose the encryption type (Deterministic or Randomized).6. Select the CEK you created. [Created in Stage 2]7. Click "Next" and follow the wizard's instructions to complete the process.
https://learn.microsoft.com/en-us/sql/relational-databases/security/encryption/always-encrypted-wizard https://learn.microsoft.com/en-us/sql/relational-databases/security/encryption/create-and-store-column-master- keys-always-encrypted
SIMULATIONYou need to ensure that you can connect to db1 by using a private IP address on a virtual network named VNET1.You may need to use SQL Server Management Studio and the Azure portal.
To connect to an Azure SQL Database using a private IP address on a virtual network via the Azure portal, you'll need to configure a Private Endpoint.Connect to an Azure SQL server using an Azure Private Endpoint using the Azure portal Create a Private Endpoint:Step 1: In the Azure portal, search for and select "Private endpoints".Step 2: Select "+ Create" to create a new Private Endpoint.Step 3: On the "Basics" tab, provide a name, resource group, and region.Step 4: On the "Resource" tab, select "Microsoft.Sql/servers" as the resource type and choose your SQL Server. [Select db1]Step 5: On the "Virtual Network" tab, select your virtual. [Select VNET1]Step 6: On the "DNS" tab, review the DNS settings and make any necessary changes. [Skip]
https://learn.microsoft.com/en-us/azure/private-link/tutorial-private-endpoint-sql-portal
SIMULATIONYou need to ensure that when non-administrative users query the SalesLT.Customer table in db1, email addresses are obscured. For example, an email address of alice@contoso.com must appear as aXXX@XXXX.com.You may need to use SQL Server Management Studio and the Azure portal.
SQL Database dynamic data masking with the Azure portalIn the Dynamic Data Masking pane in the portal, you see the recommended columns for your database. Select Add Mask for one or more columns, then select the appropriate masking function and select Save, to apply mask for these fields.In details:Enable dynamic data maskingStep 1: Launch the Azure portal at https://portal.azure.com.Step 2: Go to your database resource in the Azure portal. [Select db1]Step 3: Select the Dynamic Data Masking pane under the Security section.Step 4: In the Dynamic Data Masking configuration page, you may see some database columns that the recommendations engine has flagged for masking. In order to accept the recommendations, just click Add Mask for one or more columns and a mask is created based on the default type for this column. You can change the masking function by clicking on the masking rule and editing the masking field format to a different format of your choice. Be sure to click Save to save your settings.4.1 If possible locate the column with email addresses in the SalesLT.Customer table [If not seen skip to step 5]4.2 Click Add MaskStep 5: To add a mask for any column in your database, at the top of the Dynamic Data Masking configuration page, click Add Mask to open the Add Masking Rule configuration page. [Skip steps 5-6 step if step 4 was successful]Step 6: Select the Schema, Table and Column to define the designated field for masking.Select the followingTable: SalesLT.Customer tableColumn: [Choose the column with the email addresses]Step 7: Select how to mask from the list of sensitive data masking categories.Select Email (aXXX@XXXX.com)Step 8: Click Add in the data masking rule page to update the set of masking rules in the dynamic data masking policy.Step 9: Type the SQL authenticated users or authenticated identities from Microsoft Entra ID (formerly Azure Active Directory) that should be excluded from masking, and have access to the unmasked sensitive data.[Skip]Step 10: Click Save in the data masking configuration page to save the new or updated masking policy.
https://learn.microsoft.com/en-us/azure/azure-sql/database/dynamic-data-masking-configure-portal
You have an Azure SQL database. The database contains a table of analytical data that must be retained.You need to implement a data compression solution that maximizes a reduction in storage.Which type of compression should you use?
Answer(s): B
Columnstore archive provides the maximum data compression in an Azure SQL Database when query performance is not the top priority. While columnstore compression is already highly efficient for analytical workloads, the archive option further reduces the data size, but at the cost of increased compression and decompression time.Columnstore Compression:Clustered columnstore indexes, which are the default for large tables in Azure SQL Database, are designed for efficient storage and fast analytical queries. They compress data by storing it in a columnar format, which is particularly effective for analytical workloads.Columnstore Archive Compression:For situations where storage space is critical and query performance is less important, you can apply columnstore archive compression. This method uses a more aggressive compression algorithm, resulting in a smaller data footprint but potentially slower query execution.Trade-off:The key trade-off is between compression and query performance. Columnstore archive offers the best compression but can impact query speed, especially for frequent queries.In summary, while columnstore indexes offer excellent compression for analytical data, columnstore archive compression provides the maximum possible compression if query performance is not the primary concern.
https://brainly.com/question/61706068
HOTSPOT (Drag and Drop is not supported)You have an Azure subscription that contains an Azure SQL database named DB1 and a managed identity.You need to create a user in DB1 that will be used by the managed identity to perform automated tasks.How should you complete the query? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: FROM EXTERNAL PROVIDERCreate a user-assigned managed identitySyntax:CREATE USER{Microsoft_Entra_principal FROM EXTERNAL PROVIDER [ WITH <limited_options_list> [ ,... ] ] | Microsoft_Entra_principal WITH <options_list> [ ,... ]}[ ; ]<limited_options_list> ::=DEFAULT_SCHEMA = schema_name| OBJECT_ID = 'objectid'<options_list> ::=DEFAULT_SCHEMA = schema_name| SID = sid| TYPE = { X | E }Box 2: OBJECT_IDThe above syntax allows creation of Microsoft Entra users without validation. For this to work, the Object Id of the Microsoft Entra principal would have to be supplied and used as an SID in the T-SQL statement.The validity check of the Object Id is the responsibility of the user running the T-SQL statement.
https://learn.microsoft.com/en-us/azure/azure-sql/database/authentication-azure-ad-user-assigned-managed- identity
Post your Comments and Discuss Microsoft DP-300 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the DP-300 content, but please register or login to continue.