Final review

The last session, on Tuesday, April 27, was the day before the exam. Priya, Rosa, Grace and Malik all came, Malik by video again, and the meeting room in Portland had a plate of oatcakes on the table. Priya had planned it in three parts: a one-page review of every area, a final set of mixed questions, and the exam-day checklist. "No new material today," she said. "Today is about seeing that you already know it." This lesson follows that plan. It ends with what happens after the exam, whatever the result, and with where the GitHub Foundations certification can lead.

The one-page review

Owen's one-page review had a box for each area, with the facts he most needed to recall and the confusable pairs from lesson 10. He wrote it himself from memory first, then checked it against his notes, which is retrieval practice in its simplest form. The table below is a cleaned-up version.

Writing the page from memory took Owen eighteen minutes, and checking it took five. He had missed only two items, the merge methods in collaboration and project templates in project management, and he added both in a different color so they would stand out on a last read the next morning. The value of the page is less the finished summary than the act of producing it: every item he could recall without looking was one he would recall in the exam.

A final mixed set

Priya read ten mixed questions aloud, one from each area and three on confusable pairs, and Owen answered each with a reason, as he would think it through in the exam. Seven of them are worked here, because the reasoning matters more than the answers.

Owen answered all ten correctly, and, more importantly, gave the right reason each time. Rosa pointed out that he had stopped hesitating on the pairs that had cost him marks a week before, which was the real measure of readiness.

The exam-day checklist

Grace, who runs the print schedule and does not trust memory for anything important, turned the logistics into a checklist. Owen printed it and put it by his door.

At a test center the checklist is similar, with travel instead of a system test: plan to arrive early, bring the right ID, and expect to store belongings in a locker. Either way, the aim is the same: nothing about the day should require a decision.

In the exam

The last part of the session was a short list of rules for the 100 minutes, each one drawn from lessons 2 and 10. Owen read them aloud and Priya stopped him after each to explain why.

Managing nerves

Even a well-prepared candidate feels nervous, and a little tension sharpens attention. Too much narrows it, which is when people misread questions. Priya's advice was practical. Arrive at the desk early, so check-in is not rushed. In the first minute, before reading question one, take three slow breaths and look at the timer once, so the clock feels like a tool rather than a threat. If a run of hard questions comes early, remember that forms mix difficulties and that one hard question says nothing about the next. And if the mind goes blank on a topic, mark the question and move on; the answer often returns while reading a later question on a related feature.

Malik added that the proctor is not an adversary. If something goes wrong, such as the connection dropping or the screen freezing, the right response is to stay in view and use the chat or wait for the proctor to reconnect, not to walk away. Pearson VUE can often resume the exam, and a technical failure recorded with a case number is one of the few situations in which Microsoft waives the retake waiting period.

After the exam

If Owen passes, the certification appears on his Microsoft Learn profile, from which he can share it on professional profiles and print a certificate. It does not expire. If he does not pass, lesson 11's plan applies: keep the score report, wait at least a day, recalculate priorities from it, study for two or three weeks, and rebook within the retake policy. Either way, Priya asked him to write a short note for Hélène while the experience was fresh: what surprised him, what he would study differently, and which question styles appeared.

Rosa added one administrative step: the receipt goes to the training budget so the exam fee is reimbursed in the next pay run.

Where the certification leads

GitHub Foundations is the base for GitHub's other certifications, each of which has its own preparation program that builds on this course and its two predecessors. GitHub Actions covers workflows and automation in depth. GitHub Administration covers enterprise and organization management, identity and policy. GitHub Advanced Security covers code scanning, secret scanning and supply chain security. GitHub Copilot covers using and managing Copilot. Owen's own next step was more modest and more practical: he would take over the triage rota for open-trail-report from Malik for the summer, putting the community skills into practice.

Owen's note for Hélène, written that evening before he put his books away, was four lines long. Study from the current outline and nothing older. Learn the reason each feature exists, because the questions test reasons. Build the confusable pairs table early and read it every day. And treat the logistics as part of the exam, because the only marks you can lose before the first question are the ones a checklist saves. Priya added the note to the shared study folder, with the one-page review and the error log template, so the next candidate starts where Owen finished rather than where he began.

Owen's last word

At the end of the session, Grace asked Owen what had changed most since November, when he had first asked what a commit was. He said it was not the facts. It was that he now knew why each feature existed, so a question about a feature he had never used could still be reasoned out. That, Priya said, is exactly what a foundations exam measures. The meeting ended at 1:00, and Owen went home early, as the plan said.