Cloud-Native Architecture: Containers, Schedulers and the Control Loop · seed 1 · A4, ink-friendly. The answer key prints on its own page for grown-ups.

Declare the state, let the loop converge

Computing · Computer Systems · ages 23-24
Name ______________________   Date ____________

  1. What does a container give a process?

    • A whole new physical server
    • Isolation with a portable, shared host underneath
    • Free unlimited memory

  2. What architecture do cloud-native programs call for?

    • Many small networked microservices
    • One program per machine forever
    • One giant monolith

  3. Each microservice can be copied, moved, or restarted on its own.

    Circle one:   True   False

  4. Why split resources across many machines instead of fixing an assignment?

    • Load shifts constantly, so no fixed split stays right
    • Networks prefer fixed maps
    • Fixed assignments stay right forever

  5. A node dies with two replicas on it. What restores service?

    • Deleting the deployment
    • Manual rebuild by an operator at night
    • The control loop noticing the gap and starting replacements

  6. Why is declaring the end state better than issuing steps?

    • Steps run faster
    • The controller re-derives steps and heals drift each round
    • States need no scheduler

  7. A reconcile loop should perform brand-new actions on every pass even with no drift.

    Circle one:   True   False

  8. Your loop creates a third replica every retry. What is the fix?

    • Add more nodes
    • Retry faster
    • Compare actual with declared and create only the shortfall
LightMySky · lightmysky.comW1-mt_nV1LgSRsh_-s1

Answer key

For grown-ups. Fold this page away before handing over the rest.

Declare the state, let the loop converge W1-mt_nV1LgSRsh_-s1

  1. Isolation with a portable, shared host underneath · Isolation travels; the host is still shared.
  2. Many small networked microservices · Small services map onto replaceable cloud machines.
  3. True · Independence per service is the whole point of the split.
  4. Load shifts constantly, so no fixed split stays right · Moving load needs a scheduler that re-places copies.
  5. The control loop noticing the gap and starting replacements · Continuous reconcile closes the gap with nobody paged.
  6. The controller re-derives steps and heals drift each round · Step lists rot; desired state stays a standing target.
  7. False · No drift means no action; idle passes must be harmless.
  8. Compare actual with declared and create only the shortfall · Repeat-safe means nudging only the measured difference.
Worksheet · LightMySky