Martin is a Cloud Security Engineer of Whizlabs Inc.
As a best practice; he implemented the option to change the access key of the Blob storage regularly.
Consequently, the storage keys of Blob storage (Polybase) are also required to rotate which is the underlying storage of the dedicated SQL pool of Azure Synapse analytics.
For each storage account, whose key is required to change? He issued the following T-SQL statement.
ALTER DATABASE SCOPED CONFIGURATION { SET <set_options> }[;] <set_options>::= { DW_COMPATIBILITY_LEVEL = {AUTO| 10|20} } Does the above T-SQL statement match the requirements of this scenario?
Click on the arrows to vote for the correct answer
A. B.Correct Answer: B.
The T-SQL statement provided in the question is used to configure the compatibility level of the SQL pool in Azure Synapse Analytics. It is not related to changing the access keys of Blob storage. Therefore, the answer to the question is No, the above T-SQL statement does not match the requirements of this scenario.
To rotate the storage keys of Blob storage in Azure, one needs to use Azure PowerShell or Azure CLI or the Azure portal. The following steps can be followed to rotate the storage keys of a Blob storage account in Azure:
It's important to note that the SQL pool in Azure Synapse Analytics can be configured to use a storage account as the underlying storage for Polybase, which is used to query external data. To ensure that the SQL pool continues to function properly after rotating the access keys of the storage account, one needs to update the connection string used by the SQL pool to access the storage account with the new access key. This can be done using the ALTER EXTERNAL DATA SOURCE statement in T-SQL.
In conclusion, while the T-SQL statement provided in the question is not relevant to changing the access keys of Blob storage, it is important to update the connection string used by the SQL pool to access the storage account with the new access key after rotating the keys.