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.)

Answer options:

A.ECS Cluster with an Amazon Linux AMI
B.EC2 Auto Scaling groups
C.Lambda function written in Python 3.6
D.EC2 instance (Microsoft Windows Server 2016)
E.Red Hat Enterprise Linux (RHEL) on-premises instances

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.