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.

Practice

1. What is the main purpose of adding tags to AWS resources for cost tracking?

easy

A. To organize and identify resources for cost allocation

B. To increase the storage capacity of resources

C. To improve the speed of resource deployment

D. To automatically back up resources daily

Solution

1. Step 1: Understand the role of tags in AWS

   Tags are labels that help organize resources by adding key-value pairs.

2. Step 2: Connect tags to cost tracking

   Tags allow grouping resources to see costs clearly in reports.

3. Final Answer:

   To organize and identify resources for cost allocation -> Option A

4. Quick Check:

   Tags help track costs [OK]

Hint: Tags label resources to track costs easily [OK]

Common Mistakes:

• Thinking tags increase storage or speed
• Confusing tags with backups
• Assuming tags change resource performance

2. Which of the following is the correct syntax to add a tag with key Environment and value Production to an AWS EC2 instance using AWS CLI?

easy

A. aws ec2 tag-instance --id i-1234567890abcdef0 --key Environment --value Production

B. aws ec2 create-tags --resources i-1234567890abcdef0 --tags Key=Environment,Value=Production

C. aws ec2 add-tag --instance i-1234567890abcdef0 --tag Environment=Production

D. aws ec2 set-tags --resource i-1234567890abcdef0 --tags Environment:Production

Solution

1. Step 1: Recall AWS CLI command for tagging

   The correct command is aws ec2 create-tags with resource ID and tags specified as Key=Value pairs.

2. Step 2: Match syntax with options

   aws ec2 create-tags --resources i-1234567890abcdef0 --tags Key=Environment,Value=Production matches the correct syntax exactly.

3. Final Answer:

   aws ec2 create-tags --resources i-1234567890abcdef0 --tags Key=Environment,Value=Production -> Option B

4. Quick Check:

   Correct AWS CLI tag syntax [OK]

Hint: Use 'create-tags' with Key= and Value= pairs [OK]

Common Mistakes:

• Using wrong command names like add-tag or tag-instance
• Incorrect tag format without Key= and Value=
• Mixing resource and instance flags

3. Given the following AWS CLI command, what will be the effect?

aws ec2 create-tags --resources i-0abcd1234efgh5678 --tags Key=Project,Value=Alpha Key=Owner,Value=TeamA

medium

A. The instance will have two tags: Project=Alpha and Owner=TeamA

B. The command will fail due to multiple tags in one command

C. Only the last tag Owner=TeamA will be applied

D. The tags will overwrite existing tags on the instance

Solution

1. Step 1: Understand AWS CLI tagging with multiple tags

   The create-tags command supports multiple tags by repeating the Key=Value pairs.

2. Step 2: Analyze the command effect

   Both tags Project=Alpha and Owner=TeamA will be added to the instance.

3. Final Answer:

   The instance will have two tags: Project=Alpha and Owner=TeamA -> Option A

4. Quick Check:

   Multiple tags added together [OK]

Hint: Multiple tags can be added by repeating Key=Value pairs [OK]

Common Mistakes:

• Assuming only one tag can be added at a time
• Thinking the command fails with multiple tags
• Believing tags overwrite all existing tags

4. You tried to tag an AWS S3 bucket using this command:

aws s3api put-bucket-tagging --bucket my-bucket --tags Key=Environment,Value=Dev

But it failed. What is the likely error?

medium

A. S3 buckets cannot be tagged

B. The bucket name is invalid

C. The command should be run with root user only

D. The --tags parameter is missing the required JSON format

Solution

1. Step 1: Check S3 tagging command syntax

   The put-bucket-tagging command requires tags in JSON format under the --tagging parameter, not --tags.

2. Step 2: Identify the error cause

   Using --tags with Key=Value string causes syntax error; correct usage is JSON with --tagging.

3. Final Answer:

   The --tags parameter is missing the required JSON format -> Option D

4. Quick Check:

   S3 tagging needs JSON format [OK]

Hint: Use JSON format with --tagging for S3 bucket tags [OK]

Common Mistakes:

• Using --tags instead of --tagging with JSON
• Assuming only root user can tag buckets
• Believing S3 buckets cannot be tagged

5. You want to track costs for multiple projects in your AWS account. Which tagging strategy will give the clearest cost reports?

hard

A. Tag only the resources with the highest cost

B. Use different tag keys like Project1, Project2 for each project

C. Use a single tag key Project with unique values for each project on all resources

D. Use tags only on EC2 instances, ignoring other resources

Solution

1. Step 1: Understand best practice for cost tracking tags

   Using one consistent tag key with different values groups costs clearly by that key.

2. Step 2: Evaluate options for clarity

   Use a single tag key Project with unique values for each project on all resources uses a single key Project with unique values, making reports easy to filter and compare.

3. Final Answer:

   Use a single tag key Project with unique values for each project on all resources -> Option C

4. Quick Check:

   Consistent tag keys for clear cost reports [OK]

Hint: Use one tag key with different values for projects [OK]

Common Mistakes:

• Using multiple tag keys for similar data
• Tagging only some resources
• Ignoring tags on non-EC2 resources