SAA-C03 · Question #551
A company is building a web application that serves a content management system. The content management system runs on Amazon EC2 instances behind an Application Load Balancer (ALB). The EC2 instances
The correct answer is B. Copy the website assets to an Amazon Elastic File System (Amazon EFS) file system. Configure. Amazon EFS provides a shared, elastic, low-latency file system that can be mounted concurrently by many EC2 instances across multiple Availability Zones, delivering strong read-after-write consistency so all instances see updates almost immediately. This is the standard pattern f
Question
A company is building a web application that serves a content management system. The content management system runs on Amazon EC2 instances behind an Application Load Balancer (ALB). The EC2 instances run in an Auto Scaling group across multiple Availability Zones. Users are constantly adding and updating files, blogs, and other website assets in the content management system. A solutions architect must implement a solution in which all the EC2 instances share up-to-date website content with the least possible lag time. Which solution will meet this requirement?
Options
- AUpdate the EC2 user data in the Auto Scaling group lifecycle policy to copy the website assets
- BCopy the website assets to an Amazon Elastic File System (Amazon EFS) file system. Configure
- CCopy the website assets to an Amazon S3 bucket. Ensure that each EC2 instance downloads the
- DRestore an Amazon Elastic Block Store (Amazon EBS) snapshot with the website assets. Attach
How the community answered
(33 responses)- A9% (3)
- B85% (28)
- C3% (1)
- D3% (1)
Explanation
Amazon EFS provides a shared, elastic, low-latency file system that can be mounted concurrently by many EC2 instances across multiple Availability Zones, delivering strong read-after-write consistency so all instances see updates almost immediately. This is the standard pattern for CMS-style workloads that require shared, up-to-date assets with minimal lag. Syncing local copies from S3 (C) introduces polling windows and eventual consistency delays; hourly sync is not near-real time. Copying from a "newest instance" (A) is brittle and not scalable. EBS volumes/snapshots (D) are single-instance, single-AZ block devices and not designed for multi- writer sharing across instances/AZs. EFS's multi- AZ design and POSIX semantics provide the simplest, most reliable solution with the least operational overhead.
Community Discussion
No community discussion yet for this question.