Question : Being a QuickTechie.com AWS Developer you are trying to detach the EBS volume from an instance. Which of the below mentioned options is not the right API to detach a volume from an instance? 1. ec2-detach-volume 2. ec2-dismount-volume 3. Access Mostly Uused Products by 50000+ Subscribers 4. detach-volume
Explanation: The user can use one of the following commands to detach an EBS volume: detach-volume (AWS CLI) ec2-detach-volume (Amazon EC2 CLI) dismount-EC2Volume (AWS Tools for Windows PowerShell)
Question : Being a QuickTechie.com AWS Developer you are accessing an EBS for the first time there can be a huge reduction in the I/O. How can the user avoid this? 1. Pre-warm the EBS volumes as per the requirement 2. There is no decrease in the I/O performance the first time and the user can use it as it is 3. Access Mostly Uused Products by 50000+ Subscribers 4. Use a higher instance size which gives better I/O
Explanation: There is a 5 to 50 percent reduction in IOPS when the user first accesses each block of data on a newly created or restored EBS volume. The user can avoid this performance hit by accessing each block in advance or pre-warm the Amazon EBS volumes.
Question : A user has enabled AutoScaling with ELB. The ELB has enabled connection drainage. If Auto Scaling wants to terminate an instance, what will it do? 1. It will mark the instance deregistering and ELB will wait until the connection drainage timeout period 2. AutoScaling cannot work with ELB if connection drainage is enabled 3. Access Mostly Uused Products by 50000+ Subscribers 4. It initiates the termination process, ELB will wait till the inflight requests are completed
Explanation: If instances are part of an AutoScaling group and connection draining is enabled for the load balancer, AutoScaling will wait for the in-flight requests to complete or for the maximum timeout to expire, whichever comes first, before terminating instances due to a scaling event or health check replacement.
1. This permission change will be effective after instance restarted 2. This permission change will be effective almost immediately 3. Access Mostly Uused Products by 50000+ Subscribers 4. You have to drop this role first and create another one and launch the ec2 server again with the new role as input parameter