exam questions

Exam AWS Certified DevOps Engineer - Professional DOP-C02 All Questions

View all questions & answers for the AWS Certified DevOps Engineer - Professional DOP-C02 exam

Exam AWS Certified DevOps Engineer - Professional DOP-C02 topic 1 question 204 discussion

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?

  • A. Change the current single tag group to include only the Environment=Production tag. Add another single tag group that includes only the Name=ApplicationA tag.
  • B. Change the current single tag group to include the Department=Marketing, Environment=production, and Name=ApplicationA tags.
  • C. Add another single tag group that includes only the Department=Marketing tag. Keep the Environment=Production and Name=ApplicationA tags with the current single tag group.
  • D. Change the current single tag group to include only the Environment=Production tag. Add another single tag group that includes only the Department=Marketing tag.
Show Suggested Answer Hide Answer
Suggested Answer: A 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
thanhnv142
Highly Voted 1 year, 2 months ago
Selected Answer: A
A is correct: All tags in one tag group are OR operator. Tags are in multiple tag groups are AND operator
upvoted 9 times
...
Gomer
Highly Voted 9 months, 2 weeks ago
Selected Answer: 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
upvoted 6 times
Gomer
9 months, 2 weeks ago
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)
upvoted 2 times
...
...
Srikantha
Most Recent 2 weeks, 6 days ago
Selected Answer: B
Option B is the most effective solution, as it specifies that the deployment group should only target instances that have all three tags (Department=Marketing, Environment=Production, and Name=ApplicationA). This ensures that only instances specifically meant for ApplicationA are selected for the deployment, preventing unwanted instances (like those with Name=ApplicationB) from receiving the application.
upvoted 1 times
...
youonebe
3 months, 3 weeks ago
Selected Answer: A
This is a very tricky question, even ChatGPT can't get it right, a good one! Make sure to go through this AWS doc first and fully understand it. https://docs.aws.amazon.com/codedeploy/latest/userguide/instances-tagging.html First thing first, why ApplicationA was installed on the new EC2 instance? Reason is <single tag group, multiple tags> was used. The <Environment> and <Name> tags are both defined within this tag group. So as long as the EC2 instance has one tag matched, ApplicationA would be deployed. In this case, the new EC2 instance has <Environment=Production> tag, so ApplicationA got deployed.
upvoted 2 times
youonebe
3 months, 3 weeks ago
Now we look at the choices one by one: A. [Correct]This updates the current tag group, add a new tag group. Which means BOTH tags need to match before ApplicationA gets deployed. For the new EC2 instance, because Name=ApplicationB, hence preventing the mistake from happening. B. [Wrong] This will be very similar to the original configuration, as long as one of the 3 tags matches, ApplicationA will be deployed. This does not solve the problem. C. [Wrong] The company still needs to install ApplicationA to existing EC2 instances, adding"Department=Marketing will break the current workflow. D. [Wrong] The company still needs to install ApplicationA to existing EC2 instances, adding Department=Marketing will break the current workflow.
upvoted 1 times
...
...
DanShone
1 year, 1 month ago
Selected Answer: 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
upvoted 5 times
...
fdoxxx
1 year, 1 month ago
Selected Answer: 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
upvoted 1 times
...
Ramdi1
1 year, 2 months ago
Selected Answer: 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.
upvoted 5 times
Ramdi1
1 year, 2 months ago
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.
upvoted 1 times
...
...
Chelseajcole
1 year, 2 months ago
A. need to applicationA tag
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago