Question : How can an EBS volume that is currently attached to an EC instance be migrated from one Availability Zone to another? 1. Simply create a new volume in the other AZ and specify the original volume as the source. 2. Detach the volume, then use the ec2-migrate-volume command to move it to another AZ. 3. Access Mostly Uused Products by 50000+ Subscribers 4. Detach the volume and attach it to another EC2 instance in the other AZ.
Explanation: snapshots can be used to create multiple new EBS volumes, expand the size of a volume, or move volumes across Availability Zones. Only snapshots can be moved to another AZ
Question : Your business is building a new application that will store its entire customer database on a RDS MySQL database, and will have various applications and users that will query that data for different purposes. Large analytics jobs on the database are likely to cause other applications to not be able to get the query results they need to, before time out. Also, as your data grows, these analytics jobs will start to take more time, increasing the negative effect on the other applications. How do you solve the contention issues between these different workloads on the same data?
Explanation: Both Elasticache and Read Replicas could help here, depending on the scenario. Elasticache is for caching previously used database queries, so if this question is asking about frequent new queries, the answer has to be C. Based on the way the question is worded.
Question : You run a web application with the following components Elastic Load Balancer (ELB), Web/Application servers, 1 MySQL RDS database with read replicas, and Amazon Simple Storage Service (Amazon S3) for static content. Average response time for users is increasing slowly. What three CloudWatch RDS metrics will allow you to identify if the database is the bottleneck? Choose 3 answers
A. The number of outstanding IOs waiting to access the disk. B. The amount of write latency. C. The amount of disk space occupied by binary logs on the master. D. The amount of time a Read Replica DB Instance lags behind the source DB Instance E. The average number of disk I/O operations per second. 1. A,C,D 2. B,C,D 3. Access Mostly Uused Products by 50000+ Subscribers 4. A,B,D 5. B,C,E
Explanation: E is a metric. It states may be about the Read IOPS or Write IOPS. Here, the key term is average response time the A, B, D suit much for this scenario.