AWS Certified SysOps Administrator - Associate Questions and Answers (Dumps and Practice Questions)
Question : You have an Auto Scaling group associated with an Elastic Load Balancer (ELB). You have noticed that instances launched via the Auto Scaling group are being marked
unhealthy due to an ELB health check, but these unhealthy instances are not being terminated What do you need to do to ensure trial instances marked unhealthy by the ELB will be
terminated and replaced?
1. Change the thresholds set on the Auto Scaling group health check
2. Add an Elastic Load Balancing health check to your Auto Scaling group
3. Access Mostly Uused Products by 50000+ Subscribers
4. Change the health check set on the Elastic Load Balancer to use TCP rather than HTTP checks
Correct Answer : Get Lastest Questions and Answer :
Explanation: If you set the autoscaling group's health check type to ELB then it will automatically retire any instances that fail the ELB health checks (ie doesn't
respond in a timely manner to the URL configured)
As long as the configured health check properly reports than an instance is bad (which sounds like it is the case since you say ELB is marking the instance as unhealthy) this should
work
Auto Scaling periodically performs health checks on the instances in your group and replaces instances that fail these checks. By default, these health checks use the results of EC2
instance status checks to determine the health of an instance. If you use a load balancer with your Auto Scaling group, you can optionally choose to include the results of Elastic
Load Balancing health checks.
Auto Scaling marks an instance as unhealthy if the instance status is any state other than running, the system status is impaired, or Elastic Load Balancing reports the instance
state as OutOfService.
You can customize the health check conducted by your Auto Scaling group by specifying additional checks or by having your own health check system and then sending the instance's
health information directly from your system to Auto Scaling
After an instance is marked unhealthy because of an Amazon EC2 or Elastic Load Balancing health check, it is scheduled for replacement.
Replacing Unhealthy Instances : After an instance has been marked unhealthy as a result of an Amazon EC2 or Elastic Load Balancing health check, it is almost immediately scheduled
for replacement. It never automatically recovers its health. You can intervene manually by calling the SetInstanceHealth action (or the as-set-instance-health command) to set the
instance's health status back to healthy, but you will get an error if the instance is already terminating. Because the interval between marking an instance unhealthy and its actual
termination is so small, attempting to set an instance's health status back to healthy with the SetInstanceHealth action (or, as-set-instance-health command) is probably useful only
for a suspended group. For more information, see Suspend and Resume Auto Scaling Processes.
Auto Scaling creates a new scaling activity for terminating the unhealthy instance and then terminates it. Subsequently, another scaling activity launches a new instance to replace
the terminated instance.
When your instance is terminated, any associated Elastic IP addresses are disassociated and are not automatically associated with the new instance. You must associate these Elastic
IP addresses with the new instance manually. Similarly, when your instance is terminated, its attached EBS volumes are detached. You must attach these EBS volumes to the new instance
manually.
Add an Elastic Load Balancing Health Check to your Auto Scaling Group By default, an Auto Scaling group periodically reviews the results of EC2 instance status to determine
the health state of each instance. However, if you have associated your Auto Scaling group with an Elastic Load Balancing load balancer, you can choose to use the Elastic Load
Balancing health check. In this case, Auto Scaling determines the health status of your instances by checking the results of both the EC2 instance status check and the Elastic Load
Balancing instance health check.
Question : Which two AWS services provide out-of-the-box user configurable automatic backup-as-a-service and backup rotation options?
Choose 2 answers
A. Amazon S3
B. Amazon RDS
C. Amazon EBS
D. Amazon Red shift
1. A,B
2. B,C
3. Access Mostly Uused Products by 50000+ Subscribers
4. C,D
5. A,C
Correct Answer : Get Lastest Questions and Answer :
Explanation: By default and at no additional charge, Amazon RDS enables automated backups of your DB Instance with a 1 day retention period. Free backup storage is limited to the size of
your provisioned database and only applies to active DB Instances. For example, if you have 10GB-months of provisioned database storage, we will provide at most 10GB-months of backup
storage at no additional charge. If you would like to extend your backup retention period beyond one day, you can do so using the CreateDBInstance API (when creating a new DB
Instance) or ModifyDBInstance API (for an existing DB Instance). You can use these APIs to change the RetentionPeriod parameter from 1 to the desired number of days.
By default, Amazon Redshift enables automated backups of your data warehouse cluster with a 1-day retention period. Free backup storage is limited to the total size of storage on the
nodes in the data warehouse cluster and only applies to active data warehouse clusters. For example, if you have total data warehouse storage of 8TB, we will provide at most 8TB of
backup storage at no additional charge. If you would like to extend your backup retention period beyond one day, you can do so using the AWS Management Console or the Amazon Redshift
APIS. For more information on automated snapshots, please refer to the Amazon Redshift Management Guide. Amazon Redshift only backs up data that has changed so most snapshots only
use up a small amount of your free backup storage.
By default and at no additional charge, Amazon RDS enables automated backups of your DB Instance with a 1 day retention period.
By default, Amazon Redshift enables automated backups of your data warehouse cluster with a 1-day retention period.
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 of 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.
Correct Answer : Get Lastest Questions and Answer :
Explanation: Adding an ELB can span multi-AZ with a region. Also you will need something like Route53 to pair up the 2 ELB names.
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
Related Questions
Question : A user is having data generated randomly based on a certain event. The user wants to upload that data to CloudWatch. It may happen that event
may not have data generated for some period due to randomness. Which of the below mentioned options is a recommended option for this case?
1. For the period when there is no data, the user should not send the data at all
2. For the period when there is no data the user should send a blank value
3. Access Mostly Uused Products by 50000+ Subscribers
4. The user must upload the data to CloudWatch as having no data for some period will cause an error at CloudWatch monitoring
Question : A user is sending the data to CloudWatch using the CloudWatch API. The user is sending data minutes in the future. What will CloudWatch do
in this case?
1. CloudWatch will accept the data
2. It is not possible to send data of the future
3. Access Mostly Uused Products by 50000+ Subscribers
4. The user cannot send data for more than 60 minutes in the future
Question : A user wants to upload a complete folder to AWS S using the S Management console. How can the user perform this activity?
1. Just drag and drop the folder using the flash tool provided by S3
2. Use the Enable Enhanced Folder option from the S3 console while uploading objects
3. Access Mostly Uused Products by 50000+ Subscribers
4. Use the Enable Enhanced Uploader option from the S3 console while uploading objects
Question : Which of the below mentioned AWS RDS logs cannot be viewed from the console for MySQL?
1. Error Log
2. Slow Query Log
3. Access Mostly Uused Products by 50000+ Subscribers
4. General Log
Question : A user has launched an EBS backed EC instance in the US-East-a region. The user stopped the instance and started it back after days.
AWS throws up an `InsufficientInstanceCapacity' error. What can be the possible reason for this?
1. AWS does not have sufficient capacity in that availability zone
2. AWS zone mapping is changed for that user account
3. Access Mostly Uused Products by 50000+ Subscribers
4. The user account has reached the maximum EC2 instance limit
Question : A user has created a VPC with public and private subnets using the VPC wizard. Which of the below
mentioned statements is true in this scenario?
1. The AWS VPC will automatically create a NAT instance with the micro size
2. VPC bounds the main route table with a private subnet and a custom route table with a public subnet
3. Access Mostly Uused Products by 50000+ Subscribers
4. VPC bounds the main route table with a public subnet and a custom route table with a private subnet