Consider an Infrastructure-as-a-Service deployment, in order to seamless extend computing resources for a small start-up company, in a real-life scenario employing replicated m front-ends and n replicated back-ends.
When redirecting requests from many clients to the web application among a number of virtual servers, what situation can happen in terms of scale limitations and/or failures?

(select the option that best fits the question).

Question

Consider an Infrastructure-as-a-Service deployment, in order to seamless extend computing resources for a small start-up company, in a real-life scenario employing replicated m front-ends and n replicated back-ends.  
 When redirecting requests from many clients to the web application  among a number of virtual servers, what situation can happen in terms of scale limitations and/or failures? 
   
 (select the option that best fits the question).

Answer

In load balancing with Level-4 network rerouting, when a back-end server fails there is a long delay for 1/n of new user sessions.

Answer

In load balancing based on DNS, scale-down time is related with user session duration.

Answer

No response (no penalty if only option answered).

Answer

In load balancing with HTTP redirection, scale limitations are dependent on VM start-up time.

Answer

In load balancing with HTTP redirection, scale limitations are dependent on client arrival rate.

Crowdly

Consider an Infrastructure-as-a-Service deployment, in order to seamless extend ...

Хочете миттєвий доступ до всіх перевірених відповідей на moodle.dei.tecnico.ulisboa.pt?