Exam AWS DevOps Engineer Professional topic 1 question 21 discussion

D - there is nothing like Fargate AutoScaling group - this is serverless approach

I'll go with A) Creating a Docker image of these very customized applications is always a good idea Creating a docker image with all necessary apps, data e customizations attend the requirements B, C and D doesn't mention the required customizations of app versions or OS changes. None of them mention an AMI creation

can't be D because if you install system dependencies using appspec.yml they won't be present when new instance is added to ASG target group B is maybe technically possible to reinstall major dependencies using .ebextensions but it's terrible A is great option, but there is a typo i guess with auto scaling group

Only ECS , follow all the conditional laid in the question

I will go with D since Fargate wont give you much more flexibility to configure those OS level params

It is A, for those questioning how to do parameter tuning for OS, you can do it via the task definition for ECS Fargate, also about Autoscaling you create an Autoscaling group and associate it with your managed Fargate service.

A is the correct answer. As the apps require specific versions fof Tomcat, HAProxy and Varnish Cache, a devops engineer can create docker images based on specific version of their respective images from dockerhub or any other repo then configure environment variables / CMDs that need to be run at the startup of every container. Fargate can be used to launch those containers in a serverless way and any failing container for the above servers can be replaced automatically.

D looks like correct

A is incorrect since OS level parameters can not be done in ECS Fargate, If it was EC2 ECS then we could change the parameters

I will go with A, when we have different application ECS is the best solution

B. Upload the application code to an AWS CodeCommit repository with a saved configuration file to configure and install the software. Create an AWS Elastic Beanstalk web server tier and a load-balanced type environment that uses the Tomcat solution stack. Create an AWS CodePipeline pipeline that uses CodeCommit as a source and Elastic Beanstalk as a deployment provider. This solution provides the necessary level of control to configure the application's operating system-level parameters, as well as the ability to use specific versions of Apache Tomcat, HAProxy, and Varnish Cache. The solution also includes automated deployment of new versions through the use of AWS CodePipeline and scalability through the use of AWS Elastic Beanstalk and its ability to automatically replace faulty instances.

I'll go with D

A is excluded, AWS Fargate launch does not meet requirement, because the application will be migrated from on premises to AWS B and C highlight only Tomcat solution stack. I do not understand why.

Correct answer is D. Key is automated scaling and ability to replace faulty instances with a new one. Only a combination of CodeDeploy and Autoscaling group for EC2 as the target will satisfy this requirement.

D for sure

A - Not good to contain all software in one container. B - Not supporting all servers. C - Same as above. D - Can configure multiple servers including OS level tuning, ASG, Code Deploy. Fulfilling all key requirements.

The application's operating system-level parameters require tuning. >EC2 The solution must include a way to automate the deployment of new application versions. >CodePipeline The infrastructure should be scalable and faulty servers should be replaced automatically. >ASG