Question : You are designing a web application that stores static assets in an Amazon Simple Storage Service (S3) bucket. You expect this bucket to immediately receive over 150 PUT requests per second. What should you do to ensure optimal performance? 1. Use multi-part upload. 2. Add a random prefix to the key names. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Use a predictable naming scheme, such as sequential numbers or date time sequences, in the key names
Ans : 2 Exp : The sequence pattern in the key names introduces a performance problem. To understand the issue, let,s look at how Amazon S3 stores key names.
Amazon S3 maintains an index of object key names in each AWS region. Object keys are stored lexicographically across multiple partitions in the index. That is, Amazon S3 stores key names in alphabetical order. The key name dictates which partition the key is stored in. Using a sequential prefix, such as timestamp or an alphabetical sequence, increases the likelihood that Amazon S3 will target a specific partition for a large number of your keys, overwhelming the I/O capacity of the partition. If you introduce some randomness in your key name prefixes, the key names, and therefore the I/O load, will be distributed across more than one partition.
If you anticipate that your workload will consistently exceed 100 requests per second, you should avoid sequential key names. If you must use sequential numbers or date and time patterns in key names, add a random prefix to the key name. The randomness of the prefix more evenly distributes key names across multiple index partitions. Examples of introducing randomness are provided later in this topic.
Note The guidelines provided for the key name prefixes in the following section also apply to the bucket name. When Amazon S3 stores a key name in the index, it stores the bucket names as part of the key name (for example, examplebucket/object.jpg). Example 1: Add a Hex Hash Prefix to Key Name
One way to introduce randomness to key names is to add a hash string as prefix to the key name. For example, you can compute an MD5 hash of the character sequence that you plan to assign as the key name. From the hash, pick a specific number of characters, and add them as the prefix to the key name. The following example shows key names with a four-character hash.
If you anticipate that your workload will consistently exceed 100 requests per second, you should avoid sequential key names. If you must use sequential numbers or date and time patterns in key names, add a random prefix to the key name. The randomness of the prefix more evenly distributes key names across multiple index partitions. Examples of introducing randomness are provided later in this topic.
Question : You have a load balancer configured for VPC, and all back-end Amazon EC instances are in service. However, your web browser times out when connecting to the load balancer's DNS name. Which options are probable causes of this behavior? Choose 2 answers A. The load balancer was not configured to use a public subnet with an Internet gateway configured B. The Amazon EC2 instances do not have a dynamically allocated private IP address C. The security groups or network ACLs are not property configured for web traffic. D. The load balancer is not configured in a private subnet with a NAT instance. E. The VPC does not have a VGW configured. 1. A,B 2. B,C 3. Access Mostly Uused Products by 50000+ Subscribers 4. D,E
Ans: 1
Question : A company needs to deploy services to an AWS region which they have not previously used. The company currently has an AWS identity and Access Management (IAM) role for the Amazon EC2 instances, which permits the instance to have access to Amazon DynamoDB. The company wants their EC2 instances in the new region to have the same privileges. How should the company achieve this? 1. Create a new IAM role and associated policies within the new region 2. Assign the existing IAM role to the Amazon EC2 instances in the new region 3. Access Mostly Uused Products by 50000+ Subscribers 4. Create an Amazon Machine Image (AMI) of the instance and copy it to the desired region using the AMI Copy feature Ans : 2
Question : How can an EBS volume that is currently attached to an EC instance be migrated from one Availability Zone to another?
1. Detach the volume and attach it to another EC2 instance in the other AZ. 2. Simply create a new volume in the other AZ and specify the original volume as the source. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Detach the volume, then use the ec2-migrate-voiume command to move it to another AZ
Question : You are using an m.small EC Instance with one GB EBS volume to host a relational database. You determined that write throughput to the database needs to be increased. Which of the following approaches can help achieve this? Choose 2 answers A. Use an array of EBS volumes. B. Enable Multi-AZ mode. C. Place the instance in an Auto Scaling Groups D. Add an EBS volume and place into RAID 5. E. Increase the size of the EC2 Instance. F. Put the database behind an Elastic Load Balancer.
Explanation: RAID 5 and RAID 6 are not recommended for Amazon EBS because the parity write operations of these RAID modes consume some of the IOPS available to your volumes. Depending on the configuration of your RAID array, these RAID modes provide 20-30% fewer usable IOPS than a RAID 0 configuration. Increased cost is a factor with these RAID modes as well; when using identical volume sizes and speeds, a 2-volume RAID 0 array can outperform a 4-volume RAID 6 array that costs twice as much.
Question : You have an EC security group with several EC instances running inside it. You change the security group rules to allow inbound traffic on port 443 and you then launch several new instances in the same security group. The new rules apply:
1. Straight Away but to the new instances only. 2. Straight away to all instances within the security group. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Straight Away to the new instances, but old instances must be stopped and restarted before the new rules apply.
Explanation: Is it possible to move an instance from one security group to another? No, it is not. The security group for an instance is set at launch time and can not be changed. You have two options: 1. modify the settings for the current security group - which will affect all instances running in the specific group 2. launch a new instance in the second security group and terminate the old instance in the first security group