3.3Standard
Longer answers improve some quality scores but increase delay.
Select a configuration for service requirements.
Choose two appropriate practices.
× Incorrect
Compare quality, p95 latency, and token cost on the same set and use a safety fallback when high-impact cases fail requirements.
Detailed explanation
CorrectCompare quality, p95 latency, and token cost under the same test conditions
Configurations can be compared fairly.
IncorrectUse mean latency to claim a p95 target
Tail latency can remain too high.
IncorrectIgnore latency and cost for a small quality increase
User experience and SLO may fail.
CorrectEvaluate safety cases separately and fall back when a threshold is missed
Speed improvements must not remove safety.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 3.3・3.4の品質・レイテンシ・費用評価を確認する。
Official references
What to confirm
品質・遅延・費用・安全性の複数基準で設定を選べる。
Key points
- p95
- SLO
- Fallback
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
Quality-latency trade-off
A relationship in which additional processing can improve output while increasing time or cost.
p95 latency
The response time below which 95 percent of measured requests complete.
Question IDAWS-AIF-185
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue