Separating provider SLA from measurements | AWS Certified AI Practitioner (AIF-C01) original practice question

3.3Standard

A provider publishes an SLA.

Also protect user experience.

Choose two evaluations.

Hint 1: Focus on the requirement

Identify what must change and what must remain unchanged. Then choose the command whose scope matches that requirement.

Hint 2: Check each command's role

Separate commands that display information, change state, remove data, or affect a child process.

提供者のSLA範囲・除外・測定方法と、自社のp95遅延・エラー・品質を別に管理する: Responsibilities are separated.
依存障害・クォータ・フォールバック・連絡先・復旧手順をテストする: SLA gaps are covered.
提供者SLAを満たせば自社のUXと生成品質も保証される: Your path has other conditions.
SLAの数字だけで容量計画を決め、実測を取らない: Actual distributions are unknown.

Detailed explanation

CorrectReview provider SLA scope and exclusions separately from your p95, error, and quality metrics

Responsibilities are separated.

CorrectTest dependency failures, quota, fallback, contacts, and recovery procedures

SLA gaps are covered.

IncorrectMeeting provider SLA guarantees your UX and generation quality

Your path has other conditions.

IncorrectPlan capacity only from SLA numbers without measurements

Actual distributions are unknown.

An example you can run in a temporary verification environment.

AWS公式AIF-C01 Domain 3.3のSLA、依存関係、監視、フォールバックを確認する。

契約上のSLAと利用者向けの実性能を混同せず、依存障害への備えを設計できる。

Foundation review

Check whether the command acts on the current shell, a new process, an existing process, or a file.

Use the supplied command and compare the output with the expected result.

Question IDAWS-AIF-499

EnvironmentAWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認

Last technical review2026-08-20