Domain 1 of 6

Failure Modes in Deployed Systems

The failure modes a product team meets rather than the ones papers are written about. Hallucination, bias, injection, misuse and the quiet one, which is people trusting output further than it deserves.

Concepts

~18%

Of the exam

Practice questions

Concepts in this domain

01How AI features failThe ways an AI feature goes wrong in production, ordered by how often a product team actually meets them rather than by how much has been written about each.02Over reliance and automation biasWhy people accept output they should have checked, why it gets worse as the system gets better, and what a product can do about it.03What generative AI is good and bad atThe capabilities worth building on, the failure modes that are properties of the technology rather than bugs, and how to tell a suitable problem from an unsuitable one.04Responsible AI in practiceBias, fairness, robustness, safety and veracity treated as things you can measure and act on, plus the legal exposure that arrives with generative output.

Try a question from this domain

A support assistant has been live for four months. Usage is steady, no incidents have been raised, and nobody has measured answer quality since launch. The team reports the feature as healthy. What is the strongest objection?

AFour months is too short a period to draw any conclusion about quality.
BThe absence of complaints is weak evidence, because most people who receive a poor answer stop using the feature rather than reporting it.
CUsage should be falling if the feature is working, since it resolves issues.
DQuality cannot be measured after launch without a control group.

9 questions on this domain.

One per page, with a worked explanation.

Start the set