Amazon Amazon Certifications SAP-C01 Questions & Answers

• Question 651:

  Identify a benefit of using Auto Scaling for your application.

  A. Your application gains better fault tolerance.

  B. Your application optimizes only logistics and operations.

  C. Your application receives latency requirements in every region.

  D. You acquire clarity on prototypes in your application.

  Correct Answer: A

  When you use Auto Scaling, your applications gain better fault tolerance. Auto Scaling can detect when an instance is unhealthy, terminate it, and launch an instance to replace it. You can also configure Auto Scaling to use multiple Availability Zones. If one Availability Zone becomes unavailable, Auto Scaling can launch instances in another one to compensate.

  Reference: http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/how-as-works.html

• Question 652:

  After moving an E-Commerce website for a client from a dedicated server to AWS you have also set up auto scaling to perform health checks on the instances in your group and replace instances that fail these checks. Your client has come to you with his own health check system that he wants you to use as it has proved to be very useful prior to his site running on AWS.

  What do you think would be an appropriate response to this given all that you know about auto scaling and CloudWatch?

  A. It is not possible to implement your own health check system due to compatibility issues.

  B. It is not possible to implement your own health check system. You need to use AWSs health check system.

  C. It is possible to implement your own health check system and then send the instance's health information directly from your system to CloudWatch but only in the US East (N. Virginia) region.

  D. It is possible to implement your own health check system and then send the instance's health information directly from your system to CloudWatch.

  Correct Answer: D

  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 unhealthy if the calls to the Amazon EC2 action DescribeInstanceStatus returns any other state other than running, the system status shows impaired, or the calls to Elastic Load Balancing action DescribeInstanceHealth returns OutOfService in the instance state field. After an instance is marked unhealthy because of an Amazon EC2 or Elastic Load Balancing health check, it is scheduled for replacement. 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.

  Reference: http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/healthcheck.html

• Question 653:

  To scale out the AWS resources using manual AutoScaling, which of the below mentioned parameters should the user change?

  A. Current capacity

  B. Desired capacity

  C. Preferred capacity

  D. Maximum capacity

  Correct Answer: B

  The Manual Scaling as part of Auto Scaling allows the user to change the capacity of Auto Scaling group.

  The user can add / remove EC2 instances on the fly. To execute manual scaling, the user should modify

  the desired capacity.

  AutoScaling will adjust instances as per the requirements.

  Reference:

  http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/as-manual-scaling.html

• Question 654:

  Which of the following commands accepts binary data as parameters?

  A. --user-data

  B. -cipher text-key

  C. --aws-customer-key

  D. --describe-instances-user

  Correct Answer: A

  For commands that take binary data as a parameter, specify that the data is binary content by using the

  fileb:// prefix.

  Commands that accept binary data include: aws ec2 run-instances --user-data parameter.

  aws s3api put-object --sse-customer-key parameter. aws kms decrypt --ciphertext-blob parameter.

  Reference:

  http://docs.aws.amazon.com/cli/latest/userguide/aws-cli.pdf

• Question 655:

  You have set up Auto Scaling to automatically scale in. Consequently, you must decide which instances Auto Scaling should end first.

  What should you use to configure this?

  A. An Elastic Load Balancer

  B. A termination policy

  C. An IAM role

  D. Another scaling group

  Correct Answer: B

  If you instruct Auto Scaling to automatically scale in, you must decide which instances Auto Scaling should terminate first. This can be configured through the use of a termination policy.

  Reference: http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/ AutoScalingBehavior.InstanceTermination.html

