Question : You are thinking to use EBS PIOPS volume. Which of the below mentioned options is a right use case for the PIOPS EBS volume? 1. Log processing 2. Mongo DB 3. Access Mostly Uused Products by 50000+ Subscribers 4. System boot volume
Explanation: Provisioned IOPS volumes are designed to meet the needs of I/O-intensive workloads, particularly database workloads that are sensitive to storage performance and consistency in random access I/O throughput. Provisioned IOPS volumes are designed to meet the needs of I/O-intensive workloads, particularly database workloads, that are sensitive to storage performance and consistency in random access I/O throughput business applications, database workloads, such as NoSQL DB, RDBMS, etc.
Question : Which of the below mentioned options ensures that the user requests are always attached to a single instance? 1. Cross zone load balancing 2. Connection drainage 3. Access Mostly Uused Products by 50000+ Subscribers 4. Session affinity
Explanation: Generally an Elastic Load Balancer routes each request independently to the application instance with the smallest load. However, the user can enable the sticky session feature (also known as session affinity) which enables the load balancer to bind a user's session to a specific application instance. This ensures that all requests coming from the user during the session will be sent to the same application instance.
Question : You have enabled Application-Controlled Session Stickiness. The instance the user's session was bound to becomes unhealthy for minutes. The unhealthy instance becomes healthy again after 10 minutes. What will ELB do in this case? 1. ELB will throw an error 2. ELB will try to route the sticky session to another healthy application server 3. Access Mostly Uused Products by 50000+ Subscribers 4. ELB will route requests to the original instance again
Explanation: If an application server fails or is removed, the Elastic Load Balancer will try to route the sticky session to another healthy application server. The load balancer will try to stick to a new healthy application server and continue routing to the currently sick application server even after the failed application server comes back. However, it is up to the new application server on how it will respond to a request which it has not seen previously.