Question : You are trying to setup the schedule for AutoScaling. Where do you set the schedule in the AWS console? 1. Scaling with schedule is not supported with the AWS console 2. In AutoScaling policy configuration 3. Access Mostly Uused Products by 50000+ Subscribers 4. In AutoScaling group creation
Explanation: If the user wants to setup scaling with Schedule for AutoScaling, the user has to use CLI or Web Services. The AWS console does not support scaling with a schedule.
Question : You have instances registered for HadoopExam.com website with ELB configured through AutoScaling. And now had setup the policy to scale up when the CPU utilization is above 50%. Which CPU utilization should AWS consider here? 1. Average statistics of 10 instances observed through CloudWatch metrics 2. Maximum CPU utilization out of the 10 instances 3. Access Mostly Uused Products by 50000+ Subscribers 4. The AutoScaling group average CPU utilization
Explanation: The user can configure the AutoScaling group to automatically scale up and then scale down based on the various specified CloudWatch monitoring conditions. CloudWatch provides an average of the AutoScaling group metrics in this case.
Question : What happens when a you takes a snapshot of an EBS volume which is not the first snapshot taken of the volume? 1. It synchronously copies incremental data to S3 2. It copies all the written blocks which are on the volume 3. Access Mostly Uused Products by 50000+ Subscribers 4. It copies the whole EBS volume data to S3
Explanation: When a user creates a snapshot of an EBS volume which is not the first, it asynchronously copies the modified data only. It does not copy the whole volume or all the data written to it, but just the modified one. Only for the first snapshot it will copy all the data written on the volume and not copy the blank / empty blocks.
1. In the second instance allow inbound on port 0-65535 for the security group of the first instance 2. In the first instance allow inbound on port 0-65535 for the security group of the second instance 3. Access Mostly Uused Products by 50000+ Subscribers 4. By default each instance can talk to the other instance in the same region. It is not required to the configure security group