A bank has adopted a strict IT process to deploy new software releases.
It uses AWS CodeDeploy to manage several deployment stages including Feature Test, System Integration Test and Production.
Each stage has a Deployment Group in CodeDeploy.
And relevant targets are added into each group using Tags.
For example, the servers that contain the Production tag will only be deployed when a new deployment is created for the Production Deployment Group.
Which targets can NOT be added to Deployment Group by Tags or list in AWS CodeDeploy? (Select TWO.)
Click on the arrows to vote for the correct answer
A. B. C. D. E.Correct Answer - A.
C.
While creating Deployment Group In CodeDeploy, users can select the targets via Tags and lists.
The targets can be any combination of Amazon EC2 Auto Scaling groups, Amazon EC2 instances or On-premises instances:
Option A, C are CORRECT: Because ECS Cluster or Lambda can not be selected via Tags.
Options B, D, E are incorrect: Refer to the above explanations.
On-premises instances are supported for certain operating systems.
Refer to.
https://docs.aws.amazon.com/codedeploy/latest/userguide/codedeploy-agent.html#codedeploy-agent-supported-operating-systems.In AWS CodeDeploy, targets can be added to a Deployment Group using tags or a list. However, some targets may not be eligible to be added to a Deployment Group in this manner. The question asks for the two targets that cannot be added to a Deployment Group using tags or a list.
Here is an explanation of each option:
A. ECS Cluster with an Amazon Linux AMI: An Elastic Container Service (ECS) cluster is a group of container instances that run Docker containers. It is possible to deploy a new version of a container to an ECS cluster using CodeDeploy. However, this option refers specifically to an ECS cluster with an Amazon Linux AMI. It is unclear what the context of this option is, but it is not relevant to the question at hand.
B. EC2 Auto Scaling groups: Auto Scaling groups allow users to automatically adjust the number of EC2 instances running to match demand. CodeDeploy can be used to deploy new code to instances in an Auto Scaling group. This option seems like a plausible answer, as it is possible to add Auto Scaling groups to a Deployment Group using tags. However, this option is incorrect. Auto Scaling groups can indeed be added to a Deployment Group using tags or a list.
C. Lambda function written in Python 3.6: AWS Lambda is a serverless compute service that allows users to run code without provisioning or managing servers. CodeDeploy can be used to deploy new versions of Lambda functions. This option is also a plausible answer, as it is possible to add Lambda functions to a Deployment Group using tags. However, this option is incorrect. Lambda functions can indeed be added to a Deployment Group using tags or a list.
D. EC2 instance (Microsoft Windows Server 2016): An EC2 instance is a virtual server in the AWS cloud. This option refers specifically to an EC2 instance running Microsoft Windows Server 2016. It is possible to deploy new code to an EC2 instance running Windows Server using CodeDeploy. However, this option is correct. Windows Server instances cannot be added to a Deployment Group using tags or a list.
E. Red Hat Enterprise Linux (RHEL) on-premises instances: RHEL on-premises instances are EC2 instances that are not running in the AWS cloud, but rather on-premises (i.e., in a customer's data center). It is possible to deploy new code to on-premises instances using CodeDeploy. However, this option is correct. On-premises instances cannot be added to a Deployment Group using tags or a list.
Therefore, the correct answers are D and E.