• Question 656:

  A sys admin is maintaining an application on AWS. The application is installed on EC2 and user has configured ELB and Auto Scaling. Considering future load increase, the user is planning to launch new servers proactively so that they get registered with ELB.

  How can the user add these instances with Auto Scaling?

  A. Decrease the minimum limit of the Auto Scaling group

  B. Increase the maximum limit of the Auto Scaling group

  C. Launch an instance manually and register it with ELB on the fly

  D. Increase the desired capacity of the Auto Scaling group

  Correct Answer: D

  A user can increase the desired capacity of the Auto Scaling group and Auto Scaling will launch a new instance as per the new capacity. The newly launched instances will be registered with ELB if Auto Scaling group is configured with ELB. If the user decreases the minimum size the instances will be removed from Auto Scaling. Increasing the maximum size will not add instances but only set the maximum instance cap.

  Reference: http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/as-manual-scaling.html

• Question 657:

  You have just added a new instance to your Auto Scaling group, which receives ELB health checks. An ELB heath check says the new instance's state is out of Service.

  What does Auto Scaling do in this particular scenario?

  A. It replaces the instance with a healthy one

  B. It stops the instance

  C. It marks an instance as unhealthy

  D. It terminates the instance

  Correct Answer: C

  If you have attached a load balancer to your Auto Scaling group, you can have Auto Scaling include the results of Elastic Load Balancing health checks when it determines the health status of an instance. After you add ELB health checks, Auto Scaling will mark an instance as unhealthy if Elastic Load Balancing reports the instance state as Out of Service. Frequently, an Auto Scaling instance that has just come into service needs to warm up before it can pass the Auto Scaling health check. Auto Scaling waits until the health check grace period ends before checking the health status of the instance. While the EC2 status checks and ELB health checks can complete before the health check grace period expires, Auto Scaling does not act on them until the health check grace period expires. To provide ample warm-up time for your instances, ensure that the health check grace period covers the expected startup time for your application.

  Reference: http://docs.aws.amazon.com/autoscaling/latest/userguide/healthcheck.html

• Question 658:

  You have setup an Auto Scaling group. The cool down period for the Auto Scaling group is 7 minutes. The first scaling activity request for the Auto Scaling group is to launch two instances. It receives the activity question at time "t", and the first instance is launched at t+3 minutes, while the second instance is launched at t+4 minutes.

  How many minutes after time "t" will Auto Scaling accept another scaling activity request?

  A. 11 minutes

  B. 10 minutes

  C. 7 minutes

  D. 14 minutes

  Correct Answer: A

  If an Auto Scaling group is launching more than one instance, the cool down period for each instance starts after that instance is launched. The group remains locked until the last instance that was launched has completed its cool down period. In this case the cool down period for the first instance starts after 3 minutes and finishes at the 10th minute (3+7 cool down), while for the second instance it starts at the 4th minute and finishes at the 11th minute (4+7 cool down). Thus, the Auto Scaling group will receive another request only after 11 minutes.

  Reference: http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/AS_Concepts.html

• Question 659:

  Can a user configure a custom health check with Auto Scaling?

  A. Yes, but the configured data will not be saved to Auto Scaling.

  B. No, only an ELB health check can be configured with Auto Scaling.

  C. Yes

  D. No

  Correct Answer: C

  Auto Scaling can determine the health status of an instance using custom health checks. If you have custom health checks, you can send the information from your health checks to Auto Scaling so that Auto Scaling can use this information. For example, if you determine that an instance is not functioning as expected, you can set the health status of the instance to Unhealthy. The next time that Auto Scaling performs a health check on the instance, it will determine that the instance is unhealthy and then launch a replacement instance.

  Reference: http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/healthcheck.html

• Question 660:

  A user wants to configure AutoScaling which scales up when the CPU utilization is above 70% and scales down when the CPU utilization is below 30%.

  How can the user configure AutoScaling for the above mentioned condition?

  A. Configure ELB to notify AutoScaling on load increase or decrease

  B. Use AutoScaling with a schedule

  C. Use AutoScaling by manually modifying the desired capacity during a condition

  D. Use dynamic AutoScaling with a policy

  Correct Answer: D

  Explanation: The user can configure the AutoScaling group to automatically scale up and then scale down based on the specified conditions. To configure this, the user must setup policies which will get triggered by the CloudWatch alarms.

  Reference: http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/as-scale-based-on-demand.html