Question : You are designing a multi-platform web application for AWS The application will run on EC2 instances and will be accessed from PCs. tablets and smart phones Supported accessing platforms are Windows. MACOS. IOS and Android Separate sticky session and SSL certificate setups are required for different platform types which of the following describes the most cost effective and performance efficient architecture setup? 1. Setup a hybrid architecture to handle session state and SSL certificates on-prem and separate EC2 Instance groups running web applications for different platform types running in a VPC. 2. Set up one ELB for all platforms to distribute load among multiple instance under it Each EC2 instance implements ail functionality for a particular platform. 3. Access Mostly Uused Products by 50000+ Subscribers ELB handles session stickiness for all platforms for each ELB run separate EC2 instance groups to handle the web application for each platform. 4. Assign multiple ELBS to an EC2 instance or group of EC2 instances running the common components of the web application, one ELB for each platform type Session stickiness and SSL termination are done at the ELBs.
Answer: 4
Explanation: For EACH SSL , one ELB is needed.
Question : You are implementing a URL whitelisting system for a company that wants to restrict outbound HTTP'S connections to specific domains from their EC2-hosted applications you deploy a single EC2 instance running proxy software and configure It to accept traffic from all subnets and EC2 instances in the VPC. You configure the proxy to only pass through traffic to domains that you define in its whitelist configuration You have a nightly maintenance window or 10 minutes where ail instances fetch new software updates. Each update Is about 200MB In size and there are 500 instances In the VPC that routinely fetch updates After a few days you notice that some machines are failing to successfully download some, but not all of their updates within the maintenance window The download URLs used for these updates are correctly listed in the proxy's whitelist configuration and you are able to access them manually using a web browser on the instances What might be happening? (Choose 2 answers)
A. You are running the proxy on an undersized EC2 instance type so network throughput is not sufficient for all instances to download their updates in time. B. You have not allocated enough storage to the EC2 instance running me proxy so the network buffer is filling up. causing some requests to fall C. You are running the proxy in a public subnet but have not allocated enough EIPs to support the needed network throughput through the Internet Gateway (IGW) D. You are running the proxy on a EC2 instance in a private subnet and its network throughput is being throttled by a NAT running on an undersized EC2 instance E. The route table for the subnets containing the affected EC2 instances is not configured to direct network traffic for the software update locations to the proxy.
Explanation: Amazon offers a range of instance types with varying amounts of memory and CPU. What is not well "documented" however, is network capabilities which are simply categorized as - Low, Moderate, High, and 10Gb. Based on our experiments running Aerospike servers on AWS and iperf runs on AWS, we were able to better define these categories to the following numbers:
Low - Up to 100 Mbps Moderate - 100 Mbps to 300 Mbps High - 100 Mbps to 1.86 Gbps 10Gb - upto 8.86Gbps
Question : Refer to the architecture diagram above of a batch processing solution using Simple Queue Service (SOS) to set up a message queue between EC2 instances which are used as batch processors Cloud Watch monitors the number of Job requests (queued messages) and an Auto Scaling group adds or deletes batch servers automatically based on parameters set in Cloud Watch alarms.
You can use this architecture to implement which of the following features in a cost effective and efficient manner?
1. Reduce the overall time for executing jobs through parallel processing by allowing a busy EC2 instance that receives a message to pass it to the next instance in a daisy-chain setup. 2. Implement fault tolerance against EC2 instance failure since messages would remain in SQS and worn can continue with recovery of EC2 instances implement fault tolerance against SQS failure by backing up messages to S3. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Coordinate number of EC2 instances with number of job requests automatically thus Improving cost effectiveness. 5. Handle high priority jobs before lower priority jobs by assigning a priority metadata field to SQS messages.
Answer: 1 This architecture will help to do better Auto scalling and parallel processing based on the length of Queue. Amazon Simple Queue Service (Amazon SQS) is a scalable message queuing system that stores messages as they travel between various components of your application architecture. Amazon SQS enables web service applications to quickly and reliably queue messages that are generated by one component and consumed by another component. A queue is a temporary repository for messages that are awaiting processing.
1. Use the EC2 VM Import Connector for vCenter to import the VM into EC2. 2. Use Import/Export to import the VM as an EBS snapshot and attach to EC2. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Use me ec2-bundle-instance API to Import an Image of the VM into EC2
1. File a change request to implement Proxy Protocol support In the application Use an ELB with a TCP Listener and Proxy Protocol enabled to distribute load on two application servers in different AZs. 2. File a change request to Implement Cross-Zone support in the application Use an ELB with a TCP Listener and Cross-Zone Load Balancing enabled, two application servers in different AZs. 3. Access Mostly Uused Products by 50000+ Subscribers Use Route 53 with Latency Based Routing enabled to distribute load on two application servers in different AZs. 4. File a change request to implement Alias Resource support in the application Use Route 53 Alias Resource Record to distribute load on two application servers in different AZs.