Exam DOP-C02 All QuestionsBrowse all questions from this exam
Question 204

A company has an AWS CodeDeploy application. The application has a deployment group that uses a single tag group to identify instances for the deployment of Application. The single tag group configuration identifies instances that have Environment=Production and Name=ApplicationA tags for the deployment of ApplicationA.

The company launches an additional Amazon EC2 instance with Department=Marketing, Environment=Production, and Name=ApplicationB tags. On the next CodeDeploy deployment of Application, the additional instance has ApplicationA installed on it. A DevOps engineer needs to configure the existing deployment group to prevent ApplicationA from being installed on the additional instance.

Which solution will meet these requirements?

    Correct Answer: A

    The issue arises because the additional instance with tags Department=Marketing, Environment=Production, and Name=ApplicationB was incorrectly targeted due to an insufficiently specific tag group. The current single tag group uses Environment=Production and Name=ApplicationA tags for deployments, but this does not exclude instances with the tag Name=ApplicationB if they belong to the Production environment. To ensure precise targeting, the solution is to use multiple tag groups, which apply an AND operator between groups. The first tag group should include Environment=Production, which identifies instances in the desired environment. The second tag group should include Name=ApplicationA, which specifically targets instances intended for ApplicationA deployment. This configuration will prevent instances like the one from the Marketing department with Name=ApplicationB from being included in deployments unintentionally. Therefore, the correct approach is to change the current single tag group to include only the Environment=Production tag and add another single tag group that includes only the Name=ApplicationA tag.

Discussion
thanhnv142Option: A

A is correct: All tags in one tag group are OR operator. Tags are in multiple tag groups are AND operator

DanShoneOption: A

A: A single tag group can only contain 1 tag, so multiple Single tag groups will be needed. https://docs.aws.amazon.com/codedeploy/latest/userguide/instances-tagging.html

Ramdi1Option: A

A - Original configuration: The single tag group with Environment=Production and Name=ApplicationA tags targets any instance with both tags, resulting in ApplicationA being deployed on the new Marketing instance despite its different Name tag. Solution A: Changing the current tag group to "Environment=Production" ensures only instances in the Production environment are considered. Adding a separate tag group with "Name=ApplicationA" specifically targets instances meant for that application. The Marketing instance with Department=Marketing tag doesn't match the new criteria and avoids unintended ApplicationA installation.

Ramdi1

Reasons why other options won't work: B: Including Department=Marketing in the current tag group wouldn't change anything - all instances in Production with ApplicationA tag would be targeted. C: Adding a Department=Marketing tag group alone still leaves the original tag group targeting the Marketing instance due to the Name=ApplicationA tag. D: Removing Name=ApplicationA from the initial tag group removes a necessary criterion, potentially deploying ApplicationA to all Production instances regardless of their Name tag. Therefore, solution A provides the most precise and effective way to exclude the Marketing instance from ApplicationA deployment while maintaining the desired targeting for other instances.

GomerOption: A

I Found this question largely incomprehensible untill I understood the following concepts and mapped out everything - Single tag group: Any instance identified by at least one tag in the group is included in the deployment group. (OR Operator within individual tag groups) - Multiple tag groups: Instances that are identified by at least one tag in each of the tag groups are included. (AND Operator between multiple tag groups) https://docs.aws.amazon.com/codedeploy/latest/userguide/instances-tagging.html

Gomer

A:(YES) Block ApplicationA deployments on EC2B because it would now have to have both Production AND ApplicationA tags (AND Operator between tag groups) B: (NO) Allow ApplicationA deployments on EC2B because it has the Production tag (OR Operator within tag group) C: (NO) Allow ApplicationA deployments on EC2B because it has the Production and Marketing tags (OR Operator within tag group, AND Operator between tag groups) D: (NO) Allow ApplicationA deployments on EC2B because it has the Production and Marketing tags (OR Operator within tag group, AND Operator between tag groups)

fdoxxxOption: B

Option B is the most appropriate solution for meeting the requirements: Changing the current single tag group to include the specific tags (Department=Marketing, Environment=Production, and Name=ApplicationA) ensures that only instances with these specific tags are identified for the deployment of ApplicationA. The other options are not suitable for achieving the desired outcome

Chelseajcole

A. need to applicationA tag