Cognitive Services Built-in Policies

Correct Answers: B, D and E.

Option A is incorrect because private links provide consumer and services connectivity using Azure backbone, thereby avoiding access through public IP address.

This reduced the risk to data in transit.

Option B is correct because enabling encryption using a customer managed key gives you control over the lifecycle of the key.

That way you can rotate the keys in accordance with your compliance policies.

Option C is incorrect because disabling local authentication improves security.

Instead you use Azure Active Directory for authentication.

Option D is correct because disabling public network access safeguards you from exposing your data over the internet.

Instead use private links.

Option E is correct because it gives you control over your cognitive services data at rest.

Reference:

To learn more about Azure cognitive services built-in policies, use the link given below:

Sure, I'll be happy to explain the statements regarding Cognitive Services built-in policies for Azure Cognitive Services accounts.

A. Prohibit use of private links: This statement is not true. Cognitive Services built-in policies do not prohibit the use of private links. Private links can be used to access Cognitive Services, but this may require additional configuration and setup.

B. Enable encryption using customer managed keys: This statement is true. Cognitive Services built-in policies allow for encryption using customer-managed keys. This means that customers can control their own encryption keys, providing an additional layer of security.

C. Enable local authentication: This statement is not true. Cognitive Services built-in policies do not provide local authentication. Authentication is typically handled through Azure Active Directory or other identity providers.

D. Disable public network access: This statement is true. Cognitive Services built-in policies can be configured to disable public network access, providing an additional layer of security by ensuring that only approved network traffic can access the service.

E. Use customer owned storage: This statement is not true. Cognitive Services built-in policies do not support the use of customer-owned storage. Data generated by Cognitive Services is typically stored in Azure storage services, such as Blob storage or Cosmos DB.

In summary, the true statements regarding Cognitive Services built-in policies for Azure Cognitive Services accounts are:

• Enable encryption using customer managed keys
• Disable public network access

I hope this helps!