You have been asked to automate many routine systems administrator backup and recovery activities. Your
current plan is to leverage AWS-managed solutions as much as possible and automate the rest with the AWS
CLI and scripts.
Which task would be best accomplished with a script?
A.
Creating daily EBS snapshots with a monthly rotation of snapshots
B.
Creating daily RDS snapshots with a monthly rotation of snapshots
C.
Automatically detect and stop unused or underutilized EC2 instances
D.
Automatically add Auto Scaled EC2 instances to an Amazon Elastic Load Balancer
Answer should be B,
https://aws.amazon.com/rds/faqs/
A is correct Answer. B – taken care by part of aws.
Correction, B is correct.
https://aws.amazon.com/rds/details/#ha
I don’t think B is correct since the question asks “Which task would be best accomplished with a script?”. RDS automated backups are turned on by default, so you don’t need a script for that. There is nothing built in for EBS snapshots, so that you will definitely need a script.
Agree. Other options could be done without script. Only A you probably need to write CLI embeded script to do so.
You can automate RDS snapshots without a script. Answer is A
Why can’t the answer be C? That must be done with script too right?
It could be done by script. However, you most likely would choose using auto scaling group to perform this task for you. While option A does not have this better alternative.
You can do this with autoscale without a script.
https://aws.amazon.com/about-aws/whats-new/2013/01/08/use-amazon-cloudwatch-to-detect-and-shut-down-unused-amazon-ec2-instances/
Stop or Terminate EC2 Instances That are Unused or Underutilized
Amazon CloudWatch collects monitoring data for your AWS resources and applications. Amazon CloudWatch alarms help you react quickly to issues by emailing a notification to you or executing automated tasks when data values reach a threshold you set. Starting today, you can also set alarms that automatically stop or terminate Amazon EC2 instances that have gone unused or underutilized for too long. For example, a student who wants to stay within the AWS Free Usage Tier can set an alarm that automatically stops an instance once it has been left idle for an hour. Or, if you are a corporate IT administrator, you can create a group of alarms that first sends an email notification to developers whose instances have been underutilized for 8 hours, then terminates an instance and emails both of you if utilization doesn’t improve after 24 hours.
Since stopping an instance completes one billing hour–i don’t think adding cost to the task would help–I am leaning towards A because its snapshots can be scripted per: https://cloudacademy.com/blog/how-to-manage-ebs-volumes-snapshots-in-aws/ and https://github.com/CaseyLabs/aws-ec2-ebs-automatic-snapshot-bash
This is a trick question meant to deceive. the answer is A. RDS is already automated.
A
A is the right answer. Basically the question ask us to identify a service that not readily available on AWS so we have to write script for it.
“Your
current plan is to leverage AWS-managed solutions as much as possible”
Only service not available by AWS is backup EBS snapshot.
a
A, RDS has automatic backup functionality baked into the service. C and D are flat out wrong.
Answer is A, because BCD doesn’t require scripts.
B, configure the backup from aws console
C, you can set up cloudwatch alarm to stop instance if the cpu is under 10%
D, you can associate the asg with the elb
clue is in “You have been asked to automate many routine systems administrator backup and recovery activities” ..answers C & D doesn’t involve backup & recovery so out of equation.. out of A & B , A is the answer as RDS snapshots are already done automatically
Correct Answer is A
A is correct since the question asks “Which task would be best accomplished with a script?”. RDS automated backups are turned on by default, so you don’t need a script for that. There is nothing built in for EBS snapshots, so that you will definitely need a script.