Public-works engineers share concurrent CAD drawings across multiple workstations after migration. Which storage service selection is appropriate instead of a single instance's Amazon EBS volume?
Select an answer to reveal the explanation.
Short Explanation
CAD drawings are a shared kitchen table, not a locked drawer on one desk. EFS or FSx gives concurrent file access; a lonely EBS volume on one instance becomes everyone's single point of frustration.
Full Explanation
Public-works engineers sharing concurrent CAD drawings across multiple workstations after migration need shared file systems, not a single instance's Amazon EBS volume. Select Amazon EFS or Amazon FSx shared file systems rather than block EBS on one instance so concurrent editors get a proper multi-client file protocol for municipal engineering work. A single gp3 EBS volume attached to one EC2 instance as the shared CAD file server for all users fails concurrency and becomes a single point of failure. Amazon S3 Glacier Deep Archive as the primary interactive editing filesystem fails latency and protocol needs for CAD. Instance store volumes wiped on stop as the department's only drawing repository fails durability for engineering work product. Exam caveat: concurrent shared files need EFS/FSx; EBS is single-instance block storage. Operational check: choose EFS or FSx based on protocol/OS needs, mount from workstations or VDI, set backups, validate concurrent open/save for CAD, and retire the single-EBS share design. Document the decision in the municipal architecture decision record and re-verify controls after the first production wave so auditors see continuous improvement, not one-time tribal knowledge.