CI/CD for AI Apps — Final Exam

13 questions · pass mark 80% · 20 minute limit. The timer auto-submits at zero.

Time remaining: 20:00
  1. Question 1easy

    What do CI and CD stand for / do?

  2. Question 2easy

    What is the AI-specific addition to a standard CI/CD pipeline?

  3. Question 3medium

    Why are unit tests necessary but not sufficient for an AI app?

  4. Question 4medium

    How does an eval gate block a bad merge in CI?

  5. Question 5hard

    What cautions apply to an eval gate in CI? (Select all that apply)

    Select all that apply.

  6. Question 6medium

    Why tag deployable images by git commit SHA rather than using 'latest'?

  7. Question 7medium

    Where do secrets (like API keys) come from in a CI pipeline?

  8. Question 8hard

    What is a blue-green deployment?

  9. Question 9hard

    What triggers a rollback during a canary deploy of an AI app?

  10. Question 10medium

    How does CI/CD relate to the LLMOps discipline from Track 5?

  11. Question 11hard

    Which are CI/CD pitfalls for AI apps? (Select all that apply)

    Select all that apply.

  12. Question 12medium

    What kind of gate (two words) — running the golden-set regression suite in CI — blocks a merge on model-quality regression?

  13. Question 13hard

    What deploy strategy (one word) routes a small % of traffic to the new version and watches metrics before ramping up?

0 / 13 answered