Submitting your capstone

CGE-P and CGE-AZ finish with a capstone: a public GitHub repo scored against a published rubric. For CGE-P it is your governed fork of a deliberately non-compliant app; for CGE-AZ it is your deployed Azure pipeline. CGE-AUD has no capstone.

Order of steps

1. Finish the course.
2. Pass the exam. The capstone submission only appears after this. People often look for it earlier and cannot find it.
3. Build your capstone. For CGE-P, that is your fork of cgep-app-starter; the Capstone Brief and Capstone Companion on the Labs page walk through it. For CGE-AZ, follow the capstone section of the course.
4. Submit the repo URL from the course page.

What you submit

• A public repo URL in the form https://github.com/your-name/your-repo.
• Three confirmations: the repo is public, the work is your own, and you understand the result is final unless you appeal.

Attempts

• You get 2 attempts per certification.
• Attempts must be at least 24 hours apart.
• A submission that errors out on our side does not use up an attempt.

How it is graded

Grading reads your code, not your live cloud resources, so you can tear down your infrastructure after you submit. Automated scanners run first (terraform fmt and validate, tflint, checkov, gitleaks, semgrep, conftest), then the repo is scored against the public rubric:

• CGE-P capstone rubric
• CGE-AZ capstone rubric

Read the rubric before you submit. Each dimension lists exactly what is checked.

Before you submit, check

• The repo is public.
• The README file is named exactly README.md. A file named README (1).md or readme.txt does not count.
• No secrets, keys, or real personal data anywhere in the history.
• No Terraform plan output (plan.json, plan.txt, *.tfplan) or .terraform/ folders committed. Add them to .gitignore.
• You changed more than the starter; an unmodified fork fails automatically.

If a check fails, see Fixing a failed capstone.