Three parts. Eighty questions on the ideas, five tickets to triage, and three written answers. Allow about ninety minutes. There is no clock, and your place is saved as you go, so you can stop and come back to it.
Eighty questions, one at a time, with the answer explained straight after. For each one you also say whether you are sure or unsure. Being confidently wrong is tracked separately, because it is the thing that actually costs on a live desk.
Five real shaped tickets. You judge the type, the impact and the urgency. The priority is calculated from what you chose, never picked directly.
Three questions in your own words. Afterwards you see a model answer and mark your own against it, point by point. Marking yourself honestly is part of the exercise.
The mock is timed, and the hour runs on the clock rather than on the tab. Close it, come back inside the hour and you carry on where you stopped; come back after it and the paper is marked as it stands. Start it when you have the hour. It is the shape of the real ITIL 4 Foundation exam: forty questions, sixty minutes, closed book, sixty five percent to pass. No feedback until the end, and a different paper every time. It draws only from the questions that sit on the Foundation syllabus, so the version history and the Jahez desk practice in part one are deliberately left out of it.
The week 1 paper is fifteen questions on workplace and professional skills, twenty minutes, seventy percent to pass. It is drawn from a bank of thirty, with a quota on each of the five outcomes the week names, so no sitting can skip one. Same clock rule as the mock.
The week 4 paper is twenty questions on data gathering and the asset register, thirty minutes, seventy percent to pass. It is marked and it counts, the same as everything else here. Same clock rule as the mock: it runs whether the tab is open or not.
The week 5 paper is twenty questions on preparing and structuring a dataset, thirty minutes, seventy percent to pass. It is drawn from a bank of fifty, with a quota on each of the five outcomes the week names, so no sitting can skip one and two interns do not get the same twenty. Same clock rule again.
The week 6 paper is twenty questions on data visualization and insight communication, thirty minutes, seventy percent to pass. It is drawn from a bank of forty five, with a quota on each of the five outcomes the week names, so no sitting can skip one. Same clock rule again.
The week 7 paper is twenty questions on cloud fundamentals and least privilege, thirty minutes, seventy percent to pass. It is drawn from a bank of seventy two, with a quota on each of the five outcomes the week 7 deck names, so no sitting can skip one. Same clock rule again.
The week 8 paper is twenty questions on cloud hosting and web foundations, thirty minutes, seventy percent to pass. It is drawn from a bank of fifty five, with a quota on each of the five outcomes the Hosting Path teaches, so no sitting can skip one. Same clock rule again.
The week 9 paper is twenty questions on applied data analysis, all about the week 9 practice dataset of delivery orders, thirty minutes, seventy percent to pass. It is drawn from a bank of fifty five, with a quota on each of its five outcomes, so no sitting can skip one. Same clock rule again.
The week 10 paper is fifteen questions on presenting an analysis: one page for one question, honest titles and axes, the five minute story, peer feedback and looking back at the method, twenty minutes, seventy percent to pass. It is drawn from a bank of thirty, with a quota on each of its five outcomes, so no sitting can skip one. Same clock rule again.
The week 12 paper is fifteen questions on Power Platform: the platform map and what a Microsoft 365 license covers, canvas or model-driven, data sources and delegation, screens, forms and formulas, and good and bad use cases, twenty minutes, seventy percent to pass. It is drawn from a bank of thirty, with a quota on each of its five outcomes, so no sitting can skip one. Same clock rule again.
The week 11 paper is fifteen questions on cybersecurity controls and compliance: reading an NCA control, identity and access, protecting the estate, the cloud tenant's own controls and real incidents, twenty minutes, seventy percent to pass. It is drawn from a bank of thirty, with a quota on each of its five outcomes, so no sitting can skip one. Same clock rule again.