You are building a Docker image with the following Dockerfile. How many layers will the resulting image have?
FROM scratch
CMD /app/hello.sh

• A.2
• B.4
• C.1
• D.3

Comment: *

Name: *

Email: *

Verification: *

You have an asynchronous processing application using an Auto Scaling Group and an SQS Queue. The Auto Scaling Group scales according to the depth of the job queue. The completion velocity of the jobs has gone down, the Auto Scaling Group size has maxed out, but the inbound job velocity did not increase.
What is a possible issue?

• A.Some of the new jobs coming in are malformed and unprocessable.
• B.The routing tables changed and none of the workers can process events anymore.
• C.Someone changed the IAM Role Policy on the instances in the worker group and broke permissions to access the queue.
• D.The scaling metric is not functioning correctly.

Comment: *

Name: *

Email: *

Verification: *

Which of the following is not a supported platform for the Elastic beanstalk service

• A.Java
• B.AngularJS
• C.PHP
• D..Net

Correct Answer: B

Explanation

For more information on Elastic beanstalk, please visit the below URL:
* http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/concepts.platforms.htmI

Comment: *

Name: *

Email: *

Verification: *

Your application is currently running on Amazon EC2 instances behind a load balancer. Your management has decided to use a Blue/Green deployment strategy. How should you implement this for each deployment?

• A.Set up Amazon Route 53 health checks to fail over from any Amazon EC2 instance that is currently being deployed to.
• B.Using AWS CloudFormation, create a test stack for validating the code, and then deploy the code to each production Amazon EC2 instance.
• C.Create a new load balancer with new Amazon EC2 instances, carry out the deployment, and then switch DNS over to the new load balancer using Amazon Route 53 after testing.
• D.Launch more Amazon EC2 instances to ensure high availability, de-register each Amazon EC2 instance from the load balancer, upgrade it, and test it, and then register it again with the load balancer.

Correct Answer: C

Explanation
The below diagram shows how this can be done

1) First create a new ELB which will be used to point to the new production changes.
2) Use the Weighted Route policy for Route53 to distribute the traffic to the 2 ELB's based on a 80-20% traffic scenario. This is the normal case, the % can be changed based on the requirement.
3) Finally when all changes have been tested, Route53 can be set to 100% for the new ELB.
Option A is incorrect because this is a failover scenario and cannot be used for Blue green deployments. In Blue Green deployments, you need to have 2 environments running side by side.
Option B is incorrect, because you need to a have a production stack with the changes which will run side by side.
Option D is incorrect because this is not a blue green deployment scenario. You cannot control which users will go the new EC2 instances.
For more information on blue green deployments, please refer to the below document link: from AWS
* https://dOawsstatic.com/whitepapers/AWS_Blue_Green_Deployments.pdf

Comment: *

Name: *

Email: *

Verification: *

You are using Autoscaling for managing the instances in your AWS environment. You need to deploy a new version of your application. You'd prefer to use all new instances if possible, but you cannot have any downtime. You also don't want to swap any environment urls. Which of the following deployment methods would you implement

• A.Using "All at once" deployment method.
• B.Using "Blue Green" deployment method.
• C.Using"RollingUpdates"deploymentmethod.
• D.Using "Blue Green" with "All at once" deployment method.

Comment: *

Name: *

Email: *

Verification: *