# Container Orchestration

Container orchestration automates the deployment, placement, scaling, networking, and recovery of containerized workloads across compute resources.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/container-orchestration

> An orchestrator continually reconciles running workloads with a declared desired state, such as the required number of application replicas and their resource requirements. It helps engineers operate containerized applications reliably, but selecting a hosting platform also requires decisions about infrastructure ownership, application compatibility, security, and cost.

Practice exams covering Container Orchestration: [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 6 key aspects of Container Orchestration

Effective container orchestration combines desired-state automation with deliberate decisions about placement, scaling, deployment safety, operational ownership, and workload compatibility.

1. **Desired-state reconciliation**: Declare the required workload configuration and let controllers reconcile actual execution with that configuration. Replacement and restart behavior should be paired with meaningful health checks to avoid repeatedly launching an unhealthy application.
2. **Resource-aware placement**: Scheduling considers resource requests, platform compatibility, and placement constraints. Configure failure-domain distribution and ensure enough capacity exists to satisfy both normal operation and failure recovery.
3. **Separate workload and capacity scaling**: Increasing replica counts and increasing available compute are distinct operations. Coordinate scaling policies with provisioning delays, quotas, and downstream service limits.
4. **Controlled deployment and recovery**: Orchestration supports repeatable updates, replacement of failed instances, and controlled workload termination. Safe releases still require readiness checks, rollback rules, and application compatibility across versions.
5. **Explicit operational ownership**: Distinguish responsibility for the orchestration control plane, worker infrastructure, and application configuration. Managed control planes and serverless compute reduce different types of operational work and should not be treated as equivalent.
6. **Workload-driven platform selection**: Choose the orchestration interface and hosting capacity based on compatibility, portability needs, security constraints, team skills, and total cost. Validate requirements such as GPUs, privileged access, operating systems, and persistent storage before selecting an execution model.

## Cloud services for Container Orchestration

Amazon ECR stores application images, while Amazon ECS or Amazon EKS defines and coordinates their execution. ECS offers an AWS-native orchestration interface; EKS exposes Kubernetes APIs. Compute capacity is a separate choice: AWS Fargate handles underlying servers for supported workloads, while Amazon EC2 provides greater control over hosts and hardware. These are alternative combinations, not services every application must use together. Choose the orchestrator around application requirements and team capabilities, then choose compatible compute based on execution constraints, infrastructure ownership, scaling behavior, and cost. Image access, workload identity, network connectivity, observability, and persistent storage must be designed across the selected components.

- **[AWS Fargate](https://blowstack.com/tools/cloud-services-hub/aws-fargate)**: AWS Fargate supplies serverless compute for Amazon ECS tasks and supported Amazon EKS pods rather than acting as a separate orchestrator. It removes worker-server administration, but workload compatibility, resource sizing, networking, permissions, and supported execution features still require evaluation.
- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Amazon EC2 supplies server-based capacity for container clusters when workloads need instance-level control, specialized hardware, or capabilities unavailable in the selected serverless model. Teams must account for operating-system maintenance, capacity management, and coordination between workload scaling and node scaling.

## Container Orchestration exam questions

Real practice exam questions on Container Orchestration, with the correct answer and its explanation.

### Question 1 (SAP-C03)

**Question:**

A company runs a stateless order-validation API as eight standalone Amazon ECS tasks on AWS Fargate behind an Application Load Balancer (ALB). Deployment automation launches the tasks by calling RunTask and registers their IP addresses with the ALB target group. Occasionally, an application becomes unresponsive while its container process continues running. The ALB stops routing requests to that task, but the task remains running until an operator replaces it.

The company wants managed reconciliation to a steady-state count of eight tasks, including automatic replacement of tasks that stop or fail ALB health checks. During replacement, the scheduler must be allowed to start replacement tasks before stopping unhealthy tasks when capacity is available. To control resource consumption, the scheduler must permit up to two additional tasks but enforce an upper bound of 10 tasks in the RUNNING or PENDING state during replacements and rolling deployments. Fargate capacity, quotas, and subnet IP addresses are sufficient.

Which solution meets these requirements with the LEAST operational overhead?

**Correct answer:** Replace the standalone tasks with an ECS replica service that uses Fargate and the existing ALB target group. Set desiredCount to 8, minimumHealthyPercent to 100, and maximumPercent to 125.

**Explanation:** An ECS service maintains its desired task count and replaces tasks that stop or fail configured container or target group health checks. With desiredCount of 8, maximumPercent of 125 permits at most 10 RUNNING or PENDING tasks. This provides room to start replacements before stopping unhealthy tasks when capacity is available. The service also manages target registration without custom reconciliation code.

## Practice Container Orchestration in a full exam

Questions on Container Orchestration in each practice exam, with every answer option and an explanation for each:

- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 4 questions

## What is Container Orchestration

Container orchestration coordinates containerized workloads across a pool of compute capacity. Instead of manually starting containers on individual servers, engineers declare application requirements, including container images, CPU and memory allocations, replica counts, networking, and health checks. The orchestration control plane schedules workloads onto suitable capacity and responds when the actual state differs from the desired state. Scheduling places workloads; the container runtime executes them.

Orchestration and compute provisioning are related but separate responsibilities. An orchestrator can request additional application replicas without having enough capacity to run them. On a server-based platform, node provisioning or cluster scaling must supply that capacity. With a serverless container compute model, the provider handles underlying servers, but engineers still configure workload resources, permissions, networking, and scaling policies. Serverless containers do not eliminate orchestration; they change the infrastructure management boundary.

When modernizing an existing workload, evaluate application requirements before choosing a platform. Identify operating-system dependencies, processor architecture, privileged execution requirements, GPU needs, persistent storage, network connectivity, and licensing constraints. A container image does not make a Windows application compatible with Linux hosts, nor does it remove dependencies on local disks or external systems. Applications that need specialized hardware or host-level agents may require server-based capacity rather than a more constrained serverless execution environment.

The orchestration interface is another decision axis. A team already operating Kubernetes applications may value Kubernetes APIs, deployment tooling, and ecosystem integrations. A team focused on applications within one cloud may prefer a provider-native orchestrator with fewer platform components to manage. Managed Kubernetes reduces control-plane administration, but teams still own responsibilities such as workload configuration, access control, compatible add-ons, and upgrade planning. Kubernetes portability does not automatically extend to provider-specific identity, networking, load balancers, or storage.

For example, a stateless web application can run multiple replicas across failure domains behind a load balancer. Health checks identify instances that should not receive traffic, and the orchestrator replaces failed instances. Readiness and startup behavior must be configured correctly so that a container is not treated as ready before its application can serve requests. Placement policies and sufficient spare capacity are essential: declaring three replicas does not by itself guarantee resilience to a zone failure.

A queue-processing application illustrates a different scaling pattern. Worker counts can increase with queue depth rather than web request volume. Workers should tolerate retries, handle termination gracefully, and make processing idempotent where duplicate delivery is possible. For either workload, application scaling must be coordinated with compute capacity, dependency limits, quotas, and startup times. An autoscaling policy cannot overcome an exhausted database connection pool.

Deployments also require deliberate design. Rolling updates replace instances incrementally, while blue-green or canary approaches control exposure to new versions. Health checks, rollback criteria, connection draining, and database schema compatibility determine whether an update is safe. Orchestration automates deployment mechanics but does not prove application correctness. Similarly, restarting a failed container is recovery automation, not a solution for a persistent application defect.

Stateful applications can run under orchestration, but persistent volumes, replication, backups, and recovery procedures need explicit engineering. Security likewise requires image scanning, restricted workload identities, secret management, network controls, and appropriate isolation. Finally, compare total operating cost rather than compute prices alone: server-based capacity offers control and potential utilization savings, while serverless capacity reduces host administration but introduces its own pricing model and execution constraints. The appropriate hosting platform is the one that meets workload requirements with an operational burden the team can sustain.

## Learn Container Orchestration in lessons

1 short lesson on Container Orchestration in 1 certification course.

- SAP-C03: Container Orchestration: desired-state control for microservices (Premium), https://app.blowstack.com/lessons/container-orchestration-desired-state-control-for-microservices-sap-c03
