AWS Certified SysOps Administrator – Associate — Question 26
A company recently acquired another corporation and all of that corporation's AWS accounts. A financial analyst needs the cost data from these accounts. A
SysOps administrator uses Cost Explorer to generate cost and usage reports. The SysOps administrator notices that "No Tagkey" represents 20% of the monthly cost.
What should the SysOps administrator do to tag the "No Tagkey" resources?
Answer options
- A. Add the accounts to AWS Organizations. Use a service control policy (SCP) to tag all the untagged resources.
- B. Use an AWS Config rule to find the untagged resources. Set the remediation action to terminate the resources.
- C. Use Cost Explorer to find and tag all the untagged resources.
- D. Use Tag Editor to find and tag all the untagged resources.
Correct answer: D
Explanation
The correct answer is D, as Tag Editor is specifically designed for managing and applying tags across AWS resources. Options A and B involve broader account management and resource termination, which do not directly address the tagging of untagged resources. Option C suggests using Cost Explorer for tagging, but Cost Explorer is primarily for reporting, not tagging.