A financial technology firm is deploying a real-time transaction processing engine on Amaz… — AWS Certified Solutions Architect - Associate

A financial technology firm is deploying a real-time transaction processing engine on Amazon EC2 instances distributed across three Availability Zones. The engine requires a shared file system to store and access transaction logs concurrently. The workload requires a file system that is POSIX-compliant, supports concurrent read/write operations from all instances, scales capacity automatically, and can scale throughput dynamically to handle peak loads up to $3\text{ GB/s}$ . Which storage solution should a solutions architect recommend to satisfy these requirements?

A
Amazon EBS gp3 volume with Multi-Attach enabled, formatted with a standard XFS file system.
Amazon EFS file system configured with Elastic Throughput mode.Answer
C
Amazon EBS io2 volumes configured with EBS Multi-Attach and attached to all instances.
D
Amazon S3 bucket mounted on the instances using AWS Mountpoint for Amazon S3.

Answer

Amazon EFS file system configured with Elastic Throughput mode.

The correct option is the Amazon EFS file system configured with Elastic Throughput. Amazon EFS is a serverless, POSIX-compliant shared file system designed to span multiple Availability Zones. Elastic Throughput mode automatically adjusts the throughput performance to match dynamic workload demands up to

3\text{ GB/s}

or higher, without requiring manual capacity or performance provisioning.

Step-by-Step Solution

Identify the storage requirements from the scenario.

The requirements are: shared POSIX-compliant file access, multi-AZ deployment (three Availability Zones), concurrent read/write capabilities, automatic capacity scaling, and dynamic throughput scaling up to

3\text{ GB/s}

This establishes the constraints that the chosen storage service must satisfy.

Evaluate block storage (Amazon EBS) solutions.

Amazon EBS gp3 volumes do not support Multi-Attach. While io2 supports Multi-Attach, it is limited to a single Availability Zone and does not support automatic capacity scaling.

This rules out EBS-based solutions because the workload is distributed across three Availability Zones.

Evaluate object storage (Amazon S3) solutions.

Amazon S3 is not POSIX-compliant and does not support concurrent write updates or file locking, which makes it unsuitable for real-time transaction logging.

This rules out S3-based solutions.

Evaluate Amazon EFS with Elastic Throughput.

Amazon EFS natively supports multi-AZ POSIX-compliant concurrent access, scales capacity automatically, and Elastic Throughput dynamically handles performance peaks up to

3\text{ GB/s}

or more.

This configuration satisfies all architectural and performance requirements.

Key Concept

Amazon EFS provides a serverless, POSIX-compliant shared file system across multiple Availability Zones, with Elastic Throughput mode automatically scaling performance to meet dynamic, high-throughput demands.

Estimated Time:1m 30s

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic