A technology startup is designing the infrastructure for a new e-commerce application on AWS. The development team has implemented two major guidelines for their deployment: first, they design the application components (such as the frontend, backend APIs, and database) to interact through well-defined APIs so that changes or issues in one component do not affect the others; second, they use automated infrastructure-as-code scripts to dynamically provision temporary staging environments for testing and destroy them immediately after the test suite completes.
Which of the following AWS Cloud design principles are directly represented by these architectural guidelines? (Select TWO.)
- Loose couplingAnswer
- Disposable resources instead of fixed serversAnswer
- CTightly coupled monolithic design
- DVertical scaling to handle peak load
- EStatic infrastructure provisioning
Answer
The correct principles are loose coupling and utilizing disposable resources instead of fixed servers.
The correct principles are loose coupling and utilizing disposable resources instead of fixed servers. Designing components to interact via APIs without dependency represents loose coupling, as it limits the blast radius of failures. Using scripts to provision and immediately destroy staging environments represents using disposable resources instead of fixed servers, which reduces overhead and optimizes cost.
Step-by-Step Solution
Key Concept
AWS Cloud Design Principles (Loose Coupling and Disposable Resources)