Study DOP-C02 scaling, health checks, auto scaling, containers, serverless capacity, and self-healing design.
This task is about whether the system can adapt without an operator babysitting it. DOP-C02 is not just asking how to add capacity. It is asking whether the workload scales on the right signal and whether unhealthy components are replaced or bypassed automatically.
Strong answers choose a scaling trigger that matches the service behavior:
If the chosen metric does not reflect real demand or degradation, the scaling policy is probably weak.
Self-healing patterns often depend on:
Adding more capacity does not fix a poisoned node or bad revision if health logic is weak.
| Requirement | Strongest first fit | Why |
|---|---|---|
| Elastic compute tier under variable load | Auto scaling tied to relevant service metrics | Capacity follows demand |
| Unhealthy instances or tasks | Health checks plus automated replacement | Removes bad capacity, not just adds more |
| Burst-heavy container workload | Container-aware scaling and capacity model | Better fit than generic host scaling alone |
| Fast global or event-driven scale pattern | Serverless or loosely coupled design where appropriate | Reduces fixed bottlenecks |
When the question is about scale, ask what metric best reflects demand. When it is about recovery from unhealthy components, ask what health signal removes the bad capacity automatically.