Question

Difficulty: EasyIdentify design principles of the AWS Cloud

A financial services firm wants to modernize its transaction auditing system. The technical lead recommends using separate microservices that communicate asynchronously and ensuring that test environments can be easily created and destroyed using automated scripts.

Which of the following AWS Cloud design principles do these recommendations demonstrate? (Select TWO.)

  1. Loose couplingAnswer
  2. Disposable resourcesAnswer
  3. C
    Monolithic architecture
  4. D
    Tight coupling of components
  5. E
    Over-provisioning for peak demand

Answer

The correct design principles demonstrated are loose coupling and disposable resources.
The correct answers are loose coupling and disposable resources. Loose coupling is shown by using separate microservices communicating asynchronously, which prevents failures in one service from bringing down others. Disposable resources is shown by using automated scripts to easily create and destroy test environments, which simplifies environment replication.

Step-by-Step Solution

1
Analyze the first recommendation to use separate microservices that communicate asynchronously.
This matches loose coupling, as asynchronous communication decouples the components so they do not depend directly on each other's immediate availability.
Loose coupling is a fundamental AWS design principle to prevent single points of failure from impacting the entire system.
2
Analyze the second recommendation to easily create and destroy test environments using automated scripts.
This matches disposable resources, which encourages treating infrastructure as temporary and automated rather than static and manual.
Using disposable resources allows teams to rapidly iterate, test, and maintain consistency across environments without configuration drift.

Key Concept

AWS Cloud design principles promote system flexibility, scalability, and resiliency through practices like loose coupling (decoupling components) and utilizing disposable resources (using automation to spin up and tear down environments).
Rate this question