Study DOP-C02 reusable IaC for CloudFormation, CDK, SAM, Service Catalog, drift control, and lifecycle-managed infrastructure.
The first IaC task on DOP-C02 is not just “write templates.” AWS is testing whether infrastructure definitions are reusable, governable, and sustainable over the full lifecycle. The best answer usually reduces drift and duplicated logic before it reduces typing.
The current domain guidance points to:
That means the real question is often whether the environment is being provisioned through durable patterns, not whether one stack can be created once.
Break the decision into four questions:
Weak answers skip straight to “use CloudFormation” without deciding what is actually being reused or governed.
| Requirement | Strongest first fit | Why |
|---|---|---|
| Standard infrastructure pattern reused across many teams | Reusable IaC module or higher-level construct | Reduces copy/paste drift |
| Controlled self-service for approved patterns | Service Catalog or equivalent governed template model | Reuse plus guardrails |
| Serverless application packaging | SAM or similar purpose-fit abstraction | Stronger than hand-assembling every resource |
| Ongoing lifecycle changes with auditability | Template-driven updates and reviewed change flow | Better than console drift |
If the prompt mentions inconsistent environments, undocumented console changes, or stacks that no longer match intent, the core problem is drift management and controlled lifecycle updates, not initial provisioning.
DOP-C02 usually prefers answers that restore desired state through managed IaC workflows instead of manual correction.
When the question is about consistency across environments, prefer reusable patterns plus lifecycle-managed updates. When it is about controlled self-service, look for a governed catalog or template boundary rather than unrestricted raw provisioning.