Designing an Azure Data Solution Free Sample Questions

Explanation:
You can use Transparent Data Encryption to encrypt the data at rest The Microsoft documentation mentions the following:
Encryption
Azure SQL Data Warehouse Transparent Data Encryption (TDE) helps protect against the threat of malicious activity by encrypting and decrypting your data at rest. When you encrypt your database, associated backups and transaction log files are encrypted without requiring any changes to your applications. TDE encrypts the storage of an entire database by using a symmetric key called the database encryption key.
In SQL Database, the database encryption key is protected by a built-in server certificate. The built-in server certificate is unique for each SQL Database server. Microsoft automatically rotates these certificates at least every 90 days. The encryption algorithm used by SQL Data Warehouse is AES-256. For a general description of TDE, see Transparent Data Encryption.
You can encrypt your database using the Azure portal or T-SQL.
Since this is clearly mentioned in the Microsoft documentation, all other options are incorrect -- Reference:
https://docs.microsoft.com/en-us/azure/sql-data-warehouse/sql-data-warehouse-overview- manage-security

Explanation:
To authenticate, you can use personal access tokens.
The Microsoft documentation mentions the following:
Authentication To authenticate and access Databricks REST APIs, you use personal access tokens. Tokens are similar to passwords; you should treat them with care. Tokens expire and can be revoked.
Requirements
Token-based authentication is enabled by default for all Azure Databricks accounts launched after January 2018. If it is disabled, your administrator must enable it before you can perform the tasks described in this article. See Enable Token-based Authentication.
Since this is clearly mentioned in the Microsoft documentation, all other options are incorrect -- Reference:
https://docs.microsoft.com/en-us/azure/databricks/dev-tools/api/latest/authentication

Explanation:
You can authenticate to Azure Data Lake from Azure Databricks using Azure AD credentials The Microsoft documentation mentions the following: Authenticate to Azure Data Lake Storage using Azure Active Directory Credentials You can authenticate automatically to Azure Data Lake Storage Gen1 and Azure Data Lake Storage Gen2 from Azure Databricks clusters using the same Azure Active Directory (Azure AD) identity that you use to log into Azure Databricks. When you enable your cluster for Azure Data Lake Storage credential passthrough, commands that you run on that cluster can read and write data in Azure Data Lake Storage without requiring you to configure service principal credentials for access to storage.
Since this is clearly mentioned in the Microsoft documentation, all other options are incorrect -- Reference:
https://docs.microsoft.com/en-us/azure/databricks/data/data-sources/azure/adls-passthrough

Explanation:
The strongest encryption technique is to use Always Encrypted. This will encrypt the data at rest.
If you need to perform a search on the data, you need to use deterministic encryption The Microsoft documentation mentions the following: Selecting Deterministic or Randomized Encryption The Database Engine never operates on plaintext data stored in encrypted columns, but it still supports some queries on encrypted data, depending on the encryption type for the column.
Always Encrypted supports two types of encryption: randomized encryption and deterministic encryption.
• Deterministic encryption always generates the same encrypted value for any given plain text value. Using deterministic encryption allows point lookups, equality joins, grouping and indexing on encrypted columns. However, it may also allow unauthorized users to guess information about encrypted values by examining patterns in the encrypted column, especially if there's a small set of possible encrypted values, such as True/False, or North/South/East/West region. Deterministic encryption must use a column collation with a binary2 sort order for character columns. • Randomized encryption uses a method that encrypts data in a less predictable manner.
Randomized encryption is more secure, but prevents searching, grouping, indexing, and joining on encrypted columns.
Since this is clearly mentioned in the Microsoft documentation, all other options are incorrect -- Reference:
https://docs.microsoft.com/en-us/sql/relational-databases/security/encryption/always-encrypted- database-engine?view=sql-server-ver15

Explanation:
The strongest encryption technique is to use Always Encrypted. This will encrypt the data at rest.
For non-searchable data, you can make use of randomized encryption for the strongest possible encryption:
Selecting Deterministic or Randomized Encryption The Database Engine never operates on plaintext data stored in encrypted columns, but it still supports some queries on encrypted data, depending on the encryption type for the column.
Always Encrypted supports two types of encryption: randomized encryption and deterministic encryption.
• Deterministic encryption always generates the same encrypted value for any given plain text value. Using deterministic encryption allows point lookups, equality joins, grouping and indexing on encrypted columns. However, it may also allow unauthorized users to guess information about encrypted values by examining patterns in the encrypted column, especially if there's a small set of possible encrypted values, such as True/False, or North/South/East/West region. Deterministic encryption must use a column collation with a binary2 sort order for character columns. • Randomized encryption uses a method that encrypts data in a less predictable manner.
Randomized encryption is more secure, but prevents searching, grouping, indexing, and joining on encrypted columns.
Since this is clearly mentioned in the Microsoft documentation, all other options are incorrect -- Reference: https://docs.microsoft.com/en-us/sql/relational-databases/security/encryption/always-encrypted- database-engine?view=sql-server-ver15

B