1. A FinOps analyst at Lamna Healthcare wants to implement cost tracking for multiple Azure OpenAI model deployments consumed by different business units. Each business unit should see its own token consumption and estimated cost in Azure AI Foundry. Which two mechanisms should be configured to support this requirement? (Select TWO)
- A. Use separate Azure AI Foundry projects per business unit and associate each project with its own Azure OpenAI deployment✓ Correct
- B. Tag Azure OpenAI deployments with business-unit cost center tags and use Azure Cost Management to filter spend by tag✓ Correct
- C. Configure a single shared deployment and use custom request headers to identify the business unit in each API call
- D. Enable token consumption metrics in Azure Monitor and create workbook views filtered by deployment name
- E. Set up a single Foundry hub with all deployments in one project and use role-based access control to restrict visibility
Explanation
Using separate Foundry projects per business unit provides natural isolation of token usage and cost data within the Foundry portal. Tagging deployments with cost center tags and filtering in Azure Cost Management is the standard FinOps practice for chargeback/showback across business units. Shared deployments with custom headers do not provide native per-unit cost breakdowns in Foundry or Cost Management. Azure Monitor workbooks can show metrics by deployment name but do not map to business-unit cost centers without tagging. Using a single project with RBAC restricts visibility but does not separate cost reporting.