When configuring ECS storage for a high-performance application, which type of storage abstraction is recommended?

Question

Options

• AObject storage with frequent access tier
• BBlock storage with provisioned IOPS
• CFile storage with standard throughput
• DArchive storage for infrequent access

• A
  4% (1)
• B
  92% (23)
• D
  4% (1)

Explanation

Block storage with provisioned IOPS (option B) is the right choice because high-performance applications running on ECS need low-latency, consistent I/O throughput - provisioned IOPS block storage (like AWS EBS io1/io2) lets you reserve a guaranteed IOPS level, eliminating the noisy-neighbor problem that plagues shared storage.

Why the distractors are wrong:

• A (Object storage / frequent tier): Object storage (S3) is optimized for large, unstructured data accessed via HTTP APIs - it has high latency and is unsuitable for workloads requiring fast, random read/write operations.
• C (File storage / standard throughput): File storage (EFS Standard) is designed for shared access across many instances; standard throughput doesn't provide the deterministic, high-speed I/O a demanding application needs.
• D (Archive storage): Archive tiers (Glacier, etc.) are built for cold data with retrieval times measured in hours - the opposite of what a high-performance app requires.

Memory tip: Think of it as matching the storage personality to the workload. Block = disk-like, fast, dedicated - perfect for databases and performance-critical apps. When you see "high-performance" + "ECS" on an exam, anchor to "block + provisioned IOPS."

No community discussion yet for this question.