You are designing a multi-platform,multi-port web application for AWS. The application will run on EC2 instances and will be accessed from PCs, tablets, and smartphones. Supported accessing platforms are Windows, MAC OS, IOS, and Android. Separate SSL certificate setups are required for different platform types. Which of the following describes the most cost-effective and performance efficient architecture setup?

Answer options:

A.Setup a hybrid architecture to handle session state, SSL certificates, on-premise resources, and EC2 Instances that run the web applications for different platform types in a VPC.B.Set up an Application Load Balancer with Server Name Indicator (SNI) support, for handling the separate SSL certificates for each of the device platforms.
C.Set up two Classic Load Balancers. The first ELB handles SSL certificates for all platforms and the second ELB handles session stickiness for all platforms. For each ELB run separate EC2 instance groups to handle the web application for each the platforms.
D.Assign multiple ALBs to a group of EC2 instances running the common components of the web application. One ALB for each platform type, Session stickiness, and SSL termination.

Answer – B
In this scenario, the main architectural considerations are (1) web application has EC2 instances running multiple platforms such as Android, iOS, etc., and (2) separate SSL certificate setups are required for different platforms.
Options A is incorrect because it is not cost-effective to handle such hybrid architecture.
Option B is correct. Originally, Application Load Balancers used to support only one certificate for a standard HTTPS listener (port 443). You had to use Wildcard or Multi-Domain (SAN) certificates to host multiple secure applications behind the same load balancer. The potential security risks with Wildcard certificates and the operational overhead of managing Multi-Domain certificates presented challenges. With SNI support you can associate multiple certificates with a listener and each secure application behind a load balancer can use its own certificate.You can use host conditions to define rules that forward requests to different target groups based on the hostname in the host header (also known as host-based routing). This enables you to support multiple domains using a single load balancer.
Option C is incorrect because Classic Load Balancer cannot handle multiple SSL certificates.
Option D is incorrect as it is not required since there is support for multiple TLS/SSL certificates on Application Load Balancers. It is not cost-efficient as one ALB can achieve the requirement.
For more information on ELB, please visit the below URL-
https://aws.amazon.com/elasticloadbalancing/classicloadbalancer/faqs/