Question : An organization has configured a VPC with an Internet Gateway (IGW). pairs of public and private subnets (each with one subnet per Availability Zone), and an Elastic Load Balancer (ELB) configured to use the public subnets The applications web tier leverages the ELB. Auto Scaling and a multi-AZ RDS database instance The organization would like to eliminate any potential single points ft failure in this design. What step should you take to achieve this organization's objective? 1. Nothing, there are no single points of failure in this architecture. 2. Create and attach a second IGW to provide redundant internet connectivity. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Create a second multi-AZ RDS instance in another Availability Zone and configurereplication to provide a redundant database.
Explanation: When you create or modify your DB Instance to run as a Multi-AZ deployment, Amazon RDS automatically provisions and maintains a synchronous "standby" replica in a different Availability Zone. Updates to your DB Instance are synchronously replicated across Availability Zones to the standby in order to keep both in sync and protect your latest database updates against DB Instance failure. During certain types of planned maintenance, or in the unlikely event of DB Instance failure or Availability Zone failure, Amazon RDS will automatically failover to the standby so that you can resume database writes and reads as soon as the standby is promoted. Since the name record for your DB Instance remains the same, you application can resume database operation without the need for manual administrative intervention. With Multi-AZ deployments, replication is transparent: you do not interact directly with the standby, and it cannot be used to serve read traffic. If you are using Amazon RDS for MySQL and are looking to scale read traffic beyond the capacity constraints of a single DB Instance, you can deploy An Internet gateway is a horizontally scaled, redundant, and highly available VPC component that allows communication between instances in your VPC and the Internet. It therefore imposes no availability risks or bandwidth constraints on your network traffic. An Internet gateway serves two purposes: to provide a target in your VPC route tables for Internet-routable traffic, and to perform network address translation (NAT) for instances that have been assigned public IP addresses. (So IGW by default redundant)
At its heart, an ELB is just a collection of EC2 instances. When you create an ELB, you specify the availability zones you want that load balancer to be in. Instances to make up the load balancer will then be created in those zones. The way they avoid a single point of failure here is by returning multiple IP addresses when you do a DNS lookup. For example: .DNS lookup for website.example.com returns CNAME website-elb-12345.eu-west-1.elb.amazonaws.com .The lookup also returns the information for website-elb-12345.eu-west-1.elb.amazonaws.com. It states that the site has IP address 1.2.3.4 and IP address 2.3.4.5
It is up to the client to choose which IP address to use to make a connection. The IP addresses won't always be returned in the same order from the DNS lookup. A client could retry on an alternative IP address if they can't connect on the first attempt. The TTL on the DNS records for an ELB is only 60 seconds which means that should an ELB instance die and get replaced, the DNS will be updated everywhere fairly quickly.
Link : http://shlomoswidler.com/2009/07/elastic-in-elastic-load-balancing-elb.html
Question :
Your company has a backup policy that requires backed up data to be "quickly" accessible within minutes for the first 6 months of the data life. After the first 6 months your data can be archived. How would you automatically handle this procedure?
1. Write a script that moves data stored on an EBS volume to S3 after 6 months. 2. Use Amazon Direct Connect to store the data onsite and back it up to S3. 3. Access Mostly Uused Products by 50000+ Subscribers 4. None of the above
Explanation: Amazon RDS for MySQL currently supports MySQL 5.1, 5.5 and 5.6 (Community Edition) with InnoDB as the default database storage engine. Amazon RDS for Oracle currently supports Oracle Database 11gR2. Amazon RDS for SQL Server currently supports 2008 R2 and SQL Server 2012. Amazon RDS for PostgreSQL currently supports PostgreSQL 9.3.
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
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.
1. Use an IAM policy that references the LDAP account identifiers and the AWS credentials. 2. Use SAML (Security Assertion Markup Language) to enable single sign-on between AWS and LDAP. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Use IAM roles to automatically rotate the IAM credentials when LDAP credentials are updated. 5. Use the LDAP credentials to restrict a group of users from launching specific EC2 instance types.