Question : A user has scheduled the maintenance window of an RDS DB on Monday at AM. Which of the below mentioned events may force to take the DB instance offline during the maintenance window? 1. Enabling Read Replica 2. Making the DB Multi AZ 3. Access Mostly Uused Products by 50000+ Subscribers 4. Security patching
Explanation: Amazon RDS performs maintenance on the DB instance during a user-definable maintenance window. The system may be offline or experience lower performance during that window. The only maintenance events that may require RDS to make the DB instance offline are: Scaling compute operations Software patching. Required software patching is automatically scheduled only for patches that are security and durability related. Such patching occurs infrequently (typically once every few months. and seldom requires more than a fraction of the maintenance window.
Question : An organization has launched instances: for production and for testing. The organization wants that one particular group of IAM users should only access the test instances and not the production ones. How can the organization set that as a part of the policy? 1. Launch the test and production instances in separate regions and allow region wise access to the group 2. Define the IAM policy which allows access based on the instance ID 3. Access Mostly Uused Products by 50000+ Subscribers 4. Define the tags on the test and production servers and add a condition to the IAM policy which allows access to specific tags
Explanation: AWS Identity and Access Management is a web service which allows organizations to manage users and user permissions for various AWS services. The user can add conditions as a part of the IAM policies. The condition can be set on AWS Tags, Time, and Client IP as well as on various parameters. If the organization wants the user to access only specific instances he should define proper tags and add to the IAM policy condition. The sample policy is shown below. "Statement": [ { "Action": "ec2:*", "Effect": "Allow", "Resource": "*", "Condition": { "StringEquals": { "ec2:ResourceTag/InstanceType": "Production" } } } ]
Question : A user has configured Auto Scaling with the minimum capacity as and the desired capacity as . The user is trying to terminate one of the existing instance with the command: as-terminate-instance-in-auto-scaling-group (Instance ID) --decrement-desired-capacity What will Auto Scaling do in this scenario? 1. Terminates the instance and does not launch a new instance 2. Terminates the instance and updates the desired capacity to 1 3. Access Mostly Uused Products by 50000+ Subscribers 4. Throws an error
Explanation: The Auto Scaling command as-terminate-instance-in-auto-scaling-group (Instance ID) will terminate the specific instance ID. The user is required to specify the parameter as --decrement-desired- capacity. Then Auto Scaling will terminate the instance and decrease the desired capacity by 1. In this case since the minimum size is 2, Auto Scaling will not allow the desired capacity to go below 2. Thus, it will throw an error.