Microsoft Azure Architect Design (AZ-301) Practice Exam

What is the recommended approach to remove the AspNet-Version header from the responses of published APIs using Azure API Management?

1. Create a new policy

2. Alter the URL scheme

3. Create a new product

4. Create a new revision

The correct answer is: Create a new policy

Creating a new policy in Azure API Management is indeed the recommended approach to remove the AspNet-Version header from the responses of published APIs. In Azure API Management, policies enable you to manipulate the behavior of requests and responses at various stages in the API lifecycle. By adding a specific policy to remove the AspNet-Version header, you ensure that this header is stripped from the response before it reaches the client, enhancing security and possibly reducing information leakage about the underlying technology stack. Policies in Azure API Management can be configured at different scopes, such as at the product, API, or operation level, which provides flexibility in application management. This capability allows you to customize responses on a granular level according to the requirements of your API consumers. Choosing other options like altering the URL scheme, creating a new product, or creating a new revision does not directly address the need to remove a specific header from the API response. Altering the URL scheme changes the structure of the API’s endpoints which does not impact headers. Creating a new product involves defining a collection of APIs and does not pertain to header manipulation. Additionally, creating a new revision is related to versioning of the API, which again does not serve the purpose of addressing the presence of specific headers in the responses.