A global logistics firm is migrating its package tracking system to the AWS Cloud. In the current on-premises architecture, a single database server and a single application server are tightly coupled. During peak shipping periods, database write bottlenecks cause the front-end portal to become completely unresponsive, resulting in lost transaction details. To improve system resilience and ensure messages are not lost, which of the following strategies align with the AWS Cloud design principles of loose coupling and designing for failure? (Select TWO.)
- Introduce Amazon Simple Queue Service (Amazon SQS) to buffer incoming tracking updates before writing them to the database.Cevap
- Deploy application instances across multiple Availability Zones behind an Elastic Load Balancer.Cevap
- CHost both the application server and the database on a single high-performance Amazon EC2 instance to minimize network latency.
- DManually scale up the instance size of the application server at the start of each month to guarantee constant peak capacity.
- EConfigure application servers to store session state in local memory to ensure fast data retrieval between components.
Cevap
Introducing Amazon Simple Queue Service (Amazon SQS) to buffer incoming tracking updates before writing them to the database, and deploying application instances across multiple Availability Zones behind an Elastic Load Balancer.
The correct strategies are introducing Amazon Simple Queue Service (Amazon SQS) to buffer incoming tracking updates, which implements loose coupling, and deploying application instances across multiple Availability Zones behind an Elastic Load Balancer, which implements designing for failure.
Adım Adım Çözüm
Anahtar Kavram
AWS Cloud design principles state that loose coupling reduces interdependencies so that a failure in one component does not cascade, while designing for failure ensures system components have redundancy to survive infrastructure outages.
Tahmini Süre:1m 30s