Study DOP-C02 large-scale configuration automation for Systems Manager, State Manager, AppConfig, patching, and desired state.
This task is about keeping fleets, applications, and environments in the state you intended after initial provisioning is long finished. The exam is really testing desired-state automation and operational scale, not just “which service can run a script.”
If the scenario is about recurring drift, repeated manual fixes, patch inconsistency, or environment mismatch, the best answer usually enforces desired state automatically rather than reacting to each incident separately.
| Requirement | Strongest first fit | Why |
|---|---|---|
| Maintain fleet configuration or patch posture | Systems Manager-based automation and state patterns | Good fit for large managed fleets |
| Change runtime application configuration safely | AppConfig-style controlled config rollout | Stronger than redeploying code for every config change |
| Automate complex remediation or orchestration | Lambda plus workflow orchestration where needed | Flexible control plane for multi-step logic |
| Track inventory and compliance at scale | Managed inventory/compliance automation | Better than ad hoc host-by-host checks |
DOP-C02 often tests whether the real problem is:
Those are related but not identical. A stack template is not automatically the strongest answer for a fleet-state problem, and a patching tool is not automatically the strongest answer for reusable infrastructure design.
When the question is about keeping many systems aligned over time, look for desired-state enforcement, fleet automation, or controlled config rollout. When it is about creating the environment once, that points back to the reusable IaC lane.