Cheat sheet & self-check

Pick an answer to see if you got it, and why.

1. Q1. What does a CODEOWNERS file do?

   1. AStores passwords
   2. BMaps paths to owners so the Git server automatically requests (and can require) their review on pull requests touching those paths
   3. CLists contributors for marketing
   4. DEncrypts files
   Show answer

   B. Combined with branch protection, changes to prod/ or the network layer can't merge without the owning team's approval.

   From lesson 07 · Repositories for infrastructure and GitOps

2. Q2. A secret was committed and pushed an hour ago. What's the first step?

   1. ADelete the file in a new commit
   2. BRotate or revoke the secret immediately; clean the history afterwards
   3. CForce-push main
   4. DMake the repository private
   Show answer

   B. Assume it's already copied (clones, CI logs, forks, scanners). Rotation makes the leaked value useless; history clean-up comes second.

   From lesson 07 · Repositories for infrastructure and GitOps

3. Q3. Why run checks as pre-commit hooks AND in CI?

   1. AIt's the same thing
   2. BHooks give fast local feedback but can be skipped; CI is the enforced gate nobody can bypass
   3. CCI is optional
   4. DHooks are more secure
   Show answer

   B. Local hooks save time; CI guarantees the rule. Use both with the same configuration.

   From lesson 07 · Repositories for infrastructure and GitOps

4. Q4. A CI job only needs to build the latest commit. How should it clone?

   1. AFull clone every time
   2. BA shallow clone (--depth 1), or a partial clone if some history is needed
   3. CDownload a zip
   4. Dgit pull
   Show answer

   B. Shallow clones cut clone time and bandwidth dramatically. Jobs that compute versions from tags may need more depth or a fetch of tags.

   From lesson 08 · Large repos and troubleshooting

5. Q5. Why is committing large binary files (ISOs, model files) to normal Git a problem?

   1. AGit refuses them
   2. BEvery version stays in history forever, so every clone downloads all of them; use Git LFS or an artifact store
   3. CThey get corrupted
   4. DThey're slower to diff
   Show answer

   B. Git history is append-only; big binaries make every clone and fetch heavy. LFS stores pointers in Git and content elsewhere.

   From lesson 08 · Large repos and troubleshooting

6. Q6. git push fails with 'Updates were rejected because the tip of your current branch is behind'. Fix?

   1. Agit push --force
   2. BFetch and integrate the remote changes (pull --rebase or merge), resolve conflicts, then push
   3. CDelete the remote branch
   4. DRe-clone
   Show answer

   B. Someone pushed before you. Integrate their work; force-pushing would delete it.

   From lesson 08 · Large repos and troubleshooting