Question : QuickTechie.com is setting up a multi-site solution where the application runs on premise as well as on AWS to achieve the minimum RTP. They have database as Oracle in backend. Select the configurations which is not the requirements of the multi-site solution scenario? 1. Configure data replication based on RTO. 2. Setup a single DB instance which will be accessed by both sites. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Setup a weighted DNS service like Route 53 to route traffic across sites.
Correct Answer : Get Lastest Questions and Answer : Exp: AWS has many solutions for DR and HA. When the organization wants to have HA and DR with multi-site solution, it should setup two sites: one on premise and the other on AWS with full capacity. The organization should setup a weighted DNS service which can route traffic to both sites based on the weightage. When one of the sites fails it can route the entire load to another site. The organization would have minimal RTP in this scenario. If the organization setups a single DB instance, it will not work well in failover. Instead they should have two separate DBs in each site and setup data replication based on RTO of the organization.
Question : QuickTechie.com is hosting a scalable web application using AWS. And configured internet facing ELB and Auto Scaling to make the application scalable. Which of the below mentioned statements is required to be followed when the application is planning to host a website on VPC? 1. The ELB can be in a public or a private subnet but should have the ENI which is attached to an elastic IP. 2. The ELB must not be in any subnet; instead it should face the internet directly. 3. Access Mostly Uused Products by 50000+ Subscribers 4. The ELB must be in a public subnet of the VPC to face the internet traffic.
Correct Answer : Get Lastest Questions and Answer : Exp: : To create and use ELB load balancers within a VPC, you have to first configure your VPC environment by creating a VPC, creating one or more subnets, and then launch your instances in the subnets.
Here are some tips on configuring your VPC and subnets for Elastic Load Balancing.
Create your VPC with an Internet gateway in the region where you want to launch your instances and load balancer.
If you are a new customer or if you are using the region you have not previously used, you are likely to get a default VPC, by default. You can either use the default VPC or create your own.
Create subnets in each Availability Zone in which you want to launch your instances. Depending on your use case, your security and operational requirements, the subnets where you want to launch your instances can either be a private subnet or a public subnet.
Instances launched in a private subnet cannot communicate with the Internet. If you want your instances in private subnet to have outbound internet access only, place a network address translation (NAT) instance in a public subnet. A NAT instance enables instances in the private subnet to initiate outbound traffic to the Internet, but prevents them from receiving inbound traffic.
You can optionally create a separate subnet for your load balancer. Your instances do not need to be in the same subnet that has your load balancer. If you plan to place your load balancer and your back-end instances in separate subnets, make sure to configure the security group rules and network ACLs to allow traffic to be routed between the subnets in your VPC. If your rules are not configured correctly, instances in other subnets may not be reachable by the load balancer in a different subnet.
To ensure that your load balancer can scale properly, make sure that the subnet in which you plan to place your load balancer has CIDR block of at least a /27 bitmask (e.g., 10.0.0.0/27) and also has at least 8 free IP addresses. When you create your load balancer and place it in a subnet, this defines the subnet that traffic must enter to forward the request to registered instances.
Important
If you are creating an Internet-facing load balancer, make sure to place your load balancer in a public subnet. After you create the public subnet, make sure to associate the route table of your public subnet with the Internet gateway to enable your load balancer in the subnet to connect with the Internet.
If you are planning to register linked EC2-Classic instances with your load balancer, make sure to enable your VPC for ClassicLink after you create it, and then create your load balancer in that VPC.
The most common VPC scenarios are documented in the Scenarios for Amazon VPC. Each of these scenarios has a link to a detailed explanation of the scenario. At the end of the section is a section called Implementing the Scenario that gives you instructions on how to create a VPC for that scenario. You can follow the instructions from the scenario that best suits your use case to create your VPC environment.
Question : www.HadoopExam.com is planning to create a secure, scalable and HA system on the AWS VPC. Which of the below mentioned configurations will not help HadoopExam to achieve their goals if they are planning to use the AWS VPC? 1. Setup CloudWatch which will monitor the AWS instances and trigger an alert to the Auto Scaling group when there is some odd behaviour. 2. Setup Auto Scaling with multiple public subnets in separate zones from the same VPC. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Setup the internet facing ELB with VPC which is facing external traffic and has all instances registered with it.
Correct Answer : Get Lastest Questions and Answer : Exp: Amazon Virtual Private Cloud (Amazon VPC) enables you to define a virtual networking environment in a private, isolated section of the AWS cloud. You have complete control over your virtual networking environment. For more information, see the Amazon VPC User Guide.
Within a virtual private cloud (VPC), you can launch AWS resources such as an Auto Scaling group. An Auto Scaling group in a VPC works essentially the same way as it does on Amazon EC2 and supports the same set of features. This section provides you with an overview of Auto Scaling groups in a VPC and steps you through the process of creating an Auto Scaling group in a VPC. If you want to launch your Auto Scaling instances in Amazon EC2, see Getting Started with Auto Scaling.
Before you can create your Auto Scaling group in a VPC, you must first configure your VPC environment. You create your VPC by specifying a range of IP addresses in the classless inter-domain routing (CIDR) range of your choice (for example, 10.0.0.0/16). For more information about CIDR notation and what "/16" means, go to Classless Inter-Domain Routing on Wikipedia.
You can create a VPC that spans multiple Availability Zones then add one or more subnets in each Availability Zone. A subnet in Amazon VPC is a subdivision within an Availability Zone defined by a segment of the IP address range of the VPC. Using subnets, you can group your instances based on your security and operational needs. A subnet resides entirely within the Availability Zone it was created in. You launch Auto Scaling instances within the subnets.
To enable communication between the Internet and the instances in your subnets, you must create an Internet gateway and attach it to your VPC. An Internet gateway enables your resources within the subnets to connect to the Internet through the Amazon EC2 network edge. If a subnet's traffic is routed to an Internet gateway, the subnet is known as a public subnet. If a subnet's traffic is not routed to an Internet gateway, the subnet is known as a private subnet. Use a public subnet for resources that must be connected to the Internet, and a private subnet for resources that need not be connected to the Internet.
1. Increase the desired capacity of the Auto Scaling group 2. Increase the maximum limit of the Auto Scaling group 3. Access Mostly Uused Products by 50000+ Subscribers 4. Decrease the minimum limit of the Auto Scaling grou
1. Amazon RDS with provisioned IOPS up to the anticipated peak write throughput. 2. Amazon Simple Queue Service (SQS) for capturing the writes and draining the queue to write to the database. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Amazon DynamoDB with provisioned write throughput up to the anticipated peak write throughput.
1. Use an EC2 Instance that is launched with an EC2 role providing access to the Score Data DynamoDB table and the GameState S3 bucket that communicates with the mobile app via web services. 2. Use temporary security credentials that assume a role providing access to the Score Data DynamoDB table and the Game State S3 bucket using web identity federation. 3. Access Mostly Uused Products by 50000+ Subscribers bucket. 4. Use an IAM user with access credentials assigned a role providing access to the Score Data DynamoDB table and the Game State S3 bucket for distribution with the mobile app.
1. Use S3 with reduced redundancy to store and serve the scanned files, install the commercial search application on EC2 Instances and configure with auto-scaling and an Elastic Load Balancer. 2. Model the environment using CloudFormation use an EC2 instance running Apache webserver and an open source search application, stripe multiple standard EBS volumes together to store the JPEGs and search index. 3. Access Mostly Uused Products by 50000+ Subscribers multiple availability zones. 4. Use a single-AZ RDS MySQL instance lo store the search index 33d the JPEG images use an EC2 instance to serve the website and translate user queries into SQL.
5. Use a CloudFront download distribution to serve the JPEGs to the end users and Install the current commercial search product, along with a Java Container Tor the website on EC2 instances and use Route53 with DNS round-robin.