A generative-AI app exceeds its monthly budget as usage grows.
Find the cause while maintaining quality.
Choose two appropriate monitoring activities.
Break cost into request count, input/output tokens, model price, and user or feature dimensions, and review it with quality metrics.
Detailed explanation
Allocation shows which paths consume the budget.
Cost changes must not silently damage quality or safety.
This identifies usage drivers that affect cost.
Limits may help, but measurement is needed to understand the cause.
Check official documentation
Compare the following points with the official documentation.
Amazon Bedrock公式料金とAWSコスト管理・CloudWatchの監視情報を確認する。
Official references
What to confirm
費用を利用量と単価へ分解し、品質を維持しながら改善する方法を説明できる。
Key points
- Tokens
- Usage
- Cost allocation
Notes
- Environment: AWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
- Compare the definition with the AIF-C01 objective and the service documentation before applying it.
- Keep the concept separate from a particular answer choice or implementation step.
Foundation review
Cost driver
Model choice, token volume, request volume, and supporting processing can each affect total spend.
Attribution
An account-wide total is less actionable when usage cannot be connected to a workload owner.