Q: 3
A CloudOps engineer needs to ensure that AWS resources across multiple AWS accounts are tagged
consistently. The company uses an organization in AWS Organizations to centrally manage the
accounts. The company wants to implement cost allocation tags to accurately track the costs that are
allocated to each business unit.
Which solution will meet these requirements with the LEAST operational overhead?
Options
Discussion
Option A
B
Hmm, I actually went for B. Tagging with Lambda seems less of a trap than D, but maybe I'm missing something with tag policies?
A unless they specifically ask about fixing existing untagged resources, then maybe B. For just consistent tag enforcement org-wide and least admin pain, it's A.
A or B, but for SOA-C03 exams most recent reports point to A as the official answer. Tag policies via Organizations handle tagging across accounts with way less work than Lambda solutions. If you're following exam patterns, I'd stick with A.
Had something like this in a mock, and A was the pick there. Tag policies with Organizations scale better than Lambda or Config for cross-account tagging rules. Pretty sure about A, unless existing untagged resources are the main concern. Agree?
B tbh, Lambda for auto tagging sounds right but I think it's a bit of a trap here.
Its A since tag policies in AWS Organizations let you enforce tagging standards across all linked accounts with way less manual effort. Cost allocation tags can just be enabled in billing after. Pretty sure that's the easiest path, but open to other ideas.
This looks like one from my exam last year, in some practice sets before, and it's A. Tag policies in Organizations are the only way to consistently enforce required tags across accounts with barely any manual work, plus cost allocation tags get enabled centrally. If they asked about cleaning up existing untagged resources, that's trickier, but here it's about ongoing consistency. Pretty sure on this one.
Why is this so convoluted? B or maybe D, AWS always overcomplicates tagging.
Be respectful. No spam.