Resource tagging for cost tracking in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use resource tags for cost tracking?

Which of the following best explains why tagging cloud resources helps with cost tracking?

A Tags allow grouping resources by purpose, making it easier to allocate costs to departments or projects.

B Tags automatically reduce the cost of resources by applying discounts.

C Tags prevent unauthorized users from accessing billing information.

D Tags increase the performance of cloud resources, lowering operational costs.

💡 Hint

Think about how tags help organize resources for billing.

Tags are labels that help identify and group resources. This grouping allows cost reports to show spending by department, project, or team.

❓ Configuration

intermediate

Identify the correct AWS CLI command to tag an EC2 instance

You want to add a tag with key Project and value Alpha to an EC2 instance with ID i-1234567890abcdef0. Which AWS CLI command will do this correctly?

A aws ec2 create-tags --resources i-1234567890abcdef0 --tags Key=Project,Value=Alpha

B aws ec2 tag-instance --instance-id i-1234567890abcdef0 --tag Project=Alpha

C aws ec2 add-tags --resource-id i-1234567890abcdef0 --tags Project=Alpha

D aws ec2 set-tags --instance i-1234567890abcdef0 --tags Key=Project,Value=Alpha

💡 Hint

Check the AWS CLI command syntax for tagging EC2 resources.

The correct command is create-tags with --resources and --tags parameters specifying key and value.

❓ Architecture

advanced

Designing a tagging strategy for multi-account AWS environment

You manage multiple AWS accounts for different business units. You want to ensure consistent cost tracking across all accounts using tags. Which approach is best?

A Disable tagging to avoid confusion and rely only on account-level billing.

B Allow each account to create its own tags independently without restrictions.

C Use random tag keys and values to allow flexibility for each team.

D Define a centralized tagging policy using AWS Organizations and enforce it with Service Control Policies (SCPs).

💡 Hint

Think about how to enforce consistent tagging across multiple accounts.

Using AWS Organizations with SCPs allows enforcing tagging policies centrally, ensuring consistent tags for cost tracking.

❓ security

advanced

Preventing unauthorized tag changes on AWS resources

How can you prevent users from changing or deleting cost tracking tags on AWS resources?

A Disable tagging feature in AWS account settings.

B Create IAM policies that deny <code>ec2:DeleteTags</code> and <code>ec2:CreateTags</code> actions except for specific tags.

C Allow all users full access to tags to encourage collaboration.

D Use AWS Config to automatically remove unauthorized tags after changes.

💡 Hint

Consider how IAM policies control permissions on tagging actions.

IAM policies can restrict who can create or delete tags, protecting important cost tracking tags from unauthorized changes.

❓ service_behavior

expert

Effect of missing mandatory cost allocation tags on AWS billing reports

Your company requires the tag CostCenter on all resources for billing. You forget to apply this tag on some resources. What will happen in AWS Cost Explorer reports?

A Resources without the tag will be excluded from billing and not charged.

B AWS will automatically assign a default <code>CostCenter</code> tag to untagged resources.

C Resources without the <code>CostCenter</code> tag will appear under the <code>Unallocated</code> category in cost reports.

D AWS will generate an error and stop billing until all resources have the tag.

💡 Hint

Think about how AWS handles untagged resources in cost allocation.

Untagged resources appear as Unallocated in cost reports, making it harder to track costs accurately.