A company runs a financial transaction processing application on a fleet of containerized … — AWS Certified Solutions Architect - Associate

A company runs a financial transaction processing application on a fleet of containerized microservices using Amazon ECS on AWS Fargate. The containers are distributed across multiple Availability Zones for high availability. The application requires a shared, POSIX-compliant file system to store transaction logs and state information. The workload is highly unpredictable, with sharp traffic spikes during market open and close, requiring throughput to scale rapidly up to $3\text{ GB/s}$ during peak times while remaining minimal during off-hours. The storage solution must deliver consistent, sub-millisecond latencies for file operations. Which two actions should a solutions architect take to configure the storage solution for this application? (Choose two.)

Create an Amazon Elastic File System (Amazon EFS) file systemAnswer
Configure the file system to use Elastic throughputAnswer
C
Create an Amazon Elastic Block Store (Amazon EBS) volume with Multi-Attach enabled
D
Configure the file system to use Provisioned throughput
E
Create an Amazon FSx for Lustre file system with SSD storage

Answer

To meet the requirements of a shared POSIX-compliant file system with sub-millisecond latencies and unpredictable throughput needs on AWS Fargate across multiple Availability Zones, the solutions architect should create an Amazon Elastic File System (Amazon EFS) and configure it to use Elastic throughput.

Creating an Amazon Elastic File System (Amazon EFS) file system provides a fully managed, shared network file system that natively integrates with Amazon ECS on AWS Fargate, allowing task containers in multiple Availability Zones to concurrently read and write data. Configuring the file system with Elastic throughput allows it to dynamically scale performance up to the required

3\text{ GB/s}

without manual administrative overhead or over-provisioning cost, charging only for the data read and written.

Step-by-Step Solution

Identify compute and connectivity requirements

The application runs on Amazon ECS with AWS Fargate across multiple Availability Zones, which requires a shared, POSIX-compliant network file system that supports concurrent read/write access from independent containers across different zones.

This rules out Amazon EBS, which is a block storage service restricted to a single Availability Zone and not natively shareable across tasks in different Availability Zones without specialized clustering software.

Select the correct file system service

Select Amazon Elastic File System (Amazon EFS), which natively integrates with Amazon ECS on AWS Fargate and allows concurrent mounts from multiple Availability Zones using the NFSv4 protocol.

EFS provides the standard POSIX-compliant shared file system interface required by the application.

Determine the optimal throughput mode based on performance and cost

Configure EFS with Elastic throughput mode to dynamically handle traffic spikes up to

3\text{ GB/s}

without manual intervention, while minimizing costs during idle periods.

Elastic throughput scales performance resources automatically based on the workload demands, which is perfect for highly unpredictable transaction spikes, avoiding the high costs of Provisioned throughput.

Key Concept

Amazon EFS with Elastic Throughput provides a highly available, shared file system that dynamically scales performance to meet unpredictable spike demands for containerized workloads.

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic