To optimize token throughput for a high-traffic chatbot, you decide to enable 'Provisioned Throughput' for your Azure OpenAI deployment. What must you consider?
Trap 1: It can only be used with models deployed in the 'East US' region.
PTUs are available in multiple regions.
Trap 2: It automatically scales the number of tokens based on CPU usage.
PTUs are fixed capacity; they do not auto-scale like standard tiers.
Trap 3: Check the 'Quota' tab in the Azure Portal.
Quota tracks limits, not actual consumption.
- A
It can only be used with models deployed in the 'East US' region.
Why wrong: PTUs are available in multiple regions.
- B
It automatically scales the number of tokens based on CPU usage.
Why wrong: PTUs are fixed capacity; they do not auto-scale like standard tiers.
- C
Use 'Azure Monitor' to view the 'Tokens Per Minute' metric.
This is the correct metric to track model usage.
- D
Check the 'Quota' tab in the Azure Portal.
Why wrong: Quota tracks limits, not actual consumption.
- E
Enable 'Diagnostic Settings' for the Azure AI resource.
Why wrong: Diagnostic settings export logs but don't provide real-time monitoring graphs.
- F
It requires a 'Reserved Capacity' purchase for the entire deployment period.
PTUs involve reserving capacity to guarantee performance.
- G
It is incompatible with 'Streaming' requests.
Why wrong: PTUs support streaming just like standard deployments.
- H
Query the 'ModelUsage' table in Log Analytics.
Why wrong: This is an indirect way to calculate usage, not a native monitor metric.