Question : You have recently joined a media company, who runs their website on reserved EC instances. However, because of recent popularity, traffic had increased on the website. Your chief architect hired and asking you to implement auto scaling for the websites EC2 server, which should at the max 10 EC2 servers. These 3 reserved instances are already have 2 years remaining and their price is paid upfront.
1. You will use this three server and 7 additional on demand server for configuring auto scaling.
2. You will be having all 10 new server and that will be on spot instances in auto scaling.
4. You will be reserving 7 more instances with same configuration and put all 10 in auto scaling group.
Correct Answer : Get Lastest Questions and Answer : Explanation: A Reserved Instance on AWS is a billing concept and does not apply to a specific Amazon EC2 instance.
Each hour, the AWS billing system looks at all EC2 instances that have been running in a particular AWS account. It then compares them with any Reserved Instances that have been purchased. It compares the following attributes:
Instance Type (eg m3.large) Operating System (eg Windows) Availability Zone (eg us-west-2) For each EC2 instance that matches a Reserved Instance, no cost applies. This is because the cost has already been paid as part of the Reserved Instance purchase.
The Reserved Instance applies regardless of whether the instance was launched through Auto Scaling.
Therefore, if you have purchased one Reserved Instance and your Auto Scaling group launches instances that match the Reserved Instance (Type, OS, AZ), then one of the instances in your Auto Scaling group will be "free" (or rather, pre-paid) each hour.
If your Auto Scaling group has a minimum of 1 and a maximum of 4, then there will always be at least one EC2 instance running, so you would receive the benefit of the Reserved Instance. Any instances above 1 will be charged normally. It is recommend that you use Reserved Instances for any instance that will be running continuously.
Question : How to use Route to direct your domain to an Elastic Load Balancer fronting your web servers. Which of the following record set, you will create ? 1. AAAA 2. A 3. Access Mostly Uused Products by 50000+ Subscribers 4. MX
Ans : 3 Exp : The AWS::Route53::RecordSet type can be used as a standalone resource or as an embedded property in the AWS::Route53::RecordSetGroup type. Note that some AWS::Route53::RecordSet properties are valid only when used within AWS::Route53::RecordSetGroup.
Note that before you use AWS CloudFormation to add a recordset to hosted zone, that hosted zone must already be created in Amazon Route 53. AWS CloudFormation does not create new hosted zones.
In CloudFront, an alternate domain name, also known as a CNAME, lets you use your own domain name (for example, www.example.com) for links to your objects instead of using the domain name that CloudFront assigns to your distribution. Both web and RTMP distributions support alternate domain names.
When you create a distribution, CloudFront returns a domain name for the distribution, for example:
d111111abcdef8.cloudfront.net
When you use the CloudFront domain name for your objects, the URL for an object called /images/image.jpg is:
If you want to use your own domain name, such as www.example.com, instead of the cloud front.net domain name that CloudFront assigned to your distribution, you can add an alternate domain name to your distribution for www.example.com. You can then use the following URL for /images/image.jpg:
http://www.example.com/images/image.jpg
Question : Key Pairs consist of a public and private key where you use the private key to create a digital signature, and then AWS uses the corresponding public key to validate the signature , select the correct statement which applies correctly ? 1. Key pairs are used for all Amazon services 2. Key pairs are used only for Amazon SDKs 3. Access Mostly Uused Products by 50000+ Subscribers 4. Key pairs are used only for Elastic Load Balancing and AWS IAM Ans : 3 Exp :
Key pairs consist of a public and private key, where you use the private key to create a digital signature, and then AWS uses the corresponding public key to validate the signature. Key pairs are used only for Amazon EC2 and Amazon CloudFront.
For Amazon EC2, you use key pairs to access Amazon EC2 instances, such as when you use SSH to log in to a Linux instance.
For Amazon CloudFront, you use key pairs to create signed URLs for private content, such as when you want to distribute restricted content that someone paid for.
Question : For which of the following you can apply Multifactor Authentication ?
Ans : 2 Exp :AWS Multi-Factor Authentication (AWS MFA) provides an extra level of security that you can apply to your AWS environment. With AWS MFA enabled, when you sign in to an AWS website, you are prompted for your user name and password, as well as for an authentication code from an MFA device. Taken together, these multiple factors provide increased security for your AWS account settings and resources. You can enable MFA for the root account and for IAM users.
Question : You are closely working with AWS solution architect and he suggested to implement auto scaling for your, website hosted on EC. Why he suggested to use auto scaling configured for website? A. Using Auto scaling you can divert traffic to particular instances eg 30%, 30% and 40% on three different EC2 instances. B. You can have dynamism in your EC2 instances need, so whenever more instances required it will be launched and whenever not then they will be not used and not charged. C. Using auto scaling you can monitor the entire fleet of EC2 instances e.g. CPU monitoring D. Using auto scaling will help you to send alert on your mobile using SNS. So you will get real time picture of EC2 instances. E. Using auto scaling you can configure your own AMI and minimum number of EC2 instances.
Correct Answer : Get Lastest Questions and Answer : Explanation: : Chief architect suggested auto scaling because, he want dynamism in EC2 instance requirement, whenever heavy load is there AWS launch new EC2 instance and handle the traffic and whenever there is no heavy traffic extra instances can be stopped and can save the cost. Also you can define which AMI to use for new instances launch and what is the minimum, maximum and desired EC2 instances for auto scaling.
Question : When you configured auto scaling, you found that the launch configuration kept out side of the auto scaling, what all are the benefits you observe having it outside the auto scaling group. A. You can change the configuration for EC2 instance types without touching the currently running EC2 instances. B. You can change the AMI and new instances can be launched using new AMI and previously running can be stopped. C. Even you can apply patch to EC2 instances and bring down already running EC2 instances. D. You can have added new security rule to already running EC2 instances, without bring them down.
Correct Answer : Get Lastest Questions and Answer : Explanation: Yes, there are lot of advantages of keeping the launch configuration outside of the auto scaling group and you can have many things can be done as mentioned options in question itself.
1. Create a second, independent LDAP server in AWS for your application to use for authentication 2. Establish a VPN connection so your applications can authenticate against your existing on-premises LDAP servers 3. Access Mostly Uused Products by 50000+ Subscribers replica for authentication. 4. Create a second LDAP domain on AWS establish a VPN connection to establish a trust relationship between your new and existing domains and use the new domain for authentication
1. EC2-Classic security groups allow you to add inbound and outbound traffic rules. 2. EC2-Classic allows you to change an instance's security group. 3. Access Mostly Uused Products by 50000+ Subscribers 4. None of the above