A startup is designing a collaborative document editing platform on AWS. The development team wants to minimize the operational effort required to manage database infrastructure. They also want to ensure that testing environments can be spun up quickly for developers and completely destroyed when no longer needed to optimize costs.
Which of the following architectural decisions align with the AWS Cloud design principles of 'services not servers' and 'disposable resources'? (Select TWO.)
- Using AWS CloudFormation to define infrastructure as code, enabling testing environments to be deployed programmatically and terminated when testing is completeCevap
- Storing application metadata and user session state in Amazon DynamoDB instead of running a self-managed database cluster on virtual serversCevap
- CPackaging all application components into a single virtual machine image to ensure they always execute on the same server instance
- DDeploying a fixed capacity of Amazon EC2 instances to run continuously at maximum load to avoid the latency associated with launching new instances
- EProvisioning a self-managed database on Amazon EC2 instances to maintain complete control over operating system-level configuration and security patches
Cevap
The correct architectural decisions are using AWS CloudFormation to define infrastructure as code for dynamic environment creation and termination, and using Amazon DynamoDB for metadata storage to replace self-managed servers.
The correct options are using AWS CloudFormation for automated environment provisioning and destruction, and storing metadata in Amazon DynamoDB. AWS CloudFormation enables infrastructure as code, which directly implements the 'disposable resources' principle by allowing environments to be created and destroyed dynamically. Storing data in Amazon DynamoDB implements the 'services not servers' principle by leveraging a fully managed, serverless database service that eliminates the need to provision, patch, or maintain virtual servers.
Adım Adım Çözüm
Anahtar Kavram
AWS Cloud design principles focus on scalability, elasticity, loose coupling, disposable resources, and using managed services to reduce operational overhead.