Question

Difficulty: MediumIdentify design principles of the AWS Cloud

A healthcare technology company is migrating its legacy billing and reporting system to the AWS Cloud. The system currently processes patient invoices and generates compliance reports. The invoicing process must run continuously without interrupting the reporting system, and the reporting system only needs resources during the first week of every month when reports are compiled. Which two architectural practices should the company adopt to align with AWS Cloud design principles? (Select TWO.)

  1. Implement Amazon Simple Queue Service (Amazon SQS) to decouple the invoicing and reporting components, ensuring that a failure in report generation does not affect invoicing.Answer
  2. B
    Run the invoicing and reporting services on a single, high-performance Amazon EC2 instance to simplify inter-process communication.
  3. Use Amazon EC2 instances that are provisioned on demand to run the monthly reporting jobs and terminated immediately after the work is complete.Answer
  4. D
    Maintain a fixed, maximum-capacity fleet of Amazon EC2 instances running continuously to ensure the reporting system is always ready for the monthly workloads.
  5. E
    Design the invoicing service to write data directly and synchronously into the reporting database to ensure immediate consistency.

Answer

The company should implement Amazon Simple Queue Service (Amazon SQS) to decouple the invoicing and reporting components, and use Amazon EC2 instances that are provisioned on demand to run the monthly reporting jobs and terminated immediately after the work is complete.
Decoupling the invoicing and reporting components using Amazon Simple Queue Service (Amazon SQS) ensures that if the reporting service experiences issues, invoicing remains unaffected, fulfilling the loose coupling and design for failure principles. Additionally, provisioning Amazon EC2 instances on demand and terminating them once report generation is complete aligns with the principle of treating resources as disposable rather than static infrastructure.

Step-by-Step Solution

1
Analyze the requirements for loose coupling.
The invoicing process must not be interrupted by the reporting system, which requires decoupling them using a queueing service like Amazon SQS so that their lifecycles are independent.
This implements the 'loose coupling' and 'design for failure' principles.
2
Analyze the requirements for periodic resource utilization.
The reporting system only needs compute resources during the first week of the month, meaning compute resources should be created on demand and terminated when finished.
This implements the 'disposable resources' principle rather than keeping idle servers running constantly.

Key Concept

AWS Cloud design principles including loose coupling, design for failure, and disposable resources.
Estimated Time:1m 30s
Rate this question