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…

Question

Options

• AUse Organizations tag policies to enforce mandatory tagging on all resources. Enable cost
• BConfigure AWS CloudTrail events to invoke an AWS Lambda function to detect untagged
• CUse AWS Config to evaluate tagging compliance. Use AWS Budgets to apply tags for cost
• DUse AWS Service Catalog to provision only pre-tagged resources. Use AWS Trusted Advisor to

• A
  79% (19)
• B
  4% (1)
• C
  13% (3)
• D
  4% (1)

Explanation

Tagging is essential for governance, cost management, and automation in CloudOps operations. The AWS Organizations tag policies feature allows centralized definition and enforcement of required tag keys and accepted values across all accounts in an organization. According to the AWS CloudOps study guide under Deployment, Provisioning, and Automation, tag policies enable automatic validation of tags, ensuring consistency with minimal manual overhead. Once tagging consistency is enforced, enabling cost allocation tags in the AWS Billing and Cost Management console allows accurate cost distribution per business unit. "Use AWS Organizations tag policies to standardize tags across accounts. You can activate cost allocation tags in the Billing console to track and allocate costs." Option B introduces unnecessary complexity with Lambda automation. Option C detects but does not enforce tagging. Option D limits flexibility to Service Catalog resources only. Therefore, Option A provides a centrally managed, automated, and low-overhead solution that meets CloudOps tagging and cost-tracking requirements.

No community discussion yet for this question.