A misconfigured cost-allocation tag bills one department's cloud service to another
Given a scenario, optimize cloud environments.
AnswerCorrect answer: D — Chargeback allocates spend by resource tags, so a service tagged with the wrong department bills HR for another department's cloud service.
The human resources department was charged for a cloud service that belongs to another department. All other cloud costs seem to be correct. Which of the following is the most likely cause for this error?
100% of anonymous learners picked answer D.
Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
One department charged for one service, with everything else correct, is the signature of a tagging error on that resource, not a systemic chargeback configuration fault.
HR was charged for a cloud service belonging to another department while all other costs look correct. Chargeback systems allocate spend by resource tags, so a single service tagged with the wrong department value lands its entire bill on the wrong cost center.
Misconfigured chargeback (B) would misallocate costs broadly across many services and departments, but the scenario shows exactly one isolated misassignment.
Community Discussion (4 comments)
BigM👍 1Selected: D
Misconfigured tags
BlueMan93👍 1Selected: B
Chargebacks help to divide up usage among departments for cost and billing.
Joshuac1392👍 4Selected: D
D. Misconfigured tags Misconfigured tags are the most likely cause for the error described. Tags are metadata assigned to cloud resources to categorize and organize them, often used for cost allocation and management purposes. If the cloud service belonging to the human resources department was not properly tagged or was tagged incorrectly, the chargeback system may attribute the costs to the wrong department.
Joshuac1392👍 1
oops accidentally posted the question.
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Log in to comment, report an error, or add a note about this question.
Expert Analysis
Why the Answer Is Correct
Chargeback reporting in the cloud groups costs by metadata tags such as department or cost center, and the bill for each resource follows whatever tag value it carries. A service belonging to another department that appears on HR's invoice is the direct result of that resource carrying HR's tag, either set wrongly at creation or inherited from a template. The isolation of the error to one service, with all other costs correct, confirms the fault is in that resource's metadata rather than in the billing pipeline.
Why the Other Options Are Wrong
A, misconfigured templates, would stamp the wrong tag onto every resource created from the affected template, producing a pattern of errors rather than one. B, misconfigured chargeback, would distort allocations across the whole estate, not single out one service on one department's bill. C, security groups, filter network traffic by rules and have no involvement whatsoever in cost accounting or billing attribution.
Community Comment Notes
Joshuac1392 explains that tags are the metadata chargeback systems use to categorize and allocate costs, so a wrongly tagged resource bills to the wrong department. BlueMan93 argues for B by defining chargeback as the mechanism that divides usage among departments, but that definition actually supports D, since the mechanism fails only when the tag feeding it is wrong. The overwhelming vote backs D.