1. You have been asked to de-risk deployments at your company. Specifically, the CEO is concerned about outages that occur because of accidental inconsistencies between Staging and Production, which sometimes cause unexpected behaviors In Production even when Staging tests pass. You already use Docker to get high consistency between Staging and Production for the application environment on your EC2 instances. How do you further de-risk the rest of the execution environment, since in AWS, there are many service components you may use beyond EC2 virtual machines?

A) Use AWS(Amazon Web Service) ECS and Docker clustering. This will make sure that the AMIs and machine sizes are the same across both environments.
B) Develop models of your entire cloud system in Cloud Formation. Use this model in Staging and Production achieve greater parity.
C) Use AMPs to ensure the whole machine, including the kernel of the virtual machines, is consistent, since Docker uses Linux Container (DCC) technology, and we need to make sure the container environment Is consistent.
D) Use AWS(Amazon Web Service) Conflg to force the Staging and Production stacks to have configuration parity. Any differences will be detected for you so you are aware of risks.



2. You need to perform ad-hoc business analytics queries on well-structured data. Data comes in constantly at a high velocity. Your business intelligence team can understand SQL. What AWS(Amazon Web Service) service(s) should you look to first?

A) EMR running Apache Spark
B) Kinesis Fire hose + RDS
C) Kinesis Fire hose + Red Shift
D) EMR using Hive



3. You are planning on using the Amazon RDS facility for Fault tolerance for your application. How does Amazon RDS multi Availability Zone model work Please select:

A) A second, standby database is deployed and maintained in a different availability zone from master, using synchronous replication. .
B) A second, standby database is deployed and maintained in a different region from master using asynchronous replication.
C) A second. standby database is deployed and maintained in a different region from master using synchronous replication.
D) A second, standby database is deployed and maintained in a different availability zone from master using asynchronous replication.



4. You have an application running on an Amazon EC2 instance and you are using lAM roles to securely access AWS(Amazon Web Service) Service APIs. How can you configure your application running on that instance to retrieve the API keys for use with the AWS(Amazon Web Service) SDKs?

A) Within your application code, make a GET request to the lAM Service API to retrieve credentials for your user.
B) Within your application code, configure the AWS(Amazon Web Service) SDK to get the API keys from environment variables. because assigning an Amazon EC2 role stores keys in environment variables on launch.
C) When using AWS(Amazon Web Service) SDK5 and Amazon EC2 roles, you do not have to explicitly retrieve API keys. because the SDK handles retrieving them from the Amazon EC2 Meta Data service.
D) When assigning an EC2 lAM role to your instance in the console, in the those SDK dropdown list, select the SDK that you are using. and the Instance will configure the correct SDK on launch with the API keys.



5. Your API requires the ability to stay online during AWS(Amazon Web Service) 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?

A) Create a Route53 Latency Based Routing Record with Failover and point it to two identical deployments of your stateless API in two different regions. Make sure both regions use Auto Scaling Groups behind ELB5.
B) Create a Route53 Weighted Round Robin record, and if one region goes down, have that region redirect to the other region.
C) Use a Cloud Front distribution to serve up your API. Even if the region your API is in goes down, the edge locations Cloud Front uses will be fine.
D) Use an ELB and a cross-zone ELB deployment to create redundancy across datacenters. Even if a region fails, the other AZ will stay online.