Unit 2 — Design and implement a source control strategy

Exam weight: 10–15% · 2 topics · 9 learning objectives

Topic	Objectives	Core idea
2.1 Branching strategies	3	How many versions must you support in production?
2.2 Managing repositories	6	Keep in Git only what benefits from being versioned with the source

The three things to carry

Release branches exist for multiple supported versions. That question decides branching strategy; everything else is secondary.
Git for source, Azure Artifacts for dependencies, Git LFS for large binaries that change often. Binaries don't delta, so the cost is permanent and paid by every clone.
A committed secret is rotated first. History rewriting changes every hash and forces a re-clone — and it does not un-distribute the value.

Two protections worth knowing precisely

Require branches to be up to date — stops two individually-green PRs breaking main together.
Include administrators — otherwise the branch is unprotected exactly during an incident.

Where it connects

Branch policies (2.1) are the merge-boundary twin of environment checks (3.3). Push protection (4.3) is what stops the secret in 2.2 ever being committed.

Unit 2 — Design and implement a source control strategy

Exam weight: 10–15% · 2 topics · 9 learning objectives

Topic	Objectives	Core idea
2.1 Branching strategies	3	How many versions must you support in production?
2.2 Managing repositories	6	Keep in Git only what benefits from being versioned with the source

The three things to carry

Release branches exist for multiple supported versions. That question decides branching strategy; everything else is secondary.
Git for source, Azure Artifacts for dependencies, Git LFS for large binaries that change often. Binaries don't delta, so the cost is permanent and paid by every clone.
A committed secret is rotated first. History rewriting changes every hash and forces a re-clone — and it does not un-distribute the value.

Two protections worth knowing precisely

Require branches to be up to date — stops two individually-green PRs breaking main together.
Include administrators — otherwise the branch is unprotected exactly during an incident.

Where it connects

Branch policies (2.1) are the merge-boundary twin of environment checks (3.3). Push protection (4.3) is what stops the secret in 2.2 ever being committed.

Unit 2 — Source control strategy — roadmap

Unit 2 — Design and implement a source control strategy

The three things to carry

Two protections worth knowing precisely

Where it connects

Unit 2 — Source control strategy — roadmap

Unit 2 — Design and implement a source control strategy

The three things to carry

Two protections worth knowing precisely

Where it connects