Question : You have a web application running on six Amazon EC instances, consuming about % of resources on each instance. You are using auto-scaling to make sure that six instances are running at all times. The number of requests this application processes is consistent and does not experience spikes. The application is critical to your business and you want high availability at all times. You want the load to be distributed evenly between all instances. You also want to use the same Amazon Machine Image (AMI) for all instances. Which of the following architectural choices should you make?
1. Deploy 6 EC2 instances in one availability zone and use Amazon Elastic Load Balancer. 2. Deploy 3 EC2 instances in one region and 3 in another region and use Amazon Elastic Load Balancer. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Deploy 2 EC2 instances in three regions and use Amazon Elastic Load Balancer.
Achieve higher levels of fault tolerance for your applications by using Elastic Load Balancing to automatically route traffic across multiple instances and multiple Availability Zones. Elastic Load Balancing ensures that only healthy Amazon EC2 instances receive traffic by detecting unhealthy instances and rerouting traffic across the remaining healthy instances. If all of your EC2 instances in one Availability Zone are unhealthy, and you have set up EC2 instances in multiple Availability Zones, Elastic Load Balancing will route traffic to your healthy EC2 instances in those other zones.
Question : What are characteristics of Amazon S? Choose answers A. S3 allows you to store objects of virtually unlimited size. B. S3 offers Provisioned IOPS. C. S3 allows you to store unlimited amounts of data. D. S3 should be used to host a relational database. E. Objects are directly accessible via a URL
Q: Can I use my own host name with my Amazon S3 hosted website? Yes, you can easily and durably store your content in an Amazon S3 bucket and map your domain name (e.g. "example.com") to this bucket. Visitors to your website can then access this content by typing in your website's URL (e.g., "http://example.com") in their browser. Q: Does Amazon S3 support website redirects? Yes, Amazon S3 provides multiple ways to enable redirection of web content for your static websites. Redirects enable you to change the Uniform Resource Locator (URL) of a web page on your Amazon S3 hosted website (e.g. from www.example.com/oldpage to www.example.com/newpage) without breaking links or bookmarks pointing to the old URL. You can set rules on your bucket to enable automatic redirection. You can also configure a redirect on an individual S3 object.
Q: How much data can I store? The total volume of data and number of objects you can store are unlimited. Individual Amazon S3 objects can range in size from 1 byte to 5 terabytes. The largest object that can be uploaded in a single PUT is 5 gigabytes. For objects larger than 100 megabytes, customers should consider using the Multipart Upload capability.
Question : When an EC instance that is backed by an S-based AMI Is terminated, what happens to the data on the root volume? 1. Data is automatically saved as an E8S volume. 2. Data is automatically saved as an ESS snapshot. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Data is unavailable until the instance is restarted
Explanation: Instances that use instance stores for the root device automatically have instance store volumes available, with one serving as the root device volume. When an instance is launched, the image that is used to boot the instance is copied to the root volume (typically sda1). Any data on the instance store volumes persists as long as the instance is running, but this data is deleted when the instance is terminated (instance store-backed instances do not support the Stop action) or if it fails (such as if an underlying drive has issues). After an instance store-backed instance fails or terminates, it cannot be restored. If you plan to use Amazon EC2 instance store-backed instances, we highly recommend that you distribute the data on your instance stores across multiple Availability Zones. You should also back up the data on your instance store volumes to persistent storage on a regular basis. S3-hosted Images Instances launched from S3-hosted images use the local disk for the root partition. Once spun up, if you shut down machine down the state of the operating system is lost. The only way to persist data is to store it off-instance - for example on an attached EBS volume, on S3 or elsewhere. Aside from the lack of persistence of the state of the OS, these images are limited to being 10GB in size - not a problem for most Linux distros I know of, but a non-starter for some Microsoft images. There is also a time delaying spinning these images up, due to the time taken to copy the Image from S3 to the physical machine - the whole image has to be downloaded before the instance can start the boot up process. In practice, popular images seem to be pretty well cached and so that the delay may not be an issue for you. As with everything in AWS, the barrier to entry is so low it is worth testing this yourself to understand if this is going to be a deal breaker.
1. The use of some AWS CloudFormation resources and templates will require you to specify an Amazon EC2 key pair for authentication. 2. The use of any AWS CloudFormation resources and templates do not require you to specify an Amazon EC2 key pair for authentication. 3. Access Mostly Uused Products by 50000+ Subscribers 4. The use of any AWS CloudFormation resources and templates do not require you to specify a root account.