What should the SysOps administrator do to meet this requirement?
Activate the tags as AWS generated cost allocation tags.
Activate the tags as user-defined cost allocation tags.
Create a new cost category. Select the account billing dimension.
Create a new AWS Cost and Usage Report. Include the resource IDs.
Explanations:
AWS generated cost allocation tags are predefined tags created by AWS for certain resources, not company-defined tags. Therefore, activating them won’t display company-defined tags on the billing report.
User-defined cost allocation tags allow users to assign their own custom tags to resources. Once these tags are activated, they will appear on the billing report. This is the correct solution.
Creating a cost category allows you to organize and categorize your costs, but it does not relate to displaying company-defined tags on the billing report. Cost categories are for grouping costs, not for managing tags.
While a new AWS Cost and Usage Report can help in managing costs, it does not automatically include custom tags unless they are activated as cost allocation tags. This option alone will not ensure that company-defined tags appear on the billing report.
I rate that the answer is:
Activate the tags as user-defined cost allocation tags.