Don't forget to create account on our site to get access to more material made only for free registered user.  

Azure 70-532 Azure 70 533

Question : 15  You work as a Software Developer at ABC.com. The company has a Microsoft Azure subscription. The company has a corporate website hosted as an Azure website. The web application was created using ASP.NET and runs in stateless mode. You discover that the website is performing slowly. You add website instances in Azure to improve performance. You discover that the load on the instances is uneven. New users are directed to the new instances while existing users continue to be directed to the original instances. You need to ensure that users are evenly distributed to all instances. Which of the following actions should you perform?

  1.    You should configure a response header in the application named "Arr-Disable-Session-Affinity" with a value of False.

  2.   You should configure a response header in the application named "Arr-Disable-Session-Affinity" with a value of True.

  3.    You should modify the size of the instances.

  4.   You should modify the autoscaling metric.

Correct Answer : 2 Exp :  By default, Azure Websites comes preconfigured with Session affinity, which in many cases allows developers perform a very simple migration of their applications to cloud. This is because there is no need to worry about centralizing the session state of your application as a user will be redirected back to the same server on each subsequent request.

Some applications, however, may not require session affinity and it would be better to turn off the session affinity in Azure Websites. This can be achieved by adding the following to the web.config file. To address this, ARR 3.0 allows web applications to opt-out of session affinity. To do this, an application would need to set a special response-header that signals to ARR to disable affinity for the application.

The special response header is Arr-Disable-Session-Affinity and the application would set the value of the header to be either True or False. If the value of the header is true, ARR would not set the affinity cookie when responding to the client request. In such a situation, subsequent requests from the client would not have the affinity cookie in them, and so ARR would route that request to the backend servers based on the load balance algorithm. Note that this behavior could have serious impact on session-sensitive application, so enabling this on a web application must be considered carefully.

 

You have no rights to post comments