Exam · Git for AI builders: commits, branches and pull requests

Take the exam and earn your certificate.

A real, server-scored exam for this course. Score strictly above 80% to pass and get a genuine, verifiable certificate.

Before you start

We ask for your name and email first, the same as a PDF download, so we know you are here and your certificate can carry the right name.

We privately record your name, email and request IP for this exam request. Read the privacy notice and retention policy.

Visit Mickai on LinkedIn

Complete the security check before submitting.

Cloudflare Turnstile helps prevent automated submissions. How this check uses data.

You can retake the exam any time. Each attempt draws a fresh set of questions.

Written practice, ungraded

Write your response in your own notes, then compare it with the sample answer. This practice is separate from the scored exam and does not affect your certificate.

Practice 1

Give a paper plan for one fictional small commit, including selected files and a clear message.

Compare with a sample answer

In the practice repository, plan to inspect status and the diff, stage only prompts.txt, inspect the staged diff and commit with Add error-explainer prompt. Predict that the change moves from the second status column to the first when staged. This is a plan, not evidence that commands ran.

The sample connects selective staging to the documented status change.

Practice 2

An assistant adds a requested prompt and an unasked README edit. Describe a scoped paper review plan.

Compare with a sample answer

Read the full diff and separate the requested prompts.txt change from the README edit. Plan to stage only prompts.txt and inspect git diff --staged. Describe that one change clearly. Do not discard the README edit blindly: restoring it would lose the edit, so first decide whether it should be retained.

The plan follows the source selective staging and identifies the restore discard boundary.

Practice 3

Describe a fictional conflict-resolution plan and the limitation of backing out instead.

Compare with a sample answer

Read the HEAD and incoming sides, choose the intended combined text, remove the marker lines, then plan to add and commit the resolved file. Alternatively merge --abort tries to restore the pre-merge state; commit or stash existing changes beforehand because abort cannot always rebuild them. No merge was performed here.

The sample retains the source marker handling and abort qualification.

Practice 4

Compare stashing an uncertain tracked rewrite, unstaging a file and reverting a bad commit in a paper plan.

Compare with a sample answer

Stash an uncertain uncommitted tracked rewrite to keep an attempt for inspection; untracked files are not included by default. restore --staged unstages while retaining edits. Revert adds a new undo commit and retains the earlier commit in history. These are described choices, not performed recovery.

The sample distinguishes the saved attempt, retained edit and added history.

Practice 5

Explain the fictional deleted-key demonstration and a paper response if a real key were committed. Include an ignore-rule limit.

Compare with a sample answer

The fake .env value remains readable in an earlier snapshot after file deletion. If a real credential were committed, first revoke or rotate it with its issuer, then locate pushed or cloned copies before considering specialist history cleanup. Rewriting cannot reach other people's existing clones. An ignore rule does not remove history or stop already tracked files; never use real keys in this practice.

The sample retains the ordering, copies limit and prevention boundary without using a credential.

Practice 6

Plan a fictional local-bare branch review and write an honest review-description outline.

Compare with a sample answer

Use the course local shared repository and invented identities. Plan to fetch, inspect main...origin/add-translate-prompt, request a change if needed, and fetch and read the updated diff again before a merge decision. Describe what changed and why, what checks actually ran and their results, assistant work reviewed and unfinished risks. This paper plan has not run those checks and does not establish hosting protection.

The sample distinguishes a local review exercise from executed checks and hosting features.

About this exam

Is this exam graded?

Yes. Every question is scored on our server, never in your browser, and you need a score strictly above 80% to pass. The questions are a real, reviewed bank for this course, drawn fresh for each attempt.

Is it only multiple choice?

Yes. This is a multiple-choice knowledge assessment, with at least one question from each chapter in every attempt. Written exercises are separate practice and are not automatically scored. Passing does not establish practical professional competence or independently verify identity.

Is there a time limit?

Yes, 45 minutes, shown as a countdown once you start. If time runs out, whatever you have answered is submitted automatically.

Do I need to download the PDF first?

No. This course's full text is on its own page, so you can read it online and come straight here when you feel ready.

What do you do with my name and email?

We privately record your name, email, request IP, course and privacy acknowledgement for this request. Newsletter consent is separate and optional. See /privacy.html for storage and retention. A passed exam creates a server-stored named certificate. An email confirmation is not identity assurance.

Can I retake it if I fail?

Yes, straight away. Each attempt draws a fresh set of questions and shuffles the answer order, so it will not be identical to your last attempt, and an attempt can only be submitted once.

Is the certificate real?

It is a genuine, server-issued certificate with its own verification page and a unique ID, not a self-declared one. It records that you passed this course's exam on this date. It is not an accredited qualification, a professional licence or proof of employment.