Having received Go approval, the ramp-safety team moves into Data Understanding. What AI-specific question should they now prioritize that a traditional software project would not typically need to ask?
Select an answer to reveal the explanation.
Short Explanation
A traditional app doesn't need to ask if its data is "representative" — Data Understanding is where AI projects have to ask exactly that, or the model built on it won't hold up on a rainy Tuesday ramp shift.
Full Explanation
Entering Data Understanding, the team's central task is addressing AI-specific aspects of data understanding — chiefly, whether the available data is representative of real operating conditions, adequately and correctly labeled, and validated against ground truth, since these directly determine whether a model trained on it can generalize to production. This is a question a traditional software project simply doesn't need to ask, because traditional software doesn't learn behavior from data in the same way. Options A, B, and C are all legitimate project-management or engineering questions at some point, but none of them are unique to, or even particularly important for, an AI initiative specifically — a UI language choice, dashboard color scheme, or sprint staffing level apply equally to any software project and don't touch the AI-specific risk this phase exists to manage. The correct answer reflects the Domain II Task 3 enablers around identifying appropriate datasets, evaluating training-data requirements, and validating ground truth — the foundational work that determines whether the ramp-safety model built later in the lifecycle will actually be trustworthy once deployed.