What should the SysOps administrator do to tag the "No Tagkey" resources?

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?
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 taq all the untaqqed resources.

View Answer

Answer: D

Explanation:

"You can add tags to resources when you create the resource. You can use the resource’s service console or API to add, change, or remove those tags one resource at a time. To add tags to―or edit or delete tags of―multiple resources at once, use Tag Editor. With Tag Editor, you search for the resources that you want to tag, and then manage tags for the resources in your search results." https://docs.aws.amazon.com/ARG/latest/userguide/tag-editor.html