Five situations. For each one, name the ECO domain that owns it: I, II, III, IV or V. No task titles needed. Ten seconds each. This one is for everyone who has asked whether you need to memorise all 37 task titles. You don't need them word for word. You need to recognise who owns the work from the verb and the purpose in the situation. Let's test that. Q1. The data scientist has finished cleaning and feature engineering. Before any training starts, the AI project professional validates the transformation results and decides whether the data is ready for model development. Q2. The data science team needs compute for training, a secure development environment and a version control system. The AI project professional coordinates getting all three in place. Q3. The model has been evaluated against the agreed success criteria. The sponsor now wants the final approval decision on whether it can be deployed. Q4. The AI project professional keeps a record of every model development decision, who approved each go/no-go point, and the chain of custody for the training and test data, so an external regulator can later reconstruct how the system was built. Q5. Before anything is built, the team compares the proposed AI approach against a conventional rules-based alternative and checks whether the organisation has the computing resources and the readiness to support it. HOW TO PLAY Reply in one line, like this: Q1 ?, Q2 ?, Q3 ?, Q4 ?, Q5 ? A numeral can be the answer more than once, or not at all. Then open the first comment for the answer key, check yourself, and vote your score in the poll below. Got 5 out of 5? Tell us which one nearly caught you.

Straight exam-prep advice today, for anyone with a date on the calendar. First. Study by domain weight, not by comfort. The published split (ECO September 2025, p.5): Domain I 15%, Domain II 26%, Domain III 26%, Domain IV 16%, Domain V 17%. Domains II and III together are 52% of the exam, decided before a model ever exists. If your remaining study hours are going mostly into model development, you are polishing the domain worth the least. Second. Every task title has a verb, and the verb is the trap. Oversee, verify, manage, convey, coordinate. Almost none of them are build or code. When an answer option has the AI project professional doing the technical work personally instead of overseeing the person who does, that option is usually wrong, however correct the technical content sounds. Third. Learn to name the artefact, not just the phase. For any situational item, ask what document or deliverable should already exist at this point in the story: a deployment plan, a documented fallback, a go/no-go decision recorded on evaluation evidence, a handover with named owners. If the scenario describes something missing, the task that should have produced that missing artefact is usually your answer. Fourth. Know where the six go/no-go gates sit, and which direction a No-Go sends you. A No-Go does not end the project. It returns you to the phase that owns the missing input. The exam tests whether you know which phase that is, not whether you know the concept exists. Fifth, exam-day mechanics, verified against the ECO. 120 questions, 100 scored. The other 20 are unscored pretest items placed randomly, and you cannot tell which is which, so treat every question the same. 160 minutes total, no scheduled breaks, roughly 80 seconds per question at a flat pace. The 15-minute tutorial and the closing survey do not count against that time. If a situational item is past 90 seconds and you are still rereading the stem, mark it and move on. Come back at the end with whatever time is left.