You need to deploy an AWS stack in a repeatable manner across multiple environments. You have selected
CloudFormation as the right tool to accomplish this, but have found that there is a resource type you need to create and
model, but is unsupported by CloudFormation. How should you overcome this challenge?

You are designing an enterprise data storage system. Your data management software system requires mountable disks
and a real filesystem, so you cannot use S3 for storage. You need persistence, so you will be using AWS EBS Volumes
for your system. The system needs as low-cost storage as possible, and access is not frequent or high throughput, and
is mostly sequential reads. Which is the most appropriate EBS Volume Type for this scenario?

Your API requires the ability to stay online during AWS regional failures. Your API does not store any state, it only
aggregates data from other sources – you do not have a database. What is a simple but effective way to achieve this
uptime goal?

For AWS CloudFormation, which is true?

Which of these is not an intrinsic function in AWS CloudFormation?

You meet once per month with your operations team to review the past month’s data. During the meeting, you realize
that 3 weeks ago, your monitoring system which pings over HTTP from outside AWS recorded a large spike in latency
on your 3-tier web service API. You use DynamoDB for the database layer, ELB, EBS, and EC2 for the business logic
tier, and SQS, ELB, and EC2 for the presentation layer. Which of the following techniques will NOT help you figure out
what happened?

You are experiencing performance issues writing to a DynamoDB table. Your system tracks high scores for video games
on a marketplace. Your most popular game experiences all of the performance issues. What is the most likely problem?

What is the scope of an EBS volume?

Which of these is not a Pseudo Parameter in AWS CloudFormation?

Your CTO thinks your AWS account was hacked. What is the only way to know for certain if there was unauthorized
access and what they did, assuming your hackers are very sophisticated AWS engineers and doing everything they can
to cover their tracks?