A digital media agency runs containerized video rendering workloads on AWS. The workloads are highly unpredictable, with sudden bursts of activity when client campaigns launch. To optimize costs and efficiency, the agency utilizes Amazon Elastic Container Service (Amazon ECS) on AWS Fargate to automatically run containers only when rendering tasks are in the queue, shut them down immediately after completion, and avoid managing any underlying virtual machines.
Which AWS Cloud design principles are demonstrated by this architecture? (Select TWO.)
- Services, not serversAnswer
- Disposable resourcesAnswer
- CTight coupling of infrastructure
- DStatic capacity planning
- EMonolithic software design
Answer
The architecture demonstrates the principles of 'Services, not servers' and 'Disposable resources'. By utilizing AWS Fargate, the company does not manage the underlying virtual servers, and by spinning containers up and down on demand, they treat compute resources as disposable assets rather than static systems.
The correct principles are using services, not servers, and treating resources as disposable. By deploying AWS Fargate, a serverless container execution engine, the agency does not have to manage underlying servers, directly applying the services, not servers principle. Additionally, running containers dynamically on demand and terminating them immediately when the job is done demonstrates the principle of disposable resources, where resources are treated as temporary rather than permanent.
Step-by-Step Solution
Key Concept
AWS Cloud design principles recommend using managed and serverless services to reduce operational overhead (services, not servers) and treating compute resources as temporary, dynamic assets (disposable resources).
Estimated Time:1m 30s