3.3Standard
A new model harms safety and latency.
Return to the stable version.
Choose two practices.
× Incorrect
Route traffic to the old version after checking prompt, index, dependency, and permission compatibility, then record impact and cause.
Detailed explanation
CorrectRoute traffic to the old model and check prompt, index, dependency, and permission compatibility
The return is coherent.
IncorrectDo not record the cause after rollback
The issue can recur.
CorrectRecord impact, decision, data, old version, recovery time, and reassess after fixing cause
Recovery is explainable.
IncorrectSwitch only the model without checking dependencies
A second failure can result.
Check official documentation
Compare the following points with the official documentation.
AWS公式AIF-C01 Domain 3.3のロールバック、依存関係、変更管理を確認する。
Official references
What to confirm
旧版へ戻した後の設定・索引・権限を含めてサービスを安定化できる。
Key points
- Rollback
- Compatibility
- Cause
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
Rollback
Returning traffic or configuration to a previously approved implementation.
Compatibility
The ability of connected data, prompts, indexes, and permissions to work together.
Question IDAWS-AIF-526
EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
Last technical review2026-08-20
Report an error or rights issue