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 to the web application among a number of virtual servers, what situation can happen in the case of scaling 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 to the web application  among a number of virtual servers, what situation can happen in the case of scaling and/or failures? 
   
 (select the option that best fits the question).

Accepted Answer

In load balancing with HTTP redirection, when a front-end server fails, there is a long delay for 1/m of new user sessions.

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

In load balancing with HTTP redirection, when a front-end server fails, there is a small delay for 1/m of ongoing user sessions.

Answer

No response (no penalty).

Crowdly

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

Want instant access to all verified answers on moodle.dei.tecnico.ulisboa.pt?