Infrastructure as Code

Infrastructure as Code and Declarative State

Model infrastructure as declarative configuration, compare desired and observed state, and let a provider execute a reviewed change toward convergence.

Beginner14 min read
Infrastructure as Code lessonDelivery and reliability foundationsPractice

UNTIMED COACHING

Practice before the pressure

Use feedback to correct the model, not merely memorize an option position.

GUIDED PRACTICE

Practice the lesson questions

Answer normal lesson questions without a timer. Every answer includes an explanation, and incorrect answers can be tried again before continuing.

CONCEPT MODELS

See the lesson as a system

Use these visual guides to connect the key ideas before answering the questions.

Connect the roles in Infrastructure as Code and Declarative StateKeep configuration source, desired state, provider boundary, and change preview as separate service roles.
Connect the roles in Infrastructure as Code and Declarative StateA topic-specific model connects four distinct roles used to reason about infrastructure as code and declarative state.
Source filesFiles declare the intended network
Desired dataData describes intended infrastructure
Provider connectionConnection maps resources to platform APIs
Output evidenceEvidence compares desired and observed state
Verify Converged resultConnect converged result with its topic-specific inspection, expected outcome, and protected delivery boundary.
Verify Converged resultA verification model for infrastructure as code and declarative state connects the final service decision to its check, result, and protected boundary.
Verified resultResult matches declared network properties
Starting checkInspect verified result
Expected resultConfirm verified result
Safety boundaryProtect source files scope