Which of these is not a reason a Multi-AZ RDS instance will failover?

Which of these configuration or deployment practices is a security risk for RDS?

From a compliance and security perspective, which of these statements is true?

What does it mean if you have zero IOPS and a non-empty I/O queue for all EBS volumes attached to a running EC2
instance?

If I want CloudFormation stack status updates to show up in a continuous delivery system in as close to real time as
possible, how should I achieve this?

What is required to achieve gigabit network throughput on EC2? You already selected cluster-compute, 10GB instances
with enhanced networking, and your workload is already network-bound, but you are not seeing 10 gigabit speeds.

You need to deploy a new application version to production. Because the deployment is high-risk, you need to roll the
new version out to users over a number of hours, to make sure everything is working correctly. You need to be able to
control the proportion of users seeing the new version of the application down to the percentage point. You use ELB and
EC2 with Auto Scaling Groups and custom AMIs with your code pre-installed assigned to Launch Configurations. There
are no database-level changes during your deployment. You have been told you cannot spend too much money, so you
must not increase the number of EC2 instances much at all during the deployment, but you also need to be able to switch
back to the original version of code quickly if something goes wrong. What is the best way to meet these requirements?

Which is not a restriction on AWS EBS Snapshots?

What is the order of most-to-least rapidly-scaling (fastest to scale first)?
A) EC2 + ELB + Auto Scaling

B) Lambda
C) RDS

Your CTO has asked you to make sure that you know what all users of your AWS account are doing to change resources
at all times. She wants a report of who is doing what over time, reported to her once per week, for as broad a resource
type group as possible. How should you do this?